# Description of problem: After updating my Cauldron system yesterday, Plasma Wayland is no longer able to use hardware acceleration (it was working fine before - I'd even successfully tested 0 A.D., a graphically-intensive OpenGL game, under Plasma Wayland). The default (X11-based) Plasma session is still working fine. I think the last time I updated my Cauldron system, prior to the update that broke Wayland hardware acceleration, was on 2020-07-06 (Monday). Now, when I log in to a Plasma Wayland session, everything lags as if I were running my system in VirtualBox (which I'm not). KSysGuard shows massive CPU spikes whenever I move the cursor, and KInfoCenter reports that I'm using llvmpipe for graphics (the same software renderer that Plasma uses by default in VirtualBox - which explains the VirtualBox-like performance). My PC's graphics card is an AMD Radeon RX 5700 XT. If other Plasma users could check whether this bug affects them (don't worry, you can easily switch back to X11), I'd appreciate it (e.g. so we can figure out whether the issue is specific to AMD graphics cards). Also, if GNOME Wayland users could report on whether this bug affects them, I'd appreciate it (so we can figure out if it's a Plasma-specific issue). Unfortunately, I can't test whether Mageia 7.1 is affected by the issue, due to a separate bug (26765) preventing me from using hardware acceleration (Bug 26765 doesn't affect Cauldron, though). # How reproducible: Every time I log in to a Plasma Wayland session. # Steps to reproduce: 1. Install Mageia Cauldron 2. Install the latest updates 3. Install the package "plasma-workspace-wayland" 4. Reboot your system 5. In your display manager, select "Plasma (Wayland)" as your desktop environment. Note the "(Wayland)" part - unlike GNOME, Plasma doesn't default to Wayland, so if you just select "Plasma", you'll end up with an X11 session. 6. Log in 7. Figure out whether you're running on hardware-accelerated graphics, or on llvmpipe, e.g. by checking KInfoCenter. # Actual behaviour: The system uses llvmpipe, rather than hardware-accelerated graphics, resulting in CPU spikes and poor performance. # Expected behaviour: (Provided you have a working graphics card, and you're not running in a virtual machine) The system should use hardware-accelerated graphics (e.g. amdgpu, nouveau, intel, etc.), and desktop performance should be good, even with Plasma's desktop effects (e.g. transparency) enabled.
CC: (none) => olav
Thank you for reporting this; although it has to be noted that Plasma Wayland is very much a work in progress, and by no means yet a finished product. Here you have a reversion from something which previously worked, so a bug is in order. Thank you for the detailed information about installing, invoking & checking Plasma Wayland. > After updating my Cauldron system yesterday [2020-07-15], Plasma Wayland > is no longer able to use hardware acceleration (it was working fine before Can you please post the list of updates done on the date you say: $ rpm -qa --last | less shows them in date order, most recent first, so it is easy to select updates done on a particular day. This might give a clue as to which package update is responsible.
CC: (none) => lewyssmith
(In reply to Lewis Smith from comment #1) > > After updating my Cauldron system yesterday [2020-07-15], Plasma Wayland > > is no longer able to use hardware acceleration (it was working fine before > Can you please post the list of updates done on the date you say: > $ rpm -qa --last | less It's a rather long list of packages, so I'll attach it as a file. Thank you for the command to get the RPM log. Looking over it, it turns out that I'd been "updating my Cauldron system" on 2020-07-14 (Tuesday) 23:47, not 2020-07-15 (Wednesday). I did install a few packages 50 minutes later on 2020-07-15 (flatpak, xdg-desktop-portal-kde, discover, and the associated dependencies), but I doubt that these packages would break Plasma Wayland hardware acceleration. (In reply to Andrew Piubellini from comment #0) > I think the last time I updated my Cauldron system, prior to the update that > broke Wayland hardware acceleration, was on 2020-07-06 (Monday). Turns out I'd performed updates on 2020-07-09 (Thursday) as well. Based on the RPM log, the dates on my 0 A.D. replay files, and memory, I can construct the following timeline: * 2020-06-26 (Friday): Updated my Cauldron system from a TTY, and tested 0 A.D. in both X11 and Wayland, demonstrating that Plasma Wayland was working fine. * 2020-07-02 (Thursday): Updated my Cauldron system from a TTY. Probably ran Firefox, but I don't know whether I used X11 or Wayland for this. * 2020-07-06 (Monday): Updated my Cauldron system from a TTY, and tested 0 A.D. in both X11 and Wayland, demonstrating that Plasma Wayland was working fine. * 2020-07-09 (Thursday): Updated my Cauldron system from a TTY. Probably ran Firefox, but I don't know whether I used X11 or Wayland for this. So I'm uncertain as to whether Plasma Wayland hardware acceleration was working on this date. * 2020-07-14 (Tuesday) 23:47: Updated my Cauldron system, from a TTY. * 2020-07-15 (Wednesday) 00:36: Installed flatpak, xdg-desktop-portal-kde, and the relevant dependencies, from a Plasma X11 session. * 2020-07-15 (Wednesday) 00:44: Installed discover, the relvant dependencies and the Firefox Flatpak, all from a Plasma X11 session. Proceeded to log out, and logged in to a Plasma Wayland session. Immediately noticed (based on cursor lag) that something was horribly wrong, and checking KInfoCenter revealed I was stuck on llvmpipe. So, the last confirmed occasion of Plasma Wayland working was after the updates of 2020-07-06 (Monday), and the first confirmed occasion of Plasma Wayland being broken was after the updates of 2020-07-14 (Tuesday).
Created attachment 11753 [details] Output of 'rpm -qa --last > "rpm log.txt"'
Thanks for the extra info (but it would have sufficed to list the RPM changes since 2020-07-06 (Monday)). The timeline above is helpful. "Updated my Cauldron system from a TTY, and tested 0 A.D. in both X11 and Wayland, demonstrating that Plasma Wayland was working fine." Assigning to the KDE team.
CC: lewyssmith => (none)Assignee: bugsquad => kde
Plasma Wayland = Work in progress. Still useful fixes from upstream. Plasma 5.22 currently in beta gets fixes day after day. Status of this bug under Cauldron ? Can you also install inxi (urpmi inxi) and paste here output of: $ inxi -SGxx
Assignee: kde => ouaurelienStatus: NEW => NEEDINFOCC: (none) => ouaurelien
We are in the process to update Cauldron to latest Plasma release.
Status: NEEDINFO => NEW
Plasma 5.22.3 is in Cauldron. Please test.
Keywords: (none) => NEEDINFO
Plasma wayland is still problematic especially on nvidia - but I close this bug as old.
Resolution: (none) => OLDCC: (none) => friStatus: NEW => RESOLVED