Bug 2329570 - Mass-crash of Plasma apps on un-docking from Thunderbolt hub
Summary: Mass-crash of Plasma apps on un-docking from Thunderbolt hub
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: plasma-workspace
Version: 41
Hardware: x86_64
OS: Linux
unspecified
urgent
Target Milestone: ---
Assignee: KDE SIG
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2024-11-29 21:16 UTC by dmakovey
Modified: 2025-12-16 17:51 UTC (History)
5 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2025-12-16 17:51:37 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
Crash sample screenshot (272.70 KB, image/png)
2024-12-04 15:02 UTC, dmakovey
no flags Details
Snippet from system log around the time of crash (422.82 KB, text/plain)
2024-12-04 15:44 UTC, dmakovey
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 2330384 0 unspecified CLOSED [abrt] powerdevil: KCrash::defaultCrashHandler(): org_kde_powerdevil killed by SIGSEGV 2025-12-16 17:57:02 UTC
Red Hat Bugzilla 2330386 0 unspecified CLOSED [abrt] kf6-kded: KCrash::defaultCrashHandler(): kded6 killed by SIGSEGV 2025-12-16 17:57:05 UTC
Red Hat Bugzilla 2330389 0 unspecified CLOSED [abrt] kactivitymanagerd: KCrash::defaultCrashHandler(): kactivitymanagerd killed by SIGSEGV 2025-12-16 17:57:07 UTC
Red Hat Bugzilla 2330390 0 unspecified CLOSED [abrt] kdeconnectd: KCrash::defaultCrashHandler(): kdeconnectd killed by SIGSEGV 2025-12-16 17:57:10 UTC
Red Hat Bugzilla 2330391 0 unspecified CLOSED [abrt] xdg-desktop-portal-kde: KCrash::defaultCrashHandler(): xdg-desktop-portal-kde killed by SIGSEGV 2025-12-16 17:57:13 UTC
Red Hat Bugzilla 2330392 0 unspecified CLOSED [abrt] plasma-workspace: KCrash::defaultCrashHandler(): baloorunner killed by SIGSEGV 2025-12-16 17:57:16 UTC
Red Hat Bugzilla 2330393 0 unspecified CLOSED [abrt] konsole: KCrash::defaultCrashHandler(): konsole killed by SIGSEGV 2025-12-16 17:57:18 UTC

Description dmakovey 2024-11-29 21:16:01 UTC
I've recently upgraded from F40 to F41 and the first thing that I've noticed that whenever I unplug my Dell Precision 5690 from Thunderbolt hub I get multiple applications crashing immediately after. I have sent in the reports, but I believe problem lies not the the crashed apps but someplace else and deserves a separate report. 

Reproducible: Always

Steps to Reproduce:
1. Login to Plasma Workspace
2. Plug-in Thunderbolt cable (charging+periferials). This step can be #1 as well 
3. Use second screen through Thunderbolt connection
4. Work a bit plugged in
5. Unplug Thunderbolt cable
Actual Results:  
multiple application crashes

Expected Results:  
No crashes

Comment 1 dmakovey 2024-12-04 15:02:42 UTC
Created attachment 2061121 [details]
Crash sample screenshot

This screenshot shows the issue. This is happening now every time I undock killing running applications etc.

Comment 2 dmakovey 2024-12-04 15:44:08 UTC
Created attachment 2061134 [details]
Snippet from system log around the time of crash

I've attempted to capture most of /var/log/messages from around the time of crash

Comment 3 dmakovey 2024-12-04 15:53:52 UTC
log inspection shows a lot of SERV terminations (Signal 11) for all applications:

Dec  4 07:30:16 gldell-5690 systemd-coredump[15437]: Process 3096 (kactivitymanage) of user 1000 terminated abnormally with signal 11/SEGV, processing...
Dec  4 07:30:16 gldell-5690 systemd-coredump[15438]: Process 3153 (xdg-desktop-por) of user 1000 terminated abnormally with signal 11/SEGV, processing...
Dec  4 07:30:16 gldell-5690 systemd-coredump[15436]: Process 3526 (kgpg) of user 1000 terminated abnormally with signal 11/SEGV, processing...
Dec  4 07:30:16 gldell-5690 systemd-coredump[15434]: Process 3466 (yakuake) of user 1000 terminated abnormally with signal 11/SEGV, processing...
Dec  4 07:30:16 gldell-5690 systemd-coredump[15431]: Process 3515 (kalendarac) of user 1000 terminated abnormally with signal 11/SEGV, processing...
Dec  4 07:30:16 gldell-5690 systemd-coredump[15439]: Process 3303 (kdeconnectd) of user 1000 terminated abnormally with signal 11/SEGV, processing...
Dec  4 07:30:16 gldell-5690 systemd-coredump[15432]: Process 3513 (DiscoverNotifie) of user 1000 terminated abnormally with signal 11/SEGV, processing...
Dec  4 07:30:16 gldell-5690 systemd-coredump[15441]: Process 2613 (kwalletd6) of user 1000 terminated abnormally with signal 11/SEGV, processing...

Comment 4 dmakovey 2025-01-29 22:44:07 UTC
problem have not re-surfaced as of late (after several series of updates)

Comment 5 Adam Williamson 2025-12-02 01:48:06 UTC
This message is a reminder that Fedora Linux 41 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 41 on 2025-12-15.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
'version' of '41'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, change the 'version' 
to a later Fedora Linux version. Note that the version field may be hidden.
Click the "Show advanced fields" button if you do not see it.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora Linux 41 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora Linux, you are encouraged to change the 'version' to a later version
prior to this bug being closed.

Comment 6 Samyak Jain (RedHat) 2025-12-16 17:51:37 UTC
Fedora Linux 41 entered end-of-life (EOL) status on 2025-12-15.

Fedora Linux 41 is no longer maintained, which means that it
will not receive any further security or bug fix updates. As a result we
are closing this bug.

If you can reproduce this bug against a currently maintained version of Fedora Linux
please feel free to reopen this bug against that version. Note that the version
field may be hidden. Click the "Show advanced fields" button if you do not see
the version field.

If you are unable to reopen this bug, please file a new report against an
active release.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.