Version: Qt: 4.5.3 KDE: 4.3.2 (KDE 4.3.2) KDE su: 1.0 (using KDE 4.3.2) OS: Linux Installed from: Mandriva RPMs According to : khelpcenter help:/kdesu/configuration.html the configuration of password timeout should be set in kcmkdesu. This does not seem to exist, so how can the timeout be set?
there is a Timeout option in the [Passwords] section of kdesurc. there is obviously no kcmkdesu, so this is apparently outdated documentation (or the feature was never actually implemented).
>there is a Timeout option in the [Passwords] section of kdesurc. OK - so where is that? >there is obviously no kcmkdesu Why is this obvious? I am just a user trying to use kdesu as intended and following the documentation as it exists. > so this is apparently outdated documentation > (or the feature was never actually implemented). OK, but I am still no wiser. Where is kdesurc ? It does not exist on my system. (According to Dolphin "find file") I am currently running KDE 4.5.2
$HOME/.kde/share/config/kdesurc you can just run kwriteconfig --file kdesurc --group Passwords --key Timeout <value> the value is in seconds; the default are two hours.
(In reply to comment #3) > $HOME/.kde/share/config/kdesurc > > you can just run > kwriteconfig --file kdesurc --group Passwords --key Timeout <value> > the value is in seconds; the default are two hours. Thanks - that now works correctly in kde-4.3.5 and it does now remember the password and not ask again. However, in kde-4.5.2 and above the kdesu binary does not appear to exist, so that launchers made with "run as different user" checked, use a "kde su" dialog without the "remember password" option. [baz@jackodesktop ~]$ kdesu bash: kdesu: command not found [baz@jackodesktop ~]$ whereis kdesu kdesu: [baz@jackodesktop ~]$ plasma-desktop --version Qt: 4.7.0 KDE Development Platform: 4.5.2 (KDE 4.5.2) Plasma Workspace: 0.3 What has happened to kdesu ?
kde4 doesn't install kdesu into the user's path at all (that decision may be revised; reports already exist). if anything changed for you recently, then only because your distributor changed something or you changed the distribution method as a whole. but that's unrelated and doesn't belong into this report.
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.