|Summary:||xdg-screensaver: bad xautolock invocation for reset action|
|Product:||Portland||Reporter:||François Charlier <fcharlier>|
|Component:||xdg-utils||Assignee:||Portland Bugs <portland-bugs>|
|Status:||RESOLVED MOVED||QA Contact:|
|i915 platform:||i915 features:|
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.