KDE crash when captive portal lease expires

I am having KDE problems on all four of my laptops, which all exhibit the same symptoms. Note that I have been using NixOS for going on three years and I never experienced this issue, up through v25.05. After 25.05 became EOL, I migrated my machines to the unstable channel and the problem started immediately thereafter. I them moved a couple of machines to 25.11, which did not solve the problem, nor, in fact, did it change anything.

Issue: Parts of KDE crash whenever my captive portal lease expires.

Machines affected: Various Dell, Acer and ThinkPad laptops, all running either 25.11, or unstable. All of which were upgraded from 25.05. All are making a captive portal connection via wifi.

Pattern: The problem occurs whenever my captive portal lease expires, regardless of whether the machine is running, or not.

Machines which run 24/7 and the browser is also runng:
When I wake these machines from sleep, the panel will be gone and the wallpaper will also be gone, leaving only a blank, black display. I am able to alt-tab between any running applications. Usually, three to four KDE Crash Handler windows will pop up, but they are incapable of submitting a report, even after a new captive portal lease has been obtained. After I have a new captive portal lease, however, it is possible to click on the “Restart” button on one of the Crash Handler Windows and the panel and wallpaper will then reboot / reappear.

If, on the other hand the machine is running, but not sleeping when the captive portal lease expires, the problem does not exhibit itself. Instead, I simply have a captive portal interface tab pop up in my browser, prompting me to apply for a new lease.

Machines which run 24/7 and the browser is NOT running:
If the captive portal lease has expired, it is necessary to launch the browser from the terminal, so that a new captive portal lease may be secured. I have found no other way to reboot / restart the panel and wallpaper, without a working Internet connection. Even a reboot of the machine will not fix things, without first securing a working Internet connection.

Machines which are routinely shut down:
I have KDE configured to automatically launch the Kitty terminal when booted. If the captive portal lease is valid, there are no problems upon boot. If the captive portal lease has expired, the machine will immediately boot into a crashed scenario, with no panel and no wallpaper. It is necessary to launch the browser from the terminal, and once the browser launches, I can secure a fresh captive portal lease. I can then click the “Restart” button on one of the KDE Crash handler windows to reboot / restart the panel and the wallpaper.

When this issue occurs, it is frequently (but not always) accompanied by the same chime that sounds when a USB drive, or SD card is inserted into the machine. Instead of the chime sounding once, however, it sounds continuously until a new captive portal lease is secured.

