On Fri, 2008-04-11 at 02:19 +0000, mrklean wrote: > Hmmmmmmm..a bug not worth fixing ?? Doesn't that sound like Microsoft > ??? I thot we were different ; ((
"We" are different because "we" provide the fix. > > Tom Jaeger wrote: > > I think I was wrong about libxklavier. I don't actually know where the > > changes to the keyboard settings are applied, it's probably some gconf > > backend, who knows? That's not the point, the point is that if I can > > work around the issue by typing xmodmap -e "remove Lock = Caps_Lock" > > before reassigning Caps Lock, then it must be trivial to fix - if you > > know the codepaths involved. It boggles the mind that the problem is > > still around 4 months after the initial report. Theres more trivial (or more important) bugs then this still open after more then 4 months. at lest this one has someone interested in fixing it :) kk > > ** Attachment added: "unnamed" http://launchpadlibrarian.net/13347506/unnamed -- Caps lock LED changes state even when caps lock is mapped to ctrl https://bugs.launchpad.net/bugs/173350 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
