Bug 511290 - On startup, ethernet will look to start up and connect to internet, once the popup at the top says it's connected, it will crash plasma. Rendering its unable to be used until restart or log out/log back in.
Summary: On startup, ethernet will look to start up and connect to internet, once the ...
Status: RESOLVED WORKSFORME
Alias: None
Product: plasmashell
Classification: Plasma
Component: Startup process (other bugs)
Version First Reported In: 6.4.5
Platform: Fedora RPMs Linux
: NOR crash
Target Milestone: 1.0
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2025-10-28 20:25 UTC by random.sake412
Modified: 2025-11-27 03:46 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description random.sake412 2025-10-28 20:25:03 UTC 
SUMMARY

On startup, ethernet will look to start up and connect to internet, once the popup at the top says it's connected, it will hang and crash plasma. Rendering its unable to be used until restart or log out/log back in. This doesn't happen every time, just the occasional time the ethernet decides it needs to set a network address. 


STEPS TO REPRODUCE
1. Turn on computer
2. Log-in
3. Connect to internet via ethernet, it will say setting network address and then connect - then hang. 
This doesn't happen on every instance when the computer starts up.

OBSERVED RESULT:
Plasma will crash


EXPECTED RESULT: 
Successful boot into Fedora Kinoite without any issues to start at least. 


SOFTWARE/OS VERSIONS
(available in the Info Center app, or by running `kinfo` in a terminal window)
Linux/KDE Plasma: Fedora Kinoite 42
KDE Plasma Version: 6.4.5
KDE Frameworks Version: 6.19.0
Qt Version: 6.9.2

ADDITIONAL INFORMATION
Comment 1 TraceyC 2025-10-28 21:55:29 UTC 
As the message at the top of the summary says, if something crashed, we need a backtrace of it so we can figure out what's going on. Can you please attach a backtrace of the crash using the coredumpctl command-line program, as detailed in https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports#Retrieving_a_backtrace_using_coredumpctl ?

Thanks.
Comment 2 Bug Janitor Service 2025-11-12 03:47:50 UTC 
🐛🧹 ⚠️ This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information, then set the bug status to REPORTED. If there is no change for at least 30 days, it will be automatically closed as RESOLVED WORKSFORME.

For more information about our bug triaging procedures, please read https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging.

Thank you for helping us make KDE software even better for everyone!
Comment 3 Bug Janitor Service 2025-11-27 03:46:12 UTC 
🐛🧹 This bug has been in NEEDSINFO status with no change for at least 30 days. Closing as RESOLVED WORKSFORME.