Package: xlockmore Severity: important
Hi! I have tested this on etch and sid, with xlock running on i386 and amd64 and the xserver running on i386, and powerpc, always got the same result, whenever I run xlock over the net (with -remote wether it is through a ssh -X or directly to the port of the X server), xlock crashes in this way: $ xlock -remote -nolock -mode fzort X Error of failed request: BadAccess (attempt to access private resource denied) Major opcode of failed request: 144 (MIT-SHM) Minor opcode of failed request: 1 (X_ShmAttach) Serial number of failed request: 177 Current serial number in output stream: 178 If you had run xlock in lock mode, then you cannot get any new window opened. Maybe this problem is related or the same as the one descrived on #258891. This bug is a bit grave as if you are running in random mode and xlock chooses this mode then the session becomes open and no lock is done anymore, of course then no other window can be opened, but all the available windows become unlocked. I don't know what else to add, it seems very easy to replicate, you just have to run xlock on a machine and try to get it's output on another one. If you cannot replicate this just tell me and I'll try to come out with more data. Regards! -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
