Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 8 Oct 2006 18:04:53 +0200
From:      Jean-Yves Lefort <jylefort@FreeBSD.org>
To:        Hans Nieser <h.nieser@xs4all.nl>
Cc:        freebsd-gnome@freebsd.org
Subject:   Re: mysterious error dialog when logging into gnome 2.16.1
Message-ID:  <20061008180453.f1cb2ebc.jylefort@FreeBSD.org>
In-Reply-To: <4528FF90.4080703@xs4all.nl>
References:  <4528FC58.6030407@xs4all.nl> <4528FF90.4080703@xs4all.nl>

next in thread | previous in thread | raw e-mail | index | archive | help
--Signature=_Sun__8_Oct_2006_18_04_53_+0200_TxI3ok9qi/kt40PD
Content-Type: text/plain; charset=US-ASCII
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Sun, 08 Oct 2006 15:39:28 +0200
Hans Nieser <h.nieser@xs4all.nl> wrote:

> Hans Nieser wrote:
> > I've just updated to gnome 2.16.1 (marcuscom), but I get an error dialog
> > when I log into gnome. The dialog dissappears before I can read it so I
> > don't know what the problem is. But it's annoying nonetheless.
> >=20
> > I've checked gdm's log, xorg's log and ~/.xsession-errors but I can't
> > figure out what is causing this error. Does anyone know where else to l=
ook?
>=20
> By examining each startup program in my gnome session, I found out it is
> being caused by gnome-power-manager. Running it manually makes the same
> dialog popup (and dissappear again before I can read it) and leaves no
> output on the console. Running it with --verbose leaves this:
>=20
> hans@aphax-laptop:~$ DISPLAY=3D":0.0" gnome-power-manager --verbose
> [gpm_debug_init] gpm-debug.c:158 (15:36:52):     Verbose debugging enabled
> *** WARNING ***
> [main] gpm-main.c:183 (15:36:52):        Failed to connect to socket
> /var/run/dbus/dbus.pipe: No such file or directory
> [gpm_syslog] gpm-debug.c:140 (15:36:52):         Saving to syslog:
> Critical error: This program cannot start until you start the dbus system
> service.
> It is <b>strongly recommended</b> you reboot your computer after starting
> this service.
>=20
> As far as I know, dbus is up and running:
>=20
> hans@aphax-laptop:~$ ps auxww | grep dbus
> hans  28949  0.0  0.2  1976  1560  ??  Is    3:28PM   0:00.02 dbus-daemon
> --fork --print-address 22 --print-pid 24 --session

That's the session daemon, but it wants the system daemon:

/usr/local/etc/rd.d/dbus.sh forcestart

(add dbus_enable=3D"YES" to /etc/rc.conf to automatically start it at boot)

--=20
Jean-Yves Lefort

jylefort@FreeBSD.org
http://lefort.be.eu.org/

--Signature=_Sun__8_Oct_2006_18_04_53_+0200_TxI3ok9qi/kt40PD
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (FreeBSD)

iD8DBQFFKSGlyzD7UaO4AGoRAhT4AJ9h5Rx0jY90sRzpzol/LMk7I1yqUwCcD+mx
3y4VnPhVeIpacqEka6oC9P8=
=fz3c
-----END PGP SIGNATURE-----

--Signature=_Sun__8_Oct_2006_18_04_53_+0200_TxI3ok9qi/kt40PD--




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20061008180453.f1cb2ebc.jylefort>