On Thu, Mar 18, 2010 at 01:06:45PM +0100, Hannes wrote: > Sorry for my long silence. Since first reporting the problem, I've done > regular updates from the testing branch, of course. When I tried things > out again after reading Dimitry's suggestions today, this lead to some > interesting new developments: > > When I put scrotwm in my .xsession file and run startx, it works. > > Regularly, I'm using the Slim login manager for authentication and > session selection. Starting ScrotWM from there resulted in the > behaviour described earlier before. > > Now today, using the Slim login, it still seemed the same way (no > keybindings working), but I could switch to a VT. This was not possible > a few weeks ago. Switching back to X (even without doing anything on > the VT, not even logging in), ScrotWM keybindings suddenly work as > intended! > > So I assume part of the issue was simply caused by some temporary freak > bug in an underlying X package which has been fixed by now. What > remains is the weird behaviour when being run through a graphical login > manager.
I use xdm to manage my graphical logins, and I’ve encountered no problems so far; I’ve also tried starting a scrotwm session from GDM, both using the same .xsession file I use with xdm and selecting the appropriate session from the menu, and everything was still working. I will try starting scrotwm with startx and Slim too, just to be sure. It would be nice if you could try starting a scrotwm session from xdm, and also try the method outlined by Dimitry. Figuring out where the root of the problem lies isn’t easy, especially since I can’t reproduce the bug and Dimitry has outdated libraries on his box. Testing various configurations is just about the only thing to do, except for banging one’s head against the nearest wall. -- Andrea Bolognani <e...@kiyuko.org> Resistance is futile, you will be garbage collected.
signature.asc
Description: Digital signature
