https://bugs.kde.org/show_bug.cgi?id=474868
Nate Graham <n...@kde.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |WAITINGFORINFO
Status|REPORTED |NEEDSINFO
--- Comment #4 from Nate Graham <n...@kde.org> ---
Thanks for that gdb backtrace, it was much more helpful. There's good news and
bad news. The good news is that the backtrace shown there is a known crash
that's already been fixed! See 468430.
The bad news is that it was supposed to be fixed in 5.27.5, and you're using
5.27.7. That leaves a few options for why you might still be seeing it:
1. I've mis-identified the crash and it's not actually Bug 468430
2. Debian made a packaging boo-boo and either isn't including the commits that
fixed the crash
(https://invent.kde.org/plasma/plasma-workspace/-/commit/acbc7234937027a6cf98b173517136d4bdbdfe94
and
https://invent.kde.org/plasma/plasma-workspace/-/commit/9bea46b09e5d407697dc2cb660e72e0d538d482f)
or is somehow re-introducing it with local patching of some kind
3. Bug 468430 isn't fully fixed, and you've found a new way to trigger it.
For now I think #1 and #2 are the most likely scenario, but I judge #2 to be
likelier at this point in time. At least, it's something we should rule out.
Can you contact the Debian folks about it? Thanks a lot!
--
You are receiving this mail because:
You are watching all bug changes.
