Bug 201658 - kwallet pops up requesters that kde-dienst (KDE-daemon/service) wants access.
Summary: kwallet pops up requesters that kde-dienst (KDE-daemon/service) wants access.
Status: RESOLVED UNMAINTAINED
Alias: None
Product: akregator
Classification: Applications
Component: general (show other bugs)
Version: SVN
Platform: Debian testing Unspecified
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-07-27 13:50 UTC by M G Berberich
Modified: 2017-01-07 22:04 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 M G Berberich 2009-07-27 13:50:43 UTC
Version:            (using KDE 4.2.4)
Installed from:    Debian testing/unstable Packages

If I enter twitter into akregator or add the twitter-plasmoid everey few minutes requesters pop up, saying that the kde-daemon want's access to the wallet. 

a) This information is absolutely useless, because it neither says which application needs the access, nor what for.

b) Why do applications in KDE4 not remember passwords any more.
Comment 1 Michael Leupold 2009-07-27 14:15:55 UTC
Please only file one issue per bug report.

a) this is a duplicate of bug 180504
b) What do you mean? Do you allow access to the wallet when the dialog pops up?
Comment 2 M G Berberich 2009-07-27 14:39:24 UTC
a) possible.

b) The requester pops up every few minutes, allowing access does not prevent it to pop up again. It seems that the application is not remembering the password, but asking kwallet every time it accesses the source.
Comment 3 Michael Leupold 2009-07-27 14:45:55 UTC
Please go to the wallet configuration in systemsettings, and screenshot the contents of the "Access Control" tab (with all of the treeview expanded) so I can see what's going on there.
Comment 4 M G Berberich 2009-07-27 14:58:40 UTC
There is only one entry.
···············································
- kdewallet
    +- Dienstprogramm für Digitale Brieftasche    Immer zulassen
···············································

which means that kwalletmanager is the only application that is allowed to access the wallet always (without asking).
Comment 5 Michael Leupold 2009-07-27 15:01:48 UTC
Ah, now I get it. You press "Ask again" on the wallet dialog right? If so this is a bug in the respective applications because they try to re-read the password from the wallet.
Comment 6 M G Berberich 2009-07-27 15:53:59 UTC
probably

the requester states, that the „respective application“ is the kde-daemon.
Comment 7 Michael Leupold 2009-07-27 16:00:45 UTC
KDE-Daemon means that the kioslave which gets the information from the network requests the password using kpasswdserver (which is part of kded4). The problem is that kpasswdserver only caches passwords for a short period of time, so the applications using it should cache the password themselves. I'll reassign to the applications you mentioned.
Comment 8 Dima Ryazanov 2013-02-26 00:06:56 UTC
Not sure if this is the same bug or not, but I'm seeing this behavior in KDE 4.9.4. Every few minutes, I get a dialog box saying:

The application 'KDE Daemon' has requested to open the wallet 'kdewallet'. Please enter the password for this wallet below.

I just installed Ubuntu a few days ago and have made minimal customizations, so this is basically the default KDE behavior. In my opinion, this is a pretty terrible user experience.
Comment 9 Christophe Marin 2013-03-03 20:46:53 UTC
Doesn't look related to akregator. You may check which applications are started on your computer when this message appears
Comment 10 Denis Kurz 2016-09-24 19:42:27 UTC
This bug has only been reported for versions before 4.14, which have been unsupported for at least two years now. Can anyone tell if this bug still present?

If noone confirms this bug for a Framework-based version of akregator (version 5.0 or later, as part of KDE Applications 15.08 or later), it gets closed in about three months.
Comment 11 Denis Kurz 2017-01-07 22:04:38 UTC
Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.0 aka 15.08), please open a new one unless it already exists. Thank you for all your input.