From owner-freebsd-gnome@FreeBSD.ORG Sun Oct 8 13:39:33 2006 Return-Path: X-Original-To: freebsd-gnome@freebsd.org Delivered-To: freebsd-gnome@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AF6B216A403 for ; Sun, 8 Oct 2006 13:39:33 +0000 (UTC) (envelope-from h.nieser@xs4all.nl) Received: from smtp-vbr14.xs4all.nl (smtp-vbr14.xs4all.nl [194.109.24.34]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7F91943D45 for ; Sun, 8 Oct 2006 13:39:32 +0000 (GMT) (envelope-from h.nieser@xs4all.nl) Received: from [192.168.1.64] (aphax.nl [82.92.29.227]) by smtp-vbr14.xs4all.nl (8.13.8/8.13.8) with ESMTP id k98DdUAp087840 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Sun, 8 Oct 2006 15:39:31 +0200 (CEST) (envelope-from h.nieser@xs4all.nl) Message-ID: <4528FF90.4080703@xs4all.nl> Date: Sun, 08 Oct 2006 15:39:28 +0200 From: Hans Nieser User-Agent: Thunderbird 1.5.0.7 (X11/20060919) MIME-Version: 1.0 To: freebsd-gnome@freebsd.org References: <4528FC58.6030407@xs4all.nl> In-Reply-To: <4528FC58.6030407@xs4all.nl> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Virus-Scanned: by XS4ALL Virus Scanner Subject: Re: mysterious error dialog when logging into gnome 2.16.1 X-BeenThere: freebsd-gnome@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: GNOME for FreeBSD -- porting and maintaining List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 08 Oct 2006 13:39:33 -0000 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. > > 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 look? 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: hans@aphax-laptop:~$ DISPLAY=":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 strongly recommended you reboot your computer after starting this service. As far as I know, dbus is up and running: 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 Anyone know what to do about this?