If I define alt-f5 (for example) shortcut for maximizing window, this setting is not saved when xfwm4 is restarted. Steps to reproduce: 1 - run xfwm4-settings 2 - go to keyboard -> Maximize window and define alt-f5 as shortcut 3 - alt-f5 works ok now 4 - restart xfwm4 5 - alt-f5 no longer works, even while xfwm4-settings show that Maximize window is configured to alt-f5. If I redefine it to alt-f5 again, it works.
Works just fine here, tested on two different installations. Make sure no other application is not grabbing the key combo, try with some other key combination, does it work?
Any other combinations present the same behavior: they work fine until I restart xfwm4. After that, they are not working anymore, and the default alt-f10 key is working for maximizing instead. Strangely enough, the modified keys still appear in xfwm4-settings window. Besides, if I click on 'Clear' on the 'maximize window' entry, the following message appears in the terminal: (xfwm4-settings:18613): xfconf-WARNING **: Error check failed at IA__xfconf_channel_reset_property():694: Property "/xfwm4/custom/<Alt>F10" does not exist on channel "xfce4-keyboard-shortcuts" And it appears each time I click on 'Clear'. Could it be related? It all only happens with maximize window, other actions (for example, maximize vertically or horizontally) are all working fine.
That's really weird, what does xfconf-query give? xfconf-query -c xfce4-keyboard-shortcuts -vl
Created attachment 2133 xfconf-query when alt-f5 is not working This is what xfconf-query gives me when alt-f5 is not working for maximizing window. If I try maximizing Terminal, the following is printed: ";3~"
Created attachment 2134 This is result of xfquery when alt-f5 is working. This is result of xfconf-query when alt-f5 is working for window maximizing.
I don't know if it would help, but I am running X server 1.5.99.3.
For the output "xfquery_not_working": /xfwm4/custom/<Alt>F10 maximize_window_key ... /xfwm4/custom/<Alt>F5 maximize_window_key That should not happen, the keyboard shortcut manager should prevent that. Jannis, any idea on how/why this happen?
(In reply to comment #7) > For the output "xfquery_not_working": > > /xfwm4/custom/<Alt>F10 maximize_window_key > ... > /xfwm4/custom/<Alt>F5 maximize_window_key > > That should not happen, the keyboard shortcut manager should prevent that. > > Jannis, any idea on how/why this happen? It shouldn't happen. The only situation where I think it could happen is when migrating from one version of Xfce to another (like from beta2 to beta3). But still, it's odd. Whenever you change a shortcut from the GUI, the shortcut is first removed and then added again with the new action. This avoids having something like the above. However, if you're using xfconf-query or xfce4-settings-editor to change shortcuts, this will not work properly. Something similar may happen when migrating, but I'm not really sure about that.
Strangely enough, it still happens with 4.6.0 final.. I managed to workaround it manually by running: xfconf-query -c xfce4-keyboard-shortcuts -p "/xfwm4/custom/<Alt>F10" -s "" I don't know what causes the problem to appear though, I only used the xfwm4-settings to edit the keybindings.
same here. It seems to me that when the global config and the user config are merged together, "empty" isn't handled correctly. Instead of overwriting the value from the global config, it is ignored. When using an empty string ("") instead as Eugeni suggested, the value from the global config is replaced.
Can you check if the migration script is started? If so, can you disable it (it should not run more than once).
I am also seeing this bug. Xfce 4.6.1. It happens with my Switch to Workspace 2 keybinding, it keeps getting rebound to <alt> randomly during my session. I have found that killing xfce4-settings-helper stops this from happening, but also stops any of my keyboard shortcuts defined in Keyboard settings from working. If I restart xfce4-settings-helper, it rebinds Workspace 2 to <alt> immediately (It still shows up as <Super>F2 in my Window Manager Keyboard settings).
*** This bug has been marked as a duplicate of bug 4695 ***