Bug 492639

Summary:	NeoChat segfaults right after starting
Product:	[Applications] NeoChat	Reporter:	Frisk <online>
Component:	General	Assignee:	Tobias Fella <fella>
Status:	RESOLVED NOT A BUG
Severity:	crash	CC:	carl
Priority:	NOR
Version First Reported In:	24.08.0
Target Milestone:	---
Platform:	Arch Linux
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:
Attachments:	valgrind output gdb output

Description Frisk 2024-09-04 08:38:35 UTC

Created attachment 173306 [details]
valgrind output

***
If you're not sure this is actually a bug, instead post about it at https://discuss.kde.org

If you're reporting a crash, attach a backtrace with debug symbols; see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
***

SUMMARY
Neochat crashes with SEGFAULT right after loading initial window that allows one to login/register/choose account to use.
Yesterday I were doing a full day of experimenting with NeoChat. After a reboot it no longer launches.

STEPS TO REPRODUCE
1. Open Neochat

OBSERVED RESULT
Neochat closes shortly after starting

EXPECTED RESULT
Neochat loads main window with rooms etc.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: EndeavourOS Linux x86_64 6.10.7-arch1-1
KDE Plasma Version: Plasma 6.1.4
KDE Frameworks Version: 6.5.0
Qt Version: 6.7.2

ADDITIONAL INFORMATION
Graphics platform: Wayland

I tried generating useful backtrace with both gdb as well as valgrind, however gdb even with debug symbols downloaded does not give a useful stacktrace:
Thread 1 "neochat" received signal SIGSEGV, Segmentation fault.
0x00005555556ccf7e in ?? ()

Comment 1 Tobias Fella 2024-09-04 13:59:25 UTC

I'm afraid without debug a backtrace with debug symbols this report isn't actionable

Comment 2 Frisk 2024-09-04 17:41:07 UTC

Created attachment 173329 [details]
gdb output

I were able to download one more debug source file somehow which allowed me to obtain what looks like actually more useful backtrace. Hope it helps!

Comment 3 Frisk 2024-09-20 22:14:46 UTC

It's possible this issue no longer exists, after recent system upgrade I restarted NeoChat and it no longer crashes making me unable to reproduce the issue. Issue possibly could be closed.

Comment 4 Tobias Fella 2024-09-21 08:19:01 UTC

Right, this doesn't seem plausible for the current behavior during login