Bug 161966

Summary: KDEsu does not remember if the user wants it to remember root password or not
Product: [Applications] kdesu Reporter: Adam Jimerson <vendion>
Component: generalAssignee: kdesu bugs tracker <kdesu-bugs-null>
Status: CONFIRMED ---    
Severity: normal CC: bluedzins, finex, petr
Priority: NOR    
Version First Reported In: unspecified   
Target Milestone: ---   
Platform: openSUSE   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:

Description Adam Jimerson 2008-05-11 19:44:36 UTC
Version:            (using KDE 3.5.9)
Installed from:    SuSE RPMs
Compiler:          i586-suse-linux 
OS:                Linux

Ever sense the ability to let KDEsu remember the root password has been introduced into KDE 3, everytime I launch a program that needs my root password I have to unclick the "Remember Password" check box.  This is starting to get annoying and I don't want to accidentally let it remember my root password.  I think this works in KDE4, which is nice.
Comment 1 FiNeX 2008-05-12 13:21:04 UTC
Bug confirmed on 3.5.9.
Comment 2 Adam Jimerson 2008-05-27 04:59:31 UTC
So is there a way to get KDEsu to forget the root password?  Out of late night stupidity I forgot to uncheck the "Remember Password" option and now even though I don't want it to it is remembering my root password.
Comment 3 Maciej Pilichowski 2008-06-09 18:28:31 UTC
Kdesu should provide the same behaviour as Konqueror+kwallet. There is no point in having several mechanism for the same thing.

In other words -- please use kwallet and ask the user only at first entry of new user.
Comment 4 Pino Toscano 2008-06-10 11:00:08 UTC
*** Bug 163682 has been marked as a duplicate of this bug. ***
Comment 5 Bram Schoenmakers 2008-09-07 14:48:09 UTC
*** Bug 163639 has been marked as a duplicate of this bug. ***
Comment 6 Oswald Buddenhagen 2010-11-06 21:48:05 UTC
somebody seems to have flipped the default, but the value is still not remembered.
Comment 7 Justin Zobel 2021-03-09 23:42:29 UTC
Thank you for the bug report.

As this report hasn't seen any changes in 5 years or more, we ask if you can please confirm that the issue still persists.

If this bug is no longer persisting or relevant please change the status to resolved.