Created attachment 167528 [details] Stack trace and corresponding gdb operational log and configuration. SUMMARY Discover inconsistently reproducibly segfaults, seemingly solely when interacting with the Flathub listing for Authy that is referenced in . STEPS TO REPRODUCE 1. Install cpe:/o:opensuse:tumbleweed:20240318. 2. Install https://download.opensuse.org/repositories/openSUSE:/Factory/standard/x86_64/discover6-6.0.2-2.1.x86_64.rpm. 3. Adhere to https://forum.snapcraft.io/t/installing-snap-on-opensuse/8375#add-the-repository-1. 4. Invoke "gdb plasma-discover". 5. Enable debuginfo. 6. Search for Authy. 7. Select its Flathub listing. OBSERVED RESULT It crashed once when entering the page (which I acquired the stack trace for) EXPECTED RESULT It obviously shouldn't crash. SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20240318 KDE Plasma Version: 6.0.2 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 Kernel Version: 6.7.9-1-default (64-bit) Graphics Platform: Wayland Processors: 12 × AMD Ryzen 5 7600X 6-Core Processor Memory: 30.5 GiB of RAM Graphics Processor: AMD Radeon RX 5700 Manufacturer: ASRock Product Name: X670E Taichi ADDITIONAL INFORMATION https://discuss.kde.org/t/discover-got-flatpak-and-snap-packages-confused/12740/2?u=rokejulianlockhart
(In reply to `{third: "Beedell", first: "Roke"}`{.JSON5} from comment #0) > Discover inconsistently reproducibly segfaults, seemingly solely when interacting with the Flathub listing for Authy that is referenced in . I meant to reference https://bugs.kde.org/show_bug.cgi?id=484111#c0, apologies.
(In reply to `{third: "Beedell", first: "Roke"}`{.JSON5} from comment #1) It turns out that it has no relation to that bug. The reproduction steps appear to be to merely utilize the application whatsoever, although using the search bar and then clicking on an entry appears to increase the probability to about 90% that this bug shall occur.
Created attachment 167556 [details] 0x00007ffff55d1407 in ?? () from /lib64/libQt6Core.so.6
Created attachment 167557 [details] 0x00007fffebecde27 in ?? () from /lib64/libKF6Attica.so.6
https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports Without debug symbols on attica I don't see this going anywhere.
(In reply to Harald Sitter from comment #5) Was debuginfod not enough? Apologies — I believe I've installed the corresponding packages now and shall try to reproduce it.
Created attachment 167737 [details] 0x00007fffebecde27 in Attica::BaseJob::doWork (In reply to `{third: "Beedell", first: "Roke"}`{.JSON5} from comment #6)
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
(In reply to Bug Janitor Service from comment #8) Forgot to change status after https://bugs.kde.org/show_bug.cgi?id=484109#c7.
Thanks. The code it crashes on is most strange unfortunately. We may need to make it more assertive to figure out what's going on here. In the meantime you could fetch the terminal output of QT_LOGGING_RULES="kf.attica=true" plasma-discover and then try to trigger the crash. Maybe that sheds some light on things.
(In reply to Harald Sitter from comment #10) I've installed cpe:/o:fedoraproject:fedora:40 instead, now, and this hasn't occurred yet. I think that means that I should set this as RESOLVED WORKSFORME, but do change it if you think you can somehow tackle it with the information available.