Xlock occasionally dies with dual-head setup

[Edward Schwartz]

Binary package hint: xlockmore

I have a dual-monitor X setup. If I run xlock for a long time, sometimes when I come back it is not running anymore. Since I use xlock to lock my screen, this is a problem!

I have not tried to narrow this down to a single screensaver yet.

This is in Xlockmore version 5.27-1, Ubuntu 9.10

ProblemType: Bug
Architecture: i386
Date: Mon Dec 7 13:20:46 2009
DistroRelease: Ubuntu 9.10
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
NonfreeKernelModules: openafs wl nvidia
Package: xlockmore-gl 1:5.27-1
ProcEnviron:
 PATH=(custom, user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-15.50-generic
SourcePackage: xlockmore
Uname: Linux 2.6.31-15-generic i686

[Edward Schwartz (moo-launchpad-z-edmcman)]

Still a problem in 11.04. Maybe it's time to confirm this as a bug?

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Sorin CONSTANTINESCU (consta)]

Hello,

I have the same type of issue in Ubuntu 12.04. Can we get some help on how to troubleshoot this more? I can see in auth.log that xlock starts, but doesn't log the Stop action sometimes, which is when I find it not running.

Thanks!

//Sorin

[Sorin CONSTANTINESCU (consta)]

Could someone flag this as a security issue?

[MMlosh (mmlosh)]

I just got mail that xlockmore will be purged in the next debian release.
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=690891

The reasons aren't detailed, I found only those:

There is one serious bug: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=472076
But it doesn't really state WHAT should be fixed.

and one marked as CVE: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=318123
That xlock doesn't seem to work with smartcards or something?

And then a few for-years running bugs, which don't seem hard to fix.
Like not being to able to use it with dpms disabled, because someone succeded with a patch that adds forced dpms off, ignoring all DPMS-related parameters, but running for 3 years ago, unresolved.