https://bugs.kde.org/show_bug.cgi?id=489644
RedBearAK <redb...@redbearnet.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|NOT A BUG |---
Status|RESOLVED |REOPENED
Ever confirmed|0 |1
--- Comment #2 from RedBearAK <redb...@redbearnet.com> ---
(In reply to Nate Graham from comment #1)
> > Sometimes a dialog appears after Plasmashell crashes, and I submit the
> > crash report each time
> Thanks for that. Since the crash reports are already automatically
> submitted, I'm not sure there's anything actionable for us here — especially
> because it happens on a franken-system with GNOME and Plasma both installed.
> It's not that this is invalid, but... there be dragons. Neither the GNOME
> nor KDE developers are testing this configuration or have any interest in
> formally supporting it. It's a niche of a niche of a niche of a niche.
>
> Thanks again for the automatic crash reports!
I appreciate all that you do to make KDE better, Nate. But I will always
disagree with the idea that it is unimportant to find out why one of your own
pieces of software, especially things as central as the shell and KWin, is
allowing itself to go nuts on the CPU and then core dump just because a GTK app
user deletes some text and then later quits the GTK app. I don't think the
"fraken-system" status is ever going to be a good excuse not to take a close
look at such things. There do be dragons, but each individual desktop
environment and all its components should endeavor to be resilient even in a
mixed environment. Especially when everyone is moving toward things like
Flatpak, where more than half the apps available are probably GTK-based.
After all, it was not the GTK app that was using up CPU and crashing. It was
Plasmashell (and kwin_wayland, although I'm not aware of KWin ever crashing,
and can't tell which of the two is reacting to the other during the high CPU
usage). The lack of resilience is obviously somewhere in Plasmashell. The GTK
app was just the trigger.
If there are additional logs that would help and aren't included in the
automatic report, I can try to attach them.
I'll also try to remember to come back here and update if the issue goes away
with 6.1.2 or some other coming update on Tumbleweed. Perhaps you can let this
stay open at least for a week or so before abandoning the idea of finding out
why it is happening, just because the system also has some GNOME packages
installed.
--
You are receiving this mail because:
You are watching all bug changes.
