Date: Tue, 25 Mar 2008 14:07:23 -0400 From: Joe Marcus Clarke <marcus@marcuscom.com> To: Renato Botelho <garga@freebsd.org> Cc: gnome@freebsd.org Subject: Re: gconfd problems after upgrade Message-ID: <47E93F5B.7040103@marcuscom.com> In-Reply-To: <20080325162027.GA18824@bluepex.com> References: <20080325122224.GA82165@bluepex.com> <1206458613.93352.6.camel@shumai.marcuscom.com> <20080325155957.GA3293@bluepex.com> <20080325162027.GA18824@bluepex.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Renato Botelho wrote: > On Tue, Mar 25, 2008 at 12:59:57PM -0300, Renato Botelho wrote: >> On Tue, Mar 25, 2008 at 11:23:33AM -0400, Joe Marcus Clarke wrote: >>> On Tue, 2008-03-25 at 09:22 -0300, Renato Botelho wrote: >>>> -----BEGIN PGP SIGNED MESSAGE----- >>>> Hash: SHA1 >>>> >>>> Hello, >>>> >>>> Actually, i'm not using gnome, but, a part of its code is installed here as >>>> dependencies. After upgrade these ports to new gnome 2.22 i've started to >>>> have a problem, screen freezes, and after i move the mouse it back, it >>>> happens all the time and make impossible to use the workstation. >>>> >>>> I saw the following message on /var/log/messages: >>>> >>>> Mar 25 09:04:17 soc90 gconfd (garga-27371): Failed to send buffer >>>> Mar 25 09:04:17 soc90 last message repeated 9 times >>> These I don't see. >>> >>>> I tried to remove .gconf* on my home but nothing happened. Any ideas what's >>>> happening here and how to fix? >>> I see the mouse lock-up issue, too, and I don't think it has anything to >>> do with GNOME. It was reported on x11@ on March 5. I think it has >>> something to do with the recent X.Org jerky mouse changes. Disabling >>> moused, and having X talk directly to /dev/psm0 is a workaround. >> One more time you're right, disabling moused fixed the problem. > > Just one more problem i'm having, when i add a usb pen, it appears on > nautilus but doesn't mount, and I got this on console.log: > > Mar 25 13:03:04 soc90 kernel: Mar 25 13:03:04 soc90 > console-kit-daemon[1062]: GLib-CRITICAL: g_hash_table_destroy: assertion > `hash_table != NULL' failed > Mar 25 13:03:26 soc90 kernel: Mar 25 13:03:26 soc90 > console-kit-daemon[1062]: GLib-CRITICAL: g_hash_table_lookup: assertion > `hash_table != NULL' failed > Mar 25 13:03:26 soc90 kernel: Mar 25 13:03:26 soc90 > console-kit-daemon[1062]: GLib-CRITICAL: g_hash_table_destroy: assertion > `hash_table != NULL' failed > Mar 25 13:03:41 soc90 kernel: Mar 25 13:03:41 soc90 > console-kit-daemon[1062]: GLib-CRITICAL: g_hash_table_lookup: assertion > `hash_table != NULL' failed > > I've researched a bit, and find some entries like this, but no one about > console-kit-daemon. Any idea? The auto-mounting section of the FAQ has not been updated yet, but by default, GNOME expects you to be using GDM and thus have a ConsoleKit session record (try running ck-list-sessions). If the current session is active, then mounting of removable media will just work. If you are not using GDM, or you do not have an active CK session, then you will need to modify /usr/local/etc/PolicyKit/PolicyKit.conf. See PolicyKit.conf(5) for examples. Joe > > Thanks in advance -- PGP Key : http://www.marcuscom.com/pgp.asc
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?47E93F5B.7040103>