https://bugs.kde.org/show_bug.cgi?id=478287
Matt Fagnani <matt.fagn...@bell.net> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|WAITINGFORINFO |---
Ever confirmed|1 |0
Status|RESOLVED |REPORTED
--- Comment #10 from Matt Fagnani <matt.fagn...@bell.net> ---
(In reply to Akseli Lahtinen from comment #9)
> Hi, has this issue appeared on Fedora 40 KDE?
>
> If so, can you make sure that you have debug symbols installed and send a
> backtrace with them included?
> https://community.kde.org/Guidelines_and_HOWTOs/Debugging/
> How_to_create_useful_crash_reports#Backtraces
>
> Thanks!
I haven't seen this problem with 6.0.0-6.0.90 in Fedora 40 and Rawhide in which
I think drkonqi used the core dumps created by systemd-coredump instead of
attaching gdb directly to the crashed plasmashell processes. I don't think this
problem would happen with 6.0 and higher because the 40 s timeout before the
plasmashell.service is killed by systemd isn't a factor any longer. The 5.27
branch might still be affected, but I haven't used it in a few months.
--
You are receiving this mail because:
You are watching all bug changes.
