{"id":166,"date":"2005-02-18T10:11:09","date_gmt":"2005-02-18T14:11:09","guid":{"rendered":"http:\/\/shadow.sombragris.org\/?p=166"},"modified":"2005-02-18T11:25:34","modified_gmt":"2005-02-18T15:25:34","slug":"slackware-101-first-impressions","status":"publish","type":"post","link":"https:\/\/shadow.sombragris.org\/?p=166","title":{"rendered":"Slackware 10.1: First Impressions"},"content":{"rendered":"<p>I installed Slackware 10.1 on <tt>elrohir<\/tt> over the last week. As I said before, it was mostly a normal ride, and Patrick Volkerding is to be commended for making such an excellent distro. However, I ran into two problems.<\/p>\n<p>1. First I will tell you about the most annoying issues. For annoyances only, this got me some grey hairs and gnawing of teeth! When I first booted into Slackware, I realized that sound was no longer working. When I tried to set my mixer parameters with <tt>alsamixer<\/tt>, all I got was the message &#8220;no mixer params found&#8221;. What could I do?<\/p>\n<p>Booting into XFCe4 gave me a hint: XFCe4&#8217;s mixer allowed for selecting among multiple sound cards. Sound card 0 was devoid of all mixer elements, but lo! Sound Card 1 was there, with all my old mixer elements. Thus, it was a matter of somewhat associating the main sound port with sound card 1, right? Not precisely&#8230; Sound Card 0 was identified as snd-via82xx-modem and my main card was identified as just snd-via82xx.<\/p>\n<p>I was able to get sound working by making \/dev\/dsp a symlink to \/dev\/dsp1. KDE, however, gave me some trouble. aRts (the KDE sound server) kept crashing until I awkardly had to force directing sound to \/dev\/dsp1 using OSS (the old, legacy Linux system as opposed to the new, state-of-the-art ALSA system now in use) as the underlying sound system.<\/p>\n<p>I was uncomfortable. Even with sound working, aRts would crash randomly; the mixer did not work, and definitely the situation was not to my liking. I tried everything I knew: I tampered with the \/dev directory, used the <tt>alsaconf<\/tt> utility (which was not helpful here), and countless other hacks. But then I went into the #slackware channel of the <a href=\"http:\/\/www.oftc.net\">irc.oftc.net<\/a> network. I shared my problem in the channel, and soon one of the regulars, <tt>ka24<\/tt>, suggested I use lsmod and then to add the suspect modules to \/etc\/hotplug\/blacklist. I did so, and after a reboot, that did the trick. Sounds now works like a German toaster again!<\/p>\n<p>2. This other was much less annoying, but it worried me; and the problem was not exclusive with Slackware 10.1, but manifested itself with 10.0 as well, and the problem boy this time was OpenOffice.org.<\/p>\n<p>Slackware does not provide OpenOffice.org packages. That&#8217;s generally fine; the vanilla installer available at the <a href=\"http:\/\/www.openoffice.org\">OpenOffice.org website<\/a> is good enough.The version I used in Slackware 10.0 was 1.1.2. This version gave me no installation problems. However, when I tried to upgrade either to 1.1.3 or (later) to 1.1.4, the farthest I could go in the install was to see the initial progress meter, and then the installer would always exit quietly. Thus, I was stuck with an OpenOffice.org version with known issues for use in my job; and OpenOffice.org is critical for it.<\/p>\n<p>What could be the cause for such problematic behavior? I didn&#8217;t know. Perhaps the vanilla installers of versions 1.1.3 and 1.1.4 were compiled against libraries newer than those of Slackware 10.0, or incompatible with it. All in all, I was worried; future versions of the program were leaving me behind, and thus I refused to let the issue go. I filed <a href=\"http:\/\/www.openoffice.org\/issues\/show_bug.cgi?id=39693\">Issue 39693<\/a> with OpenOffice.org; and if you see the report, you will notice that it even was closed once. I requested its re-opening, and supplied a stacktrace to help pinpoint the issue down. For many days, I had no luck.<\/p>\n<p>When I first upgraded to Slackware 10.1 on <tt>elrohir<\/tt>, I had high hopes that the newer OpenOffice.org versions would work. Therefore, I was happy to learn that OO.o 1.1.4 installed and launched seamlessly right after my Slackware install. However, there was a problem. Some time at a later stage in my upgrade, while rebuilding my older configuration, invoking OO.o resulted invariably in a crash before program startup could be completed. I deleted everything related to OO.o, and tried to reinstall, but oops! now the installer showed the same problem as before in Slackware 10.0!<\/p>\n<p>I was very disappointed in one way; but on the other, I had some clues. What I did after installing OpenOffice.org on the first time was installing some Bitstream fonts I got from a legacy Corel Draw! box I got. I installed almost all of my fonts under the Type 1 format, and I know that OO.o is picky with that format. So, I got an idea to test: First, I deleted all the AFM (Adobe Font Metrics) files in my Type 1 directory:<\/p>\n<p><tt>[root: \/usr\/local\/share\/fonts] # rm .\/*.afm<\/tt><\/p>\n<p>Then, I rebuilt the AFM files with <tt>pf2afm<\/tt>:<\/p>\n<p><tt>[root: \/usr\/local\/share\/fonts] # for i in *.pfb; do pf2afm $i; done<\/tt><\/p>\n<p>With a fresh and home-made set of font metrics, I tried to install OO.o again, and guess what: It worked like a Swiss clock engine! I can enjoy OO.o 1.1.4 normally now, so I can say that the problem is solved.<\/p>\n<p>However, the issue remains. Obviously, OpenOffice.org versions 1.1.3 and up chokes on some AFM files; but then, why is it that version 1.1.2 never had a problem? This is obviously a regression, and an issue of quality assurance that should be solved. Thankfully, we are working on it. I plan to submit my AFM font sets to OO.o on Monday so they could study the root of the problem.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>I installed Slackware 10.1 on elrohir over the last week. As I said before, it was mostly a normal ride, and Patrick Volkerding is to be commended for making such an excellent distro. However, I ran into two problems. 1. First I will tell you about the most annoying issues. For annoyances only, this got&#8230;<\/p>\n","protected":false},"author":159,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[5],"tags":[],"class_list":["post-166","post","type-post","status-publish","format-standard","hentry","category-computers"],"_links":{"self":[{"href":"https:\/\/shadow.sombragris.org\/index.php?rest_route=\/wp\/v2\/posts\/166","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/shadow.sombragris.org\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/shadow.sombragris.org\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/shadow.sombragris.org\/index.php?rest_route=\/wp\/v2\/users\/159"}],"replies":[{"embeddable":true,"href":"https:\/\/shadow.sombragris.org\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=166"}],"version-history":[{"count":0,"href":"https:\/\/shadow.sombragris.org\/index.php?rest_route=\/wp\/v2\/posts\/166\/revisions"}],"wp:attachment":[{"href":"https:\/\/shadow.sombragris.org\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=166"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/shadow.sombragris.org\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=166"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/shadow.sombragris.org\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=166"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}