This is just crazy. I've been having this problem since 12.04.... 12.10...13.04... and now 13.10. Each time, I hope for a resolution. This means that for approaching two years, my keyboard settings have been resetting on each computer I own. An old Thinkpad x41, a newer x61 and my desktop, a homebuilt AMD.
This is Unity on 13.10.
This includes Alt-<1-9> for desktop switching.
Alt instead of Super for window moving.
Alt-W for gnome-terminal (a custom shortcut - I can't use the built in terminal short-cut because it doesn't allow configuring the window size and position).
At this point, I think my options are:
1. switch to gnome-shell (not sure if this will work)
2. switch to KDE (horrors)
3. buy a Mac (talk about limiting my UI)
4. Get frustrated enough to figure out your code and fix it myself, not that I have the foggiest idea of how to approach it but I'm getting to that point.
5. Just implement the start-up script workaround and forget about it.. leave it broken. I should have done this a long time ago (assuming it'll work). This is probably my next likely step.
It would be much easier if you just fixed it. Please. Please. Please.
This is just crazy. I've been having this problem since 12.04.... 12.10...13.04... and now 13.10. Each time, I hope for a resolution. This means that for approaching two years, my keyboard settings have been resetting on each computer I own. An old Thinkpad x41, a newer x61 and my desktop, a homebuilt AMD.
This is Unity on 13.10.
This includes Alt-<1-9> for desktop switching.
Alt instead of Super for window moving.
Alt-W for gnome-terminal (a custom shortcut - I can't use the built in terminal short-cut because it doesn't allow configuring the window size and position).
At this point, I think my options are:
1. switch to gnome-shell (not sure if this will work)
2. switch to KDE (horrors)
3. buy a Mac (talk about limiting my UI)
4. Get frustrated enough to figure out your code and fix it myself, not that I have the foggiest idea of how to approach it but I'm getting to that point.
5. Just implement the start-up script workaround and forget about it.. leave it broken. I should have done this a long time ago (assuming it'll work). This is probably my next likely step.
It would be much easier if you just fixed it. Please. Please. Please.