Bug 481701

Summary:	Neochat segfaults immediately upon opening the program
Product:	[Applications] NeoChat	Reporter:	Adam Fontenot <adam.m.fontenot+kde>
Component:	General	Assignee:	Tobias Fella <fella>
Status:	RESOLVED DUPLICATE
Severity:	crash	CC:	carl, duha.bugs
Priority:	NOR	Keywords:	qt6
Version First Reported In:	24.01.95
Target Milestone:	---
Platform:	Arch Linux
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:
Attachments:	crash traceback

Description Adam Fontenot 2024-02-22 22:13:51 UTC

Created attachment 166029 [details]
crash traceback

SUMMARY

Neochat segfaults immediately upon opening the application, without any interaction.

STEPS TO REPRODUCE
1. Log into your account (username, password) using Neochat.
2. Search for a room and join the room (I clicked on a couple of KDE rooms). Neochat immediately crashed for me, with no backtrace. That's probably Bug 479735.
3. Open Neochat again.

OBSERVED RESULT
Segfault. Backtrace is *not* similar to 479735, I see a crash in `QJsonObject`.

EXPECTED RESULT
No segfault.

SOFTWARE/OS VERSIONS
Operating System: Arch Linux 
KDE Plasma Version: 5.93.0
KDE Frameworks Version: 5.249.0
Qt Version: 6.7.0
Kernel Version: 6.7.4-arch1-1 (64-bit)
Graphics Platform: Wayland

Comment 1 duha.bugs 2024-02-23 14:24:40 UTC

(In reply to Adam Fontenot from comment #0)

> 1. Log into your account (username, password) using Neochat.
> 2. Search for a room and join the room (I clicked on a couple of KDE rooms).
> Neochat immediately crashed for me, with no backtrace. That's probably Bug
> 479735.

This is likely https://bugs.kde.org/show_bug.cgi?id=478229

Comment 2 Adam Fontenot 2024-02-23 14:30:12 UTC

(In reply to duha.bugs from comment #1)
> This is likely https://bugs.kde.org/show_bug.cgi?id=478229

It's possible but the traceback is very different. I crash in libQuotient, whereas that library is not in the two backtraces for the bug you linked.

Maybe I'll copy my traceback over to the Gitlab in case it's useful there.

Comment 3 Tobias Fella 2024-02-23 19:17:19 UTC

Yes, this is that bug, it just manifests in a different way.

*** This bug has been marked as a duplicate of bug 478229 ***