Bug 514348 - Captive portal network causes looping shell crash
Summary: Captive portal network causes looping shell crash
Status: NEEDSINFO BACKTRACE
Alias: None
Product: plasmashell
Classification: Plasma
Component: Networking in general (other bugs)
Version First Reported In: 6.5.4
Platform: Other Linux
: NOR crash
Target Milestone: 1.0
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2026-01-08 21:08 UTC by Wilbur Jaywright
Modified: 2026-01-08 22:12 UTC (History)
1 user (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Wilbur Jaywright 2026-01-08 21:08:12 UTC
SUMMARY
I tried to connect to a guest Wi-Fi network I know has a captive portal. After starting to connect, Plasma crashed. Plasma then auto-restarted, asked me if I wanted to file an error report, but upon still trying to complete the connection in the background it crashed again. Plasma proceeded to crash over and over, opening an additional error report window every time.

STEPS TO REPRODUCE
1. Try to connect to a captive portal guest Wi-Fi network.
2. Wait for the connection to complete.

OBSERVED RESULT
Plasma will continue to crash in a loop until the Wi-Fi network is out of range or removed from the list of known network.

EXPECTED RESULT
Plasma doesn't crash, connects to the network, and opens the page of the captive portal correctly.

SOFTWARE/OS VERSIONS
Windows: Not involved.
macOS: Not involved.
(available in the Info Center app, or by running `kinfo` in a terminal window)
Linux/KDE Plasma: Fedora 43 x64
KDE Plasma Version: 6.5.4
KDE Frameworks Version: 6.21.0
Qt Version: 6.10.1

ADDITIONAL INFORMATION
I should note that Brave Flatpak and not Firefox DNF is my default browser on this machine.
Comment 1 Nicolas Fella 2026-01-08 22:12:54 UTC
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!