After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 585222 - Key repeat and speed settings gets lost
Key repeat and speed settings gets lost
Status: RESOLVED DUPLICATE of bug 610245
Product: gnome-settings-daemon
Classification: Core
Component: plugins
2.26.x
Other All
: Normal normal
: ---
Assigned To: gnome-settings-daemon-maint
gnome-settings-daemon-maint
: 594138 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2009-06-09 08:12 UTC by Emanuel Indermühle
Modified: 2010-10-13 14:40 UTC
See Also:
GNOME target: ---
GNOME version: 2.25/2.26



Description Emanuel Indermühle 2009-06-09 08:12:01 UTC
Please describe the problem:
After restart or after a night with "screen locked" the keyboard
is not acting as the settings specify.

When opening keyboard-settings window, it shows the sliders on the right position, but the keyboard is not acting this way. When i slightly move the sliders, the settings are applied again. 

Steps to reproduce:
1. change keyboard settings to a noticable difference from default setting.
2. restart or wait with "screen locked" for a night


Actual results:
Keyboard setting is not applied any more.


Expected results:
Keyboard setting should be applied.

Does this happen every time?
not sure

Other information:
Comment 1 Emanuel Indermühle 2009-06-09 08:20:42 UTC
I restarted the computer a minute ago. The setting didn't get lost. 
I think I have to investigate a little more to find out when it actually happens.
Comment 2 Emanuel Indermühle 2009-06-09 08:30:12 UTC
I created this bug when I noticed I had a similar problem as it was report in ubuntu bug 383397: https://bugs.launchpad.net/bugs/383397
Comment 3 daniel 2009-06-09 11:30:23 UTC
I reported the report on Ubuntu (https://bugs.launchpad.net/bugs/383397). I have observed the behaviour in relation to hibernating/waking my laptop. Specifically (copied from launchpad report):

The "Repeat Keys" settings under gnome-keyboard-properties (menu System --> Prefererences --> Keyboard) are consistently lost after my laptop running up-to-date Ubunty Jaunty wakes up from hibernate.

Specifically:
1. I set the key repeat speed to fast (80% on slider).
2. Key repeats are set and working correctly.
3. Hiberate laptop.
4. Wake up laptop.
5. Key repeats are not set (back to slow default).
6. Open up keyboard preferences and move slider one pixel up and one pixel back down.
7. Key repeats now set again and working correctly.

I have not yet tested whether other settings are affected but the key repeats behaviour is 100% repeatable.

PS I'm running Ubuntu Jaunty with the gnome-control-center on version 1:2.26.0-0ubuntu3.

Hope this helps.

Let me know if you need anything else.
Comment 4 Jens Granseuer 2009-06-10 17:46:50 UTC
Sounds a lot like bug 564687, but that should have been fixed a while ago.
Comment 5 Emanuel Indermühle 2009-06-12 10:07:36 UTC
Today it happened again: 
The Screen was locked for a day. After unlocking it, the keyboard repeat frequency was again set to default value. The settings in the gnome-panel-settings instead show the customized values. Changing them a little bit return the correct keyboard behavior.
Comment 6 Jens Granseuer 2009-09-04 14:21:34 UTC
*** Bug 594138 has been marked as a duplicate of this bug. ***
Comment 7 Oliver Joos 2010-01-28 13:45:20 UTC
I added an upstream report with details about this bug on:
https://bugs.freedesktop.org/show_bug.cgi?id=26293

This bug has 5 duplicates on launchpad.net (see https://bugs.launchpad.net/bugs/427168). So please consider to raise its importance and to reopen its duplicate bug 594138.

IMHO a fix might involve Gnome because gconf is where keyboard rate and delay are stored persistently.
Comment 8 Bastien Nocera 2010-02-17 13:38:02 UTC
Seems like a dupe of bug 610245, which has a patch.
Comment 9 Bastien Nocera 2010-10-13 14:40:18 UTC
Will mark this as a duplicate of bug 610245. Please reopen this bug if the patch in the other bug didn't fix your problem.

*** This bug has been marked as a duplicate of bug 610245 ***