Logs filled wih "Key spec duplicated" errors, but config is only binding keys once (using simple_key_binder) about qtile HOT 11 CLOSED

I had this in my logs, but can't reproduce with the 0.24.0 tag; can you confirm that it happens with the recent release?

from qtile.

I just upgraded to 0.24.0 on Void Linux, rebooted, and the same messages are still there. My bar is also messed up (one tray icon at the far left, on top of another widget, instead of in the tray icon area)---still need to look into that.

from qtile.

Can you post your config and I'll see if I can recreate the issue(s).

from qtile.

Hi @elParaguayo
It's still the same config that I posted above. Thanks for having a look!

PS the two tray applications I am running (in my autostart.sh) are nm-applet and blueman-applet. The blueman-applet appears in the same place it used to (far right of the tray area), but nm-applet somehow moved to the far left of the bar, and is painted directly on top of my menu launcher icon. Oddly, I can still access both of them by moving the mouse a bit higher or a bit lower :)

Something also changed in the Battery widget. I used to have battery icons but after upgrading to 0.24.0 it is now showing an asterisk.

Also, this morning I just noticed that a group sometimes spontaneously moves onto my second monitor (when it was just showing background) without me doing anything except typing this Github comment on the primary monitor.

No idea why any of this would have changed... it's very strange.

from qtile.

I can recreate the duplicate key issue. It seems to be triggered by this line:

dgroups_key_binder = simple_key_binder(mod)

Commenting it out stops the errors. Will investigate more.

Haven't looked at the other two issues. Ideally, you could you separate them into separate issues here so I can deal with them individually and keep this thread just for the duplicate keys part.

EDIT: Ha - it was my commit that caused this: 9d65ae2 Need to find a fix that doesn't cause a regression of that other issue.

from qtile.

Try #4659

from qtile.

Awesome---thanks! I have been uncertain on whether I should use dgroups_key_binder or not. I thought I read somewhere that it wasn't needed, but I'm pretty sure I tried commenting that line out and then I didn't have any group-switching keys. Is it better if we define the keys ourselves instead of calling that? Or no preference?

Yes, I need to poke around with the unrelated issues and see if I am doing something stupid. If that doesn't turn up anything I'll open a separate issue(s).

from qtile.

The default config doesn't use the binder but it shouldn't generate log messages when it's used and you should be able to use either.

from qtile.

To clarify, though, if I don't use dgroups_key_binder, then I need to explicitly provide those bindings in the config file? (I took someone else's config and modified it heavily, so at some point I should probably go look at what is in the default config...)

I tested the commit and everything looks good, thanks. On this startup my tray apps are in their proper places too. I wonder if there is another race going on. Oh, and I traced the battery widget problem to my /sys/class/power_supply/BAT0 statuses. There seem to be quite a few statuses which all mean "battery is charged"...

from qtile.

Yes, if you remove the key binder you'll need to add bindings yourself. Have a look at the default config to see how this is done.

from qtile.

Super, thanks.

from qtile.