[Intrepid]: screen not locked after resume

On Mon, 2009-02-02 at 14:35 +0000, Gerd Bavendiek wrote:
> Public bug reported:
>
> Binary package hint: pm-utils
>
> Hi,
>
> after resume pm-utils on Intrepid
>
> lulu:/home/bav> dpkg -l | grep pm-utils
> ii pm-utils 1.1.2.4-1ubuntu8 utilities and scripts for power management
>
> do not lock the screen. This way everyone has immediately access to my
> desktop. Think of ~/Private, which is unencrypted after resume !!!
>
> There is /etc/acpi/resume.d/90-xscreensaver.sh, but I did not find such
> a script in pm-utils. For the time being I hacked my own version, but I
> really think this should be addressed.
>
> I'm running xfce, if that makes any difference.
>
> BTW, 90-xscreensaver.sh does not care about gnome-screensaver.
>
> Gerd
>
> ** Affects: pm-utils (Ubuntu)
> Importance: Undecided
> Status: New
>
In GNOME, gnome-power-manager takes care of locking the screen using
gnome-screenshot before calling pm-utils. If I'm not mistaken, it's the
same in the case of XFCE. Perhaps it's a misconfiguration on your part?
Please try with a clean home directory (perhaps temporarily create a new
user), and see if it works.

Either way, since pm-utils isn't what takes care of locking the screen,
I'm marking the pm-utils bug as invalid.

  affects ubuntu/pm-utils
  status invalid

  affects ubuntu/gnome-power-manager
  status new
--
Chow Loong Jin

hyperair,

thanks for responding.

As you suggested, I tried using a "fresh" user - but nothing changed.

I than found bug #42052, a very old bug, which seems to be still alive in Intrepid - at least for xfce-users.

Citing from https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/42052

Jarno Suni wrote on 2008-12-16:

...
In Xfce4:
Additionally choose Power Management in Screensaver preferences and choose a way to suspend/hibernate.
You can not use the "Ask me" option in Power Management preferences like above (or you can, but it doesn't lock screen when you resume). Then use that way to suspend/hibernate. In summary: whenever you suspend/hibernate using the Quit dialog, screen will not be locked.

So from my point of view this is true.

So for the time being adding a script to /etc/pm/sleep.d is at least a solution for a real problem. It works for me
and my data is safe now.

If you give me further hints how to debug I'd really like to help to find the root cause though !

Thanks

Gerd

On Tue, 2009-02-03 at 20:19 +0000, Gerd Bavendiek wrote:
> hyperair,
>
> thanks for responding.
>
> As you suggested, I tried using a "fresh" user - but nothing changed.
>
> I than found bug #42052, a very old bug, which seems to be still alive
> in Intrepid - at least for xfce-users.
>
> Citing from https://bugs.launchpad.net/ubuntu/+source/gnome-power-
> manager/+bug/42052
>
> Jarno Suni wrote on 2008-12-16:
>
> ...
> In Xfce4:
> Additionally choose Power Management in Screensaver preferences and choose a way to suspend/hibernate.
> You can not use the "Ask me" option in Power Management preferences like above (or you can, but it doesn't lock screen when you resume). Then use that way to suspend/hibernate. In summary: whenever you suspend/hibernate using the Quit dialog, screen will not be locked.
>
>
> So from my point of view this is true.
>
> So for the time being adding a script to /etc/pm/sleep.d is at least a solution for a real problem. It works for me
> and my data is safe now.
>
> If you give me further hints how to debug I'd really like to help to
> find the root cause though !
>
> Thanks
>
> Gerd
>
In that case does setting "When the suspend button is pressed" to
"Suspend" make it lock screen? By the way, the screen locking is done
before the suspend/hibernate process and not after.

For debugging instructions, do the same as in this post and attach the
resulting file:
https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/42052/comments/4

Also, may I see the script you're using in /etc/pm/sleep.d?
--
Chow Loong Jin

hyperair wrote:
> On Tue, 2009-02-03 at 20:19 +0000, Gerd Bavendiek wrote:
...
> In that case does setting "When the suspend button is pressed" to
> "Suspend" make it lock screen? By the way, the screen locking is done
> before the suspend/hibernate process and not after.

Sorry, I do not know where to set this. I did not find it in
gnome-screensaver-preferences nor in gnome-power-preferences.

I installed Jaunty for test purposes (this time using Gnome desktop, not
XFCE). Triggering suspend I can see gnome-screensaver being switched on
before suspending as you stated. Unfortunately resuming in Jaunty does
not work for me, but this is another story ...

>
> For debugging instructions, do the same as in this post and attach the
> resulting file:
> https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/42052/comments/4
>
> Also, may I see the script you're using in /etc/pm/sleep.d?

I'd prefer PM for this.

Kind regards

Gerd

--
------------------------------------------------------------------------
Gerd Bavendiek Linux Users check out:
<email address hidden> http://linos.wordpress.com
------------------------------------------------------------------------

On Fri, 2009-02-06 at 11:49 +0000, Gerd Bavendiek wrote:
> hyperair wrote:
> > On Tue, 2009-02-03 at 20:19 +0000, Gerd Bavendiek wrote:
> ...
> > In that case does setting "When the suspend button is pressed" to
> > "Suspend" make it lock screen? By the way, the screen locking is done
> > before the suspend/hibernate process and not after.
>
> Sorry, I do not know where to set this. I did not find it in
> gnome-screensaver-preferences nor in gnome-power-preferences.
It's in gnome-power-preferences. See the attached screenshot for
reference.
>
> I installed Jaunty for test purposes (this time using Gnome desktop, not
> XFCE). Triggering suspend I can see gnome-screensaver being switched on
> before suspending as you stated. Unfortunately resuming in Jaunty does
> not work for me, but this is another story ...
>
> >
> > For debugging instructions, do the same as in this post and attach the
> > resulting file:
> > https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/42052/comments/4
> >
> > Also, may I see the script you're using in /etc/pm/sleep.d?
>
> I'd prefer PM for this.
Then E-mail it to me.
--
Chow Loong Jin

hyperair wrote:
> On Fri, 2009-02-06 at 11:49 +0000, Gerd Bavendiek wrote:
>> hyperair wrote:
>>> On Tue, 2009-02-03 at 20:19 +0000, Gerd Bavendiek wrote:
>> ...
>>> In that case does setting "When the suspend button is pressed" to
>>> "Suspend" make it lock screen? By the way, the screen locking is done
>>> before the suspend/hibernate process and not after.
>> Sorry, I do not know where to set this. I did not find it in
>> gnome-screensaver-preferences nor in gnome-power-preferences.
> It's in gnome-power-preferences. See the attached screenshot for
> reference.

Sorry, I misunderstood your hint.

There is no difference between our configurations. If an xfce-user uses
the Quit-dialog, the screen will not be locked (this is what Jarno Suni
stated in #42052). If I change the action for power-button-is-pressed
from xfce-quit to suspend gnome-screensaver is run immediately (I have
no suspend button).

So you are right: pm-utils works fine.

My script is just a workaround to a bug in xfce (?) ...

Thanks for your time !

Gerd

--
------------------------------------------------------------------------
Gerd Bavendiek Linux Users check out:
<email address hidden> http://linos.wordpress.com
------------------------------------------------------------------------

Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering is this still an issue for you? Could you try to reproduce the same with Ubuntu 9.04? Thanks in advance.

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!