winkey.desktop superkey problem [Solved]

[colejv]

Edit:
Fix is

Code: Select all

rc-update del keymaps default; rc-update add keymaps boot

than reboot the computer


New install of 64bit 4.0 (and it has been excellent) so far.

So I thought I would play with compiz a bit, several of the compiz features use the superkey and this does not work in sabayon, in the past I have just remapped the key bindings in compiz but I figured there has to be a better way.So a couple of posts said to delete winkey.desktop from /home/<user>/.kde3.5/Autostart. I am not one to just delete things so I moved it from Autostart to my home folder and rebooted. Now hitting the superkey causes the system to drop out of X?, OK playing with compiz is not that important (my youngest has a habbit of walking over to my desk and hitting random keys), so I moved the file back and restarted. no luck it appears the superkey still causes the system to cycle through run levels.

below is from var/log/messages you can see me open up /var/log/messages after that I hit the key

Google leads me to beilive that "Unknown Key Released" is related to my Microsoft wireless keyboard and is not relavent to the problem.
I think that the only relavent entry here is "fbcondecor: console 5" but does anybody else have any ideas?

Code: Select all

Dec 26 15:30:01 main cron[12388]: (root) CMD (test -x /usr/sbin/run-crons && /usr/sbin/run-crons )
Dec 26 15:31:07 main [  382.336436] atkbd.c: Unknown key released (translated set 2, code 0x81 on isa0060/serio0).
Dec 26 15:31:07 main [  382.336447] atkbd.c: Use 'setkeycodes e001 <keycode>' to make it known.
Dec 26 15:31:09 main kdm: :0[10864]: pam_unix(kde:session): session opened for user joshuac by (uid=0)
Dec 26 15:31:23 main NetworkManager: <info>  Updating allowed wireless network lists.
Dec 26 15:31:23 main NetworkManager: <WARN>  nm_dbus_get_networks_cb(): error received: org.freedesktop.NetworkManagerInfo.NoNetworks - org.freedesktop.NetworkManagerInfo.NoNetworks.
Dec 26 15:31:41 main sudo:  joshuac : TTY=pts/0 ; PWD=/home/joshuac ; USER=root ; COMMAND=/usr/bin/less /var/log/messages
Dec 26 15:31:41 main sudo: pam_unix(sudo:session): session opened for user root by (uid=0)
Dec 26 15:31:41 main sudo: pam_unix(sudo:session): session closed for user root
Dec 26 15:32:07 main [  441.894062] atkbd.c: Unknown key released (translated set 2, code 0x81 on isa0060/serio0).
Dec 26 15:32:07 main [  441.894067] atkbd.c: Use 'setkeycodes e001 <keycode>' to make it known.
Dec 26 15:33:08 main [  503.315271] atkbd.c: Unknown key released (translated set 2, code 0x81 on isa0060/serio0).
Dec 26 15:33:08 main [  503.315276] atkbd.c: Use 'setkeycodes e001 <keycode>' to make it known.
Dec 26 15:34:08 main [  563.638777] atkbd.c: Unknown key released (translated set 2, code 0x81 on isa0060/serio0).
Dec 26 15:34:08 main [  563.638782] atkbd.c: Use 'setkeycodes e001 <keycode>' to make it known.
Dec 26 15:35:08 main [  623.409309] atkbd.c: Unknown key released (translated set 2, code 0x81 on isa0060/serio0).
Dec 26 15:35:08 main [  623.409314] atkbd.c: Use 'setkeycodes e001 <keycode>' to make it known.
Dec 26 15:36:08 main [  683.207322] atkbd.c: Unknown key released (translated set 2, code 0x81 on isa0060/serio0).
Dec 26 15:36:08 main [  683.207327] atkbd.c: Use 'setkeycodes e001 <keycode>' to make it known.
Dec 26 15:36:18 main [  692.756239] fbcondecor: console 5 using theme 'sabayon'
Dec 26 15:36:18 main [  692.774528] fbcondecor: switched decor state to 'on' on console 5
Dec 26 15:36:33 main login[12305]: pam_unix(login:session): session opened for user root by LOGIN(uid=0)
Dec 26 15:36:33 main login[12611]: ROOT LOGIN  on 'tty6'


