It seems that I encountered a problem similar to what Daniek C has. From Jan. 1st my Fujitsu laptop SH782 running Ubuntu 14.04 repetitively fails to start the working environment after I correctly enter the login password. The login screen appears again and again.
According to the log files, I guess something wrong gets /usr/bin/X terminated. .xsession-errors ---------------------------------------------------------------------------------------------- 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: gnome-session (Unity) main process (2474) terminated with status 1 init: unity-settings-daemon main process (2460) killed by TERM signal init: at-spi2-registryd main process ended, respawning init: logrotate main process (2364) killed by TERM signal init: update-notifier-crash (/var/crash/_usr_bin_Xorg.0.crash) main process (2415) killed by TERM signal init: update-notifier-crash (/var/crash/_usr_lib_ibus_ibus-ui-gtk3.1000.crash) main process (2426) killed by TERM signal init: xsession-init main process (2452) killed by TERM signal init: hud main process (2467) killed by TERM signal init: unity-panel-service main process (2480) killed by TERM signal ---------------------------------------------------------------------------------------------- ---------------------------------------------------------------------------------------------- [+0.03s] DEBUG: Launching process 1312: /usr/bin/X -core :0 -seat seat0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch : : [+7.63s] DEBUG: Session pid=1407: Authentication complete with return value 0: Success [+7.63s] DEBUG: Session pid=1359: Authenticate result for user harold: Success : : [+7.66s] DEBUG: Session pid=1407: Logging to .xsession-errors [+7.67s] DEBUG: Activating VT 7 [+7.67s] DEBUG: Activating login1 session c2 [+8.08s] DEBUG: Session pid=1407: Exited with return value 0 [+8.08s] DEBUG: Seat: Session stopped [+8.08s] DEBUG: Seat: Stopping display server, no sessions require it [+8.08s] DEBUG: Sending signal 15 to process 1312 ---------------------------------------------------------------------------------------------- -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to at-spi2-core in Ubuntu. https://bugs.launchpad.net/bugs/1228567 Title: at-spi2 daemon error messages in .xsession-errors Status in at-spi2-core package in Ubuntu: Fix Released Bug description: Sometimes I get the following messages in .xsession-errors 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 I use a Lenovo Thinkpad Twist convertible with touch screen, using Onboard in tablet mode. Can perhaps have a relation with bug 1227173. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/at-spi2-core/+bug/1228567/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
