Bug 458309

Summary: Broken access to kwallet after login
Product: [Frameworks and Libraries] frameworks-kwallet Reporter: pipapo <piral>
Component: generalAssignee: Valentin Rusu <valir>
Status: RESOLVED DUPLICATE    
Severity: normal CC: kdelibs-bugs, mk.mateng, nicolas.fella
Priority: NOR    
Version: 5.97.0   
Target Milestone: ---   
Platform: Neon   
OS: Linux   
Latest Commit: Version Fixed In:
Attachments: Some output while log into an account

Description pipapo 2022-08-25 18:12:53 UTC
Created attachment 151589 [details]
Some output while log into an account

SUMMARY
***
After upgrade from 5.96.0 to 5.97.0 kwallet needs long time to start and is asking for the passphrase to open the standard wallet. Applications like kmail/nextcloud are not getting their password for their accounts automatically.
***

STEPS TO REPRODUCE
1. Login to plasma session

OBSERVED RESULT
kwallet starts slow and can't provide passwords to applications

EXPECTED RESULT
Applications get passwords seamlessly.

SOFTWARE/OS VERSIONS
Operating System: KDE neon 5.25
KDE Plasma Version: 5.25.4
KDE Frameworks Version: 5.97.0
Qt Version: 5.15.5
Graphics Platform: Wayland

ADDITIONAL INFORMATION
Same results occurs for a new user account. Some suspicious lines from syslog when log in.
Comment 1 Nicolas Fella 2022-08-25 19:49:40 UTC
> Some suspicious lines from syslog when log in.

What lines are suspicious?
Comment 2 pipapo 2022-08-25 20:10:19 UTC
(In reply to Nicolas Fella from comment #1)
> > Some suspicious lines from syslog when log in.
> 
> What lines are suspicious?

Sorry, relevant instead of suspicious maybe a better expression. I tried to extract something helpfull.
I'm not an expert and I'm ready to assist for further, helpful debuging.
Comment 3 michaelk83 2022-08-26 08:37:31 UTC
Probably a duplicate of https://bugs.kde.org/show_bug.cgi?id=458085
Comment 4 Nicolas Fella 2022-08-26 10:39:18 UTC

*** This bug has been marked as a duplicate of bug 458085 ***
Comment 5 pipapo 2022-09-16 11:32:26 UTC
With the upgrade to 5.98 everything is working fine again. Many thanks to all involved developers!