| Summary: | Discover crashed when I searched "nuclear" and clicked the button to remove nuclear music app | ||
|---|---|---|---|
| Product: | [Applications] Discover | Reporter: | armoire.mountable405 |
| Component: | discover | Assignee: | Plasma Bugs List <plasma-bugs-null> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | crash | CC: | aleixpol, nate |
| Priority: | NOR | Keywords: | drkonqi |
| Version First Reported In: | 5.27.3 | ||
| Target Milestone: | --- | ||
| Platform: | Flatpak | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
armoire.mountable405
2023-04-03 14:40:31 UTC
Thank you for the bug report! Unfortunately I can't reproduce the crash myself on current git master, and the backtrace is incomplete and missing debug symbols for the following lines that we need to figure out exactly what's going wrong: > #4 0x00007ff40c4bc2f0 in () at /usr/lib64/qt5/plugins/discover/flatpak-backend.so > #5 0x00007ff42db88163 in TransactionListener::qt_metacall(QMetaObject::Call, int, void**) () at /usr/lib64/plasma-discover/libDiscoverCommon.so Could you please install debug symbols for Discover and its Flatpak backend package, reproduce the crash, and attach a new symbolicated backtrace? See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports for details about how to do this. Thanks again! (In reply to Nate Graham from comment #1) > Thank you for the bug report! Unfortunately I can't reproduce the crash > myself on current git master, and the backtrace is incomplete and missing > debug symbols for the following lines that we need to figure out exactly > what's going wrong: > > > #4 0x00007ff40c4bc2f0 in () at /usr/lib64/qt5/plugins/discover/flatpak-backend.so > > #5 0x00007ff42db88163 in TransactionListener::qt_metacall(QMetaObject::Call, int, void**) () at /usr/lib64/plasma-discover/libDiscoverCommon.so > > Could you please install debug symbols for Discover and its Flatpak backend > package, reproduce the crash, and attach a new symbolicated backtrace? See > https://community.kde.org/Guidelines_and_HOWTOs/Debugging/ > How_to_create_useful_crash_reports for details about how to do this. > > Thanks again! I can't really reproduce it again myself, but I suspect it was because of X11 or the old qt. A bit of an off topic, but could you probably suggest any way to update qt for my distro (openSUSE Tumbleweed)? Tumbleweed should already have an up-to-date Qt; it's a rolling release distro. According to your bug report, you have Qt 5.15.8 which is current for Plasma. If you can't reproduce the crash, you can always install debug symbols and use `coredumpctl` to re-symbolicate the existing crash report and then paste it in here. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports#Retrieving_a_backtrace_using_coredumpctl. 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! This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now 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 Thank you for helping us make KDE software even better for everyone! |