Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 940581 - x11-misc/xss-lock: SIGHUP causes exit rather than screensaver reset
Summary: x11-misc/xss-lock: SIGHUP causes exit rather than screensaver reset
Status: UNCONFIRMED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All Linux
: Normal normal
Assignee: No maintainer - Look at https://wiki.gentoo.org/wiki/Project:Proxy_Maintainers if you want to take care of it
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-10-01 06:59 UTC by Stefan Huber
Modified: 2024-10-01 16:52 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Stefan Huber 2024-10-01 06:59:43 UTC 
The man page of xss-lock lies about the behavior of SIGHUP, which is supposed to reset the screensaver.

However, since 2014, commit 2627bce2, it does something different:

    g_unix_signal_add(SIGTERM, (GSourceFunc)exit_service, loop);
    g_unix_signal_add(SIGINT,  (GSourceFunc)exit_service, loop);
    g_unix_signal_add(SIGHUP,  (GSourceFunc)exit_service, loop);

So SIGUP became equivalent to SIGTERM some 10 years ago.

This commit supposed to fix xss-lock issue #6:
https://bitbucket.org/raymonad/xss-lock/issues/6/hang-high-cpu-on-session-exit


I filed a issue upstream, but since xss-lock was not changed for 10 years, Gentoo might supply a quick fix in the man page:
https://bitbucket.org/raymonad/xss-lock/issues/208/sighup-causes-exit-rather-than-screensaver