https://bugs.kde.org/show_bug.cgi?id=524392
Dan A <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected] --- Comment #14 from Dan A <[email protected]> --- I encountered this issue after upgrading to KDE Plasma 6.8.0 on EndeavourOS, running on a 2019 MacBook Pro 16-inch with a T2 Linux kernel. **System information:** - Distribution: EndeavourOS (Arch Linux) - KDE Plasma: 6.8.0 - Session: Wayland (KWin) - Kernel: 7.2.9-arch1-Watanare-T2-4-t2 - Hardware: MacBook Pro 16-inch (2019), Intel i7-9750H, AMD Radeon 5500M / Intel UHD 630 **Symptoms:** After logging into Plasma, `baloo_file_extractor` repeatedly aborts with SIGABRT during Qt platform initialization. Relevant journal messages: ``` Failed to create wl_display (No such file or directory) Could not load the Qt platform plugin "wayland" in "" even though it was found. could not connect to display Could not load the Qt platform plugin "xcb" in "" even though it was found. This application failed to start because no Qt platform plugin could be initialized. ``` The backtrace includes: ``` QMessageLogger::fatal QGuiApplicationPrivate::createPlatformIntegration QGuiApplicationPrivate::createEventDispatcher QCoreApplicationPrivate::init QGuiApplicationPrivate::init ``` **Troubleshooting performed:** 1. Verified that my active Wayland session uses `wayland-1`, and `/run/user/1000/wayland-1` exists. 2. Verified the systemd user environment includes: ``` XDG_RUNTIME_DIR=/run/user/1000 DISPLAY=:1 WAYLAND_DISPLAY=wayland-1 ``` 3. Restarted `kde-baloo.service`. The journal still showed extractor crashes around the restart, although some entries came from the previous Baloo process. 4. Inspected the environment of the newly started Baloo daemon, confirming that the same display variables were present. 5. Applied `QT_QPA_PLATFORM=offscreen` to the systemd user environment and restarted Baloo. No further extractor errors appeared during the test. 6. Created a service-specific systemd override: ``` [Service] Environment="QT_QPA_PLATFORM=offscreen" ``` Afterward, the service ran without further observed crashes. **Baloo status with workaround:** ``` Baloo File Indexer is running Indexer state: Idle Total files indexed: 30,327 Files waiting for content indexing: 0 Files failed to index: 9 Current size of index is 52.50 MiB ``` This suggests an issue with Qt platform initialization in the Baloo extractor. The offscreen workaround appears effective, although I have not yet verified behavior after another reboot. I can provide additional journal logs, coredumps, or environment information if needed. -- You are receiving this mail because: You are watching all bug changes.
