Read-only mirror of https://gitlab.gnome.org/GNOME/gnome-shell
af9ab5dbb6
If Mutter exits with an exit status of 0, then that most likely means that it was replaced by another window manager and we shoudln't try to start the previous window manager and the panel. (We don't actually know about the panel, but assume that if someone is replacing us they know what they are doing.) When Mutter exits with a signal, we know we want to restart. When Mutter exits with a non-signal non-zero exit status, it's ambiguous - we could be exiting because we lost the connection to the X server, or because of a assertion failure in gnome-shell. We assume the latter; if the X server is gone, all that will happen is a bit of noise. To know why Mutter exited accurately, we always wait() and kill() the Mutter process, and then, if running in Xephyr, clean up Xephyr afterwards. This has the nice side effect of exiting when gnome-shell does and not forcing the user to close Xephyr manually. http://bugzilla.gnome.org/show_bug.cgi?id=591171 |
||
|---|---|---|
| .settings | ||
| data | ||
| js | ||
| po | ||
| src | ||
| tools/build | ||
| .gitignore | ||
| .project | ||
| AUTHORS | ||
| autogen.sh | ||
| configure.ac | ||
| COPYING | ||
| MAINTAINERS | ||
| Makefile.am | ||
| README | ||