Bug 1611040

Summary:	shutdown/reboot time allowed for app cleanup
Product:	[Fedora] Fedora	Reporter:	Nick Levinson <Nick_Levinson>
Component:	gnome-session	Assignee:	Ray Strode [halfline] <rstrode>
Status:	CLOSED EOL	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	28	CC:	alexl, john.j5live, lnykryn, mclasen, mschmidt, msekleta, rhughes, rstrode, sandmann, sanjay.ankur, s, systemd-maint, zbyszek
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-05-28 18:57:01 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Nick Levinson 2018-08-02 01:18:58 UTC

Please pardon the component selection. (The menu is hard to use and unwieldy in length, I have no idea which component to select, and "other" or "unknown" appear to be absent.) Here's the issue:

When a user leaves the OS, the OS quits from apps. Apps may need time to clean themselves up but users may need immediate exits. A Firefox browser bug report response said: "If you leave Firefox running and shutdown or restart the system, the Firefox process will not have a chance to clean the cache up - it takes time, and the system will kill it."/"There is probably no way to tell Fedora to wait until it's done. Windows has a feature like that when you shutting the system down" (https://bugzilla.mozilla.org/show_bug.cgi?id=1476152#c1). I asked about this at https://ask.fedoraproject.org/en/question/124255/rebootshutdown-with-app-running-and-how-f28-affects-apps-cleanup-at-that-moment/ but, so far, no answer has come.

I don't know how Fedora behaves on this point and basically can't find out, so here's my feature request:

Fedora should default to the most thorough exit, so apps can have all the time they wish for cleanup and app exit. But the user, root or nonroot, should be allowed to specify in advance a number of seconds that should not be exceeded for apps to use before exiting. The default should be 3 seconds, but other people may prefer a different default. For nondefaults, the number of seconds could be zero (forcing an immediate exit) or infinite (which wouldn't cause a freeze but might coincide with a freeze unless the user disconnects both AC and DC power). I don't know if any situation found by 99% of users would ever require more than 30 seconds; if I'm right, then nondefaults could be 1, 2, 3, 5, 10, 15, 20, and 30 secs. When that number of seconds is reached, all apps should be forced to quit regardless of state of cleanup.

As a bonus, if a long number of seconds or infinity is selected, a dialog should appear during that time period with the dialog offering immediate quits from all apps so departure from the OS will be quick.

As a better bonus, that dialog should list which apps have not yet quit and the user should be allowed to select which apps should be forced to quit immediately, with the procedure.

Comment 1 Ankur Sinha (FranciscoD) 2018-08-02 10:23:35 UTC

Hi!

Thanks for the report. Yeh, this isn't the right component, and there isn't a right component for this because it isn't an issue related to a specific package. The only place I can think of where this could be brought up would be the devel list. 

I'm not entirely sure what the shutdown process is. `man systemctl` does provides some information, but you'll really need to speak to the devs to see exactly what's happening. I'm reassigning this to systemd, since that handles the shutdown process nowadays (or so I gather).

Thanks!

Comment 2 Zbigniew Jędrzejewski-Szmek 2018-08-19 08:18:38 UTC

As I wrote on the mailing list, firefox is running as part of a session scope managed by gnome session, and the systemd timeouts are not applicable. I'll reassign this to gnome-session.

Comment 3 Michal Schmidt 2018-08-19 16:20:38 UTC

We have the mechanism of inhibitors:
https://www.freedesktop.org/wiki/Software/systemd/inhibit/
Firefox could grab a shutdown delay inhibitor to get up to 5 seconds between receiving a PrepareForShutdown() signal and the actual shutdown being executed.

Comment 4 Ben Cotton 2019-05-02 21:03:53 UTC

This message is a reminder that Fedora 28 is nearing its end of life.
On 2019-May-28 Fedora will stop maintaining and issuing updates for
Fedora 28. It is Fedora's policy to close all bug reports from releases
that are no longer maintained. At that time this bug will be closed as
EOL if it remains open with a Fedora 'version' of '28'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 28 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 5 Ben Cotton 2019-05-28 18:57:01 UTC

Fedora 28 changed to end-of-life (EOL) status on 2019-05-28. Fedora 28 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.