Bug 499690 - Neochat never recovers lost connection
Summary: Neochat never recovers lost connection
Status: RESOLVED WORKSFORME
Alias: None
Product: NeoChat
Classification: Applications
Component: General (other bugs)
Version First Reported In: 24.12.2
Platform: Flatpak Linux
: NOR normal
Target Milestone: ---
Assignee: Tobias Fella
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2025-02-08 18:50 UTC by Tanguy Fardet
Modified: 2025-03-12 03:47 UTC (History)
3 users (show)

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 Tanguy Fardet 2025-02-08 18:50:07 UTC 
SUMMARY

Once the connection is lost, NeoChat never seems to be able to recover and the "NeoChat is offline. Please check your network connection." banner stays up forever.


STEPS TO REPRODUCE
1. Open NeoChat
2. Disconnect network connection and wait for banner
3. Reconnect network connection

OBSERVED RESULT

Banner stays on, new messages are never fetched

EXPECTED RESULT

Connection is recovered.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Kernel 6.11.0, Wayland
KDE Plasma Version: 6.2.5
KDE Frameworks Version: 6.10.0
Qt Version: 6.8.1
Comment 1 Justin Zobel 2025-02-10 09:10:43 UTC 
I'm also using the 24.12.2 version from Flatpak/Flathub and I can't replicate this issue. If you do this test in a busy room, disconnect, reconnect and leave the windows for 60 seconds, does it disappear?
Comment 2 Bug Janitor Service 2025-02-25 03:46:51 UTC 
🐛🧹 ⚠️ This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information, then set the bug status to REPORTED. If there is no change for at least 30 days, it will be automatically closed as RESOLVED WORKSFORME.

For more information about our bug triaging procedures, please read https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging.

Thank you for helping us make KDE software even better for everyone!
Comment 3 Bug Janitor Service 2025-03-12 03:47:30 UTC 
🐛🧹 This bug has been in NEEDSINFO status with no change for at least 30 days. Closing as RESOLVED WORKSFORME.