Bug 446643 - Plasma panels and desktop are blocked from appearing until a KDED module that wants to access the a password in the wallet is able to do so
Summary: Plasma panels and desktop are blocked from appearing until a KDED module that...
Status: RESOLVED WORKSFORME
Alias: None
Product: plasmashell
Classification: Plasma
Component: general (show other bugs)
Version: 5.23.4
Platform: Arch Linux Linux
: NOR normal
Target Milestone: 1.0
Assignee: David Edmundson
URL:
Keywords: usability
Depends on:
Blocks:
 
Reported: 2021-12-07 21:05 UTC by Wolfgang Mader
Modified: 2023-05-27 03:45 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
kwallet dialog block plasma panel (1.68 MB, image/jpeg)
2021-12-07 21:05 UTC, Wolfgang Mader
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Wolfgang Mader 2021-12-07 21:05:55 UTC
Created attachment 144328 [details]
kwallet dialog block plasma panel

SUMMARY
I have a password-less automatic login from SDDM to plasma desktop. Thus, on first login, kwallet is closed since no credentials have been passed yet. Consequently, kwallet password dialog pops up as the first thing after login in order to retrieve the password for wifi. However, until I respond to that dialog the plasma panel is not shown, see attachment.

STEPS TO REPRODUCE
1. Set up a password-less automatic login.
2. Set up something that needs an open kwallet right from the start, e.g. a wifi you automatically log into.
3. It could be important that the password request comes from a plasma panel citizen. I could imaging that not kwallet itself block the plasma panel, but the guy living in the panel who waits for his password request call to return.
4. Start your machine and watch the password dialog pop-up.
5. Observe that the plasma panel is not drawn.

OBSERVED RESULT
Plasma panel is only drawn after the password dialog has been completed.


EXPECTED RESULT
Plasma panel should come up w/o being blocked from the password dialog.

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 
KDE Frameworks Version: 
Qt Version: 

ADDITIONAL INFORMATION
Comment 1 Nate Graham 2021-12-08 16:58:00 UTC
Weird interaction with kwallet for sure. Is it possible to have a passwordless wallet? If so, then ideally the lack of both passwords would match and the wallet would be automatically unlocked at login.

However given that you have a passwordless user account, clearly security isn't a concern, so you can work around this by setting up your wifi network to save its password for all users in cleartext. This bypasses KWallet, so KWallet won't try to open on login so that it can connect to wifi.
Comment 2 Nate Graham 2023-04-27 22:27:11 UTC
I know a it more about this issue now. As of Plasma 5.27, now when you set up auto-login, you'll see a message telling you to remove the password for your wallet (which is totally possible and will work around this issue). Clearly if you're doing auto-login, then local security isn't a factor and it should be safe to have a passwordless wallet too.

However the issue is probably still valid even given that, since we can't guarantee that the wallet will be automatically unlocked on login.

I'm a bit surprised though, since I've never seen plasmashell get blocked by a kded module that's waiting for its password. It's a shame it doesn't tell you specifically which kded module is waiting.

Any chance you can upgrade to Plasma 5.27, not apply the workaround I specified (or un-apply it), and then try again?
Comment 3 Bug Janitor Service 2023-05-12 03:46:03 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 4 Bug Janitor Service 2023-05-27 03:45: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!