Created attachment 895884 [details] emerge --info This segfault occurs immediately after launching nheko or after clicking a few ui elements. I have built both qtbase and nheko with debug flags and attached a backtrace of nheko. It appears the issue is with libQt6Gui.so.6
Created attachment 895885 [details] nheko backtrace
i'm not able to reproduce this. however, i use glibc and gcc. it has been suggested in chat that the problem might be the same as in <https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=3b4f3c13ff83e5a9b0470252393279b02c323d7f> could you try rebuilding sys-libs/libcxx and sys-libs/libcxxabi with MYCMAKEARGS="-DLIBCXX_TYPEINFO_COMPARISON_IMPLEMENTATION=1" in package.env[1] before rebuilding dev-qt/qtbase? [1] <https://wiki.gentoo.org/wiki//etc/portage/package.env>
ping @ray - can you try that out or did the problem fix itself for you?
Sorry for the belated response. We had a conversation over matrix in the gentoo room with parona. It was concluded that this fix wasn't something that would help in my case so I didn't bother trying it. It has been a while since then and a few packages have been updated. However, I do get a few crashes here and there, maybe it's the same issue or a different issue entirely but I would have to upload another backtrace. Kind regards,
Created attachment 897672 [details] nheko backtrace 2 Here is another backtrace that I have just obtained after using nheko for a few minutes.
Not sure if the guru's maitnainer want this bug, but given it was assigned to qt@ I'll just go ahead and close this for now (feel free to keep discussing it though). This package isn't in ::gentoo and I'm not aware of this affecting anything else at the moment. This sound more like something that should be analyzed upstream. There's also no telling whether is really a Qt regression (could've been working by accident with UB given the type of error, happens that bumps end up exposing such issues). If it is, should ideally be reported to Qt's upstream, then maybe we'll get a fix to backport.
(if feeling adventurous, could try qtbase-6.7.9999 in case it may be already fixed, or even 6.8.9999 albeit that one may be more broken, don't even bother with 6.9999 -- 6.7.3 is not due until August 30 or later, and 6.8 late September).
