https://bugs.kde.org/show_bug.cgi?id=521631
Bug ID: 521631
Summary: kwin_wayland crashes repeatedly when ~/.cache is
deleted + reboot
Classification: Plasma
Product: kwin
Version First 6.7.0
Reported In:
Platform: Fedora RPMs
OS: Linux
Status: REPORTED
Severity: crash
Priority: NOR
Component: generic-crash
Assignee: [email protected]
Reporter: [email protected]
Target Milestone: ---
Created attachment 193270
--> https://bugs.kde.org/attachment.cgi?id=193270&action=edit
drkonqi_log
DESCRIPTION
After removing ~/.cache from a TTY and rebooting, the system generates a high
volume of crash reports (20+) during session startup. DrKonqi reports numerous
"Unable to find file" errors for various PIDs, and the
drkonqi-coredump-launcher.socket becomes saturated with incoming connections.
The kcrash-metadata directory does not exist in ~/, preventing any meaningful
crash report from being generated.
The issue is reproducible consistently by deleting ~/.cache and restarting the
session. The system is configured to start with an empty session (Settings >
Session > "Start with an empty session"), but the crashes still occur.
STEPS TO REPRODUCE
1. Switch to a TTY (Ctrl+Alt+F3) and log in as the user.
2. Execute: rm -rf ~/.cache
3. Switch back to the graphical session (Ctrl+Alt+F1) and reboot or log out and
log back in.
4. After the session starts, observe the system logs.
OBSERVED RESULT
- Multiple coredumps are generated (20+).
- DrKonqi shows repeated "Unable to find file" errors for PIDs, with the
following pattern:
"Unable to find file for pid X expected at 'kcrash-metadata/...ini'"
- The drkonqi-coredump-launcher.socket is saturated, dropping connections:
"drkonqi-coredump-launcher.socket: Too many incoming connections (16),
dropping connection."
- The directory ~/kcrash-metadata does not exist, preventing DrKonqi from
handling the crashes.
- Log excerpt (timestamps in UTC):
10:18:12.353 UTC init.scope iscsi.service: Unit cannot be reloaded because it
is inactive.
10:18:24.505 UTC init.scope iscsi.service: Unit cannot be reloaded because it
is inactive.
10:18:39.664 UTC init.scope iscsi.service: Unit cannot be reloaded because it
is inactive.
10:18:45.737 UTC init.scope iscsi.service: Unit cannot be reloaded because it
is inactive.
10:18:56.333 UTC init.scope drkonqi-coredump-launcher.socket: Too many
incoming connections (16), dropping connection. (repeated 11 times)
10:18:56.460 UTC drkonqi-coredump-launcher@1-2-2628_24884-1000.service Unable
to find file for pid 11909 expected at
"kcrash-metadata/drkonqi-coredump-launcher.6802f09da56d47068b59c40ee76d8fa1.11909.ini"
10:18:56.469 UTC drkonqi-coredump-launcher@0-1-2628_24884-1000.service Unable
to find file for pid 2414 expected at
"kcrash-metadata/kwin_wayland.6802f09da56d47068b59c40ee76d8fa1.2414.ini"
10:18:56.527 UTC drkonqi-coredump-launcher@7-8-2628_24884-1000.service Unable
to find file for pid 12225 expected at
"kcrash-metadata/drkonqi-coredump-launcher.6802f09da56d47068b59c40ee76d8fa1.12225.ini"
10:18:56.544 UTC drkonqi-coredump-launcher@11-12-2628_24884-1000.service
Unable to find file for pid 12336 expected at
"kcrash-metadata/drkonqi-coredump-launcher.6802f09da56d47068b59c40ee76d8fa1.12336.ini"
10:18:56.545 UTC drkonqi-coredump-launcher@12-13-2628_24884-1000.service
Unable to find file for pid 12356 expected at
"kcrash-metadata/drkonqi-coredump-launcher.6802f09da56d47068b59c40ee76d8fa1.12356.ini"
10:18:56.558 UTC drkonqi-coredump-launcher@13-14-2628_24884-1000.service
Unable to find file for pid 12374 expected at
"kcrash-metadata/drkonqi-coredump-launcher.6802f09da56d47068b59c40ee76d8fa1.12374.ini"
10:18:56.576 UTC drkonqi-coredump-launcher@10-11-2628_24884-1000.service
Unable to find file for pid 12317 expected at
"kcrash-metadata/drkonqi-coredump-launcher.6802f09da56d47068b59c40ee76d8fa1.12317.ini"
10:18:56.585 UTC drkonqi-coredump-launcher@9-10-2628_24884-1000.service
Unable to find file for pid 12295 expected at
"kcrash-metadata/drkonqi-coredump-launcher.6802f09da56d47068b59c40ee76d8fa1.12295.ini"
10:18:56.593 UTC drkonqi-coredump-launcher@6-7-2628_24884-1000.service Unable
to find file for pid 12179 expected at
"kcrash-metadata/drkonqi-coredump-launcher.6802f09da56d47068b59c40ee76d8fa1.12179.ini"
10:18:56.602 UTC drkonqi-coredump-launcher@3-4-2628_24884-1000.service Unable
to find file for pid 12043 expected at
"kcrash-metadata/drkonqi-coredump-launcher.6802f09da56d47068b59c40ee76d8fa1.12043.ini"
10:18:56.620 UTC drkonqi-coredump-launcher@4-5-2628_24884-1000.service Unable
to find file for pid 12072 expected at
"kcrash-metadata/drkonqi-coredump-launcher.6802f09da56d47068b59c40ee76d8fa1.12072.ini"
10:18:56.630 UTC drkonqi-coredump-launcher@2-3-2628_24884-1000.service Unable
to find file for pid 11974 expected at
"kcrash-metadata/drkonqi-coredump-launcher.6802f09da56d47068b59c40ee76d8fa1.11974.ini"
10:18:56.634 UTC drkonqi-coredump-launcher@14-15-2628_24884-1000.service
Unable to find file for pid 12404 expected at
"kcrash-metadata/drkonqi-coredump-launcher.6802f09da56d47068b59c40ee76d8fa1.12404.ini"
10:18:56.651 UTC drkonqi-coredump-launcher@8-9-2628_24884-1000.service Unable
to find file for pid 12273 expected at
"kcrash-metadata/drkonqi-coredump-launcher.6802f09da56d47068b59c40ee76d8fa1.12273.ini"
10:18:56.661 UTC drkonqi-coredump-launcher@5-6-2628_24884-1000.service Unable
to find file for pid 12106 expected at
"kcrash-metadata/drkonqi-coredump-launcher.6802f09da56d47068b59c40ee76d8fa1.12106.ini"
10:18:56.666 UTC drkonqi-coredump-launcher@15-16-2628_24884-1000.service
Unable to find file for pid 12453 expected at
"kcrash-metadata/drkonqi-coredump-launcher.6802f09da56d47068b59c40ee76d8fa1.12453.ini"
EXPECTED RESULT
Deleting ~/.cache should not cause any crashes. The session should start
normally without generating coredumps or saturating the DrKonqi socket. The
directory ~/kcrash-metadata should be created as needed, and any crash should
be handled properly.
SOFTWARE/OS VERSIONS
Operating System: Fedora Linux 44
KDE Plasma Version: 6.7.0
KDE Frameworks Version: 6.27.0
Qt Version: 6.11.1
Kernel Version: 7.0.12-201.fc44.x86_64 (64-bit)
Graphics Platform: Wayland
ADDITIONAL INFORMATION
- The issue occurs even though the session is set to "Start with an empty
session" (Settings > Session).
- The crash affects multiple PIDs, but `kwin_wayland` (PID 2414 in the log)
appears to be one of the first affected components.
--
You are receiving this mail because:
You are watching all bug changes.
