User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.0.1) Gecko/20060313 Debian/1.5.dfsg+1.5.0.1-4 Firefox/1.5.0.1 Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.0.1) Gecko/20060313 Debian/1.5.dfsg+1.5.0.1-4 Firefox/1.5.0.1 When I run xfce-show-setting in 4.4beta1 and assign ALT-F1 through ALT-F4 to go to workspace 1 through 4, ALT-F3 and ALT-F4 work fine. ALT-F1 seems hardcoded to bring up help. ALT-F2 seems hardcoded to bing up the run dialogue. Despite the settings plugin showing that they should be taking me to a particular workspace. Reproducible: Always Steps to Reproduce:
This isn't a bug. Open the Keyboard settings dialog (xfce-setting-show keyboard); the Shortcuts tab, and add a new keyboard shortcuts theme. Now you can remove the shortcuts for Alt+F1 and Alt+F2.
As pointed by Stfan, you need to disable Alt-F1 and Alt-F2 in the general keyboard shortcut editor to be able to use these in xfwm4.
Hmm, ok. I can see that this does indeed work as you've said once I do that. Can I suggest at the least that you warn if you're about to specify a key that the shortcut editor already has bound or that (ideally and yes, I realise this is probably a bit late for 4.4) the xfwm4 keyboard setup is merged with the shortcut editor some how, possibly into its own settings plugin. I imagine users will find having two places to set keypresses quite confusing.
Merging xfwm4 shortcuts with general launcher shortcuts wouldn't help as the key might also be grabbed by any other application running on the display (ie not just the WM, but any client application can grab keys)...
Right, but having all the Xfce managed shortcuts in one place would be less confusing to users. I predict that I'll have to deal with Debian users tripping over this in future is all. If you don't want to merge them then that's fair enough; I just wanted to put the case for merging them to you. I think some people have always found it a bit odd that from the settings dialogue when you click on keyboard you can't manage the xfwm4 key bindings.
Is there a way to catch this when the shortcut is assigned? Like will XGrabKey() fail (or something)?
Yeah... the XGrabKey() manpage says: BadAccess A client attempted to grab a key/button combination already grabbed by another client. So can't we just catch BadAccess errors and warn the user the key combo is already used?
Hmhm, it seems the check for BadAccess() stuff is still not integrated? It'd be nice if the Keyboard Settings and Xfwm4 settings were able to check if a shortcut is already taken before setting it. I can't reopen it, but I don't think it can be considered as fixed currently. I can't change the subject either, but would rename it to: “No warning when trying to add a shortcut if it's already taken”. Do you want me to open another bug, or should we stick with this one? Cheers,