{"id":86,"date":"2006-06-08T22:04:27","date_gmt":"2006-06-08T21:04:27","guid":{"rendered":"http:\/\/jerome.harckmans.be\/?p=86"},"modified":"2006-06-08T22:04:27","modified_gmt":"2006-06-08T21:04:27","slug":"upgrade-to-dapper-drake","status":"publish","type":"post","link":"https:\/\/jerome.harckmans.be\/?p=86","title":{"rendered":"Upgrade to Dapper Drake"},"content":{"rendered":"<p>Today I decided to updgrade my Ubuntu 5.04 System (Breezy) to the latest version, i.e. Ubuntu 6.06 (Dapper Drake). After some 764Mb of new packages, some (un-happy) removals, some installations, and some error saying that the upgrade process has been stopped due to an unforeseen error (huh!), I could manually reboot my system into its new version!<\/p>\n<p>I&#8217;m a big supporter of FVWM, and use it daily instead of Gnome, which I find too slow, as I use aTerm for the same reason and conky for monitoring my system. How big was my surprise too see just after logging in a pink conky, black on black window titles, and aterm refusing to start due to some color error.<\/p>\n<p>After some debugging, here is what I found out:<\/p>\n<p>When starting aterm, I got this error:<\/p>\n<p><code>aterm: can't load color black<\/code><\/p>\n<p>followed by identical output for a bunch of various colors. I suspected the same happens with conky and FVWM, which cannot extrapolate HEX colors from these color names.<\/p>\n<p>The solution was to modify the line in the <code>\/etc\/X11\/xorg.conf<\/code> file which define the path to the rgb color file (rgb.txt). After the upgrade, it has simply moved from some <code>\/usr\/X11...\/lib\/...<\/code> location to <code>\/etc\/X11\/rgb.txt<\/code>.<\/p>\n<p>Simply putting<\/p>\n<p><code>RgbPath    =\"\/etc\/X11\/rgb\"<\/code><\/p>\n<p>in the Xorg config file did the trick (don&#8217;t type the .txt!!!).<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Today I decided to updgrade my Ubuntu 5.04 System (Breezy) to the latest version, i.e. Ubuntu 6.06 (Dapper Drake). After some 764Mb of new packages, some (un-happy) removals, some installations,<\/p>\n","protected":false},"author":3,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":[],"categories":[3,6],"tags":[],"_links":{"self":[{"href":"https:\/\/jerome.harckmans.be\/index.php?rest_route=\/wp\/v2\/posts\/86"}],"collection":[{"href":"https:\/\/jerome.harckmans.be\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/jerome.harckmans.be\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/jerome.harckmans.be\/index.php?rest_route=\/wp\/v2\/users\/3"}],"replies":[{"embeddable":true,"href":"https:\/\/jerome.harckmans.be\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=86"}],"version-history":[{"count":0,"href":"https:\/\/jerome.harckmans.be\/index.php?rest_route=\/wp\/v2\/posts\/86\/revisions"}],"wp:attachment":[{"href":"https:\/\/jerome.harckmans.be\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=86"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/jerome.harckmans.be\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=86"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/jerome.harckmans.be\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=86"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}