Open carlsmedstad opened 4 years ago
Can you share a log when you reproduce the bug rather than just starting up Sway?
Sure, sway reports mouse clicks both with and without the commit I mentioned:
00:00:02.643 [DEBUG] [types/seat/wlr_seat_pointer.c:382] button_count=1 grab_serial=0 serial=7
00:00:02.739 [DEBUG] [types/seat/wlr_seat_pointer.c:382] button_count=0 grab_serial=7 serial=8
00:00:03.221 [DEBUG] [types/seat/wlr_seat_pointer.c:382] button_count=1 grab_serial=7 serial=9
00:00:03.291 [DEBUG] [types/seat/wlr_seat_pointer.c:382] button_count=0 grab_serial=9 serial=10
00:00:03.799 [DEBUG] [types/seat/wlr_seat_pointer.c:382] button_count=1 grab_serial=9 serial=11
00:00:03.901 [DEBUG] [types/seat/wlr_seat_pointer.c:382] button_count=0 grab_serial=11 serial=12
00:00:04.393 [DEBUG] [types/seat/wlr_seat_pointer.c:382] button_count=1 grab_serial=11 serial=13
00:00:04.495 [DEBUG] [types/seat/wlr_seat_pointer.c:382] button_count=0 grab_serial=13 serial=14
Full logs: https://gist.github.com/carlsmedstad/927061b62b8127a7687e6ee17495c63a
The rest of the logs look identical too, which makes sense since that commit does not affect any logging to my knowledge.
It does however break mouse interaction with blockets for me.
Sway Version:
Debug Log:
Configuration File: https://github.com/carlsmedstad/dotfiles/blob/master/.config/sway/config
Description:
swaymsg reload
a couple of times it starts working again.I've been able to narrow it down to the commit c22caa54 and with that commit reverted my issue is solved.
To reproduce, use i3blocks together with a mouse-interactable blocklet such as medialplayer.