| Summary: | Discover crashes when I close it after an update. | ||
|---|---|---|---|
| Product: | [Applications] Discover | Reporter: | Eduardo Baldino <eduardo> |
| Component: | discover | Assignee: | Plasma Bugs List <plasma-bugs-null> |
| Status: | RESOLVED FIXED | ||
| Severity: | crash | CC: | aleixpol, j.rebitz, nate |
| Priority: | NOR | ||
| Version First Reported In: | 5.24.7 | ||
| Target Milestone: | --- | ||
| Platform: | Kubuntu | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | 5.25 | |
| Sentry Crash Report: | |||
| Attachments: |
KDE Crash Handler screen shots
KDE Crash Handler screen shots (the right ones) Try to backtrace the discover close after update bug Reproduced bug backtrace |
||
|
Description
Eduardo Baldino
2022-11-28 12:45:45 UTC
If something crashed, we need a backtrace of it so we can figure out what's going on. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports. Can you please attach one? Thanks! Created attachment 154146 [details]
KDE Crash Handler screen shots
As I tried (poorly) to explain in the original post, the KDE Crash Handler does not generate a backtrace. I have attached the Crash Handler screens. Now, if you want me figure out by myself how to install debug symbol packages, figure out by myself which one I should install, install it, and then figure out by myself how to manually get a backtrace, then I'm sorry I tried to help. It doesn't look like you got to the page with the backtrace. You have to keep clicking next. Created attachment 154152 [details]
KDE Crash Handler screen shots (the right ones)
"You have to keep clicking next." Wow. I'll forgive you condescension, but only because I did screw up when saving the images, and ended up posting repeated images. I've posted updated images. > A useful backtrace could not be generated Then the bug report isn't actionable, I'm afraid. Without a backtrace, there's no way for developers to debug the issue. If you'd like to make it actionable, you can try installing debug symbols for Discover and its backends. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports#Ubuntu-based_distros_.28Ubuntu.2C_Kubuntu.2C_KDE_Neon.2C_Linux_Mint.29 Ideally this wouldn't be necessary, but unfortunately not all distros make it easy. 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! Created attachment 157385 [details]
Try to backtrace the discover close after update bug
Same here for me. I have tried to create my first backtrace. I will make another backtrace with the next update possibility to get clearer error messages if necessary. Created attachment 157501 [details]
Reproduced bug backtrace
Thanks! Unfortunately the backtrace looks to be deep in Qt in the Javascript engine. Coupled with the fact that this bug is reported against Plasma 5.24 which is no longer in support due to the 5.27 LTS being released, I don't think there's anything we can do here, sorry. :/ I am saddened by the lengths to which you guys go to avoid doing the work... Hej Nate, thanks for the hint with the unsupported Plasma 5.24. I have now installed Plasma 5.25. from the (k)ubuntu backports and lo and behold, wonderful, the error is fixed. Cheers, Johannes Fabulous, thanks for following up! |