Bug 104349 - xdg-screensaver: bad xautolock invocation for reset action
Summary: xdg-screensaver: bad xautolock invocation for reset action
Status: RESOLVED MOVED
Alias: None
Product: Portland
Classification: Unclassified
Component: xdg-utils (show other bugs)
Version: unspecified
Hardware: All Linux (All)
: medium normal
Assignee: Portland Bugs
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-12-20 13:55 UTC by François Charlier
Modified: 2019-02-16 13:39 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description François Charlier 2017-12-20 13:55:19 UTC
xdg-screensaver invokes a xautolock with a wrong parameter for the reset action.

Currently it executes: "xautolock -restart"

To do what the manpage says, it should instead execute: "xautolock -unlocknow"

Calling with '-restart' causes some issues where xautolock will not work correctly after the call.



- From xdg-screensaver manpage:

       reset          Turns the screensaver off immediately. If the screen was locked the user may be asked to authenticate first.



- From xautolock manpage:

       -restart        Causes an already running xautolock process (if there is one and it does not have -secure switched on) to restart.

       -unlocknow      Causes  an already running xautolock process (if there is one, if it does not have -secure switched on, and is not currently disabled) to unlock the display immediately (if it's locked) by sending the locker a SIGTERM signal.
Comment 1 GitLab Migration User 2019-02-16 13:39:42 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/xdg/xdg-utils/issues/120.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.