After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 674964 - don't require the user to log out after software updates
don't require the user to log out after software updates
Status: RESOLVED OBSOLETE
Product: gnome-settings-daemon
Classification: Core
Component: updates
unspecified
Other Linux
: Normal normal
: ---
Assigned To: Richard Hughes
gnome-settings-daemon-maint
Depends on:
Blocks: 657011
 
 
Reported: 2012-04-27 14:40 UTC by Allan Day
Modified: 2013-07-16 16:33 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Allan Day 2012-04-27 14:40:05 UTC
We currently ask the user to log out and log back in again after some software updates. It would be good to avoid this, since log out is an odd concept to have on a single user system.
Comment 1 Matthias Clasen 2012-04-27 14:41:39 UTC
what updates currently fall into the category of 'requires logout, but not restart' ?

seems to me that most core updates should be 'requires restart' and most app updates should just ask the user for restarting the app afterwards.
Comment 2 William Jon McCann 2012-05-09 17:21:17 UTC
Agree. That entire category of things assumes that there aren't other user sessions on the system too. And this includes gdm / login screen sessions.

For apps, restarting the app afterwards is a bad idea too because the app may fail during exit due to missing stuff. This was historically a big problem with Firefox.

I suppose ideally for apps we'd have a way to keep the app files around until the last instance exits. Perhaps this is like unlinking and leaving a file descriptor open.

But agree for the core - just restart and make it snappy.
Comment 3 Colin Walters 2012-05-09 18:43:25 UTC
There's no good way for PackageKit to distinguish between applications and the system, because everything is just a package.

I think probably the best fix here is to:

s/logout/restart/
s/reboot/restart/

And just optimize "restart" to be "log out" if we don't need to actually reboot.
Comment 4 Bastien Nocera 2013-04-18 07:38:11 UTC
Isn't this fixed now? I'm pretty sure it's not g-s-d's updates plugin that triggers that dialogue.
Comment 5 Richard Hughes 2013-07-16 16:33:38 UTC
We're discussing the offline updates stuff for F20 which will fix this, i.e. make all the updates offline.