[SOLVED] Lithium main menu won't run using .xbindsrc

phuturism · 2020-08-16 13:37:32

jgmenu won't launch using the defined keybindings as per the .xbindsrc file. Will launch using a rightclick on desktop or "jgmenu_run" in a terminal. I used to love just hitting the windows key to launch the menu anywhere but that doesn't work either if I remove the "+ space" from the .xbindsrc file.

# Show main menu
"jgmenu_run"
    Mod4 + space

Mod4 and spacebar work in other contexts.

Last edited by phuturism (2020-08-24 13:47:29)

damo · 2020-08-16 15:03:55

Did you edit .xbindrc without restarting xbindkeys?

Are you running a bunsenlabs or openbox session?

In .config/bunsen/autostart do you have

    ## Alias Super key to Super+Space for single-key menu.
    ## See 'man xcape' for other possibilities.
    xcape -e 'Super_L=Super_L|space'

phuturism · 2020-08-17 04:32:05

damo wrote:

Did you edit .xbindrc without restarting xbindkeys?
Are you running a bunsenlabs or openbox session?
In .config/bunsen/autostart do you have
    ## Alias Super key to Super+Space for single-key menu.
    ## See 'man xcape' for other possibilities.
    xcape -e 'Super_L=Super_L|space'

1. yes, I did edit without restarting
2. bunsenlabs
3. yes I have that in autostart

If I run

$ killall -HUP xbindkeys
$ xbindkeys

it works! But on logout/reboot it doesn't work again, how can I get xbindkeys to be read at the start of each session? I note it's in bl autostart already

Last edited by phuturism (2020-08-17 05:11:18)

damo · 2020-08-17 09:28:12

In ~/.config/bunsen/autostart do you have

# start keybinds daemon
# (If this clashes with some window manager's keybinds,
# you can move it to the window-manager-dependent section below.)
xbindkeys_autostart

What happens if you run

/usr/bin/xbindkeys_autostart

phuturism · 2020-08-17 12:28:33

damo wrote:

In ~/.config/bunsen/autostart do you have

# start keybinds daemon
# (If this clashes with some window manager's keybinds,
# you can move it to the window-manager-dependent section below.)
xbindkeys_autostart

What happens if you run

/usr/bin/xbindkeys_autostart

1. yes, have that in autostart
2. nothing - no errors in terminal but menu still won't activate on mod4 key combination

If I then kill and restart xbindkeys as below it works!

killall -HUP xbindkeys && xbindkeys

damo · 2020-08-17 14:55:08

phuturism wrote:

...
2. nothing - no errors in terminal but menu still won't activate on mod4 key combination
If I then kill and restart xbindkeys as below it works!
killall -HUP xbindkeys && xbindkeys

I guess you could try putting that command in your autostart hmm

phuturism · 2020-08-17 15:18:35

damo wrote:

phuturism wrote:
...
2. nothing - no errors in terminal but menu still won't activate on mod4 key combination
If I then kill and restart xbindkeys as below it works!
killall -HUP xbindkeys && xbindkeys
I guess you could try putting that command in your autostart

