https://bugs.kde.org/show_bug.cgi?id=449326
Fabian Vogt <fab...@ritter-vogt.de> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |fab...@ritter-vogt.de
--- Comment #7 from Fabian Vogt <fab...@ritter-vogt.de> ---
openQA encounters this regularly (almost every run) as well, and I can
reproduce it locally.
The reason appears to be that $DISPLAY is set in the activation environment,
and so kwin tries to use the X11 backend with the old value of $DISPLAY.
This is not unset by cleanupPlasmaEnvironment on logout because it is already
part of the "oldSystemdEnvironment".
Doing just that would only address it partially though, it's still possible for
it to be set by an improperly terminated Plasma session or just after switching
from a different DE which doesn't unset $DISPLAY.
If it's not "supported" to start a nested session, I suggest to just unset
$DISPLAY in startplasma-wayland. If it is, then checking for
`XDG_SESSION_TYPE=x11` before might be an option. $WAYLAND_DISPLAY is probably
similarly affected, but that is at least cleaned up properly by
startplasma-wayland.
Jan 29 15:33:51 localhost.localdomain kwin_wayland_wrapper[2162]: No backend
specified through command line argument, trying auto resolution
Jan 29 15:33:51 localhost.localdomain kwin_wayland_wrapper[2162]: Invalid
MIT-MAGIC-COOKIE-1 keyInvalid MIT-MAGIC-COOKIE-1 key
Jan 29 15:33:51 localhost.localdomain kwin_wayland_wrapper[2173]: No backend
specified through command line argument, trying auto resolution
Jan 29 15:33:51 localhost.localdomain kwin_wayland_wrapper[2173]: Invalid
MIT-MAGIC-COOKIE-1 keyInvalid MIT-MAGIC-COOKIE-1 key
Jan 29 15:33:51 localhost.localdomain kwin_wayland_wrapper[2175]: No backend
specified through command line argument, trying auto resolution
Jan 29 15:33:51 localhost.localdomain kwin_wayland_wrapper[2175]: Invalid
MIT-MAGIC-COOKIE-1 keyInvalid MIT-MAGIC-COOKIE-1 key
Jan 29 15:33:51 localhost.localdomain kwin_wayland_wrapper[2177]: No backend
specified through command line argument, trying auto resolution
Jan 29 15:33:51 localhost.localdomain kwin_wayland_wrapper[2177]: Invalid
MIT-MAGIC-COOKIE-1 keyInvalid MIT-MAGIC-COOKIE-1 key
Jan 29 15:33:51 localhost.localdomain kwin_wayland_wrapper[2179]: No backend
specified through command line argument, trying auto resolution
Jan 29 15:33:51 localhost.localdomain kwin_wayland_wrapper[2179]: Invalid
MIT-MAGIC-COOKIE-1 keyInvalid MIT-MAGIC-COOKIE-1 key
Jan 29 15:33:51 localhost.localdomain kwin_wayland_wrapper[2182]: No backend
specified through command line argument, trying auto resolution
Jan 29 15:33:51 localhost.localdomain kwin_wayland_wrapper[2182]: Invalid
MIT-MAGIC-COOKIE-1 keyInvalid MIT-MAGIC-COOKIE-1 key
Jan 29 15:33:51 localhost.localdomain kwin_wayland_wrapper[2184]: No backend
specified through command line argument, trying auto resolution
Jan 29 15:33:51 localhost.localdomain kwin_wayland_wrapper[2184]: Invalid
MIT-MAGIC-COOKIE-1 keyInvalid MIT-MAGIC-COOKIE-1 key
Jan 29 15:33:51 localhost.localdomain kwin_wayland_wrapper[2186]: No backend
specified through command line argument, trying auto resolution
Jan 29 15:33:51 localhost.localdomain kwin_wayland_wrapper[2186]: Invalid
MIT-MAGIC-COOKIE-1 keyInvalid MIT-MAGIC-COOKIE-1 key
Jan 29 15:33:51 localhost.localdomain kwin_wayland_wrapper[2188]: No backend
specified through command line argument, trying auto resolution
Jan 29 15:33:51 localhost.localdomain kwin_wayland_wrapper[2188]: Invalid
MIT-MAGIC-COOKIE-1 keyInvalid MIT-MAGIC-COOKIE-1 key
Jan 29 15:33:51 localhost.localdomain kwin_wayland_wrapper[2190]: No backend
specified through command line argument, trying auto resolution
Jan 29 15:33:51 localhost.localdomain kwin_wayland_wrapper[2190]: Invalid
MIT-MAGIC-COOKIE-1 keyInvalid MIT-MAGIC-COOKIE-1 key
Jan 29 15:33:51 localhost.localdomain kwin_wayland_wrapper[2192]: No backend
specified through command line argument, trying auto resolution
Jan 29 15:33:51 localhost.localdomain kcminit_startup[2166]: The Wayland
connection broke. Did the Wayland compositor die?
Jan 29 15:33:51 localhost.localdomain ksplashqml[2165]: The Wayland connection
broke. Did the Wayland compositor die?
Jan 29 15:33:51 localhost.localdomain kwin_wayland_wrapper[2192]: Invalid
MIT-MAGIC-COOKIE-1 keyInvalid MIT-MAGIC-COOKIE-1 key
Jan 29 15:33:51 localhost.localdomain systemd[1371]: Started KDE Config Module
Initialization.
Jan 29 15:33:51 localhost.localdomain systemd[1371]: Starting KDE Daemon...
Jan 29 15:33:51 localhost.localdomain systemd[1371]: Starting KDE Session
Management Server...
Jan 29 15:33:51 localhost.localdomain systemd[1371]: plasma-ksplash.service:
Main process exited, code=exited, status=1/FAILURE
Jan 29 15:33:51 localhost.localdomain systemd[1371]: plasma-ksplash.service:
Failed with result 'exit-code'.
Jan 29 15:33:51 localhost.localdomain systemd[1371]: Failed to start Splash
screen shown during boot.
Jan 29 15:33:51 localhost.localdomain kded5[2194]: Failed to create wl_display
(No such file or directory)
Jan 29 15:33:51 localhost.localdomain kded5[2194]: qt.qpa.plugin: Could not
load the Qt platform plugin "wayland" in "" even though it was found.
Jan 29 15:33:51 localhost.localdomain kded5[2194]: This application failed to
start because no Qt platform plugin could be initialized. Reinstalling the
application may fix this problem.
Available platform plugins
are: eglfs, linuxfb, minimal, minimalegl, offscreen, vnc, wayland-egl, wayland,
wayland-xcomposite-egl, wayland-xcomposite-glx, xcb
--
You are receiving this mail because:
You are watching all bug changes.
