Let's see. When it fails I log in via ssh and watch what's happening. As the .xsession-errors indicates, it's spinning on a unity-2d-panel failure, but unity-2d-shell is running and doesn't report any errors. Eventually it gives up as noted, ending with
gnome-session[22299]: WARNING: Application 'unity-2d-panel.desktop' killed by signal gnome-session[22299]: WARNING: App 'unity-2d-panel.desktop' respawning too quickly gnome-session[22299]: CRITICAL: We failed, but the fail whale is dead. Sorry.... As expected, metacity seems fine, and C-M-t brings up a terminal. If I run unity-2d-panel from that shell, it takes a while to begin starting up, and then I get the results in the attached unity-2d- panel.typescript. ** Attachment added: "unity-2d-panel.typescript" https://bugs.launchpad.net/ubuntu/+source/unity-2d/+bug/993694/+attachment/3186860/+files/unity-2d-panel.typescript -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/993694 Title: unity-2d does not start if user has logged in on unity To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-2d/+bug/993694/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
