Bug 371867 - KDE Wallet is pushy
Summary: KDE Wallet is pushy
Status: RESOLVED WORKSFORME
Alias: None
Product: kwalletmanager
Classification: Applications
Component: general (show other bugs)
Version: 16.08
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: Valentin Rusu
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-10-30 14:59 UTC by stefano.d
Modified: 2022-12-26 05:20 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 stefano.d 2016-10-30 14:59:18 UTC
KDE Wallet is pushing itself for every service.
When I start Chrome the first time after rebooting, KDE Wallet wants my password and I don't know why. When I press cancel, KDE Wallet just appears in the next moment. This game continues until I enter my password.
Know, I service called kded5 (I don't even know this service!) asked with KDE Wallet my password. Same game: I click cancel and it appears again until I enter my password.
I think I have the same problem with KMail (not using anymore) and VPN.

To make it clear: I don't want to use it! I *NEVER* asked for! And I don't had any similar problems with Gnome.

I want it to be quiet by default. This should be possible, because other desktops don't have this problem.

KDE folks: A desktop has to be quiet! I want just to work! I don't want to spent hours to set up my desktop for a normal workflow how I know it from other desktops.

I'm using Fedora 23 with Plasma 5.7.5
Comment 1 stefano.d 2016-10-30 17:42:12 UTC
Sorry, I can't edit my report.

"Know, I service called kded5 " should be "Now, a service called kded5 ...".
Comment 2 Christoph Feck 2016-11-02 03:58:18 UTC
- You can create a wallet with an empty password. But then the wallet file is not encrypted.
- You can use kwallet-pam extension to automatically use the user password to unlock/decrypt the wallet file. You might need to ask in a forum of your distribution to set it up.
- for network passwords, you can configure connections to work system-wide, but then the netword password might be stored unencrypted.
Comment 3 stefano.d 2016-11-02 06:22:15 UTC
Actually I reported this, because I wanted a good default behaviour.
I want to install Linux for my girlfriend on her PC and I don't want to tell her, that she has to spend hours to configure her PC until it works how she expects it.
So, if this is really the solution, I will recommend her Gnome.
Comment 4 Christoph Feck 2016-11-02 14:24:10 UTC
The default behavior favors security over simplicity, in other words, you need to supply a password to unlock/decrypt the content stored in the wallet.

If your distribution does not setup kwallet-pam extension by default, you could search for a distribution that does. This is not something that can be decided by KDE developers.
Comment 5 Justin Zobel 2022-11-26 00:13:46 UTC
Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version?

If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!
Comment 6 Bug Janitor Service 2022-12-11 05:06:47 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 7 Bug Janitor Service 2022-12-26 05:20:40 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!