Date: Sun, 26 Apr 2009 21:52:02 +0200 From: Andreas Wetzel <mickey242@gmx.net> To: Joe Marcus Clarke <marcus@marcuscom.com> Cc: gnome@freebsd.org Subject: Re: upgraded to gnome 2.26.1 this AM - all icons missing Message-ID: <49F4BB62.4040303@gmx.net> In-Reply-To: <1240771243.58743.160.camel@shumai.marcuscom.com> References: <20090424180051.1679D17975@bsd.mvh> <20090425134344.8B7A517192@bsd.mvh> <1240685447.58743.123.camel@shumai.marcuscom.com> <20090425192824.5579918DFF@bsd.mvh> <49F475A5.2080609@gmx.net> <1240771243.58743.160.camel@shumai.marcuscom.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Joe Marcus Clarke wrote: > On Sun, 2009-04-26 at 16:54 +0200, Andreas Wetzel wrote: >> I have had the same thing on one machine I upgraded from 2.24 this morning. >> Log in via gdm was slow, and then no icons... >> A quick investigation revealed that gnome-settings-daemon was somehow hung. >> When trying to start it manually with --debug --no-daemon, i got a message >> like this right after trying to initialize the 'media-keys' plugin: >> >> socket(): Protocol not supported >> >> and then it hung. I was able to get around this by manually disabling the >> media-keys plugin via gconf-editor. It would be nice, if the program were >> telling *which* protocol is not supported. >> >> On another machine, which I just upgraded, i am too seeing such 'Protocol not >> supported' messages, when starting gnome-settings-daemon' manually, although >> it does not hang. Is the red coloring of these messages supposed to mean that >> these should normally not happen? :-) > > What version of FreeBSD are you running? 7.1-RELEASE-p3 on both of those machines. -- Keep it icy man. I don't want to end up a corpse before my time because you were daydreaming.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?49F4BB62.4040303>