Bug 451640 - loses all connections when another virtual console / desktop session is active
Summary: loses all connections when another virtual console / desktop session is active
Status: REPORTED
Alias: None
Product: konversation
Classification: Applications
Component: general (show other bugs)
Version: 1.8.21123
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: Konversation Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-03-18 03:00 UTC by Forest
Modified: 2022-03-18 03:00 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Forest 2022-03-18 03:00:40 UTC 
SUMMARY

I often switch between multiple X instances / desktop sessions, using Control+Alt+F7/F8 (or the Switch User feature of the desktop environment).

When I run Konversation in session 1 and switch to session 2 for 10 minutes or so, Konversation loses its network connections.

STEPS TO REPRODUCE
1. Join one or more servers & channels in Konversation.
2. Use the desktop environment's Switch User feature to enter a new desktop session.
3. Wait 11-12 minutes.
4. Switch back to the first desktop session.

OBSERVED RESULT

All IRC connections are lost, and channel tabs are grayed out. Message traffic during the time spent in the other session is presumably lost.

When returning, Konversation begins trying to reestablish the connections, showing these message in server windows:

[Error] Connection to server irc.oftc.net (port 6697) lost: The TLS/SSL connection has been closed.
[Info] Trying to reconnect to irc.oftc.net (port 6697) in 10 seconds.

EXPECTED RESULT

Konversation should not have lost its connections or missed any message traffic while the other desktop session was active.

SOFTWARE/OS VERSIONS
Linux Version: 5.16.0 and 5.10.0
KDE Plasma Version: 5.20.5
KDE Frameworks Version: 5.78.0
Qt Version: 5.15.2

ADDITIONAL INFORMATION

Tested with Konversation packages from both Debian Stable and Debian Unstable. Problem exists in both.