Hi Markus, your mail was not sent to the Debian BTS. I suppose that was not intentional.
Markus Grunwald <[email protected]> writes: > They're attached. The logs reveal that dunst correctly grabs the key combination: 000:<:0032: 16: Request(33): GrabKey owner-events=true(0x01) grab-window=0x00000081 modifiers=Control key=0x41 pointer-mode=Asynchronous(0x01) keyboard-mode=Asynchronous(0x01) You can see that key 0x41, which is 65 in decimal, corresponds to the space key: keycode 65 = space space space nobreakspace KP_0 KP_0 U202F Unfortunately, there is no KeyPress event in the log, so from what I can tell, dunst does everything correctly, but just doesn’t get any input. > Hmm, yes, quite so. I have i3 running and an open urxvt. Even on a blank > workspace, the dunst message doesn't react on keypresses. > What else could steal the keys? Not too sure. Can you change the shortcuts to something somewhat obscure and see if that is working? -- Best regards, Michael -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
