Created attachment 173712 [details] loading screen SUMMARY After launching NeoChat it gets totally stuck on the initial loading screen STEPS TO REPRODUCE 1. Open NeoChat OBSERVED RESULT Stuck on loading screen EXPECTED RESULT Able to login/see chats SOFTWARE/OS VERSIONS Operating System: KDE neon 6.0 KDE Plasma Version: 6.0.4 KDE Frameworks Version: 6.3.0 Qt Version: 6.7.0 Kernel Version: 6.5.0-35-generic (64-bit) Graphics Platform: Wayland Processors: 4 × AMD A8-9600 RADEON R7, 10 COMPUTE CORES 4C+6G Memory: 14.6 GiB of RAM Graphics Processor: AMD Radeon R7 Graphics ADDITIONAL INFORMATION
how long did you wait on that screen? in how many rooms is your account (roughly)?
(In reply to Tobias Fella from comment #1) > how long did you wait on that screen? in how many rooms is your account > (roughly)? I left it open for about an hour, 2 rooms. I just opened it and showed a message: "access token was not found..." closed and opened again and the message was not showed again.
🐛🧹 ⚠️ 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!
When neochat gets stuck here, it's because it can't get the access token. This usually means that either something about your setup is broken (e.g., no kwallet or other backend for qtkeychain), that the access token was deleted, etc., so not errors in neochat itself. NeoChat should certainly do a better job at showing these errors, but that's surprisingly difficult :/
(In reply to Tobias Fella from comment #4) > When neochat gets stuck here, it's because it can't get the access token. > This usually means that either something about your setup is broken (e.g., > no kwallet or other backend for qtkeychain), that the access token was > deleted, etc., so not errors in neochat itself. > > NeoChat should certainly do a better job at showing these errors, but that's > surprisingly difficult :/ So, even if the bug is not in Neochat itself, there should be at least some timeout and then a message, so probably is worth keeping this open for it. Let me know where in the code is this and I can do something about it.