[colejv]

OK well I have spent quite a bit of time (and at least ten reboots) trying to figure this out and come up with nothing,I tried turning of compiz,created xmodmapping's and still nothing, then I started testing other sessions and they all worked properly (log in as root,fluxbox,gnome) and finally kde/openbox and they all worked properly now I am logged back in as kde default and it is working properly

[pajamabama]

Did you get the super key to work? There is an issue with KDE and the compiz super key. I don't know if it applies to kde4 (i'm downloading SL4 now), but in 3.5 you have to select a (US or whatever is appropriate for your locale) keyboard layout in the KDE control center. KDE Control Center -> Reigonal & Accessibility -> Keyboard Layout then check 'Enable Keyboard Layouts'. Then the super button should work with compiz.

[colejv]

It was working, Apparently I hosed my system when I was trying to add a test user, I have never needed to add another user to sabayon, in freebsd I would have used "adduser testuser" and ran through the dialog imagine my suprise when there was no dialog in sabayon, so I figured there was probably a gui user tool and found "Users and Groups" ran through the adduser filling things in and clicked ok (as soon as I clicked ok it registered that the User ID was set at 0 by default) Surely it would not do that? but everything seemed fine So I posted the above and went about setting up my system, Later I opened a terminal and tryed to su "no user root" then I tryed to sudo "no password for user" at which point I decided it was just probably better to rebuild.

So now on the freshly rebuilt system I have left the winkey file alone (I don't really use those compiz features anyway), so imagine my suprise when I hit the superkey and it dropped into a maintenance prompt

I am thinking about digging up a ps2 keyboard to verify it is not my keyboard, and looking at whether or not kbfx is at fault (I had installed it both times)

[dagurasu]

I hosed my logins in exactly the same way. I've been adding users since slackware was just about all there was and I should know better than using some fancy gui for this, just was getting in the spirit of how user friendly sabayon seemed to be and got a little carried away. This is a serious bug though as it is exactly where you are lead to if you just type "user" on the kde search start menu search. I had a brand fresh install so rther than try to recover I just installed again(I wanted to partition diferently anyway), but as far as I could tell it wasn't as simple just removing the offending user from the password file or deleting the root users password and booting in single user mode... something was messed up a bit more than that.

This issue is probably worthy of it's own post.

Anyway, if anyone figures how to disable the windows key from switching to a VT i'm interested... not that I've speant any time fidling with it myself.

[colejv]

Glad to know I am not alone, I typed "user" as well and really should know better. Also I was thinking I was the only one having a problem with the superkey. Anyway my youngest has done it twice to me now by banging on the keyboard nothing like going to use the computer and having to restart. So I will be looking into it again

[colejv]

OK not that it makes any sense but for the second time It is working again this time all I did was log into a kde/openbox session hit the superkey then logout and log back into the default session.I am going to check if it survives a reboot

[Tanis Shadow]

Hi there,
I've got the same problem. Hitting the super key switches to the maintenance prompt. And the same happens when I use ALT+F1 (or F2 or F3 and so on).
Since I'm using Gnome I would normaly use ALT+F2 for the run application window but right now ....
I have searched for quite some time now but I haven't found a solution yet so if anything turns up it would be if some could post it here.
Tanis Shadow

[colejv]

ok it did not survive a reboot and logging directly into KDE/openbox did not work (superkey switched run level), logging into KDE then logging out then logging into kde/openbox then logging back into kde, resulted in the menu opening (this is the first time this install has done this) which is actually the expected behavior since I have left winkey.desktop alone wanting to avoid this mess. so when I log in now one of three things can happen when I press the superkey

1 The menu opens (This is what should happen)
2 Nothing but it will activate compiz features (this is ultimately what i would like)
3 Toggles run levels (This I don't want and this seems to be what happens everytime I restart)

So I am still looking

[Tanis Shadow]

I am looking into one option right now, namely disabling console switching altogether.
I found some hints stating that the option "Option "DontVTSwitch" "Off" " in the Section "ServerLayout" in xorg.conf is responsible for not being able to switch consoles
(http://forum.soft32.com/linux/gentoo-xo ... 31247.html see second post)

Haven't tried yet, I am still looking if I find something else.