FS#42825 - [xlockmore] xlock quits unexpectedly leaving the screen unlocked

Attached to Project: Community Packages
Opened by David Costa (zarel) - Monday, 17 November 2014, 23:10 GMT
Last edited by Sergej Pupykin (sergej) - Wednesday, 19 November 2014, 12:11 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Sergej Pupykin (sergej)
Architecture All
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
when I launch "xlock -mode pyro2" it keeps complaining about a missing font for a while, then it quits with an error related to X. This is a security problem indeed because it maked the computer unlocked while it is unattended (it quits after several seconds).

I found also that calling xlock "in window" quits immediately, as before only with mode pyro2.

Additional info:
* xlockmore 5.43-2

Steps to reproduce:
launch "xlock -inwindow -mode pyro2" without having the '-*-helvetica-bold-r-*-240-*' font installed. It will crash immediately with this output:

xlock: can not find font: -b&h-lucida-medium-r-normal-sans-24-*-*-*-*-*-iso8859-1, using fixed...
can not find font '-*-helvetica-bold-r-*-240-*'
X Error of failed request: BadAccess (attempt to access private resource denied)
Major opcode of failed request: 88 (X_FreeColors)
Serial number of failed request: 413
Current serial number in output stream: 415

Any other mode will work, except random, which will eventually try to launch pyro2.
Running it fullscreen (i.e. "xlock -mode pyro2") results in the same output but the line
"can not find font: '-*-helvetica-bold-r-*-240-*'" is repeated many times.
This task depends upon

Closed by  Sergej Pupykin (sergej)
Wednesday, 19 November 2014, 12:11 GMT
Reason for closing:  Fixed
Comment by Sergej Pupykin (sergej) - Tuesday, 18 November 2014, 17:44 GMT
I think you should pass -fnt to xlock if you have not installed default font. Not sure how to fix it in deps. I think I just can add post install message about fonts.
Comment by David Costa (zarel) - Tuesday, 18 November 2014, 21:39 GMT
as a temporary measure until it's fixed upstream a post install would do it (IMHO). I'm going to report it to the developer via mail.

Loading...