@Kevin: It is difficult to decide where to report this bug. But I agree, we should do this. @radostyle: glad to hear it works for you, too! Whether the problems with modmap files are related or not, we should treat this bug isolated, because the fixes might be different.
IMHO xset is a candidate to fix: 1 xset r rate 300 36 , unplug/replug keyboard , xset q => delay,rate=660,25 2 after replugging external keyboard becomes 660,25, but internal one stays at 300,36 3 replugging while in a console (ctrl+alt+F1) doesn't change anything - unless I switch to X (ctrl+alt+F7)! 4 xset r rate 300 39 , xset q => 300,40 (this is perhaps a hardware limitation) But this all looks like xset stores the values in the keyboard hardware only and sometimes chooses the wrong (external) one to read them from. If that's right then only gconftool-2 stores these values reliably. Then an udev-rule calling gconftool-2 would be a valid fix, if that's possible at all. I found a solution for a similar issue here: http://ubuntuforums.org/archive/index.php/t-1282582.html Anyway if you agree, I will report this issue to gnome.org AND freedesktop.org with links to each other, so that well-informed people can help to decide where to fix it. -- usb keyboard settings reset on plugin https://bugs.launchpad.net/bugs/427168 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