Apparently there is a known KDE bug (#514348) which can cause KDE to crash when connecting to a captive portal, but I have never had any issues connecting. My issue is strictly related to the captive portal lease expiration event.

Here are the logs (both in reverse order), paired with the latest Crashed Process Viewer report from two different machines, beginning (presumably) from the time that the captive portal lease had expired. I have quite a large collection of Crash Handler reports now, since 25.05 went EOL, but I know of no way to submit them to anyone, apart by dropping them into Pastebin and sharing them this way. Whenever this problem occurs, the Crash Handler also does not function correctly and is incapable of submitting a report. It would be useful if a crash report could be selected and submitted via the Crashed Process Viewer itself, eh? But sadly, AFAIK, it does not posses this functionality.

Machine 1:

Machine 2:

Any and all suggestions would be appreciated.

Thanks in advance!

It is late Friday night / early Saturday morning, so as anticipated, my captive portal lease expired, my KDE wallpaper is gone (just a blank, black display) and my panel is gone. I have four Crash Handler windows which all say the same thing:

Gathering crash information failed for unknown reasons. You can retry, close the window, or view detailed output.

CRASH HANDLER has closed unexpectedly

You can help us improve KDE Software by reporting this error.

Followed by the following two buttons labeled:

Send Automatic Report

See Developer Information

When I click on the Send Automatic Report button, it is broken. It gives me a progress bar, but otherwise does nothing as far as I can tell, apart from it now offers me a “Restart” button, when if pressed, will return my wallpaper and return my panel. Note that this “Restart” button is not effective, until I first go into my browser and negotiate a new captive portal lease!

When I click on See Developer Information I get the following output:

Starting debugger /nix/store/2m2sjdjj7l772mkippd9iz3gvd7xvlp2-gdb-host-cpu-only-16.3/bin/gdb --init-eval-command=set auto-solib-add off --nw --nx --batch --init-eval-command=set debuginfod enabled on --command=/tmp/drkonqi.ldinLF --command=/tmp/drkonqi.Ufcdhe --core=/tmp/drkonqi-core.wubDoW/core /nix/store/dnqcrlx8y2zqpmcmzp8p1bysgy50myyk-plasma-workspace-6.5.5/bin/.plasmashell-wrapped

warning: Can’t open file /memfd:JITCode:QtQml (deleted) during file-backed mapping note processing

warning: Can’t open file /memfd:pulseaudio (deleted) during file-backed mapping note processing

warning: Can’t open file anon_inode:i915.gem during file-backed mapping note processing

warning: Can’t open file /memfd:unknown-usage:QtQml (deleted) during file-backed mapping note processing

warning: Can’t open file /memfd:wayland-shm (deleted) during file-backed mapping note processing

warning: Can’t open file /memfd:JSGCHeap:QtQml (deleted) during file-backed mapping note processing

warning: Can’t open file /memfd:kwin-dmabuf-feedback-table (deleted) during file-backed mapping note processing

warning: Can’t open file /memfd:JSVMStack:QtQml (deleted) during file-backed mapping note processing

warning: Can’t open file /memfd:sljit (deleted) during file-backed mapping note processing

[New LWP 25516]

[New LWP 25524]

[New LWP 25568]

[New LWP 25581]

[New LWP 25574]

[New LWP 25525]

[New LWP 25571]

[New LWP 25593]

[New LWP 25550]

[New LWP 25576]

[New LWP 25573]

[New LWP 25622]

[New LWP 25577]

[New LWP 25598]

[New LWP 25578]

[New LWP 25579]

[New LWP 25618]

[New LWP 25580]

[New LWP 25565]

[New LWP 25523]

[New LWP 25566]

[New LWP 25567]

[New LWP 25572]

[New LWP 25619]

[New LWP 25575]

[New LWP 25531]

[New LWP 25599]

[Thread debugging using libthread_db enabled]

Using host libthread_db library “/nix/store/wqfs0wh0wp6vdcbbck3wzk5v15qy17m7-glibc-2.40-66/lib/libthread_db.so.1”.

Core was generated by `/nix/store/dnqcrlx8y2zqpmcmzp8p1bysgy50myyk-plasma-workspace-6.5.5/bin/.plasmashell-wrapped --no-respawn’.

Program terminated with signal SIGSEGV, Segmentation fault.

#0 0x00007fa90a69caac in __pthread_kill_implementation () from /nix/store/wqfs0wh0wp6vdcbbck3wzk5v15qy17m7-glibc-2.40-66/lib/libc.so.6

[Current thread is 1 (Thread 0x7fa904c20cc0 (LWP 25516))]

Traceback (most recent call last):

File “/nix/store/nhafjx4hga6712g34wgnwgyq7l41ckva-drkonqi-6.5.5/share/drkonqi/gdb/python/gdb_preamble/preamble.py”, line 608, in print_preamble

print_preamble_internal()

~~~~~~~~~~~~~~~~~~~~~~~^^

File “/nix/store/nhafjx4hga6712g34wgnwgyq7l41ckva-drkonqi-6.5.5/share/drkonqi/gdb/python/gdb_preamble/preamble.py”, line 582, in print_preamble_internal

resolve_modules()

~~~~~~~~~~~~~~~^^

File “/nix/store/nhafjx4hga6712g34wgnwgyq7l41ckva-drkonqi-6.5.5/share/drkonqi/gdb/python/gdb_preamble/preamble.py”, line 577, in resolve_modules

image = CoreImage(line)

File “/nix/store/nhafjx4hga6712g34wgnwgyq7l41ckva-drkonqi-6.5.5/share/drkonqi/gdb/python/gdb_preamble/preamble.py”, line 545, in _init_

raise NoBuildIdException(f’No build id found in core image: {eu_unstrip_line}')

NoBuildIdException: No build id found in core image: 0x7fa8a55b6000+0xb048 - /nix/store/7jqg4j92w709cxdswz66xxny4405mlg8-libxkbcommon-1.11.0/lib/libxkbregistry.so.0 - libxkbregistry.so.0

No build id found in core image: 0x7fa8a55b6000+0xb048 - /nix/store/7jqg4j92w709cxdswz66xxny4405mlg8-libxkbcommon-1.11.0/lib/libxkbregistry.so.0 - libxkbregistry.so.0

Sentry is attempting to send 2 pending events

Waiting up to 30 seconds

Press Ctrl-C to quit

Debugging ended with exit code ‘1’ and exit status ‘NormalExit’

Welcome to my regularly scheduled Saturday morning core dump! (here is part 1 of the journal in reverse order): Jan 31 00:48:04 pocomoke systemd-timesyncd[609]: Timed out waiting for reply fro - Pastebin.com

And, here is part 2 of my regularly scheduled Saturday morning core dump (again in reverse order): https://pastebin.com/kJt5tk0H