4 ms·
I have to take issue with your comment on keyboard use, because that single wart is dealbreaker keeping me from using Ubuntu. I give Ubuntu another shot every
by chao- 14y ago
I have to take issue with your comment on keyboard use, because that single wart is dealbreaker keeping me from using Ubuntu.
I give Ubuntu another shot every X.10 release just to see if they've finally made the desktop environment satisfactory, and I must say they are getting really, really close. The Menu system is getting close to making sense in Unity, Pulseaudio throws fewer temper tantrums, significantly less hardware issues, and everything is much snappier (especially compared to memories of Unity from its Ubuntu Netbook Remix days).
But I can't customize my keybindings for crap.
And you're probably thinking "That's BS, of course you can! It's under [submenu] of [menu] of [option] of [settings application name]." And you'd be right. It's just that some subset of keybindings will reset to their defaults every time you do a full power-down of the computer. Rinse and repeat until they're all back to their defaults.
It varies which hotkeys will be reset. Sometimes Metacity ones will reset. Sometimes GNOME bindings will reset. Sometimes opening the Unity configuration will reset the Metacity keys. Sometimes it doesn't! I even wrote a shell script to run all the proper `gsettings set org.gnome.desktop.interface [blah]` incantations upon login, but when that didn't work reliably (again: Metacity keybindings vs. Unity appeared to be the problem) I gave up.
This has been my experience in Ubuntu 11.10, some mid-2012 version of Mint (with Cinnamon) and Ubuntu 12.10, so it's not strictly Canonical's fault. However they haven't seen fit to address it in their user experience, and so I portion out a slice of the blame for them.
- illumen 14y agoGreat bug report :) Hopefully someone from Canonical will see this, and can send it to the appropriate people!
- qznc 14y agoIt is not a great bug report. The response will probably be "works for me". A great bug report specifies exactly how to reproduce a certain behavior and also specifies the expected behavior, what should have happened.
- chao- 14y agoIt is not a great bug report. In fact, as qznc states, it's not a bug report at all. However, in my weeklong attempts to deal with the issue, I came across a few formal bug reports submitted to various projects. If I recall correctly, and since the issue is a fight between two different application components that wish to manage keybindings, the bug reports had responses of the "It's not our fault, it's the other package!" variety.