Comments
nemobis
Appears to have fixed the 25.0.0 performance regression which made some AMD systems unusable (https://bodhi.fedoraproject.org/updates/FEDORA-2025-ef64588235#comment-3986595). Works ok on my AMD A8-7600.
Thank you!
Still makes some AMD systems (like AMD A8-7600) unusable, as 25.0.0. https://bodhi.fedoraproject.org/updates/FEDORA-2025-ef64588235#comment-3986595
I'll paste some log messages here for better discoverability. From journalctl -p5 | grep wayland, these warnings are fine:
mar 04 00:11:52 fedora sddm-helper-start-wayland[1555]: "No backend specified, automatically choosing drm\n"
mar 04 00:11:52 fedora sddm-helper-start-wayland[1555]: "Accepting client connections on sockets: QList(\"wayland-0\")\n"
mar 04 00:11:52 fedora sddm-helper-start-wayland[1555]: "kwin_wayland_drm: drmSetClientCap for Atomic Mode Setting failed. Using legacy mode on GPU \"/dev/dri/card0\"\n"
While these are critical and go away after the downgrade:
mar 04 00:11:53 fedora sddm-helper-start-wayland[1555]: "kwin_core: Failed to open drm node: \"\"\nkwin_scene_opengl: couldn't find dev node for drm device \n"
mar 04 00:11:53 fedora sddm-helper-start-wayland[1555]: "libEGL warning: egl: failed to create dri2 screen\n"
mar 04 00:11:53 fedora sddm-helper-start-wayland[1555]: "libEGL warning: egl: failed to create dri2 screen\n"
mar 04 00:11:54 fedora sddm-helper-start-wayland[1555]: "libEGL warning: egl: failed to create dri2 screen\n"
mar 04 00:11:54 fedora sddm-helper-start-wayland[1555]: "libEGL warning: egl: failed to create dri2 screen\n"
mar 04 00:11:54 fedora sddm-helper-start-wayland[1555]: "QSoundEffect(pulseaudio): Error decoding source file:///usr/share/maliit/keyboard2/sounds/key_tick2_quiet.wav\n"
mar 04 00:11:56 fedora sddm-helper-start-wayland[1555]: "QSGContext::initialize: depth buffer support missing, expect rendering errors\nQSGContext::initialize: stencil buffer support missing, expect rendering errors\n"
mar 04 00:12:02 fedora sddm-helper-start-wayland[1555]: "QThreadStorage: Thread 0x5576805f7a90 exited after QThreadStorage 7 destroyed\n"
mar 04 00:12:02 fedora sddm-helper[1717]: Could not open stderr to "/home/federico/.cache/wayland-errors"
If you don't have that last line, maybe you can get more information from ~/.cache/wayland-errors.
This utterly breaks the desktop environment on AMD A8-7600 as well: kwin-wayland uses all the CPU and goes down to about 1 fps. One of the logged errors is "libEGL warning: egl: failed to create dri2 screen". Version 24.2.4 with the same kernel (6.13.5) and Plasma 6.3 is fine.
More info on https://discuss.kde.org/t/kde-plasma-6-3-in-fedora-41-unusably-slow-kwin-wayland-high-cpu-usage/30979
Thanks a lot @than! This was amazingly fast.
As for the test failures,
/usr/lib64/chromium-browser/chrome-sandbox in chromium on x86_64 carries insecure mode 4755 but has no fileinfo rule for owner specification
Not sure what that is. A regular file.
$ LANG=en stat /usr/lib64/chromium-browser/chrome-sandbox
File: /usr/lib64/chromium-browser/chrome-sandbox
Size: 227984 Blocks: 448 IO Block: 4096 regular file
Device: 0,34 Inode: 3200314 Links: 1
Access: (4755/-rwsr-xr-x) Uid: ( 0/ root) Gid: ( 0/ root)
Context: system_u:object_r:chrome_sandbox_exec_t:s0
Access: 2024-03-23 02:00:00.000000000 +0200
Modify: 2024-03-23 02:00:00.000000000 +0200
Change: 2024-03-26 09:03:30.277487427 +0200
Birth: 2024-03-26 09:03:26.640800620 +0200
Upgrade works fine. The ~/.config/chromium/screen_ai/ directory was removed and I've not seen it being recreated so far (I've only opened a couple websites and a PDF file).
I confirm, unusable in KDE. 0:3.8.1-3.fc21 is perfectly functional.
Forgot the last question
Works for me
(That's using kernel 6.13.9-200.fc41.x86_64.)