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.
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 22299]: WARNING: App 'unity- 2d-panel. desktop' respawning too quickly 22299]: CRITICAL: We failed, but the fail whale is dead. Sorry....
gnome-session[
gnome-session[
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.typescrip t.