Bug 153202 - Mouse Settings not save changes
Summary: Mouse Settings not save changes
Status: RESOLVED WORKSFORME
Alias: None
Product: systemsettings
Classification: Applications
Component: kcm_mouse (show other bugs)
Version: 3.96.2
Platform: Compiled Sources Linux
: NOR normal
Target Milestone: ---
Assignee: Marie Loise Nolden
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-12-01 04:10 UTC by Teddy Widhi Laksono
Modified: 2009-01-01 14:08 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Teddy Widhi Laksono 2007-12-01 04:10:42 UTC 
Version:            (using KDE Devel)
Installed from:    Compiled sources
Compiler:          GCC Mandriva 2008 
OS:                Linux

Its look after i change the mouse setting in SystemSettings, for example i try to change Double-Click to open files radio button. after i logout the KDE and re-login again, the changes not saved.
Comment 1 Bill Egert 2008-01-05 17:19:20 UTC 
I can confirm this using 4.00.80 compiled from svn.

Every time I login I need to re-adjust my Pointer Acceleration mouse settings.

Compiled on Kubuntu.
Comment 2 Martin Klapetek 2008-01-13 10:02:25 UTC 
Same here, version 4.0 installed on Fedora 8 from rpms.
Comment 3 Bill Egert 2008-02-11 01:16:02 UTC 
Problem still exists as of Rev 773072.

From the looks of it, if I use whole values they work.  A setting of 0.7 does not.  The value is definitely being saved in the config file, it just doesn't want to read it.
Comment 4 Bill Egert 2008-02-11 02:06:51 UTC 
Fix committed at rev 77342
Comment 5 David Geiger 2008-07-06 22:35:47 UTC 
Problem still exists in 4.0.4 version shipped with openSUSE 11.0.
Whole values actually do work - thanks for the hint. However, the set value is correctly stored in kcminputrc.
Comment 6 FiNeX 2008-12-31 14:55:50 UTC 
Cannot reproduce on current trunk (~4.2 beta2).

Are you still experiencing this bug?
Comment 7 Martin Klapetek 2008-12-31 16:48:55 UTC 
No, it's been ok since like 4.1 beta release.