any clues hy Gnome isn't autobooting?

[Jeremy Messenger]

On Sun, 03 Jun 2007 18:31:03 -0500, Gary Kline <kline at tao.thought.org>  
wrote:

> On Sun, Jun 03, 2007 at 11:57:53AM -0500, Jeremy Messenger wrote:
>> On Sat, 02 Jun 2007 18:51:24 -0500, Gary Kline <kline at tao.thought.org>
>> wrote:
>>
>> >	  622  ??  Is     0:00.01 /usr/local/sbin/gdm-binary
>> >
>> >	Next, I typed kdm and after an error that I couldn't catch from
>> >	the console --I can grep or find the strings if that will help--
>> >	and after kdm thought about it, the kdm xlogin stuff popped up.
>> >	I selected Gnome, and  voila!
>>
>> Do you have anything in ~/.xsession-errors?
>
> 	Good one!
>
> 	Yes, there were a slew of errors mostly, I think, from KDE
> 	trying  to  spawn whatever initialization stuff it stashes in
> 	/tmp.  After I quit KDE and tried Gnome, there were/are both
> 	WARNING's anf CRITICAL level errors.
>
> 	errors file read in below.  (abbrvt'd :)
>
>
> SESSION_MANAGER=local/tao2.thought.org:/tmp/.ICE-unix/787
>
> (nautilus:1163): Liboobs-WARNING **: Failed to connect to socket  
> /var/run/dbus/system_bus_socket: No such file or directory
> Initializing gnome-mount extension
>
> ** (nautilus:1163): WARNING **: Cannot connect to system bus:  
> org.freedesktop.DBus.Error.FileNotFound : Failed to connect to socket  
> /var/run/dbus/system_bus_socket: No such file or directory
>
> ** (nautilus:1163): WARNING **: Could not initialize hal context

It shows that you don't have dbus, hal and etc running. Follow this:  
http://www.freebsd.org/gnome/docs/faq2.html#full-gnome

Cheers,
Mezz

> (nautilus:1163): GLib-GObject-CRITICAL **: g_object_new: assertion  
> `G_TYPE_IS_OBJECT (object_type)' failed
>
> (nautilus:1163): GLib-GObject-CRITICAL **: g_object_weak_ref: assertion  
> `G_IS_OBJECT (object)' failed
> Shutting down gnome-mount extension
> seahorse nautilus module initialized
>
> ** (gnome-panel:1160): WARNING **: Failed to authenticate with GDM
> DCOPClient::attachInternal. Attach failed Could not open network socket
> DCOPClient::attachInternal. Attach failed Could not open network socket
> kbuildsycoca running...
> DCOP Cleaning up dead connections.
> Window manager warning: Invalid WM_TRANSIENT_FOR window 0x3e specified  
> for 0x2200010 (KDE Text-t).
> Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message  
> with a timestamp of 0 for 0x2200010 (KDE Text-t)
> Window manager warning: meta_window_activate called by a pager with a 0  
> timestamp; the pager needs to be fixed.
> Launched ok, pid = 1209
> Window manager warning: Invalid WM_TRANSIENT_FOR window 0x3e specified  
> for 0x2200438 (Open - ktt).
> khelpcenter: WARNING: Main template file name is empty.
>
> ** (gnome-panel:1160): WARNING **: Failed to authenticate with GDM
> Window manager warning: Invalid WM_TRANSIENT_FOR window 0x2200700  
> specified for 0x220072f (Query Voic).
> Window manager warning: Invalid WM_TRANSIENT_FOR window 0x3e specified  
> for 0x2200010 (KDE Text-t).
> Window manager warning: Invalid WM_TRANSIENT_FOR window 0x3e specified  
> for 0x2200937 (Open - ktt).
> QFile::open: No file name specified
> Window manager warning: Invalid WM_TRANSIENT_FOR window 0x22000f8  
> specified for 0x2200b78 (Confirm Qu).
> X Error: BadWindow (invalid Window parameter) 3
>   Major opcode:  7
>   Minor opcode:  0
>   Resource id:  0x22000f8
> QObject::connect: No such signal KTTSDLib::signalCallPreferences()
> QObject::connect:  (sender name:   'KTTSD-Library')
> QObject::connect:  (receiver name: 'MainWindow')
> kio (KMimeType): WARNING: KServiceType::offers : servicetype  
> KSayIt/FXPlugin not found
> Window manager warning: Invalid WM_TRANSIENT_FOR window 0x3e specified  
> for 0x2a00005 (Configure ).
> Window manager warning: Invalid WM_TRANSIENT_FOR window 0x2a00305  
> specified for 0x2a0032f (Query Voic).
> Window manager warning: Invalid WM_TRANSIENT_FOR window 0x2a0038d  
> specified for 0x2a003b7 (Query Voic).
>
>
> 	Part of the errs like the XErr: BadWindow lines started showing
> 	up weeks ago when I ssh around.  My best guess is an ssh config
> 	error.  But why would Gnome care about this?  What if my FBSD
> 	computer were standalone?
>
> 	The glib failures are head-scratches too... .
>
> 	HTH!
>
> 	gary
>
>
>>
>> Cheers,
>> Mezz
>>
>



-- 
mezz7 at cox.net  -  mezz at FreeBSD.org
FreeBSD GNOME Team  -  FreeBSD Multimedia Hat (ports, not src)
http://www.FreeBSD.org/gnome/  -  gnome at FreeBSD.org
http://wiki.freebsd.org/multimedia  -  multimedia at FreeBSD.org