On Thu, Jun 14 2012, Roland Hieber wrote: > I usually start awesome through startx on tty1, by the command line > > $ startx & vlock > > I can normally use awesome, but when I switch back to tty1, where vlock runs > in > foreground, and press enter (to see the password prompt again), then switch > back > to X, the awesome status bar vanishes and awesome no longer reacts to user > input. The only way to get it working again is kill awesome (or X) and restart > it. (Note that this behaviour also occurs if I run startx in foreground > without > vlock, and then press enter and switch back to X, so I guess vlock is not to > blame here.) When I attach gdb to the awesome process, I see that awesome > gets a > SIGTTIN in that case, and stops, leaving me on the gdb prompt. > > The problem also persists when I rename my rc.lua, so the default config is > loaded. I have also stripped down my .xinitrc to a minimal example that > triggers the bug, and it now only consists of the line > > exec ck-launch-session dbus-launch --sh-syntax --exit-with-session awesome
I don't think vlock is to blame neither. But I don't think it's an
awesome issue too. I think it's an X problem. Could you try with another
window manager?
--
Julien
pgpwFYN74ln0s.pgp
Description: PGP signature
