http://qa.mandrakesoft.com/show_bug.cgi?id=1747
------- Additional Comments From [EMAIL PROTECTED] 2003-03-05 02:43 ------- >> Fix this bug with new version xlockmore-5.06-1mdk. The problem is that the current package in cooker is xlockmore-5.04-4mdk not 5.06-1.. so to be correct this bug entry should still be opened until the new package is uploaded.. ? Thanks. Have a nice day, Fabrice. ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is. ------- Reminder: ------- assigned_to: [EMAIL PROTECTED] status: RESOLVED creation_date: description: Hello, I run xlock as: $ /usr/bin/xlock -mode blank -sound -locksound \ /usr/share/sounds/xlockmore/thank-you.au -infosound \ usr/share/sounds/xlockmore/identify-please.au -validsound \ /usr/share/sounds/xlockmore/complete.au -invalidsound \ /usr/share/sounds/xlockmore/not-programmed.au (all in one line without the backslashes...) and when I enter an incorrect passwd, my xlock hang there. I know when your passwd is incorrect, it will make you wait some time to discourage you of brute forcing it, but in this case it's way way too long (it basically hang). On the other hand, when I enter my password correctly, it does work fine! If I go into text console ALT+CTRL+F1, and come back to X, then xlock doesn't even redraw the display. a # strace -p PID_OF_XLOCK shows nothing at all, and a ps indicate that xlock in not in uninterruptible mode.. so I have no cule what's wrong ! I call xlock this way everyday for a few months, and only the last few days this started to happen :( I use all the latest cooker packages. Anybody's got a clue of what's wrong ? (with xlock or with me ;-) ? ) Have a nice day.
