A comment <https://bugzilla.gnome.org/show_bug.cgi?id=571417#c31> on the upstream bugzilla entry for this bug suggested a solution which should work. nautilus has a gconf entry /apps/nautilus/preferences/exit_with_last_window, which determines whether it will exit when it has no windows to display (including the desktop). exit_with_last_window=true by default. Thus, with show_desktop=false and exit_with_last_window=true, nautilus will exit when launched by gnome-session, and gnome-session will then respawn it, leading to the original bug. However, with show_desktop=false and exit_with_last_window=false, nautilus will continue running after gnome-session launches it, avoiding both the original bug and the current bug of not handling automounting anymore.
The comment suggested just setting /apps/nautilus/preferences/exit_with_last_window=false as a mandatory gconf setting. This seems sensible. It should have no effect with show_desktop=true, as nautilus will already continue running in that case. With show_desktop=false, it should unbreak things. Thus, could you please: - Change gnome-session to include the file manager in the required components list again - Remove the autostart file from nautilus that only starts nautilus if show_desktop=true - Set /apps/nautilus/preferences/exit_with_last_window=false in mandatory gconf settings. - Make the new versions of gnome-session and nautilus declare Breaks for older versions of each other, to ensure that they get upgraded together. (Actually, the new nautilus could just declare Breaks for the specific versions of gnome-session that didn't launch nautilus, but you can't specify a range of versions and enumerating specific versions seems error-prone.) Thanks, Josh Triplett -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
