Thats exactly my problem. I've answered Musee, but i dont answered to the mailing list to therefore i append my answer to musee here:
Thanks =) And woah what a quick reply! i tried it and the problem persists. But there is an error, that could help: The XKEYBOARD keymap compiler (xkbcomp) reports: > warning: Type "ONE_LEVEL" has 1 levels, but <RALT> has 2 symbols > Ignoring extra symbols Errors from xkbcomp are not fatal to the X server so is it the Xserver after all? i've cleared the slim.log and logged in twice for you to see the difference, there isnt any, im afraid. at the second login, it runs perfectly. -> http://pastebin.com/fzscDaCH . I hope it helps =) .xinitrc looks pretty much naked. I didnt do mutch tweaking after all, because im quite a noobie in this linux thing :D http://pastebin.com/YgNsyMkr <- maybe i missed somehting essential? thanks for your help! kindest regards, Jonas p.s. first time using a maling list =X 2012/5/27 Wayne Werner <waynejwer...@gmail.com> > > On May 27, 2012 5:34 AM, "Jonas Dörken" <chieftr...@googlemail.com> wrote: > > > > Hihi awesome community =), > > > > im apologizing at the beginning for my bad english =( > > > > i have a problem with Awesome. It runs peferctly fine after i killed it > at the beginning, until then i wasnt able to "click" anything or use > commands. So i pkill Awesome, the Slimloginwindow pops back up, i log in > and it runs perfectly as it should. Theres no error or something, but i do > think it has to do with the keygrabber.lua but i dont now exactly why. I'm > using Slim as my login manager and i just exec awesome in the xinit. I'm > using archlinux at the moment, hope that helps! > > > > kindest regards, > > Jonas > > > > P.s. could it be a problem with the xserver? Therefore it would be a > topic for the archlinux mailinglist ... Hope that isnt the case and im > failing right now =D > > I don't think so. I have the same issue both back when I was using Ubuntu, > and now that I'm using Arch. I log in and I can usually launch one or two > apps. Then the mod4 key no longer has any effect. I've been lazily trying > to use xev to see if the whole key event is gone or if awesome is just not > responding. > > I keep forgetting, so I'm not sure. In any case it usually happens the > first time I startx. I have to manually switch to tty1 and ctrl-c my > xsession and then startx again. Then I have no problems. > > -Wayne >
