jpds posted me the pertinent bits from the .xsession-errors:
** (gnome-fallback-mount-helper:1522): DEBUG: ConsoleKit session is active 0
gnome-session[1430]: WARNING: Application 'compiz.desktop' killed by signal
gnome-session[1430]: WARNING: App 'compiz.desktop' respawning too quickly
gnome-session[1430]: CRITICAL: We failed, but the fail whale is dead. Sorry....
So, compiz is definitely getting stuck in a loop. gnome-session notices it's failing and (I guess) restarts the session.
I'd follow the usual compiz troubleshooting steps from here. Enable debugging; test a guest session; run compiz through gdb; disable compiz plugins one by one, etc.
jpds posted me the pertinent bits from the .xsession-errors:
** (gnome- fallback- mount-helper: 1522): DEBUG: ConsoleKit session is active 0 1430]: WARNING: Application 'compiz.desktop' killed by signal 1430]: WARNING: App 'compiz.desktop' respawning too quickly 1430]: CRITICAL: We failed, but the fail whale is dead. Sorry....
gnome-session[
gnome-session[
gnome-session[
So, compiz is definitely getting stuck in a loop. gnome-session notices it's failing and (I guess) restarts the session.
I'd follow the usual compiz troubleshooting steps from here. Enable debugging; test a guest session; run compiz through gdb; disable compiz plugins one by one, etc.