You are not logged in.
I'm having trouble keybinding absolutely anything to <Alt>Up and/or <Alt>Down. For example the following keybind should open Chromium when I hold the ALT and UP ARROW keys:
<keybind key="A-Up">
<action name="Execute">
<startupnotify>
<enabled>true</enabled>
<name>Web Browser</name>
</startupnotify>
<command>chromium</command>
</action>
</keybind>
But chromium fails to open. Although there are many key combinations where I can get chromium to open, I've listed two interesting ones as examples here:
one: <keybind key="A-Left">
two: <keybind key="W-Up">
The first suggests that the ALT key I have works in combination with the left/right arrow keys.
The second suggests that the UP and DOWN arrow keys also work when combined with the SUPER key.
So I can safely assure you that my keyboard is working correctly and that I am reconfiguring OB after updating my rc.xml.
I also checked the rest of my rc.xml file and couldn't find any duplicate instances of A-Up and/or A-Down.
It seems I'm just unable to bind anything to the key combination: ALT + UP and/or ALT + DOWN. Any thoughts on what could be going on here would greatly be appreciated!
Cheers,
Steve
Offline
Works A-Up works fine for me, after reconfiguring openbox
Offline
You could test whether you are calling Chromium properly by calling it to open automatically on a specified desktop when Openbox starts.
I use the following to open Firefox on desktop 5:
<application class="Firefox">
<desktop>5</desktop>
<maximized>yes</maximized>
<focus>yes</focus>
<position force="yes">
<x>0</x>
<y>0</y>
<monitor>0</monitor>
</position>
</application>
This post in a thread over at Spiralinear.org has some info' that helped me a lot when I was first messing about with my rc.xml (thanks go to urukrama), it could most especially be of assistance if Chromium uses a different name or class, also the case of the first letter of the name can bring it all undone:
Offline
Ok, I've had some luck, but am still having difficulties. Here's what I've done since:
1. Copied the rc.xml file from the live cd.
2. Copied this file to both /etc/xdg/openbox/rc.xml and ~/.config/openbox/rc.xml
3. I went Preferences -> Openbox config -> Key Editor to open obkey program.
4. I then inserted four sibling keybinds for: ALT+Up, ALT+Down, ALT+Right and ALT+Left each with the chroot option.
5. Save and Reboot.
6. I then go Preferences -> Openbox config -> Key Editor to open obkey again.
7. I remove the four keybinds I just made.
And this fixes the keybinding problem I have had. The ALT+Up and ALT+Down keys now allow me to freely navigate Terminator (up and down, respectively) after splitting vertically. Perfect. This is exactly what I wanted to achieve.
However if I reboot, the problem persists and I need to restart these steps to make sure ALT+Up and ALT+Down are unbound. And I need ALT+Up and ALT+Down unbound to navigate Terminator easily.
So ... it seems (at least I think it seems ...) that upon booting my machine, something is being bound on top of ALT+Up and ALT+Down. What is it? What could this be? Is there an easy way to find out what is being bound?
Offline
I have not used chrooted keychains but this may help
Offline
Solved. ALT+Up and ALT+Down were bound in "Mixer" (Volume control). I must have forgot that I bound this. I should probably log everything or stop drinking...
Thanks all.
Offline
Will mark thread as solved, beers are on Steve ![]()
Offline