Bug 184663

Summary:	"suspend to xxx" should have real buttons within "leave window"
Product:	[Unmaintained] ksmserver	Reporter:	Ed Guenthner <edgue>
Component:	ui	Assignee:	Lubos Lunak <l.lunak>
Status:	RESOLVED FIXED
Severity:	wishlist	CC:	alex.danila.web, korossy, nate, olly
Priority:	NOR
Version:	unspecified
Target Milestone:	---
Platform:	Ubuntu
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Ed Guenthner 2009-02-17 15:16:58 UTC

Version:            (using KDE 4.2.0)
OS:                Linux
Installed from:    Ubuntu Packages

When using the "leave" menu option or the "logout" widget, KDE presents a window with three choices: logout, "turn off" and "restart". 

On top of the "turn off" button one can find a small pull-down triangle that can be used to NOT turn off the computer but to suspend to ram/disk. 

It happened several times to me, that I missed to "pull down" the right way. 
So instead of suspend-to-ram I selected "turn off". 
But these are two really different actions with really different consequences! 
They SHOULD NOT be "that close" UI wise. 

Sometimes people act in a hurry - a user interface should be forgiving ... and not using a "worst case" choice as default. 

You see, when I want to "suspend to ram" i have many programs running. I really dont want to shutdown!

xfce and gnome provide different buttons for these actions. You say "quit" and you have a set of buttons that are clearly seperated. Why is KDE different here?

A minimum requirement would be to have this CONFIGURABLE!

Comment 1 Funkster 2009-05-18 12:41:48 UTC

I'm surprised that so few people have complained about this, the current setup is bound to cause pain and anguish world wide!

Separate buttons definitely required.

Comment 2 Oswald Buddenhagen 2009-06-01 13:43:26 UTC

*** Bug 194851 has been marked as a duplicate of this bug. ***

Comment 3 Lubos Lunak 2009-11-23 20:05:31 UTC

*** Bug 197164 has been marked as a duplicate of this bug. ***

Comment 4 Daniel Morris 2017-01-06 11:43:59 UTC

This has been fixed for a long time with Plasma5 and should be closed

Comment 5 Nate Graham 2020-01-31 18:34:14 UTC

Yeah, this is fixed now.