Re: [ANNOUNCE] GARNOME 2.17.5 -- "Same procedure as every year, James"
- From: "Joseph E. Sacco, Ph.D." <joseph_sacco comcast net>
- To: garnome-list <garnome-list gnome org>
- Subject: Re: [ANNOUNCE] GARNOME 2.17.5 -- "Same procedure as every year, James"
- Date: Mon, 15 Jan 2007 17:44:20 -0500
The culprit is system-tool-back-ends, which is a work in progress.
What to do... There are two options:
Option #1:
uninstall gnome-system-tools
gnome-systems-tools uses liboobs which is a wrapper for
system-tools-backends.
Presently, gnome-system-tools applications are "read-only" and do not
allow you to change anything unless you are root. Eventually, g-s-t
will use policykit which allow an admin group to be defined.
Option #2:
* As root:
- create a group named stb-admin
[the name is a configure option for system-tools-backends]
- add yourself to this group
- start the GARNOME system-dbus
- manually start $garnome/bin/system-tools-backends before launching the
desktop.
-Joseph
==============================================================
On Mon, 2007-01-15 at 22:46 +0100, Stef van der Made wrote:
> Hi,
>
> A little update. The issues with glib have been solved with the latest
> update 2.12.8
>
> but when starting garnome and specificaly nautilus I get this error
>
> bash-2.05b$ nautilus
> GTK Accessibility Module initialized
> Bonobo accessibility support initialized
>
> (nautilus:8157): Liboobs-WARNING **: Failed to connect to socket
> /usr/test/garnome/var/run/dbus/system_bus_socket: Connection refused
>
> Liboobs-CRITICAL **: OobsSession object hasn't connected to the bus,
> cannot register OobsObject
> aborting...
>
> (process:8157): GLib-CRITICAL (recursed) **: g_key_file_set_value:
> assertion `g_key_file_is_key_name (key)' failed
> aborting...
>
>
> I'm starting dbus with this command in the X session start
>
> DBUS_LAUNCH="$GARNOME/bin/dbus-launch --exit-with-session"
>
> I keep getting this error on dbus
>
>
> (nautilus:3424): Liboobs-WARNING **: Failed to connect to socket
> /usr/test/garnome/var/run/dbus/system_bus_socket: No such file or
> directory
>
> Does anybody have any tips on what I could check ?
>
> Thanks
>
> Stef
>
--
joseph_sacco [at] comcast [dot] net
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]