D27077: [RFC] [Logout screen] Shorten timeout to 10 seconds

ngraham abandoned this revision. ngraham added a comment. All right, sounds like this isn't a clear winner. REPOSITORY R120 Plasma Workspace REVISION DETAIL https://phabricator.kde.org/D27077 To: ngraham, #vdg, #plasma Cc: ahiemstra, rikmills, broulik, cfeck, davidedmundson,

D27077: [RFC] [Logout screen] Shorten timeout to 10 seconds

ahiemstra added a comment. > So maybe this isn't actually a destructive action at all. After all, an app with unsaved changes or active processed will block the logout/shutdown absent user interaction. That only happens if you happen to have unsaved changes. Many applications will

D27077: [RFC] [Logout screen] Shorten timeout to 10 seconds

davidedmundson added a comment. > But the timeout isn't used to give apps more time needed to clean up before they confirm the session can be closed? If I understand it correctly, there should be two timeouts? That's different Order is action invoked This confirmation /

D27077: [RFC] [Logout screen] Shorten timeout to 10 seconds

ngraham added a comment. In D27077#604505 , @broulik wrote: > Having Kickoff confirm shutdown could be superfluous as you already had to go through the trouble of opening it, going to "Leave", but for e.g. the lock logout entry or generic "

D27077: [RFC] [Logout screen] Shorten timeout to 10 seconds

rikmills added a comment. In D27077#604505 , @broulik wrote: > Having Kickoff confirm shutdown could be superfluous as you already had to go through the trouble of opening it, going to "Leave", but for e.g. the lock logout entry or generic "

D27077: [RFC] [Logout screen] Shorten timeout to 10 seconds

broulik added a comment. Having Kickoff confirm shutdown could be superfluous as you already had to go through the trouble of opening it, going to "Leave", but for e.g. the lock logout entry or generic " Leave" in the desktop context menu I'd still want a confirmation. REPOSITORY R120

D27077: [RFC] [Logout screen] Shorten timeout to 10 seconds

ngraham added a comment. In D27077#604428 , @cfeck wrote: > But the timeout isn't used to give apps more time needed to clean up before they confirm the session can be closed? If I understand it correctly, there should be two timeouts?

D27077: [RFC] [Logout screen] Shorten timeout to 10 seconds

cfeck added a comment. But the timeout isn't used to give apps more time needed to clean up before they confirm the session can be closed? If I understand it correctly, there should be two timeouts? REPOSITORY R120 Plasma Workspace REVISION DETAIL https://phabricator.kde.org/D27077

D27077: [RFC] [Logout screen] Shorten timeout to 10 seconds

davidedmundson added a comment. The (broken) rationale is you can just bash the power button and walk away. Useful if you have a large lab of machines or something. In practice apps can then block logout afterwards. (And probably it's there because windows at the time worked like

D27077: [RFC] [Logout screen] Shorten timeout to 10 seconds

cfeck added a comment. Why is there a timeout at all? REPOSITORY R120 Plasma Workspace REVISION DETAIL https://phabricator.kde.org/D27077 To: ngraham, #vdg, #plasma Cc: cfeck, davidedmundson, plasma-devel, Orage, LeGast00n, The-Feren-OS-Dev, jraleigh, zachus, fbampaloukas, GB_2,

D27077: [RFC] [Logout screen] Shorten timeout to 10 seconds

davidedmundson added a comment. It's meant as a confirmation screen as it's a destructive action, which a user would confirm. No one is meant to be sitting around waiting for the timeout so I don't see a compelling reason to make it shorter. None of the bug reports have a good reason

D27077: [RFC] [Logout screen] Shorten timeout to 10 seconds

ngraham created this revision. ngraham added reviewers: VDG, Plasma. Herald added a project: Plasma. Herald added a subscriber: plasma-devel. ngraham requested review of this revision. REVISION SUMMARY A lot of people seem to think the 30-second timeout is way too long; See Bug 253405 and