tag:blogger.com,1999:blog-6112936277054198647.post8782642693717588379..comments2024-03-12T00:42:06.642+10:00Comments on Who-T: XKB breaking grabs - CVE-2012-0064Peter Huttererhttp://www.blogger.com/profile/17204066043271384535noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-6112936277054198647.post-53535644518636520522015-05-29T05:34:26.591+10:002015-05-29T05:34:26.591+10:00Wouldn't it be better to bring back an API to ...Wouldn't it be better to bring back an API to control this, though, as requested at ? Apps go haywire like this all too often, and you shouldn't have to choose between debugging apps that take grabs and screensaver locking, anyway.<br /><br />Though even if that were done, it would be important to wait for screensavers to actually use it before flipping the default for grab:break_actions, since the XF86Misc extensions itself is obviously not going to be reintroduced, so screensavers would need to be adapted to check for and use the new thing.SamBhttps://www.blogger.com/profile/06560268240719951351noreply@blogger.comtag:blogger.com,1999:blog-6112936277054198647.post-82813027247233492282015-04-14T17:00:13.421+10:002015-04-14T17:00:13.421+10:00Nice post, thanks for the info!
While experimenti...Nice post, thanks for the info!<br /><br />While experimenting with the grab:break_actions option I noticed an oddity - it only seems to take effect if run within the actual graphics environment.<br /><br />ie. if I run the following in an xterm:<br /><br /># reset options to default set<br />$ setxkbmap -option -option ctrl:nocaps -option terminate:ctrl_alt_bksp<br /><br />$ xkill& sleep 1; setxkbmap -option grab:break_actions<br /><br />Xkill grabs the cursor, then after one second setkxbmap runs and I can press ctrl-alt-/ to clear xkill's grab.<br /><br />However if run xkill by itself and switch to a different virtual terminal to run 'setxkbmap -display :1 -option grab:break_actions', when I switch back to my X display ctrl-alt-/ has no effect.<br /><br />My DISPLAY is definitely :1, and I can see the option has been set via 'setxkbmap -query' - it just doesn't _work_ until I set the option from within the graphical environment itself.<br /><br /><br />I just thought of another test while writing this - if I ssh into the machine and run setxkbmap -display :1 that way while xkill has a grab, ctrl-alt-/ works as expected. Seems like the x server needs to be visible when setxkbmap runs - does that sound like a bug or is there a rational explanation I'm not aware of?<br /><br />-sqweek<br />sqweekhttps://www.blogger.com/profile/14378512713887720261noreply@blogger.com