[xubuntu-users] xubuntu 12.10 has stopped boo

[Pierce Randall]

On 03/29/2013 05:01 PM, Chris Green wrote:
> I run xubuntu 12.10 and the system has stopped booting, it fails to get
> to the login screen.  It's not *very* broken because I can still run
> startx from one of the consoles and it runs the  GUI OK, it's just the
> login that isn't working.
>
> The .xsession-errors has *loads* of errors, as follows:-
>
>      openConnection: connect: No such file or directory
>      cannot connect to brltty at :0
>
>      (xfwm4:3369): Gdk-CRITICAL **: IA__gdk_error_trap_pop: assertion `gdk_error_traps != NULL' failed
>
>      (polkit-gnome-authentication-agent-1:3406): GLib-CRITICAL **: g_variant_new_string: assertion `string != NULL' failed
>
>      (polkit-gnome-authentication-agent-1:3406): polkit-gnome-1-WARNING **: Failed to register client: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.gnome.SessionManager was not provided by any .service files
>
>      (xfsettingsd:3419): xfsettingsd-WARNING **: Failed to get the _NET_NUMBER_OF_DESKTOPS property.
>      ** Message: applet now removed from the notification area
>      ** Message: using fallback from indicator to GtkStatusIcon
>      ** Message: applet now embedded in the notification area
>      thunar-volman: Unsupported USB device type.
>      thunar-volman: Unsupported USB device type.
>      thunar-volman: Unknown block device type.
>      thunar-volman: Could not detect the volume corresponding to the device.
>      thunar-volman: Unsupported USB device type.
>      thunar-volman: Unsupported USB device type.
>      thunar-volman: Unknown block device type.
>      thunar-volman: Could not detect the volume corresponding to the device.
>      thunar-volman: Unsupported USB device type.
>      thunar-volman: Unsupported USB device type.
>      thunar-volman: Unknown block device type.
>      thunar-volman: Could not detect the volume corresponding to the device.
>      ** Message: applet now removed from the notification area
>
>      (nm-applet:3387): Gdk-CRITICAL **: gdk_error_trap_pop_internal: assertion `trap != NULL' failed
>      /usr/bin/blueman-applet:79: GtkWarning: IA__gdk_error_trap_pop: assertion `gdk_error_traps != NULL' failed
>        gtk.main()
>
>      (update-notifier:3416): Gdk-WARNING **: update-notifier: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.0.
>
>
>      (polkit-gnome-authentication-agent-1:3406): Gdk-WARNING **: polkit-gnome-authentication-agent-1: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.0.
>
>
>      (nm-applet:3387): Gdk-WARNING **: nm-applet: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.0.
>
>      applet.py: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.0.
>      blueman-applet: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.0.
>      Xsession: X session started for chris at Thu Mar 28 18:55:35 GMT 2013
>      localuser:chris being added to access control list
>      openConnection: connect: No such file or directory
>      cannot connect to brltty at :0
>      Setting IM through im-switch for locale=en_GB.
>      Start IM through /etc/X11/xinit/xinput.d/all_ALL linked to /etc/X11/xinit/xinput.d/default.
>
>      (xfwm4:3327): Gdk-CRITICAL **: IA__gdk_error_trap_pop: assertion `gdk_error_traps != NULL' failed
>
>      (polkit-gnome-authentication-agent-1:3347): GLib-CRITICAL **: g_variant_new_string: assertion `string != NULL' failed
>
>      (polkit-gnome-authentication-agent-1:3347): polkit-gnome-1-WARNING **: Failed to register client: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.gnome.SessionManager was not provided by any .service files
>
>      (xfsettingsd:3384): xfsettingsd-WARNING **: Failed to get the _NET_NUMBER_OF_DESKTOPS property.
>      ** Message: applet now removed from the notification area
>      ** Message: using fallback from indicator to GtkStatusIcon
>      ** Message: applet now embedded in the notification area
>      thunar-volman: Unsupported USB device type.
>      thunar-volman: Unsupported USB device type.
>      thunar-volman: Unknown block device type.
>
>      (Thunar:3333): Gdk-CRITICAL **: IA__gdk_window_get_window_type: assertion `GDK_IS_WINDOW (window)' failed
>
>      (Thunar:3333): Gdk-CRITICAL **: IA__gdk_window_get_window_type: assertion `GDK_IS_WINDOW (window)' failed
>      thunar-volman: Unsupported USB device type.
>      thunar-volman: Unsupported USB device type.
>      thunar-volman: Unknown block device type.
>
>      (Thunar:3333): Gdk-CRITICAL **: IA__gdk_window_get_window_type: assertion `GDK_IS_WINDOW (window)' failed
>
>      (Thunar:3333): Gdk-CRITICAL **: IA__gdk_window_get_window_type: assertion `GDK_IS_WINDOW (window)' failed
>
>      (xfce4-terminal:3621): Gdk-CRITICAL **: IA__gdk_window_get_window_type: assertion `GDK_IS_WINDOW (window)' failed
>      ReminderFox  clh(1)  {rmFx_cmdLine: [xpconnect wrapped nsICommandLine]}
>      ReminderFox  clh(1)  {rmFx_cmdLine: [xpconnect wrapped nsICommandLine]}
>      Failed to open VDPAU backend libvdpau_nvidia.so: cannot open shared object file: No such file or directory
>      Failed to open VDPAU backend libvdpau_nvidia.so: cannot open shared object file: No such file or directory
>      Failed to open VDPAU backend libvdpau_nvidia.so: cannot open shared object file: No such file or directory
>      Failed to open VDPAU backend libvdpau_nvidia.so: cannot open shared object file: No such file or directory
>      Failed to open VDPAU backend libvdpau_nvidia.so: cannot open shared object file: No such file or directory
>      Failed to open VDPAU backend libvdpau_nvidia.so: cannot open shared object file: No such file or directory
>      NOTE: child process received `Goodbye', closing down
>      thunar-volman: Unsupported USB device type.
>      thunar-volman: Unsupported USB device type.
>      thunar-volman: Unknown block device type.
>
>      (Thunar:3333): Gdk-CRITICAL **: IA__gdk_window_get_window_type: assertion `GDK_IS_WINDOW (window)' failed
>      NOTE: child process received `Goodbye', closing down
>      ** Message: applet now removed from the notification area
>      xscreensaver: 19:00:39: SIGHUP received: restarting...
>      xscreensaver: 19:00:39: running as chris/chris (1000/1000)
>
>      xscreensaver: 19:00:40: Can't open display: :0.0
>      xscreensaver: 19:00:40: running as chris/chris (1000/1000)
>
>      xscreensaver: 19:00:40: Errors at startup are usually authorization problems.
>                    But you're not logging in as root (good!) so something
>                    else must be wrong.  Did you read the manual and the FAQ?
>
>                    http://www.jwz.org/xscreensaver/faq.html
>                    http://www.jwz.org/xscreensaver/man.html
>
>      Loading configuration plugins
>      blueman-applet version 1.23 starting
>      Stale PID, overwriting
>      Using gconf config backend
>      Using gconf config backend
>      Using gconf config backend
>      Using gconf config backend
>      Using gconf config backend
>      Using gconf config backend
>      Using gconf config backend
>      Using gconf config backend
>      Using gconf config backend
>      Using gconf config backend
>      Using gconf config backend
>      Traceback (most recent call last):
>        File "/usr/lib/python2.7/dist-packages/blueman/plugins/applet/AppIndicator.py", line 60, in on_notify
>          self.update_icon()
>        File "/usr/lib/python2.7/dist-packages/blueman/plugins/applet/AppIndicator.py", line 74, in update_icon
>          self.indicator.set_icon(self.Applet.Plugins.StatusIcon.props.icon_name)
>      TypeError: sighandler() takes no arguments (2 given)
>
>      (blueman-applet:3366): libappindicator-WARNING **: Unable to send signal for NewIcon: The connection is closed
>
> Can anyone suggest what might be wrong?
>
Perhaps you need to add sleep to lightdm or whatever program you use to 
bring up X window manager? All these errors might occur because X is 
loading before other important drivers or kernel modules open. I had 
this problem a while ago with X loading before my graphics driver, and I 
fixed it by adding two seconds of sleep before lightdm. If that's what 
the problem is (and it may very well not be), then add the line "sleep 
2" to the line before "exec lightdm" in /etc/init/lightdm.conf.