Oops, missed these lines in the output before, but they look more
likely/suspect (to me):

_X11TransNAMEDOpenClient: Device /tmp/.X11-pipe/X0 is not a FIFO
_X11TransOpen: transport open failed for local/prickle:0

On Mon, 2010-01-04 at 12:58 -0500, Joanmarie Diggs wrote:
> Hey Brian.
> 
> In the Dept of Lousy Coincidences, this morning I did a fresh install of
> build 130 on my netbook. I'm seeing the very same problems as Rich.
> Before, when the netbook was progressively updated, build 130 was fine.
> So.... Mind if I play? :-)
> 
> On Mon, 2010-01-04 at 09:18 -0600, Brian Cameron wrote:
> 
> > I would recommend the following:
> > 
> > 1) Check the $HOME/.xsession-errors file and see if there are any useful
> >     error messages there which might indicate the failure.  Also,
> >     checking the Xorg logs in /var/log and /var/log/gdm may also
> >     highlight something useful.
> 
> Here's the tail end of mine:
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> (nautilus:743): Gtk-WARNING **: About JDS: missing action About JDS
> 
> (nautilus:743): Gtk-WARNING **: Go to Burn CD: missing action Go to Burn
> CD
> 
> (nautilus:743): Gtk-CRITICAL **: file gtkwidget.c: line 6112: assertion
> `GTK_IS_WIDGET (widget)' failed
> 
> (nautilus:743): Gtk-CRITICAL **: file gtkuimanager.c: line 1958:
> assertion `GTK_IS_MENU_SHELL (menushell)' failed
> 
> (nautilus:743): Gtk-WARNING **: About JDS: missing action About JDS
> /usr/lib/python2.6/vendor-packages/twisted/internet/_sslverify.py:5:
> DeprecationWarning: the md5 module is deprecated; use hashlib instead
>   import itertools, md5
> /usr/lib/python2.6/vendor-packages/codeina/httpdownload.py:14:
> DeprecationWarning: the sha module is deprecated; use the hashlib module
> instead
>   import sha
> _X11TransNAMEDOpenClient: Device /tmp/.X11-pipe/X0 is not a FIFO
> _X11TransOpen: transport open failed for local/prickle:0
> /usr/lib/python2.6/vendor-packages/gtk-2.0/gtk/__init__.py:57:
> GtkWarning: could not open display
>   warnings.warn(str(e), _gtk.Warning)
> /usr/lib/python2.6/vendor-packages/codeina/ui/igtk/window.py:13:
> Warning: invalid (NULL) pointer instance
>   gtk.Window.__init__ (self)
> /usr/lib/python2.6/vendor-packages/codeina/ui/igtk/window.py:13:
> Warning: file gsignal.c: line 2238: assertion `G_TYPE_CHECK_INSTANCE
> (instance)' failed
>   gtk.Window.__init__ (self)
> /usr/lib/python2.6/vendor-packages/codeina/ui/igtk/downloadprogress.py:23: 
> GtkWarning: file gtksettings.c: line 1000: assertion `GDK_IS_SCREEN (screen)' 
> failed
>   self.cancel_button = gtk.Button (stock=gtk.STOCK_CANCEL)
> /usr/lib/python2.6/vendor-packages/codeina/ui/igtk/downloadprogress.py:23: 
> Warning: file gobject.c: line 1630: assertion `G_IS_OBJECT (object)' failed
>   self.cancel_button = gtk.Button (stock=gtk.STOCK_CANCEL)
> /usr/lib/python2.6/vendor-packages/codeina/ui/igtk/downloadprogress.py:23: 
> Warning: value "TRUE" of type `gboolean' is invalid or out of range for 
> property `visible' of type `gboolean'
>   self.cancel_button = gtk.Button (stock=gtk.STOCK_CANCEL)
> 
> ** (gnome-power-manager:744): WARNING **: ERROR: Did not receive a
> reply. Possible causes include: the remote application did not send a
> reply, the message bus security policy blocked the reply, the reply
> timeout expired, or the network connection was broken.
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> 
> > 2) Try starting a failsafe terminal from the GDM login screen and run
> >     "dbus-launch --exit-with-session gnome-session --debug".  This
> >     will cause gnome-session to run with extra debug output and may
> >     also display other useful error messages that might not otherwise
> >     be shown in the $HOME/.xsession-errors file.
> 
> When I try this, I just see the errors from the top of .xsession-errors,
> the last one being:
> 
> (nautilus:839): Gtk-WARNING **: About JDS: missing action About JDS
> 
> > Does this point you towards anything useful that highlights what the
> > problem may be?
> 
> Given that this machine used to be fine running build 130, I'm guessing
> it's not power manager.(??) I'll look at codeina-related errors unless
> you spot something else.
> 
> Thanks! Take care.
> --joanie
> 


Reply via email to