Bug 1190346 - Thunderbird cannot connect after re-connecting to network or after resume from suspend
Summary: Thunderbird cannot connect after re-connecting to network or after resume fro...
Status: RESOLVED UPSTREAM
Alias: None
Product: openSUSE Distribution
Classification: openSUSE
Component: X11 Applications (show other bugs)
Version: Leap 15.3
Hardware: x86-64 openSUSE Leap 15.3
: P5 - None : Normal (vote)
Target Milestone: ---
Assignee: Charles Robertson
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-09-09 14:05 UTC by Alexander Krupp
Modified: 2022-08-05 16:35 UTC (History)
2 users (show)

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments
Partial TB log. From 15:25:51 on, the WLAN has been operational (7.45 KB, text/plain)
2021-09-09 14:05 UTC, Alexander Krupp
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Alexander Krupp 2021-09-09 14:05:38 UTC
Created attachment 852399 [details]
Partial TB log. From 15:25:51 on, the WLAN has been operational

Reproduction:

1) Disconnect WLAN with KDE Network Manager 
2) Start Thunderbird
3) Wait until it gives the "cannot connect" message
4) Connect WLAN with KDE Network Manager
5) Press "Get Messages" in Thunderbird
6) Expect "cannot connect" message, goto step 5) ad infinitum

The issue also occurs after resuming from suspend state, or on a fresh login where Thunderbird is auto-started in the background and KDE is waiting for wallet credentials, before it connects to a WLAN with user specific credentials. 

Sometimes Firefox exhibits the same problem, however, I did not try to reproduce this, as for me the issue with Thunderbird is far more annoying. The problem existed throughout Leap 15.2, 15.3 on this system. I have attached a TB log, slightly censored for privacy. 

Workaround:

- Restart Thunderbird
Comment 1 Alexander Krupp 2022-08-05 16:32:17 UTC
Not reproducible anymore with TB 91.11.0.
Comment 2 Alexander Krupp 2022-08-05 16:35:23 UTC
Resolved upstream, apparently.