I could, seems a bit hacky but ok. I haven't changed much in terms of configuration as this is a fresh install, wondering why it doesn't work for me :-(

Thanks for the help so far Damo

Last edited by phuturism (2020-08-17 15:19:17)

damo · 2020-08-17 17:30:02

phuturism wrote:

... I haven't changed much in terms of configuration as this is a fresh install, wondering why it doesn't work for me :-(
Thanks for the help so far Damo

Useful information to provide, considering this is a "bug report". So what have you changed?

phuturism · 2020-08-18 04:21:03

damo wrote:

Useful information to provide, considering this is a "bug report". So what have you changed?

As far as config files go, nothing except adding some new entries in the xkeybindsrc file. Haven't changed bl-rc. Apart from that, installed chrome, slack, zoom, telegram-desktop, added tlp and tlpui, nordvpn, some required addition of repos or download of *.deb installers. Added debian backports.

# For the benefit of emacs users: -*- shell-script -*-
###########################
# xbindkeys configuration #
###########################
#
# Version: 1.8.6
#
# This file is adapted for BunsenLabs Linux.
#

# NOTE: There is a gui available for editing keybinds - 'xbindkeys-config'.
# However we don't recommend its installation and use because it has some bugs.

# The format of a command line is:
#    "command to start"
#       associated key
#

# To identify a key, you can run 'xbindkeys --key' or
# 'xbindkeys --multikey' in a terminal
# and put one of the two output lines in this file.

# List of modifiers:
#   Release, Control, Shift, Mod1 (Alt), Mod2 (NumLock),
#   Mod3 (CapsLock), Mod4, Mod5 (Scroll).
#
# Mod4 is also known as the Super or Windows key.
#
# The release modifier is not a standard X modifier, but you can
# use it if you want to catch release events instead of press events.
#
# By default, xbindkeys does not pay attention to the modifiers
# NumLock, CapsLock and ScrollLock.
# Uncomment the lines below if you want to pay attention to them.
#
#keystate_numlock = enable
#keystate_capslock = enable
#keystate_scrolllock= enable

# NOTE xbindkeys reloads its configuration file each time it has changed.
# If you want to force it to reload its configuration file,
# you can send a HUP signal:
#
#       killall -HUP xbindkeys
#
# Or if that's not enough, a full restart:
#
#       pkill -x xbindkeys
#       xbindkeys_autostart
#
# (Sometimes this is needed.)
# When a HUP signal is sent to xbindkeys,
# changes in $HOME/.xbindkeysrc take effect only after moving the mouse.

# See 'man xbindkeys' for more information.

# Show main menu
"jgmenu_run"
    Mod4 + space

# Run Program
"gmrun"
    Alt + F2

# Show dmenu
"~/.config/dmenu/dmenu-bind.sh"
    Alt + F3

# Terminal
"x-terminal-emulator"
    Mod4 + t

# Web Browser
"x-www-browser"
    Mod4 + w

# File Manager
"bl-file-manager"
    Mod4 + f

# File Manager
"webcamoid"
    Mod4 + k

# Editor
"bl-text-editor"
    Mod4 + e

# Media Player
"bl-media-player"
    Mod4 + m

# Volume
"pavucontrol"
    Mod4 + v

# Bittorrent
"transmission-gtk"
    Mod4 + b

# Google Chrome
"google-chrome"
    Mod4 + c

# Telegram
"telegram-desktop"
    Mod4 + g

# Zoom
"zoom"
    Mod4 + z

# htop task manager
"x-terminal-emulator -T 'htop task manager' -e htop"
    Mod4 + h

# Lock Screen
"bl-lock"
    Mod4 + l

# Logout
"bl-exit"
    Mod4 + x

# Kill a Window
"xkill"
    Mod4 + Escape

# Print Screen (xfce)
"xfce4-screenshooter"
    Print

# Print Screen (scrot)
"scrot '%Y-%m-%d--%s_$wx$h_scrot.png' -e 'mv $f ~/Pictures/screenshots/ ; bl-image-viewer ~/Pictures/screenshots/$f'"
    Alt + Print

# Scrot with 10s delay
"scrot -d 10 '%Y-%m-%d--%s_$wx$h_scrot.png' -e 'mv $f ~/Pictures/screenshots/ ; bl-image-viewer ~/Pictures/screenshots/$f'"
    Control + Alt + Print

# Show xbindkeys settings
# (install tk to use this)
#"xbindkeys_show"
#    Control + Shift + q

##################################
# End of xbindkeys configuration #
##################################

damo · 2020-08-18 04:24:56

Do any of those keybinds clash with anything in bl-rc.xml?

phuturism · 2020-08-18 13:21:43

damo wrote:

Do any of those keybinds clash with anything in bl-rc.xml?

No. bl-rc.xml still has the section corresponding to launching the old bl menu AND a commented out section to launch the jgmenu - so I admitted defeat and commented out the jgmenu section in .xbindsrc and uncommented the section in bl-rc.xml thusly

<!-- jgmenu is now launched by Mod4 + space in ~/.xbindkeysrc -->

    <keybind key="W-space">
      <action name="Execute">
        <startupnotify>
          <enabled>false</enabled>
          <name>jgmenu</name>
        </startupnotify>
        <command>jgmenu_run</command>
      </action>
    </keybind>

It works! This is a hack I can live with. Strange that xbindkeys works with a kill/restart. Something obvious must be wrong but I can't see it :-)

Last edited by phuturism (2020-08-18 13:30:21)

phuturism · 2020-08-24 13:48:35

I've marked this as [SOLVED] as the rc workaround is OK for me and we never got to the root cause

EDIT - for other reasons did a clean install and the problem is gone on the new installation.

Last edited by phuturism (2020-09-04 08:55:06)

#1 2020-08-16 13:37:32

[SOLVED] Lithium main menu won't run using .xbindsrc

#2 2020-08-16 15:03:55

Re: [SOLVED] Lithium main menu won't run using .xbindsrc

#3 2020-08-17 04:32:05

Re: [SOLVED] Lithium main menu won't run using .xbindsrc

#4 2020-08-17 09:28:12

Re: [SOLVED] Lithium main menu won't run using .xbindsrc

#5 2020-08-17 12:28:33

Re: [SOLVED] Lithium main menu won't run using .xbindsrc

#6 2020-08-17 14:55:08

Re: [SOLVED] Lithium main menu won't run using .xbindsrc

#7 2020-08-17 15:18:35

Re: [SOLVED] Lithium main menu won't run using .xbindsrc

#8 2020-08-17 17:30:02

Re: [SOLVED] Lithium main menu won't run using .xbindsrc

#9 2020-08-18 04:21:03

Re: [SOLVED] Lithium main menu won't run using .xbindsrc

#10 2020-08-18 04:24:56

Re: [SOLVED] Lithium main menu won't run using .xbindsrc

#11 2020-08-18 13:21:43

Re: [SOLVED] Lithium main menu won't run using .xbindsrc

#12 2020-08-24 13:48:35

Re: [SOLVED] Lithium main menu won't run using .xbindsrc

Board footer