https://bugs.kde.org/show_bug.cgi?id=526259
york <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected] --- Comment #1 from york <[email protected]> --- I encountered very similar symptoms on Ubuntu 26.04.1 with Plasma 6.6.6 (plasma-workspace 4:6.6.6-0ubuntu0.1), Qt 6.10.2 and SDDM 0.21. In my case the earlier X11 session was Plasma X11, not Xfce. Sequence: - Installed plasma-session-x11/kwin-x11/Xorg to compare a Wine application between X11 and Wayland. - Logged into Plasma X11, then logged out and returned to Plasma Wayland during the same boot. - Subsequently the bottom panel was invisible even though plasma-plasmashell.service was active. Logging out and back into Wayland did not reliably clear the problem. Observed during diagnosis: - XDG_SESSION_TYPE=wayland and kwin_wayland was running. - systemctl --user show-environment contained QT_QPA_PLATFORM=xcb. - /proc/<pid>/environ showed the same xcb override in plasmashell, Konsole, Dolphin, Discover and System Settings. The affected Qt applications were using the X11 platform rather than native Wayland. - loginctl show-user reported Linger=yes. - Display Configuration showed global scaling as 100% and offered no useful refresh-rate selection, while reading the outputs with QT_QPA_PLATFORM=wayland kscreen-doctor -o showed the actual two 2560x1440 outputs at scale 1.3 and about 75 Hz. The X11-backed settings view also reported a gap which was absent from the native Wayland output layout. - Chinese input stopped working in several KDE/Qt applications while it still worked in native Wayland Chromium/Electron applications. This may be a consequence of the different input path; I have not established a separate input-method bug. Recovery and limitations: Explicitly using the Wayland Qt platform restored the display settings and input in newly started Qt applications. Restarting plasmashell without the inherited QT_QPA_PLATFORM override restored the panel. During troubleshooting I added a Wayland session environment override and a plasmashell service override, and removed the test-only X11 packages. A full reboot followed by direct Wayland login then left the panel, display settings and tested input methods working normally. Because those configuration changes and package removal preceded the reboot, this is not a clean reboot-only or uninstall-only experiment. I cannot establish that uninstalling X11 was necessary, and I have not identified the process that initially put xcb into the user-manager environment. No full environment dump is attached. I am happy to help test a targeted fix or collect specific, non-sensitive diagnostics if useful. Please let me know the requested steps. Thank you. -- You are receiving this mail because: You are watching all bug changes.
