GNOME Bugzilla – Bug 592881
Require an explicit --xephyr option
Last modified: 2009-08-27 19:36:02 UTC
The current behavior where it tries to run in Xephyr if it thinks there is a window manager already running is confusing to people who want to try it out - see, e.g.: https://bugzilla.redhat.com/show_bug.cgi?id=518948 The default behavior without --replace should be like other window managers - try to start, fail if there is a window manager already running. This is easier now that we don't kill the panel in the wrapper before the shell starts. --xephyr would also allow deterministically running it xephyr no matter what window manager you already having running; a problem I've hit before because the script doesn't currently recognize mutter.
Created attachment 141872 [details] [review] Require an explicit --xephyr option Instead of starting Xephyr automatically, require --xephyr to be passed explicitly. This makes the operation easier to understand and has the benefit of allowing running in Xephyr mode when some other window manager (like gnome-shell!) is running. We also want to emphasize that Xephyr is a development tool, and not a good preview of the user-interface.
Comment on attachment 141872 [details] [review] Require an explicit --xephyr option looks good. (the semantics are broken if you're running a non-dbus-gnome-panel but no window manager and then run gnome-shell without "--replace", but... um, don't do that then.)
(In reply to comment #2) > (From update of attachment 141872 [details] [review]) > looks good. > > (the semantics are broken if you're running a non-dbus-gnome-panel but no > window manager and then run gnome-shell without "--replace", but... um, don't > do that then.) Yeah. :-) Pushed.