Public bug reported:
Hi,
I'd like to use my Windows key as a Super key, and it seems to not be
set up for that in my dist. When I run xev, the Windows key is reported
as "Select". Same when I try to bind it in e.g. the Keyboard Shortcuts
dialog.
I've found some other bugs which seem to be simila
Here's the output of gconftool:
[EMAIL PROTECTED]:~$ gconftool-2 -R /desktop/gnome/peripherals/keyboard/kbd
layouts = []
model = generic
options = []
overrideSettings = true
--
Windows Key gets mapped as "Select" rather than "Super"
https://launchpad.net/bugs/67781
--
desktop-bugs mailing
I'm now sure how to find out what key is configured to gnome-window-
properties for the move action. When I run "gnome-window-properties" I
get a dialog saying "Window manager "beryl" has not registered a
configuration tool". (I'm running Beryl.)
--
Windows Key gets mapped as "Select" rather than
My apologies, I didn't realize the window manager would have an effect
on how the keyboard is interpreted. I will raise a bug with the Beryl
project as well.
I've turned off Beryl completely and after restarting gdm I get a
slightly improved behaviour:
xev now reports Super_L for the Windows key,
Ok, it turned out I had xserver-glx from Beryl installed. I've
uninstalled it and installed the Ubuntu xserver-glx and the keyboard
mapping is working better now, although I seem to have lost the keyboard
I had before. Is there any way to rerun the keyboard detection code
that's used when installin
Right, after purging and reinstalling all xserver packages and gdm, and
dpkg-reconfiguring the xserver, the keyboard mapping is working
properly.
Thanks for your help.
--
Windows Key gets mapped as "Select" rather than "Super"
https://launchpad.net/bugs/67781
--
desktop-bugs mailing list
deskt
