Plasma Wayland session is totally broken in our current implementation but all infrastructure is HERE! See: https://community.kde.org/Plasma/Wayland/Nvidia We have: nvidia-current-455.66-3 QT 5.15.5 Plasma 5.19.5 Adding "nvidia-drm.modeset=1 nouveau.modeset=0" to Kernel command line Removing "nokmsboot" from above kernel command line (update grub) Add "KWIN_DRM_USE_EGL_STREAMS=1" to /etc/profile.d/kwin.sh All seems here and OK. Sadly, selecting Plasma Wayland session on SDDM results of Plasma Wayland session crashs after log in. See wayland-session.log from /$HOME/local/share/sddm/ : dbus-daemon[2522]: [session uid=1000 pid=2522] Activating service name='org.freedesktop.systemd1' requested by ':1.0' (uid=1000 pid=2532 comm="/usr/bin/dbus-update-activation-environment --syst") dbus-daemon[2522]: [session uid=1000 pid=2522] Activated service 'org.freedesktop.systemd1' failed: Process org.freedesktop.systemd1 exited with status 1 dbus-update-activation-environment: warning: error sending to systemd: org.freedesktop.DBus.Error.Spawn.ChildExited: Process org.freedesktop.systemd1 exited with status 1 No backend specified through command line argument, trying auto resolution kf.globalaccel.kglobalacceld: No desktop file found for service "userfeedbackconsole.desktop" libEGL warning: DRI2: failed to create dri screen libEGL warning: Not allowed to force software rendering when API explicitly selects a hardware device. libEGL warning: DRI2: failed to create dri screen _XSERVTransSocketUNIXCreateListener: ...SocketCreateListener() failed _XSERVTransMakeAllCOTSServerListeners: server already running libEGL warning: DRI2: failed to create dri screen libEGL warning: Not allowed to force software rendering when API explicitly selects a hardware device. libEGL warning: DRI2: failed to create dri screen glamor: No eglstream capable devices found glamor: 'wl_drm' not supported Missing Wayland requirements for glamor GBM backend Missing Wayland requirements for glamor EGLStream backend Failed to initialize glamor, falling back to sw KCrash: Attempting to start /usr/bin/plasmashell KCrash: Application 'plasmashell' crashing... dbus-daemon[2522]: [session uid=1000 pid=2522] Activating service name='org.kde.KSplash' requested by ':1.75' (uid=1000 pid=3156 comm="/usr/bin/plasmashell") org.kde.knotifications: WaitForName: Service was not registered within timeout So, Humm. Sad. Not ready for Prime Time. Seems Plasmashell can't see where are EGLStream External Platform from NVIDIA on system. Should we wait for Plasma Workspace 5.20 ? Assigning to KDE maintainers.
Blocks: (none) => 17523
Update to this: with latest nvidia-current drivers, with latest version of: KDE Plasma Version: 5.20.3 KDE Frameworks Version: 5.75.0 Qt Version: 5.15.1 Wayland session is WORKS FOR ME with nvidia drivers! Since there is a fix done upstream in how QT stuff looks for presence of nvidia drivers. (https://invent.kde.org/plasma/kwin/commit/f6c4cc6b8da7b2edd86843c5bde93a45b3eabcf3) See: https://community.kde.org/Plasma/Wayland/Nvidia Managed to have "nvidia-drm.modeset=1 nouveau.modeset=0" added to Kernel command line. Remove unnecessary env variable. Firefox is OK, even DRM streaming site (Netf..). BUT some drawbacks: - Bug 26101: MCC can't launch under XWayland as root as in GNOME. - Main panel with icons and tasks-manager has a weird color. Will upload a screenshot later.
Created attachment 12050 [details] Bad color for Plasma panel under Wayland with nvidia drivers Screenshot of the bad color in Plasma Panel. Note also that Kickoff menu has weird behavior when mouse hovers items, it displays menus of precedent item. Mouse must come from right to have good development. Desktop effects are OK. mggapplet is unable to run well, nor to get display (like MCC bug).
Created attachment 12051 [details] Bad color for Plasma panel under Wayland with nvidia drivers (but Dolphin and other apps are ok) An other screenshot of the weird bug.
Created attachment 12052 [details] wayland-session.log file Added wayland-session.log when doing some above tests. MCC and mgaapplet can't run. See Bug 26101.
https://community.kde.org/Plasma/Wayland_Showstoppers
Status on RC take 5? For errata?
CC: (none) => fri
(In reply to Morgan Leijström from comment #6) > Status on RC take 5? > For errata? This is not ready to be user friendly. Tools don't handle properly the Wayland stuff. So Errata. Comment 2 and onwards are still valid. For MCC and root gui, we should implement that is do for GNOME Wayland too. For errata also, Root GUI don't work in Wayland Plasma for now until it is enabled by a fix in a script: xhost +si:localuser:root
I have put a link in errata now. The Root GUI problem you mention, is it the same as https://wiki.mageia.org/en/Mageia_8_Errata#Applications_that_run_as_root_fail_to_run_in_grahics_mode ?
Keywords: (none) => IN_ERRATA8
(In reply to Morgan Leijström from comment #8) > I have put a link in errata now. > > The Root GUI problem you mention, is it the same as > https://wiki.mageia.org/en/ > Mageia_8_Errata#Applications_that_run_as_root_fail_to_run_in_grahics_mode ? This is the same. Modulo on nvidia-based system, with nvidia-nonfree driver, transparency is not possible. Wrong colors are displayed and Kicker (Application Menu) can sometimes displays wrong entries or last submenu entries for new submenu...
(In reply to Aurelien Oudelet from comment #9) > (In reply to Morgan Leijström from comment #8) > > I have put a link in errata now. > > > > The Root GUI problem you mention, is it the same as > > https://wiki.mageia.org/en/ > > Mageia_8_Errata#Applications_that_run_as_root_fail_to_run_in_grahics_mode ? > > This is the same. > Modulo on nvidia-based system, with nvidia-nonfree driver, transparency is > not possible. Wrong colors are displayed and Kicker (Application Menu) can > sometimes displays wrong entries or last submenu entries for new submenu... Still the case on Cauldron. Will dig further this with KDE Neon implementation to see if we do something wrong. Remark, only nvidia-current (version 460-80) is supported by KDE Wayland and accelerated XWayland stuff will be in nvidia 470 and later.
Summary: Plasma Wayland session broken => Plasma Wayland session broken on nvidia based graphicsTarget Milestone: Mageia 8 => Mageia 9Keywords: Triaged => (none)
What is the current state on Cauldron?