https://bugs.kde.org/show_bug.cgi?id=372197
--- Comment #10 from Stefan Brüns <stefan.bru...@rwth-aachen.de> --- Although I agree its not a bug in kscreenlocker, I still have two remarks: 1. kscreenlocker_greet is hard to debug, as it immediate turns of ptrac'ing, and only allows it late during the initialization if '--testing' is set. Imho it would be better to only disable ptrace right before app.exec(). I think from a security standpoint this would be fine as well, but allowed catching errors during initilization. Relevant greeter code: https://github.com/KDE/kscreenlocker/blob/42ad07d79785e51641f97f7d20709fee6ab54060/greeter/main.cpp#L63 If you agree, I would prepare a patch. 2. stderr is not catched by the screen locker daemon. When starting kscreenlocker_greet manually, e.g.: $> XAUTHORITY=/home/stefan/.Xauthority_ /usr/lib64/libexec/kscreenlocker_greet --testing No protocol specified QXcbConnection: Could not connect to display :0 Abgebrochen , there is a somewhat helpful error message ("No protocol specified" points clearly to xauth problems). -- You are receiving this mail because: You are watching all bug changes.
