Locked keyring makes Evolution Mail unable to work

[SilviaIreneM]

Windows Version

Microsoft Windows [Ver 10.0.26100.2314]

WSL Version

2.3.26.0

Are you using WSL 1 or WSL 2?

• WSL 2
• WSL 1

Kernel Version

5.15.167.4-1

Distro Version

Ubuntu 24.04

Other Software

Starting evolution Mail, I'm able to get access to IMAP mail but it doesn't keep the password; in ews mail (office365), I get

Failed to obtain access token from address “https://login.microsoftonline.com/**[MSTenant_here]**/oauth2/v2.0/token”: Object does not exist at path “/org/freedesktop/secrets/collection/login”

Running seahorse, is clearly missing Login keyring and if I try to add it I get

Couldn't add keyring - no such secret collection at path /

Keyring is locked and there's no way to unlock it.

On older wsl installation (kernel 5.10.16.3) everything was working properly.

Partially workarounded by disabling systemd in /etc/wsl.conf but I think is just a workaround, not a fix, that'why I'm filing this issue (workaround comes from WSL crashes when building application #12238)

Repro Steps

install wsl2
install Ubuntu 24.04
install Evolution Mail, seahorse
launch Evolution (see above)
lauch Seahorse (see above)

editing /etc/wsl.conf putting systemd=false in place of systemd=true workarounds the issue

Expected Behavior

launch Evolution and Seahorse and having them correctly working (or, better, having keyring unlocked

Actual Behavior

see above

Diagnostic Logs

WslLogs-2024-12-17_15-16-08.zip

[github-actions]

Logs are required for review from WSL team

If this a feature request, please reply with '/feature'. If this is a question, reply with '/question'.
Otherwise please attach logs by following the instructions below, your issue will not be reviewed unless they are added. These logs will help us understand what is going on in your machine.

How to collect WSL logs

Download and execute collect-wsl-logs.ps1 in an administrative powershell prompt:

Invoke-WebRequest -UseBasicParsing "https://raw.githubusercontent.com/microsoft/WSL/master/diagnostics/collect-wsl-logs.ps1" -OutFile collect-wsl-logs.ps1
Set-ExecutionPolicy Bypass -Scope Process -Force
.\collect-wsl-logs.ps1

The script will output the path of the log file once done.

If this is a networking issue, please use collect-networking-logs.ps1, following the instructions here

Once completed please upload the output files to this Github issue.

Click here for more info on logging
If you choose to email these logs instead of attaching to the bug, please send them to [email protected] with the number of the github issue in the subject, and in the message a link to your comment in the github issue and reply with '/emailed-logs'.

View similar issues

Please view the issues below to see if they solve your problem, and if the issue describes your problem please consider closing this one and thumbs upping the other issue to help us prioritize it!

Closed similar issues:

• System Keyring Access Issues in WSL2 (#10265), similarity score: 0.73
• enabling systemd makes evolution think it is offline (#9027), similarity score: 0.70

Note: You can give me feedback by thumbs upping or thumbs downing this comment.

[github-actions]

Diagnostic information

Issue was edited and new log file was found: https://github.com/user-attachments/files/18167013/WslLogs-2024-12-17_15-16-08.zip
.wslconfig found
Detected appx version: 2.3.26.0

[sirredbeard]

Is gnome-keyring-daemon running?

What if you manually create a keyring with secret-tool store --label='login' --password?