Launchpad has imported 6 comments from the remote bug at
https://bugzilla.xfce.org/show_bug.cgi?id=9030.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.

------------------------------------------------------------------------
On 2012-06-16T06:38:52+00:00 scar wrote:

I've marked this bug major, as it causes a user-defined security
setting's failure.

I've a full xfce install on Arch Linux, and I've noticed the following:

In xfce4-power-managers settings I've checked the lock screen after
resume fom sleep/hibernate option, and when I hibernate or suspend from
the power managers tray  icon, it follows my settings.

However, I think the REAL way of quitting your desktop is by design,
tradition, logic and whatever, is by the xfce4-session-logout dialog.
And this one DOES NOT RESPECT the power managers settings. So, on a
laptop, if I suspend it, everyone can resume and use my machine without
any password checking. I think this is a really serious issue.

Tested: GUI (suspend/hibernate) xfce4-session-logout
        CLI xfce4-session-logout ( with --suspend and --hibernate options)

Does not work.

So there's an inconsistency between the two utilities, and I thionk, because 
Xfce is a Desktop Environment, its elements should respect each others settings.
And I think the one that has to be modified is Xfce-session-logout, because the 
power manager works correctly.

package: xfce4-session 4.10.0-3

Reply at:
https://bugs.launchpad.net/xfce4-session/+bug/1101982/comments/0

------------------------------------------------------------------------
On 2012-06-16T12:03:50+00:00 Yves-Alexis Perez wrote:

Did you try “lock screen before sleep” in the last tab of xfce4-session
settings?

Reply at:
https://bugs.launchpad.net/xfce4-session/+bug/1101982/comments/1

------------------------------------------------------------------------
On 2012-06-16T22:10:32+00:00 scar wrote:

Thank you, it did the trick.
Sorry for lamenting.

Reply at:
https://bugs.launchpad.net/xfce4-session/+bug/1101982/comments/2

------------------------------------------------------------------------
On 2012-06-17T08:23:36+00:00 Yves-Alexis Perez wrote:

No problem. I'm retitling and adjusting severity. I think there might
already be a bug for the same thing, which I think is planner (or even
already fixed) for 4.12

Reply at:
https://bugs.launchpad.net/xfce4-session/+bug/1101982/comments/3

------------------------------------------------------------------------
On 2014-01-04T00:06:37+00:00 Jarno Suni wrote:

As for inconsistency, they use different methods for launching suspend
and hibernate: you can notice that, if you have lock-on-sleep unchecked
for both, and use gnome-screensaver daemon or light-locker: if you
suspend by xfce4-session, it will lock, but not if you suspend by xfce4
-power-manager.

Reply at:
https://bugs.launchpad.net/xfce4-session/+bug/1101982/comments/7

------------------------------------------------------------------------
On 2014-06-03T01:44:50+00:00 Chris Bainbridge wrote:

This issue is already fixed in xfce4-power-manager 
according to https://bugs.launchpad.net/xfce4-session/+bug/1101982 and 
http://git.xfce.org/xfce/xfce4-power-manager/commit/?id=bed10b8068d549bf0dd59542c90dec9f6b576e64

Reply at:
https://bugs.launchpad.net/xfce4-session/+bug/1101982/comments/12


** Changed in: xfce4-session
       Status: Unknown => Confirmed

** Changed in: xfce4-session
   Importance: Unknown => Wishlist

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1101982

Title:
  inconsistent settings for lock screen between xfce4-session and xfce4
  -power-manager

To manage notifications about this bug go to:
https://bugs.launchpad.net/xfce4-power-manager/+bug/1101982/+subscriptions

-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to