By default, Bugzilla does not search the list of RESOLVED bugs.
You can force it to do so by putting the upper-case word ALL in front of your search query, e.g.: ALL tdelibs
We recommend searching for bugs this way, as you may discover that your bug has already been resolved and fixed in a later release.
Bug 431 - KDE forgets certain keyboard settings
Summary: KDE forgets certain keyboard settings
Status: NEW
Alias: None
Product: TDE
Classification: Unclassified
Component: tdeaccessibility (show other bugs)
Version: 3.5.13.x [Trinity]
Hardware: i386 Linux
: P5 major
Assignee: Timothy Pearson
URL:
Depends on: 850
Blocks:
  Show dependency tree / graph
 
Reported: 2011-02-03 00:25 CST by Luc
Modified: 2018-05-27 11:12 CDT (History)
3 users (show)

See Also:
Compiler Version:
TDE Version String:
Application Version:
Application Name:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Luc 2011-02-03 00:25:03 CST 
I use a netbook that I can carry around, but I plug an external keyboard to it when I'm at home. The netbook has a US International keyboard, the keyboard at home is Brazilian, ABNT2 layout. Whenever I plug/unplug the keyboard and switch layouts, I lose my Repeat Delay/Rate configuration, so the keyboard feels a little bit slow. So I have to open Control Center, Peripherals, Keyboard, readjust the delay and click OK. The number never seems to have changed, but the keyboard definitely feels different. Redoing the config fixes it, but it's obviously annoying. I also have to do that ritual every time I boot/reboot/log out.

I also have my Esc and Caps Lock keys swapped. Sometimes KDE forgets that too, although a lot less often.

I wish KDE would remember all those keyboard settings, they are very important to me. None of the mouse settings ever seems to get lost across sessions or reboots.
Comment 1 Julius Schwartzenberg 2012-02-07 17:18:46 CST 
I have this problem as well. To reproduce:

1. Boot a notebook with an external keyboard already plugged in and try moving the cursor around in a large document with the cursor keys.

2. Unplug the external keyboard (or boot a notebook without an external keyboard plugged in) and plug the external keyboard in. Then try moving the cursor around again in a large document. It will seem very inconvenient compared to the first attempt now.
Comment 2 Timothy Pearson 2012-02-07 17:47:23 CST 
This bug, along with the infamous numlock bug, need the still-to-be-written TDE udev interface library to be properly fixed.  See http://trinitydesktop.org/wiki/bin/view/Developers/TUComputerAPI for the specification.

In short, TDE does not handle device hotplugging in a sane manner.  Trying to hack around the problem will not help and risks introducing more bugs; the best and safest solution is to implement true systemwide hotplug support for TDE via the above library specification.
Comment 3 Aleksey Midenkov 2014-05-16 05:11:16 CDT 
You don't need udev library here and moreover MUST NOT use it, because Xorg configuration and udev devices are two different things. Xorg can ignore some devices after all.

You may wish to catch some events from Xorg which will notify you about keyboard state change:

PropertyNotify event, serial 14, synthetic NO, window 0x3a5,
    atom 0x126 (_XKB_RULES_NAMES), time 301157, state PropertyNewValue

PropertyNotify event, serial 15, synthetic NO, window 0x3a5,
    atom 0x126 (_XKB_RULES_NAMES), time 303685, state PropertyNewValue

Though these are not very informative, you may wish to find a better ones. Look at XkbNewKeyboardNotify, it may become useful here.

http://www.x.org/releases/X11R7.6/doc/libX11/specs/XKB/xkblib.html#xkb_event_types