Summary: | Skanlite crashed on window change when displaying scan output. | ||
---|---|---|---|
Product: | [Plasma] kwin | Reporter: | Roke Julian Lockhart Beedell <4wy78uwh> |
Component: | general | Assignee: | KWin default assignee <kwin-bugs-null> |
Status: | RESOLVED WORKSFORME | ||
Severity: | crash | Keywords: | drkonqi |
Priority: | NOR | Flags: | 4wy78uwh:
performance-
4wy78uwh: Wayland- 4wy78uwh: X11+ 4wy78uwh: Intel- 4wy78uwh: NVIDIA- |
Version: | 5.27.10 | ||
Target Milestone: | --- | ||
Platform: | openSUSE | ||
OS: | Linux | ||
URL: | https://download.opensuse.org/repositories/openSUSE:/Factory/standard/x86_64/skanlite-23.08.4-2.2.x86_64.rpm | ||
See Also: | https://bugs.kde.org/show_bug.cgi?id=480917 | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Roke Julian Lockhart Beedell
2024-02-05 19:24:07 UTC
> https://bugs.kde.org/show_bug.cgi?id=480916#c0
Very strangely, it turns out that Skanlite didn't actually crash in any apparent way — my output window is still there, and I was able to save the output. I don't know why DrKonqi reported that it had crashed. I don't know how to triage this now.
The backtrace lacks debug symbols, without them it's unclear where kwin crashed. Can you install debug packages for kwin and submit a new backtrace? when you do that, please also reset bug report status (In reply to Vlad Zahorodnii from comment #2) > The backtrace lacks debug symbols, without them it's unclear where kwin > crashed. Can you install debug packages for kwin and submit a new backtrace? > when you do that, please also reset bug report status The problem is that zypper says none are unavailable, although it turns out that I have the biggest (Qt6) update I've ever had yet to do, so I'll do that first. However, your documentation on how to retroactively reproduce a backtrace is really confusing for me — I'm still used to GNOME abrt, which makes it a button press. 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! (In reply to Vlad Zahorodnii from comment #2) I'm guessing that since I don't know how to reproduce it, I would need to install the debug symbols and then extract the old trace via coredumpctl? |