We saw from one log batch that after such a crash (not exit(1), but after a SIGSEGV) gnome-session tried restarting compiz a few times, but still wasn't able to start it for good. So I'm afraid that even if an exit(1) is fired, compiz will still be unable to start correctly. But at least we won't have an ugly crash but a graceful exit.
-- You received this bug notification because you are a member of compiz packagers, which is subscribed to compiz in Ubuntu. https://bugs.launchpad.net/bugs/833729 Title: compiz crashed with SIGSEGV in CompositeScreen::compositingActive() To manage notifications about this bug go to: https://bugs.launchpad.net/compiz-core/+bug/833729/+subscriptions _______________________________________________ Mailing list: https://launchpad.net/~compiz Post to : [email protected] Unsubscribe : https://launchpad.net/~compiz More help : https://help.launchpad.net/ListHelp
