[SOLVED] Fluxbox keys magic

What I'd like to do seems a little complicated. I've got a laptop here and no USB mouse, and for some games (Most notably Minecraft), I'd like to bind a letter to the right mouse button because using the button on this cheap trackpad is awkward.
It seems I can get what I want just using fluxbox keys, but I'm not sure. I'd like to bind an unused key to execute a script that comments/uncomments another line in keys that binds a letter to right mouse clicks. I'm not quite sure if that's possible, though. Also, I'm relatively new to unix-like OS's so I'm not sure how to implement the script. I'm capable of reading man pages, but if someone could point me to the right direction I'd appreciate it; what utilities are best for this job?
Last edited by Bellum (2011-09-09 08:39:50)

Well, I tried using keymodes but ended up disabling all the default keys. Probably just an error on my part, but I've come up with an alternative solution. It's not as clean, but I just have two keys files and a keybinding to activate a script that switches between the two. Consider my original idea. After giving a cursory glance at sed, it's amazing how quickly I came up with a solution to avoid it. xD
This is solved, anyway. Here is my solution:
keys
Control 163 :MacroCmd {Exec ~/.fluxbox/scripts/keyToMouse.sh} {reconfig}
#None f :ExecCommand xdotool click 3
keys.two
Control 163 :MacroCmd {Exec ~/.fluxbox/scripts/keyToMouse.sh} {reconfig}
None f :ExecCommand xdotool click 3
keyToMouse.sh
#!/bin/bash
mv ~/.fluxbox/keys.two ~/.fluxbox/k
mv ~/.fluxbox/keys ~/.fluxbox/keys.two
mv ~/.fluxbox/k ~/.fluxbox/keys
After all that, I guess it ended up being pretty straightforward.

Similar Messages

[SOLVED] fluxbox middle click to group tabs doesnt work[solved]

I remember that a while ago when I installed fluxbox thatmiddle clicking the titlebar and dragging it to another window will group them together, but this does'nt happen anymore... I've tried every possible combination with the mouse and I can't get them to group together. I even installed and uninstall and built fluxbox from source from scratch. I can't find any documentation that says something changed. What happended? Any input on this will be greatly appreciated.
EDIT: mods feel free to delete this thread ctrl and left click works.
Last edited by aluser (2011-05-07 23:31:54)

My system works as you describe (middle click titlebar and drag). I believe this functionality is controlled by your ~/.fluxbox/keys file. In my 'keys' file, I have the following line.
OnTitlebar Mouse2 :StartTabbing
Perhaps your 'keys' file has changed.

Fluxbox/keys - two command using one combination of keyboard keys

I want to run 2 commands using pressing alt+v, it should be done using this command in fluxbox keys:
Mod1 V :MacroCmd {gksudo pon vpn-doma} {gksudo sh /home/r-c/.vpn-doma-routy}
but this doesnt work. I want to first execute this command: gksudo pon vpn-doma and after executing this: gksudo sh /home/r-c/.vpn-doma-routy
When I execute it separately in terminal, it works. ALso I restarted fluxbox enviroment. Can you help?

Are you now using a macro with {exec <command 1>} {exec <command 2>} ?
That may start them at the same time, but in the command I put above, the second command should not start until the first is complete (and returns true/success).
You could add delay, if needed, as follows
gksudo pon vpn-doma && sleep 1 && gksudo sh /home/r-c/.vpn-doma-routy
Edit: specifically
Mod1 V :exec "gksudo pon vpn-doma && gksudo sh /home/r-c/.vpn-doma-routy"
Ditch the macro, it should not be needed.
Last edited by Trilby (2012-03-25 15:45:21)

[SOLVED] Function Keys Problem On Dell Inspiron N5010

Yesterday I bought a new laptop (Dell Inspiron N5010) and immediately installed Arch Linux on it. But when I launched the installation framework, I needed to use fdisk to partition my drive manually and to open another tty, ctrl + alt + f2 or up to f7, none of them worked. When I use f4 or f5 for example, it changes the brightness of the screen cause these keys have icons on them which represent the brightness control. So I quitted, took care of that fdisk issue and got back, installed Arch Linux successfully. When launched in GNOME 3, nothing was changed. It still uses f1, f2, ... and so on as "just function keys" without using "Fn" key. It's fine somehow cause my system automatically detected those keys, I can use every single function of my keyboard. But without using Fn key, I can't actually use any fx key for my own use. For example, I can't use Tilda anymore cause when I use only f1, it tries to open monitor control stuff.
So... any ideas?
Edit: It seems that this problem is all about Arch Linux. A friend of mine has the same laptop and he has just tried Mint Debian RC and function keys worked properly. So, there's a problem and it seems it's related to Arch Linux (or maybe Xorg version, somehow?).
Last edited by Jeaquares (2011-05-18 13:07:06)

