polybar: Broken mouse clicks

Output with trace log:

- bar: Received button press: 1 at pos(253, 7)
- Found matching input area
warn: Uncaught input event, forwarding to shell... (input: �)
* Executing shell command: �
- command: Waiting for pid 7513 to finish...
warn: command: Exited with failed status 127

Clicking on the bar results in the error above. On the latest commit, it appears for every clickable module (and also the fallback handlers), but on 2.4.6 only the bspwm and script modules don’t work (on my setup at least).

Note: scrolling still works fine.

About this issue

Original URL
State: closed
Created 7 years ago
Comments: 25 (9 by maintainers)

Commits related to this issue

fix(signals): Use pointer to value Only pass pointers to emitted signal value since the signal receivers will be called on the same thread as the signal emitter. Refs #302 — committed to polybar/polybar by jaagr 7 years ago

Most upvoted comments

It’s working again, thanks.

SageEx on Jan 9, 2017

Confirming that menu execution commands don’t work, while the main menu button works fine as said in the previous comment.

NBonaparte on Jan 5, 2017

Clicks are broken again in menu (menu-N-N-exec) and bspwm, scrolling works well:

warn: Uncaught input event, forwarding to shell... (input: )

polybar 2.4.6 

Features: +alsa +curl -i3 +mpd +network 

Build type: RelWithDebInfo
Compiler: /usr/bin/c++
Compiler flags: -march=x86-64 -mtune=generic -O2 -pipe -fstack-protector-strong -Wall -Wextra -Werror -O2 -pedantic -pedantic-errors
Linker flags: -Wl,-O1,--sort-common,--as-needed,-z,relro

Deluxo on Jan 4, 2017