Bug 38270 - apply button does not always save settings
Summary: apply button does not always save settings
Status: RESOLVED WORKSFORME
Alias: None
Product: kcontrol
Classification: Miscellaneous
Component: kcmscreensaver (show other bugs)
Version: 2.0
Platform: Mandrake RPMs Linux
: NOR normal
Target Milestone: ---
Assignee: kscreensaver bugs tracking
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2002-02-17 16:18 UTC by spearminator
Modified: 2008-06-18 22:53 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description spearminator 2002-02-17 16:12:15 UTC
(*** This bug was imported into bugs.kde.org ***)

Package:           kcmscreensaver
Version:           2.0 (using KDE 2.2.1 )
Severity:          normal
Installed from:    Mandrake Linux Vitamin
Compiler:          gcc version 2.96 20000731 (Mandrake Linux 8.1 2.96-0.62mdk)
OS:                Linux (i686) release 2.4.8-26mdk
OS/Compiler notes: 

When I try to change my screen saver settings in KDE Control Center I hit apply but the settings don't take effect.  I know this because when I restart KDE Control the settings are the same as before.  I don't know if this is a Control Center problem or specifically a screen saver config problem.

I've also noticed that occasionally the applied settings stick but more often than not they don't.

(Submitted via bugs.kde.org)
(Called from KBugReport dialog)
Comment 1 Jean-D. Ackle 2002-12-31 17:43:23 UTC
I have noticed the same as to settings that don't always stick.  In my case,   
using KDE 3.0.3 in Mandrake Linux 9.0 (iso image install), and with one   
particular module: the Login Manager in KDE Control Center.  Specifically, it   
does keep the changes to who can halt and reboot the machine on the console (  
Sessions tag) and which users to display (Users tag) but it doesn't last for 
more than two or three logout-login processes.  Then it is automatically reset 
to the preset values. 
jeanackle@mail.pt 
Comment 2 Maksim Orlovich 2003-01-06 21:10:43 UTC
Jean: It's quite possible that msec is messing with those settings.  
Comment 3 Matt Rogers 2003-11-26 04:48:47 UTC
this has worked for me in CVS HEAD for quite some time now. No need to keep it around. :)