xdunlapx wrote:The function key on my dell laptop was set to the F keys, meaning you have to hit the function key and then an F key to activate the F key. I switched it in the bios so I don't have to hit the function key to activate the F keys. So I would have had to hit Fn+Ctrl-Alt-F1 for example to get to TTY 1. Now since i switched it off in the bios All I have to do is hit Ctrl-Alt-F1 to get to the terminal. But in order to turn off wifi from the F key (for example) I have to hit Fn+F2. It's switched.
I can't tell you how this was helpful. I've never noticed that there was an option in BIOS's Advanced menu for this. I updated it as "Function Key" and it solved my problem, thanks.

[Solved] The "¨^~"-key does not work for me in URxvt in Awesome

Hello.
I can not understand why I can not write e.g. ^ or ~ using the "^¨~"-key on my keyboard (norwegean layout) in URxvt (extra/rxvt-unicode) in Awesome WM (aur/awesome-git).
Although I have tested in other window managers e.g. dwm, and the key works fine in urxvt there, I am not yet sure whether this is a problem in URxvt or Awesome. When I started using Awesome and URxvt some years ago, this was not an issue yet.
I hope someone has a clue as to what is causing this, and/or how it can be fixed.
Regards,
Rasmus
Edit: added [Solved] tag
Last edited by rusma (2011-08-23 17:30:28)

MaikB wrote:
When I first fired up awesome almost a year ago I needed to add
awful.util.spawn_with_shell("setxkbmap -layout de -variant nodeadkeys")
to my rc.lua to make my german keyboard work. While I'm not sure if your current and my past issue are related, I decided to post since setxkbmap wasn't mentioned yet ( In this thread and in the one karol linked to).
Thanks.
I added
awful.util.spawn_with_shell("setxkbmap -layout no -variant nodeadkeys")
at the end of my local rc.lua, and now it works. Yay!

[SOLVED] AltGr key suddenly isn't AltGr anymore

My AltGr key all of a sudden seems to have changed into a normal Alt key, so I'm unable to produce a couple of characters. Any idea what's going on? Apart from a "sudo pacman -Syu" I didn't do anything regarding any configuration or system things.
My keyboard layout in Xfce 'Settings' dialogue is also still the same as always, I just checked that.
(Well and pressing CTRL+ALT together to "emulate" ALT+GR doesn't work either.)
If I press ALT+CTRL+F1 to switch to a virtual terminal, there AltGr key actually works fine in there! So it's just under Xfce apparently (and in the login screen too).
Last edited by Jindur (2012-03-01 14:19:46)

Try (re)setting your keyboard layout with the following command. Replace "be" with whatever your desired layout is. List is normally found in /usr/share/X11/xkb/rules/xorg.lst)
setxkbmap be
If that indeed solves your problem, you can then put the following in /etc/X11/xorg.conf.d/10-evdev.conf (again replace "be" with whatever your desired layout is obviously).
Section "InputClass"
Identifier "evdev keyboard catchall"
MatchIsKeyboard "on"
MatchDevicePath "/dev/input/event*"
Driver "evdev"
Option "XkbLayout" "be"
EndSection

[SOLVED] Dead keys on console in UTF-8 locale

Hello,
I want to share something interesting I found out about dead keys support on the Linux console (i.e., without X).
I live in Canada and use the "Canadian French" keyboard, which uses dead keys for several diacritical marks (e.g., to type ê I push and release the ^ key, then type the e key). It works perfectly under X, but I was unable to type any character using dead keys on the console. On the other hand, non-ASCII characters like "é" that do not use dead keys worked perfectly.
After some googling, I found many posts claiming the kernel did not support dead keys when the console was in Unicode mode. So I changed the locale to a non-UTF-8 setting in /etc/rc.conf, and indeed dead keys started working. But this was not useful to me, since editing UTF-8 files resulted in gibberish, and I did not want to regress back to Latin1 encoding or have to support both encodings. I tried many combinations of settings, but none worked. For a few days, I thought there was no way to have dead keys and Unicode working on the Console.
But then I started to install Arch Linux on another computer and noticed that when I set the keyboard to Canadian French with the "km" utility before installing (the keymap is called "cf"), dead keys worked, even though the locale was Unicode! So there was a way to do it.
I started digging and trying new things, and found out that after the following incantations, I was able to enable dead keys for Unicode on the console:
kbd_mode -a
sudo loadkeys cf
kbd_mode -u
This sets the console to ASCII mode, loads the "cf" keymap, and sets the console back to Unicode. I found it by trial and error, and I have no idea why it works or whether it breaks anything. I'm posting here to ask if there are easier ways to have a functional Canadian French keyboard on the console, and to document what I did in case someone has a similar problem.
Last edited by pguertin (2010-01-23 21:44:33)

