Created attachment 159574 [details] Elisa core dump SUMMARY *** The Flatpak version of Elisa (running on a Kinoite 38.20230609.0 host) produces a segmentation fault every time it is ran. Debug info generated by `flatpak-coredumpctl app/org.kde.elisa/x86_64/stable`: Program terminated with signal SIGSEGV, Segmentation fault. #0 QQmlRefPointer<QQmlTypePrivate const>::QQmlRefPointer (other=..., this=0x7f33f49fcc60, this@entry=0x7f33f49fcbe0) at ../../include/QtQml/5.15.9/QtQml/private/../../../../../src/qml/qml/ftw/qqmlrefcount_p.h:152 152 ../../include/QtQml/5.15.9/QtQml/private/../../../../../src/qml/qml/ftw/qqmlrefcount_p.h: Directory not empty. The entire output is attached in case I missed something important. *** STEPS TO REPRODUCE 1. Run `flatpak run org.kde.Elisa` OBSERVED RESULT Elisa exists with SIGSEGV. EXPECTED RESULT Elisa starts normally. SOFTWARE/OS VERSIONS Linux: Kinoite 38.20230609.0, Flatpak 1.15.4-1.fc38, Kernel 6.3.6-200.fc38.x86_64 KDE Plasma Version (host): 5.27.5 KDE Frameworks Version (host): 5.106.0 Qt Version (host): 5.15.9 Flatpak runtime: org.kde.Platform/x86_64/5.15-22.08 Flatpak SDK: org.kde.Sdk/x86_64/5.15-22.08 ADDITIONAL INFORMATION Elisa Flatpak commit: 8a797c047cb29f0b4a2094c78dd58d9778c80505f4ebe8c8bc6175c7909a12d7
Can you attach the backtrace of the crash? The attachment doesn't seem to include that information.
(In reply to Nate Graham from comment #1) > Can you attach the backtrace of the crash? The attachment doesn't seem to > include that information. When running the application, it produced no output whatsoever, I only got a SIGSEGV exit status. After running `flatpak-coredumpctl app/org.kde.elisa/x86_64/stable` I got the attached output, nothing more. Unfortunately, that is all the information I managed to gather at the time. Shortly after filing this report, I installed the flatpak from the Fedora repo, which fixed the issue (and now that I think about it, I really should've left a comment about it to help narrow down the cause). I've just now tried to reproduce the issue by reinstalling the Flathub version and rolling it back to the specific commit, but this time it started without issue. I don't have a snapshot from that time period, so I can't test the specific host-flatpak combination again.
Ok, thanks anyway!