Comment 8 for bug 1285444

Revision history for this message
Markus (markusb) wrote :

I have the same problem since I updated the system today. Nothing has chenges besides the upgrade and the reboot afterwards. I can login using the 'classic' interface, but Unity does not work.

My .xsession-errors file lokks very similar to the one above:

markus@markus-ThinkPad-W530:~$ cat .xsession-errors.unity-broken
Script for ibus started at run_im.
init: at-spi2-registryd main process ended, respawning
init: at-spi2-registryd main process ended, respawning
init: at-spi2-registryd main process ended, respawning
init: at-spi2-registryd main process ended, respawning
init: at-spi2-registryd main process ended, respawning
init: at-spi2-registryd main process ended, respawning
init: at-spi2-registryd main process ended, respawning
init: at-spi2-registryd main process ended, respawning
init: at-spi2-registryd main process ended, respawning
init: at-spi2-registryd main process ended, respawning
init: at-spi2-registryd respawning too fast, stopped
init: unity-settings-daemon main process (10653) terminated with status 1
init: unity-settings-daemon main process ended, respawning
init: gnome-session (Unity) main process (10687) terminated with status 1
init: unity-panel-service main process (10694) terminated with status 1
init: unity-panel-service main process ended, respawning
init: unity-settings-daemon main process (11411) killed by TERM signal
init: Disconnected from notified D-Bus bus
init: logrotate main process (10595) killed by TERM signal
init: indicator-bluetooth main process (10748) killed by TERM signal
init: indicator-power main process (10754) killed by TERM signal
init: indicator-datetime main process (10759) killed by TERM signal
init: indicator-printers main process (10769) killed by TERM signal
init: indicator-session main process (10777) killed by TERM signal
init: indicator-application main process (10794) killed by TERM signal
init: unity-panel-service main process (11412) killed by TERM signal

I have deleted the .Xauthority file, reinstalled the Nvidia-driver, etc. These do not help.