I have the exact same issue.
The weird thing for me is that before I was using gentoo and never had a problem with dead keys and unicode. Also, I confirm that dead keys is working when booting from the archlinux installation cd. Either run 'loadkeys cf' rigth after login or pass 'keymap=cf' as a boot parameter to the kernel line by editing it in grub before booting.
Your solution is interesting, however the cf.map.gz file is the same on the installation cd (and on my gentoo system) so it should works without editing it.
In my quest to solve this issue, I found something interesting. I added the 'keymap' hook in /etc/mkinitcpio.conf and regenerated the image by issuing
mkinitcpio -g /boot/kernel26.img
This alone didn't solved the issue, but then I REMOVED the keymap assignation in /etc/rc.conf (i.e. leaving it as
KEYMAP=
), rebooted... and voilà, it now works.
Furthermore, now if I run
sudo loadkeys cf
after login it stops working (well of course because it's the same as defining KEYMAP="cf" in /etc/rc.conf). Issuing the 3 commands of your first post make it works again. OK so I did one more test: boot from the archlinux installation cd by adding the 'keymap=cf' boot parameter to the kernel line and then run 'loadkeys cf' after login to see if it breaks dead keys. But no, it still works.
So is this issue comes from a newer version of the kernel/loadkeys/mkinitcpio/...? How different is the kernel and initramfs images of the installation cd compared to the installed system ?

[SOLVED] Mulitmedia keys on xfce4?????

I have tried Lineakd with no luck from this wiki: http://wiki.archlinux.org/index.php/Ext … ak_Program ..... I built all of the packages, followed all of the instructions, and it still didn't work for my mulitmedia keys.
I have also attempted to try acpi_listen from this guide: http://wiki.archlinux.org/index.php/Acpi_hotkeys but I got an error saying I had no "sockets?" file in /var something (I foget the exact error message), so I moved on to the lineakd way.
From this wiki: http://wiki.archlinux.org/index.php/Extra_Keyboard_Keys ..... when I tried to setkeycodes to the same ones that work in Gnome, I got this error message: "Couldnt get a file descriptor referring to the console"
My multimedia keys are detected in Gnome with no troubles, but I want to go back to using xfce4 because I like it better. I hope there is a way to get these mulitmedia volume/mute/stop/play/next/previous buttons working on xfce4.
**********EDIT after SOLVED*******************
keytouch is the way to go: http://wiki.archlinux.org/index.php/Ext … ch_Program
It was the last way I tried and it worked perfectly on xfce4. Very simple to figure out and configure.
Last edited by methuselah (2008-09-22 13:57:22)

thank you runical, on xfce4 (Settings - Removable Drives and Media) you are able to configure it.
btw: xfce4 uses thunar for that and thunar uses gvfs package to funktion
Last edited by xabit (2014-11-18 18:21:50)

[solved] XF86AudioRaiseVolume Key not working in XFCE with Toshiba Z30

Symptoms:
It is possible to assign an action to XF86AudioRaiseVolume (or XF86AudioLowerVolume) in xfce4-keyboard-settings, but when XF86AudioRaiseVolume is pressed, nothing happens. (Not even failsafe test commands.)
With xfce4-volumed, the mute-key works, but not XF86AudioRaiseVolume and XF86AudioLowerVolume.
With volumeicon, the following terminal output is send:
$ volumeicon
** (volumeicon:13084): WARNING **: Binding 'XF86AudioRaiseVolume' failed!
Failed to bind XF86AudioRaiseVolume
** (volumeicon:13084): WARNING **: Binding 'XF86AudioLowerVolume' failed!
Failed to bind XF86AudioLowerVolume
** (volumeicon:13084): WARNING **: Binding 'XF86AudioMute' failed!
Failed to bind XF86AudioMute
xev outputs:
for lower:
KeymapNotify event, serial 40, synthetic NO, window 0x0,
keys: 20 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
for raise:
KeymapNotify event, serial 40, synthetic NO, window 0x0,
keys: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
Any ideas how to make them work?
(In Gnome-Shell, they work out of the box.)
I put this in the Laptop subforum, because with my netbook, all this works. I know, the Desktop Environments Subforum would also been an option.
Last edited by Carl Karl (2014-10-08 18:26:15)

OK OK, of course pacman -R xfce4-volumed is not enough, a killall xfce4-volumed is also neccesarry! volumeicon works now, solved.

[Solved] FN key locked in on position after update S431

Hello,My computer did updates and I restarted. Upon restart, the green light on the fn key is permanently on and it won't turn off. How do I fix this problem? I went into bios, but the only option available is fn/crtl key switch. I have a brand new Lenovo Thinkpad S431 running Windows 8 FIXED: APPARENTLY PRESSING FN + ESC ENABLES FUNCTION LOCK. I FEEL SILLY, BUT AT LEAST I SOLVED THE PROBLEM. HOPEFULLY THIS IS HELPFUL TO SOMEONE ELSE IN THE FUTURE.

Took the effort to register just to say thanks. People who are Googeling come here so... Thanks. Saves me an annoying light on my work laptop.

[Solved] Windows key isn't Super_L/Mod4 anymore

After a recent update, my Windows key wouldn't work anymore, meaning it doesn't procude my regular Fluxbox bindings. Following this nice wiki: http://fluxbox-wiki.org/index.php?title=Mod4
I found out that Mod isn't set anymore:
zsh/3 1572 % xmodmap
xmodmap: up to 2 keys per modifier, (keycodes in parentheses):
shift Shift_L (0x32), Shift_R (0x3e)
lock Caps_Lock (0x42)
control Control_L (0x25), Control_R (0x6d)
mod1 Alt_L (0x40), Alt_R (0x71)
mod2 Num_Lock (0x4d)
mod3
mod4
mod5 Scroll_Lock (0x4e)
So I tried
xmodmap -e 'add mod4 = Super_L'
and
xmodmap -e 'keycode 115 = Super_L'
As it states on the wiki, but neither of them helped, xmodmap -pm still shows the same emptiness for Mod4. I also created an .Xmodmap, put the key assignments in there and loaded it, but it still wouldn't work. Any suggestions?
Btw.: xev output for the windows key is this:
KeyRelease event, serial 35, synthetic NO, window 0x2200001,
root 0x87, subw 0x0, time 53871339, (170,38), root:(430,312),
state 0x10, keycode 115 (keysym 0xffeb, Super_L), same_screen YES,
XLookupString gives 0 bytes:
XFilterEvent returns: False
Last edited by kelnoky (2008-10-23 08:09:05)

Alright, sorry. That was a little premature, a simple restart X helped...
I'll go stand in that corner over there now.

[SOLVED]Fn keys broken after update

Hi,
After a system upgrade the fn keys controlling the keyboard backlight don't work. Other fn keys work fine
Update log:
[2013-09-20 17:55] [PACMAN] starting full system upgrade
[2013-09-20 17:58] [PACMAN] upgraded dbus (1.6.12-1 -> 1.6.14-1)
[2013-09-20 17:58] [ALPM] warning: /etc/systemd/logind.conf installed as /etc/systemd/logind.conf.pacnew
[2013-09-20 17:58] [ALPM-SCRIPTLET] ==> systemd 205 restructures the cgroup hierarchy and changes internal
[2013-09-20 17:58] [ALPM-SCRIPTLET] protocols. You should reboot at your earliest convenience.
[2013-09-20 17:58] [ALPM-SCRIPTLET] ==> The "timestamp" hook for mkinitcpio no longer exists. If you used
[2013-09-20 17:58] [ALPM-SCRIPTLET] this hook, you must remove it from /etc/mkinitcpio.conf. A "systemd"
[2013-09-20 17:58] [ALPM-SCRIPTLET] hook has been added which provides this functionality, and more.
[2013-09-20 17:58] [PACMAN] upgraded systemd (204-3 -> 207-3)
[2013-09-20 17:58] [PACMAN] upgraded bluez-utils (5.7-1 -> 5.8-1)
[2013-09-20 17:58] [PACMAN] upgraded cogl (1.14.0-4 -> 1.14.0-5)
[2013-09-20 17:58] [PACMAN] upgraded empathy (3.8.3-1 -> 3.8.4-1)
[2013-09-20 17:58] [PACMAN] upgraded firefox (23.0.1-1 -> 24.0-1)
[2013-09-20 17:58] [ALPM-SCRIPTLET] Generating locales...
[2013-09-20 17:58] [ALPM-SCRIPTLET] el_GR.UTF-8... done
[2013-09-20 17:58] [ALPM-SCRIPTLET] en_US.UTF-8... done
[2013-09-20 17:58] [ALPM-SCRIPTLET] Generation complete.
[2013-09-20 17:58] [PACMAN] upgraded glibc (2.18-3 -> 2.18-4)
[2013-09-20 17:58] [PACMAN] upgraded gmime (2.6.17-1 -> 2.6.18-1)
[2013-09-20 17:58] [PACMAN] upgraded gnome-desktop (1:3.8.3-2 -> 1:3.8.4-1)
[2013-09-20 17:58] [PACMAN] upgraded gnome-color-manager (3.8.2-1 -> 3.8.3-1)
[2013-09-20 17:58] [PACMAN] upgraded gnome-settings-daemon (3.8.4-2 -> 3.8.5-1)
[2013-09-20 17:58] [PACMAN] upgraded gnome-control-center (3.8.4.1-2 -> 3.8.5-1)
[2013-09-20 17:58] [PACMAN] upgraded gnome-shell-extensions (3.8.3.1-2 -> 3.8.4-1)
[2013-09-20 17:58] [PACMAN] upgraded gnome-themes-standard (3.8.3-1 -> 3.8.4-1)
[2013-09-20 17:58] [PACMAN] upgraded graphviz (2.32.0-1 -> 2.32.0-2)
[2013-09-20 17:58] [PACMAN] upgraded icedtea-web-java7 (1.4-2 -> 1.4.1-1)
[2013-09-20 17:58] [PACMAN] upgraded lib32-glibc (2.18-3 -> 2.18-4)
[2013-09-20 17:58] [PACMAN] upgraded libpng (1.6.3-1 -> 1.6.5-1)
[2013-09-20 17:58] [PACMAN] upgraded lib32-libpng (1.6.3-1 -> 1.6.5-1)
[2013-09-20 17:58] [PACMAN] upgraded libusbx (1.0.16-2 -> 1.0.17-1)
[2013-09-20 17:58] [PACMAN] upgraded linux-firmware (20130725-1 -> 20130903-1)
[2013-09-20 17:58] [ALPM-SCRIPTLET] >>> Updating module dependencies. Please wait ...
[2013-09-20 17:58] [ALPM-SCRIPTLET] >>> Generating initial ramdisk, using mkinitcpio. Please wait...
[2013-09-20 17:58] [ALPM-SCRIPTLET] ==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'default'
[2013-09-20 17:58] [ALPM-SCRIPTLET] -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux.img
[2013-09-20 17:58] [ALPM-SCRIPTLET] ==> Starting build: 3.11.1-1-ARCH
[2013-09-20 17:58] [ALPM-SCRIPTLET] -> Running build hook: [base]
[2013-09-20 17:58] [ALPM-SCRIPTLET] -> Running build hook: [udev]
[2013-09-20 17:58] [ALPM-SCRIPTLET] -> Running build hook: [autodetect]
[2013-09-20 17:58] [ALPM-SCRIPTLET] -> Running build hook: [modconf]
[2013-09-20 17:58] [ALPM-SCRIPTLET] -> Running build hook: [block]
[2013-09-20 17:58] [ALPM-SCRIPTLET] -> Running build hook: [filesystems]
[2013-09-20 17:58] [ALPM-SCRIPTLET] -> Running build hook: [keyboard]
[2013-09-20 17:58] [ALPM-SCRIPTLET] -> Running build hook: [fsck]
[2013-09-20 17:58] [ALPM-SCRIPTLET] ==> Generating module dependencies
[2013-09-20 17:58] [ALPM-SCRIPTLET] ==> Creating gzip initcpio image: /boot/initramfs-linux.img
[2013-09-20 17:58] [ALPM-SCRIPTLET] ==> Image generation successful
[2013-09-20 17:58] [ALPM-SCRIPTLET] ==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'fallback'
[2013-09-20 17:58] [ALPM-SCRIPTLET] -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-fallback.img -S autodetect
[2013-09-20 17:58] [ALPM-SCRIPTLET] ==> Starting build: 3.11.1-1-ARCH
[2013-09-20 17:58] [ALPM-SCRIPTLET] -> Running build hook: [base]
[2013-09-20 17:58] [ALPM-SCRIPTLET] -> Running build hook: [udev]
[2013-09-20 17:58] [ALPM-SCRIPTLET] -> Running build hook: [modconf]
[2013-09-20 17:58] [ALPM-SCRIPTLET] -> Running build hook: [block]
[2013-09-20 17:58] [ALPM-SCRIPTLET] ==> WARNING: Possibly missing firmware for module: bfa
[2013-09-20 17:58] [ALPM-SCRIPTLET] ==> WARNING: Possibly missing firmware for module: aic94xx
[2013-09-20 17:58] [ALPM-SCRIPTLET] ==> WARNING: Possibly missing firmware for module: smsmdtv
[2013-09-20 17:58] [ALPM-SCRIPTLET] -> Running build hook: [filesystems]
[2013-09-20 17:58] [ALPM-SCRIPTLET] -> Running build hook: [keyboard]
[2013-09-20 17:58] [ALPM-SCRIPTLET] -> Running build hook: [fsck]
[2013-09-20 17:58] [ALPM-SCRIPTLET] ==> Generating module dependencies
[2013-09-20 17:58] [ALPM-SCRIPTLET] ==> Creating gzip initcpio image: /boot/initramfs-linux-fallback.img
[2013-09-20 17:58] [ALPM-SCRIPTLET] ==> Image generation successful
[2013-09-20 17:58] [PACMAN] upgraded linux (3.10.10-1 -> 3.11.1-1)
[2013-09-20 17:58] [PACMAN] upgraded orc (0.4.17-1 -> 0.4.18-1)
[2013-09-20 17:58] [ALPM-SCRIPTLET]
[2013-09-20 17:58] [ALPM-SCRIPTLET] ==> The file /etc/sysctl.conf has been removed from this
[2013-09-20 17:58] [ALPM-SCRIPTLET] ==> package, as all its settings are now kernel defaults.
[2013-09-20 17:58] [ALPM-SCRIPTLET]
[2013-09-20 17:58] [ALPM-SCRIPTLET] ==> If you had customized it, you need to rename it as
[2013-09-20 17:58] [ALPM-SCRIPTLET] ==> /etc/sysctl.d/99-sysctl.conf since from version 207 on
[2013-09-20 17:58] [ALPM-SCRIPTLET] ==> systemd only applies settings from /etc/sysctl.d/* .
[2013-09-20 17:58] [ALPM-SCRIPTLET]
[2013-09-20 17:58] [PACMAN] upgraded procps-ng (3.3.8-2 -> 3.3.8-3)
[2013-09-20 17:58] [PACMAN] upgraded raptor (2.0.9-2 -> 2.0.10-2)
[2013-09-20 17:58] [PACMAN] upgraded systemd-sysvcompat (204-3 -> 207-3)
[2013-09-20 17:58] [PACMAN] upgraded tali (3.8.0-1 -> 3.8.1-1)
[2013-09-20 17:58] [PACMAN] upgraded transmission-gtk (2.81-1 -> 2.82-1)
[2013-09-20 17:58] [PACMAN] upgraded udisks2 (2.1.0-3 -> 2.1.1-1)
[2013-09-20 17:58] [ALPM-SCRIPTLET] In order to use the new version, reload all virtualbox modules manually.
[2013-09-20 17:58] [PACMAN] upgraded virtualbox-host-modules (4.2.18-1 -> 4.2.18-3)
[2013-09-20 17:58] [PACMAN] upgraded xorg-xinput (1.6.0-1 -> 1.6.1-1)
[2013-09-20 17:58] [PACMAN] upgraded xvidcore (1.3.2-1 -> 1.3.2-2)
and Dmesg
[ 1053.214014] atkbd serio0: Unknown key pressed (translated set 2, code 0x97 on isa0060/serio0).
[ 1053.214022] atkbd serio0: Use 'setkeycodes e017 <keycode>' to make it known.
[ 1053.455447] atkbd serio0: Unknown key pressed (translated set 2, code 0x96 on isa0060/serio0).
[ 1053.455455] atkbd serio0: Use 'setkeycodes e016 <keycode>' to make it known.
I can see what the issue is (somehow the update broke the keyboard "hooks"), but don't know how to fix it cleanly (with what to "hook" the keys).
Seems like a silly situation, so i start the thread in the newbies section.
thanks in advance
Last edited by mpir (2013-09-25 18:12:08)

Solution:
prerequisites: xorg-xev
i) get the keyodes with dmesg | tail {i used the eXX number, not the hex}
ii) test the scancode to keycode binding using
setkeycodes [scancode_you_found] [keycode]
and then
xev
. You want your key to show up as "XF86KbdBrightnessUp/Down", my keycodes were 229 and 230
iii) make the change permanant by:
creating a new service
/etc/systemd/system/setkeycodes.service
[Unit]
Description=Change keycodes at boot
[Service]
Type=oneshot
ExecStart=/usr/bin/setkeycodes [scancode] [keycode]
ExecStart=/usr/bin/setkeycodes [scancode] [keycode]
[Install]
WantedBy=multi-user.target
and enabling the service
systemctl enable setkeycodes
cheers

[Solved] Shift key doesn't work correctly

Hi!
I have a strange problem for a while. If I hold down the shift key and type the computer releases it itself. Example: I press down the shift key and type some upper case chars and suddenly I am writing lower case chars without releasing the shift key! I already tested another keyboard and nothing changed. And I have the feeling that the problem only occurs with Linux, not with Windows, which is installed on the same computer. But I dont know for sure, because I don't spent mach time with windows ;-)
Here is my xorg.conf:
Section "Device"
Identifier "nvidiacard"
Driver "nvidia"
EndSection
Section "Screen"
Identifier "screen0"
Device "nvidiacard"
EndSection
Section "ServerLayout"
Identifier "Builtin Default Layout"
Screen "screen0"
EndSection
And this is my /etc/hal/fdi/policy/10-keymap.fdi:
<?xml version="1.0" encoding="ISO-8859-1"?> 
<deviceinfo version="0.2">
<device>
<match key="info.capabilities" contains="input.keymap">
<append key="info.callouts.add" type="strlist">hal-setup-keymap</append>
</match>
<match key="info.capabilities" contains="input.keys">
<merge key="input.xkb.rules" type="string">base</merge>

<merge key="input.xkb.model" type="string">keyboard</merge>
<match key="/org/freedesktop/Hal/devices/computer:system.kernel.name"
string="Linux">
<merge key="input.xkb.model" type="string">evdev</merge>
</match>
<merge key="input.xkb.layout" type="string">de</merge>
<merge key="input.xkb.variant" type="string">nodeadkeys</merge>
</match>
</device>
</deviceinfo>
Before that I had a static configuration with the same problem. Any idea?
Thanks,
Thomas
Last edited by Murray_B (2009-12-02 20:05:45)

Okay, the question if the problem occurs in console was good - no it doesn't!
I played a bit and started X11 with only xterm (no windowmanager) and there
were no problem. I had also no problem with openbox and xterm. So I moved
away my xfce-config and started with a clean one. No problem. I add
everything of my config again (one thing after another) - and there are no
problems any more!?!? Don't know what happened, but I could work again,
thank you!
Thomas

[SOLVED] Remapping keys using udev hwdb doesn't work on rightAlt

hi, I had posted this topic in the [ newbie corner ] subforum for days, but got no repliy. I hope I can find luck here.
I'm trying to use udev hwdb for swapping pairs of keys ( esc, caps_lock ) and ( rightAlt , rightCtrl ) . I followed the instruction here Map Scancodes to Keycodes with procedures describe blow. I only succeed in exchanging pair (esc, caps_lock) but failed in (rightAlt, rightCtrl).
Details of Procedures:
Create an empty file under /usr/lib64/udev/hwdb.d with file name 90-custom-keys.hwdb . Add the following lines into this file.
keyboard:dmi:bvn*:bvr*:bd*:svnDell*:pn*
KEYBOARD_KEY_01=capslock
KEYBOARD_KEY_3a=esc
KEYBOARD_KEY_e038=rightctrl
KEYBOARD_KEY_e01d=rightalt
Rebuilding hwdb.bin
udevadm hwdb --update
Testing and reboot my system
udevadm --debug test /devices/platform/i8042/serio0/input/input0/event0
udevadm --debug test-builtin keyboard /devices/platform/i8042/serio0/input/input0/event0
Parts of the testing result of the last command looks like
device 0x1ce3890 has devpath '/devices/platform/i8042/serio0/input/input0/event0'
device 0x1ce3890 filled with db file data
keyboard: mapping scan code 1 (0x1) to key code 58 (0x3a)
keyboard: mapping scan code 58 (0x3a) to key code 1 (0x1)
keyboard: mapping scan code 129 (0x81) to key code 164 (0xa4)
keyboard: mapping scan code 130 (0x82) to key code 166 (0xa6)
keyboard: mapping scan code 164 (0xa4) to key code 166 (0xa6)
keyboard: mapping scan code 216 (0xd8) to key code 152 (0x98)
keyboard: mapping scan code 217 (0xd9) to key code 191 (0xbf)
keyboard: mapping scan code 57373 (0xe01d) to key code 100 (0x64)
Error calling EVIOCSKEYCODE: Invalid argument
keyboard: mapping scan code 57400 (0xe038) to key code 97 (0x61)
Error calling EVIOCSKEYCODE: Invalid argument
keyboard: mapping scan code 237 (0xed) to key code 226 (0xe2)
unload module index
Thie last 6 lines seems to be complaining the problem, saying that 0xe038 and 0xe01d are invalid scancodes.
But they are scancodes of rightAlt and rightCtrl respectively, which I got from
showkey -s
After rebooting the system with the above settings, esc works as caps_lock and caps_lock works as esc but rightAlt and rightCtrl has no changes.
Last edited by kejingzhang (2013-10-10 02:32:29)

Thanks plam and Raynman for your help . Follow your hints, I succeed the swapping key task in an alternative method.
Using the command 'setkeycodes' and adding these commands into a systemd controlled service script, keymaps are exchanged as gdm started.
Here is my script and steps for doing this.
Created a file with filename custom-keys.service under /etc/systemd/system. Add the following context to the file.
[Unit]
Description=Keymap Custom
Requires=gdm.service
After=gdm.service
[Service]
Type=oneshot
ExecStart=/usr/bin/setkeycodes 1 58
ExecStart=/usr/bin/setkeycodes 3a 1
ExecStart=/usr/bin/setkeycodes e01d 100
ExecStart=/usr/bin/setkeycodes e038 97
[Install]
WantedBy=graphical.target
Enable the script so setkeycodes commands will automatically executed when gdm starts
systemctl enable custom-keys
The next time you reboot your system, key changes will take effect. To test if your config works, try
systemctl start custom-keys

[Solved] Disabled key for LXDE

Hi again,
I'm unhappy that I have to claim for your help again but I'm encountering some trouble installing LXDE. The problem ist discribed precisely in the internet and there are workarounds given to get things straighten out but I think, there might be some drawbacks.
One place the error is discribed is in the bugsection of this page. The bug is marked as closed over there giving the reason that it's fixed. Nevertheless I keep encountering that error. As an additional comment about closing "archlinux-keyring 20130525-2" is given. I checked that package. It is already installed on my machine.
As aforementiones ther are some workarounds. One is given by flexiondotorg who suggest to just reenable the relevant key. That might work for sure but I guess there is a reason for the key being disabled. Maybe there are some pagages, maybe malicious ones, signed using that key without authorization. That it would be advisable not to reenable that key, wouldn't it?
Now I'm left alone with two questions I'm not able to find a satisfying answer for myself. First of all I'm wondering, why the bug report is closed and marked as fixed, while I continue to get exactly the same error. Is it going to be fixed anyway or it's just me who doesn't see the point how it is fixed?
The second arising question is whether there is a way to get the LXDE package anyway making sure that the package is not manipulated using a stolen key from Mr. Wallace.
Last edited by disjunkt (2013-07-04 05:07:45)

Ok, i did my homework and got some enlightments. You can disable, revoke and delete a key and their components respectively. But each one of these mean a (slightly) different thing obviously.
If you have to void a key, for whatever reason, you'll have to delete or rather revoke the key. However there are some advantages to revoking the key. I'm not going to carry that out in detail, but you can do some reading about that stuff in The GNU Privacy Handbook. By the way, the "redundant selfsigning" ist not a redundant selfsigning, but a rovoking of the uid. That's also explained in the Privacy Handbook.
Disabling a key on the other hand is not described in the Privacy Handbook but there is a brief description in the GnuPG (2.0) manual stating that you can "Disable or enable an entire key. A disabled key can not normally be used for encryption." If i understand alright, that will be just a local setting. If you disable a key, won't be used for encryption on your machine, but it would not effect others. Disabling and enabling a key or a key component doesn't change anything with that key. A revoked key will stay revoked.
Finally I'm not 100% sure, but I think re-enabling a key shouldn't affect any security concerns. Please correct me, if I'm misled. Or if you can confirm that for sure, you'll be very welcome to do that as well. Besides that I can't think about a reason why you disable a key. Maybe someone can also point me in a direction here.

[SOLVED] Fluxbox keys magic

Similar Messages

Maybe you are looking for