GNOME Bugzilla – Bug 629304
Bad logic when Xephyr not found
Last modified: 2010-09-22 18:42:28 UTC
Reported by G. Michael Carter in https://bugzilla.redhat.com/show_bug.cgi?id=632663 When trying to run gnome-shell without Xephyr installed, he got: === gnome-shell:437:<module>:NameError: name 'xephyr' is not defined Traceback (most recent call last):
+ Trace 223637
if xephyr:
=== So it seems like we have some logic bug - probably just need a xephyr = None somewhere.
Created attachment 170853 [details] [review] gnome-shell.in: Make xephr available within the scop of run_shell
Created attachment 170854 [details] [review] gnome-shell.in: Make xephr available within the scope of run_shell Fix subject (typo)
Review of attachment 170854 [details] [review]: ::: src/gnome-shell.in @@ +305,2 @@ normal_exit = False + xephyr = None If you add this here (presumably for the case where start_xephyr() throws), then you should remove the existing xephyr = None
Created attachment 170855 [details] [review] gnome-shell.in: Make xephr available within the scope of run_shell
Review of attachment 170855 [details] [review]: Looks good
Attachment 170855 [details] pushed as 8591a2f - gnome-shell.in: Make xephr available within the scope of run_shell