The migration script does not seem to check for conflicts. I had a setting for CTRL-F1 before, and apparently the (new?) defaults for xfwm4 bind CTRL-F1 to switch to the first workspace. But even if I double click on my shortcut, and set it again to be CTRL-F1, I don't get a conflict. Same for CTRL-F2 (which I had also bound to a shortcut before migration). For CTRL-F3 I do get a conflict though.
I'm not really interested in fixing this in the migration script... since conflict resolution is the job of the shortcuts code, this should be fixed there, I'd say. Even if it can't notify the user of a shortcut conflict for stuff set by the migration script, it should at least fail gracefully and not do something weird when you try to change it yourself.
I see it this way: Support the user in migrating from 4.4 to 4.6 is definitely nice. But in many cases it won't work. The keyboard shorcuts work fine if you stick to using the GUI. The system is not written with this kind of situation in mind. I'm not really considering this a bug, it's more like a design decision. Maybe not the best one but still.
Thing is, though, I'm not sure how this would happen if your kbd shortcuts didn't *already* have conflicts. The migration script just reads out your currently-active xfwm4 keytheme and the currently-active shortcuts theme (via MCS), and stuffs everything in Xfconf. So nothing should be "lost" here -- if all your shortcuts worked and had no conflicts before, they should continue to be that way. If there were conflicts before and you didn't notice or couldn't be arsed enough to fix them, then, well, you still have conflicts.
Oh, I see. I just reread David's initial comment. That is kinda weird, though, that resetting the shortcuts in the GUI doesn't always generate a conflict dialog. Jannis, any ideas?
(In reply to comment #4) > Oh, I see. I just reread David's initial comment. That is kinda weird, > though, that resetting the shortcuts in the GUI doesn't always generate a > conflict dialog. Jannis, any ideas? Hm. It should work. I just tried with <Ctrl>F1 and I got a conflict. Not really sure what to say about this. No keybinding is treated in a special way.
So it seems that if there was a conflict before, then the application shortcuts took precedence. Maybe the migration script can take that into account, as the conflict was not something the user actually observed before. It's all kinda hard to reproduce this, since I didn't save my 4.4 config. I'll see if I can't get some additional info in from a VM installation.
No, if there's a conflict already, what takes precedence depends on how fast xfwm4 starts up in relation to how fast xfce4-settings-helper starts up. You can't say, really. Didn't save 4.4 config? Well, did you specifically *delete* your 4.4 config? If not, it's still there...
*** This bug has been marked as a duplicate of bug 4695 ***