Hi, Brandon! I rebooted the computer hoping that it'll cure the problem, but it did not. But when I ran xlock from the terminal, that's what I get:
$ xlock & [1] 766 $ X Error of failed request: BadMatch (invalid parameter attributes) Major opcode of failed request: 78 (X_CreateColormap) Serial number of failed request: 309724 Current serial number in output stream: 309731 [1]+ Exit 1 xlock $ echo $? 0 Is this iinformation useful? What would you say, should I contact the package maintainer? Thank you, Sasha. > On Wed, 25 Feb 1998, Alexander Kushnirenko wrote: > > > I got strange behaviour of xlock after recent updates of hamm. I lock the > > terminal in the night, everything looks fine, there is a password prompt > > and > > screensaver running. But when I come back in the morning screen is > > unlocked. > > Also for some reason the list of authorised nodes, which I setup with xhost > > command is cleared. > > Sounds like a seg fault/core dump. Next time, run it from a command line, > look at the return value (echo $? in bash). I think there are some bugs > in the libc6 (well I guess there are always bugs), which periodically > causes problems. But all in all, I think it's pretty stable. > > Good luck, > Brandon > > ----- > Brandon Mitchell <[EMAIL PROTECTED]> "We all know linux is great... it > PGP: finger -l [EMAIL PROTECTED] does infinite loops in 5 seconds" > Phone: (757) 221-4847 --Linus Torvalds > > > -- > TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to > [EMAIL PROTECTED] . > Trouble? e-mail to [EMAIL PROTECTED] . -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .