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 675672 - Abnormal HD activities when chosing keyboard sensitivities
Abnormal HD activities when chosing keyboard sensitivities
Status: RESOLVED DUPLICATE of bug 646764
Product: gnome-control-center
Classification: Core
Component: Keyboard
3.4.x
Other Linux
: Normal normal
: ---
Assigned To: Control-Center Maintainers
Control-Center Maintainers
Depends on:
Blocks:
 
 
Reported: 2012-05-08 12:07 UTC by SebastienManen
Modified: 2013-04-03 10:05 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description SebastienManen 2012-05-08 12:07:17 UTC 
Hello, 

I found this bug in gnome control center. In the keyboard section of the gnome-control-center when you modify any parameters you will ear some high I/O on the disk.

This is also the case for the mouse properties. This is not the case for the sound section (balance).

OS : ubuntu 12.04

uname -a :
Linux pangolin 3.2.0-24-generic-pae #37-Ubuntu SMP Wed Apr 25 10:47:59 UTC 2012 i686 i686 i386 GNU/Linux

If you want more information, feel free to ask.
Comment 1 André Klapper 2012-05-08 12:26:05 UTC 
Why do you consider this a bug?
Did you report this to Ubuntu's bugtracker?
Comment 2 SebastienManen 2012-05-08 12:51:09 UTC 
In my opinion the disk should not write each time we change keyboard properties. It should wait that the user release the mouse button to store the final value. It seems to be what's done in the sound properties.

Yes it's been reported to ubuntu teams :
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/996392
Comment 3 Bastien Nocera 2013-04-03 10:05:37 UTC 
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.

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