Bug 27296 - Plasma Wayland session broken
Summary: Plasma Wayland session broken
Status: NEW
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: x86_64 Linux
Priority: Normal normal
Target Milestone: Mageia 8
Assignee: KDE maintainers
QA Contact:
URL:
Whiteboard:
Keywords: IN_ERRATA8, Triaged
Depends on:
Blocks: 17523
  Show dependency treegraph
 
Reported: 2020-09-20 16:29 CEST by Aurelien Oudelet
Modified: 2021-02-23 15:10 CET (History)
2 users (show)

See Also:
Source RPM:
CVE:
Status comment:


Attachments
Bad color for Plasma panel under Wayland with nvidia drivers (143.46 KB, image/png)
2020-12-03 14:36 CET, Aurelien Oudelet
Details
Bad color for Plasma panel under Wayland with nvidia drivers (but Dolphin and other apps are ok) (338.55 KB, image/png)
2020-12-03 14:40 CET, Aurelien Oudelet
Details
wayland-session.log file (9.31 KB, text/plain)
2020-12-03 14:42 CET, Aurelien Oudelet
Details

Description Aurelien Oudelet 2020-09-20 16:29:23 CEST
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.
Aurelien Oudelet 2020-10-29 16:13:22 CET

Blocks: (none) => 17523

Comment 1 Aurelien Oudelet 2020-12-03 14:22:00 CET
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.
Comment 2 Aurelien Oudelet 2020-12-03 14:36:31 CET
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).
Comment 3 Aurelien Oudelet 2020-12-03 14:40:51 CET
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.
Comment 4 Aurelien Oudelet 2020-12-03 14:42:42 CET
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.
Comment 5 Aurelien Oudelet 2020-12-03 14:47:45 CET
https://community.kde.org/Plasma/Wayland_Showstoppers
Comment 6 Morgan Leijström 2021-02-05 20:46:38 CET
Status on RC take 5?
For errata?

CC: (none) => fri

Comment 7 Aurelien Oudelet 2021-02-05 23:07:50 CET
(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
Comment 8 Morgan Leijström 2021-02-06 11:53:37 CET
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

Comment 9 Aurelien Oudelet 2021-02-23 15:10:06 CET
(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...

Note You need to log in before you can comment on or make changes to this bug.