You are not logged in.
I'm having trouble with some keys in Awesome3. Some keys aren't detected: the most important keys that aren't detected are Print Screen and my multimedia keys, all of which work perfectly in Openbox.
Here are the output of showkey and xev in different WMs. In all these tests, I press the following keys:
asdf<Tab><Volume up><Volume down>
Openbox's xev output
$ xev | grep -A2 --line-buffered '^KeyRelease' | sed -n '/keycode /s/^.*keycode \([0-9]*\).* (.*, \(.*\)).*$/\1 \2/p'
38 a
39 s
40 d
41 f
23 Tab
123 XF86AudioRaiseVolume
122 XF86AudioLowerVolume
Awesome3's xev output
$ xev | grep -A2 --line-buffered '^KeyRelease' | sed -n '/keycode /s/^.*keycode \([0-9]*\).* (.*, \(.*\)).*$/\1 \2/p'
38 a
39 s
40 d
41 f
23 Tab
Notice how the last two keys don't show up.
Showkey in a real console
Using showkey in Awesome3 gives the same output.
$ showkey
kb mode was UNICODE
[ if you are trying this under X, it might not work
since the X server is also reading /dev/console ]
press any key (program terminates 10s after last keypress)...
keycode 28 release
keycode 30 press
keycode 30 release
keycode 31 press
keycode 31 release
keycode 32 press
keycode 32 release
keycode 33 press
keycode 33 release
keycode 15 press
keycode 15 release
keycode 115 press
keycode 115 release
keycode 114 press
keycode 114 release
dmesg doesn't outputs any error or scancode.
I searched the wiki for information, but I couldn't find anything that solved this problem, so I need help getting those keys to work in Awesome3.
Last edited by FunkNapkin (2009-07-14 14:45:10)
Arch64, Openbox & Awesome3
Offline
Awesome does not use keycodes any more. They just changed that in the last point release. Exciting, huh?
I now use:
awful.key({}, "#121", function () awful.util.spawn_with_shell('amixer sset PCM toggle') end),
for mute toggle. Volume down is #122, volume up is #123.
Offline
Awesome does not use keycodes any more. They just changed that in the last point release. Exciting, huh?
Great...
I'll modify my rc.lua with the numbers. I'm guessing I use the numbers provided by Showkey, or do I need the numbers Openbox's xev gives?
Edit: It's a good thing I have openbox installed, I need these numbers. It's solved now, thanks for your help!:)
Last edited by FunkNapkin (2009-07-13 21:38:31)
Arch64, Openbox & Awesome3
Offline
I'll modify my rc.lua with the numbers. I'm guessing I use the numbers provided by Showkey, or do I need the numbers Openbox's xev gives?
I think xev is not related to Openbox at all, but to X server
Offline
FunkNapkin wrote:I'll modify my rc.lua with the numbers. I'm guessing I use the numbers provided by Showkey, or do I need the numbers Openbox's xev gives?
I think xev is not related to Openbox at all, but to X server
Xev doesn't detect some keys when used in Awesome. Because of that, I had to use another WM to find the numbers needed in the rc.lua, and Openbox is already installed. AFAIK, it could've been any WM except Awesome.
Hope that clarifies what I said in my previous posts. But the problem is solved now, so everything's good for me.
Arch64, Openbox & Awesome3
Offline
It seems that after a reboot, my multimedia keys aren't working anymore. Here's a section of my rc.lua, to see if there's something wrong with it:
-- Shortcuts for multimedia keyboard and Print Screen
awful.key({ }, "#122", function () awesome.util.spawn("ossvol -d 1") end),
awful.key({ }, "#123", function () awesome.util.spawn("ossvol -i 1") end),
awful.key({ }, "#121", function () awesome.util.spawn("ossvol -t") end),
--awful.key({ }, "#150", function () awesome.util.spawn("sudo pm-suspend") end),
awful.key({ }, "#107", function () awesome.util.spawn("scrot -q 100 -e 'mv $f ~/screenshots/ 2>/dev/null'") end),
awful.key({ }, "#172", function () awesome.util.spawn("mpc toggle") end),
awful.key({ }, "#174", function () awesome.util.spawn("mpc stop") end),
awful.key({ }, "#171", function () awesome.util.spawn("mpc next") end),
awful.key({ }, "#173", function () awesome.util.spawn("mpc prev") end)
Arch64, Openbox & Awesome3
Offline