| Summary: | PlasmaShell crashed on log in, with inconsistent QPalette focus states in DrKonqi, after ANR'ing before (and during) the previous logout | ||
|---|---|---|---|
| Product: | [Plasma] plasmashell | Reporter: | Roke Julian Lockhart Beedell <4wy78uwh> |
| Component: | generic-crash | Assignee: | Plasma Bugs List <plasma-bugs-null> |
| Status: | RESOLVED NOT A BUG | ||
| Severity: | crash | CC: | kdedev |
| Priority: | NOR | Keywords: | drkonqi |
| Version First Reported In: | master | ||
| Target Milestone: | 1.0 | ||
| Platform: | Fedora RPMs | ||
| OS: | Linux | ||
| See Also: |
https://bugzilla.redhat.com/show_bug.cgi?id=2411800 https://bugs.kde.org/show_bug.cgi?id=507936 |
||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | https://crash-reports.kde.org/organizations/kde/issues/290964/events/e3f7b4bc9a3041c6a0b388b850eb46fa/ | ||
| Attachments: |
New crash information added by DrKonqi
A Screenshot Of The Inconsistent Window A Screencast That Demonstrates The Inconsistency Of The Window's Colour Scheme Upon Selection |
||
|
Description
Roke Julian Lockhart Beedell
2025-11-09 17:33:51 UTC
Created attachment 186651 [details]
New crash information added by DrKonqi
DrKonqi auto-attaching complete backtrace.
Also reported downstream, at https://bugzilla.redhat.com/show_bug.cgi?id=2411800#c13 (and https://retrace.fedoraproject.org/faf/reports/bthash/8f3a9f4163dbe16a68020d15987a236acdb5c56e, for P6M). Created attachment 186652 [details] A Screenshot Of The Inconsistent Window Apologies about the blur. See https://bugs.kde.org/show_bug.cgi?id=510982#c6. Created attachment 186654 [details]
A Screencast That Demonstrates The Inconsistency Of The Window's Colour Scheme Upon Selection
I have attached the screencast, as I aforestated.
Comment on attachment 186654 [details] A Screencast That Demonstrates The Inconsistency Of The Window's Colour Scheme Upon Selection Perhaps, this inconsistent appearance correlates with https://discuss.kde.org/t/settings-day-night-cycle-isnt-working/41524?u=rokejulianlockhart, if this bug caused it. Thanks for the bug report! Unfortunately it reports multiple distinct issues, which will make it not actionable. See https://community.kde.org/Get_Involved/Issue_Reporting#Multiple_issues_in_a_single_Bugzilla_ticket for more explanation. The crash has the same backtrace as bug 507936, and doesn't need to be reported again. Can I ask you to submit a new bug report for each specific issue that isn't the crash? Thanks again! (In reply to TraceyC from comment #6) > Thanks for the bug report! Unfortunately it reports multiple distinct > issues, which will make it not actionable. See > https://community.kde.org/Get_Involved/ > Issue_Reporting#Multiple_issues_in_a_single_Bugzilla_ticket for more > explanation. > > Can I ask you to submit a new bug report for each specific issue that isn't > the crash? Thanks again! Thanks, too. However, I was only really reporting the crash, unless you think that the other information is actionable, considering that I don't see a way to reproduce it. I'm a little wary to file bugs that'll likely be closed as WAITINGFORINFO, since I presume it's not a great use of your time. > The crash has the same backtrace as bug 507936, and doesn't need to be > reported again. Got any ideas on how to tell what it is before I report? Abrt tells me when a trace matches something I've already reported, but Konqi doesn't. Unless I just don't report ANRs for PlasmaShell, I'm not sure how to tell whether one's a Mesa bug or not. I can't really read traces. (In reply to Roke Julian Lockhart Beedell from comment #7) > Thanks, too. However, I was only really reporting the crash, unless you > think that the other information is actionable, considering that I don't see > a way to reproduce it. I'm a little wary to file bugs that'll likely be > closed as WAITINGFORINFO, since I presume it's not a great use of your time. Thank you for being considerate. If you can find a way to reliably reproduce the theming issue with Dr Konqi, it would be worth reporting. Without a way to reproduce, I'm afraid you're right, we wouldn't be able to do much. > > The crash has the same backtrace as bug 507936, and doesn't need to be > > reported again. > > Got any ideas on how to tell what it is before I report? Abrt tells me when > a trace matches something I've already reported, but Konqi doesn't. Unless I > just don't report ANRs for PlasmaShell, I'm not sure how to tell whether > one's a Mesa bug or not. I can't really read traces. Unfortunately, the only way to tell if a crash is the same as another is to read the backtrace. In the case of this and the other report, the backtraces are identical, if you were interested in seeing how we compare. They are an excellent example to learn from. We also have a howto on reading the backtraces, if you're interested https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging/Identifying_duplicates#Identifying_duplicates_(crashes)_:_C++_Backtraces |