Pressing the following keys in order leads to scroll lock led being turned on: 9 <space> m p If then I press Enter, the screen turns black and I can't do anything (didn't try sshing). Alt+SysRq S U B helps to reboot. I have a dvorak layout, so for the bug to be reproducible in qwerty you might have to press "9 <space> m r <enter>" If I login in terminal and startx, the bug isn't observed. Reproducible: Always Steps to Reproduce: 1. setup slim 2. login into X 3. press: 9 <space> m p enter (might be "9 <space> m r enter") 4. experience a hang I'm using x11-base/xorg-server-1.6.5-r1 WM: x11-wm/awesome-3.4.2
Created attachment 214762 [details] emerge --info
Hi, I grabbed slim-1.3.1-r4 and typed that sequence both before and after logging in, and nothing happened. > WM: x11-wm/awesome-3.4.2 I'm using fluxbox. Perhaps it's a problem with awesome, or buggy X drivers or something. Could you possibly try to reproduce it using another WM? It might help in narrowing down the possibilities. Thanks, Vincent.
(In reply to comment #2) > Hi, > > I grabbed slim-1.3.1-r4 and typed that sequence both before and after logging > in, and nothing happened. > > > WM: x11-wm/awesome-3.4.2 > > I'm using fluxbox. Perhaps it's a problem with awesome, or buggy X drivers or > something. Could you possibly try to reproduce it using another WM? It might > help in narrowing down the possibilities. > > Thanks, > Vincent. > Downgrade to awesome 3.3.4 solved the problem. I should change the offending application =)
Not reproduced in awesome-3.4.3 A weird bug.
removed 3.4.2 from portage tree. close.
it reappeared in 3.4.3, but I gave up slim, so I can't help you anymore.
(In reply to comment #6) > it reappeared in 3.4.3, but I gave up slim, so I can't help you anymore. > A bit of clarification, it is reproduced but with another key sequence which I was unable to memorize.
Suddenly, some idea has come into my head. Can you tell me, is it possible that this bug is somehow connected with the fact that the VT on which slim opens is used in inittab?
(In reply to comment #8) > Suddenly, some idea has come into my head. Can you tell me, is it possible that > this bug is somehow connected with the fact that the VT on which slim opens is > used in inittab? > I wonder why nobody tried to reproduce this/confirm my suspicions. I think I should close this, because after the config modifications is has never reproduced.
