Red Hat Bugzilla – Bug 525395
Suspend button in logout dialog doesn't lock the screen
Last modified: 2011-11-14 14:39:22 EST
Description of problem:
Suspend button in Action Buttons on xfce-panel just suspends computer but it doesn't lock the screen. So everybody is able to use your laptop without password needs after this suspend via "Action Buttons" - screen wasn't locked.
If i close the cap of my laptop it will suspend and lock correctly (power manager is set for suspend after closing the cap).
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Click to icon "Quit" (Action Buttons)
2. Click to suspend
3. Close and open cap of your laptop or use functional key for wake
Suspend without locking screen
Suspend and after waking your screen is locked
$ rpm -q xfce4-panel
The action buttons in xfce4-panel only have "Logout" and "Lock Screen". You are talking about the logout dialog, right?
Probably yes. There are following buttons: "Log Out", "Restart", Shut Down", "Suspend" and "Hibernate" in this dialog.
Ok, thanks for the clarification. I will look at this after the weekend.
I took a look and it's way more complicated than I thought. Changes like this should be happening upstream, but the author of xfce4-session has no intentions to do so. Quote from http://bugzilla.xfce.org/show_bug.cgi?id=4805#c7:
"I'm going to reject this. xfce4-power-manager supports this already, and does a fine job. It's silly to duplicate this in more than one place. Conceptually, the session manager isn't the place for this anyway.
I'm planning on having xfce4-session's suspend/hibernate buttons (and possibly
shutdown/reboot as well) send those actions to the power manager if present, so
when that's done, the screen will lock appropriately."
Hope no one is disappointed now. Another quote, just to show how clear upstream is about this:
"My original assertion still stands: xfce4-session WILL NOT support locking the
screen after suspend. I've already explained why and I don't intend to rehash
*** Bug 587633 has been marked as a duplicate of this bug. ***