A few days ago I upgraded my system from Fedora 39 (which is EOL since November this year) to Fedora 41. This new Fedora release is my first experience with Plasma 6. It’s been a rough one so far
Several applications will launch but won’t show a usable GUI. For example
Opening firefox with my default profile will try to restore 6 windows. This goes into an endless screen redraw frenzy in which I never get a fully rendered webpage. This even hinders other applications I attempt to start while it’s in this weird state. For example if I then also start chromium, it won’t reach a state in which I can click on its buttons or type something in the address bar. Closing both applications (from the command-line), and then only starting chromium does give me a normally functioning chromium instance. For now I have worked around this by forcing firefox to use software rendering. I had to log in to a Gnome(X11) session to be able to change this setting by the way. There were plenty of errors logged on the console during the faulty launch attempts (using WebRender), but I lost them while switching between Gnome and Plasma. If needed I can redo the experiment to copy the exact error messages (something with GLX1, if I remember correctly).
I have been using Kontact on a daily basis to manage mails and my calendar. Since the upgrade to Plasma 6.2 it may or may not launch properly. It looks so far that when I try shortly after logging it it works, but if I wait an indefinite amount of time, it will launch but fail to display a window. It will appear on the task bar, but that’s it. When launched from the command line I see these error messages being logged:
qt.core.qobject.connect: QObject::disconnect: No such slot Akonadi::StatisticsProxyModel::_q_sourceDataChanged(QModelIndex, QModelIndex, QList<int>)
QWaylandGLContext::makeCurrent: eglError: 0x3003, this: 0x556d5409e290
QRhiGles2: Failed to make context current. Expect bad things to happen.
Failed to create QRhi for QBackingStoreRhiSupport
qt.svg.draw: The requested buffer size is too big, ignoring
We have an error during reading password "Entry not found"
org.kde.pim.messagelist: Circular reference loop detected in the message tree
org.kde.pim.messagelist: Circular reference loop detected in the message tree
The last two lines are probably not relevant, but I added them for completeness.
As soon as a kde application fails to run, many others will fail as well. For in the login session I’m typing this kontact fails to launch, and I also tried systemsettings (from the command line). It gives a very similar error message:
QWaylandGLContext::makeCurrent: eglError: 0x3003, this: 0x55964666b990
QRhiGles2: Failed to make context current. Expect bad things to happen.
Failed to create QRhi for QBackingStoreRhiSupport
I wanted to check something in digikam. I does nothing at all - no messages logged to console, no window being displayed, it won’t even appear on the task bar
I have searched around on several fora (this one, kde’s,…) but honestly I don’t even know where to begin. Is this a configuration issue, a bug, poor hardware?
I would really appreciate some guidance here to sort this out. As it currently stands it’s impossible for me to use Plasma as my daily driver. Yet I dislike the alternatives as well: switching to another DE (Gnome does work but I very much prefer Plasma as that’s what I have been using for years), or reverting back to Fedora 39 (which still has Plasma 5 on X11, but is now EOL).
Some system information for reference:
Operating System: Fedora Linux 41
KDE Plasma Version: 6.2.4
KDE Frameworks Version: 6.8.0
Qt Version: 6.8.0
Kernel Version: 6.11.10-300.fc41.x86_64 (64-bit)
Graphics Platform: Wayland
Processors: 8 × Intel® Core™ i7-6700K CPU @ 4.00GHz
Memory: 47.0 GiB of RAM
Graphics Processor: NVIDIA GeForce GT 1030/PCIe/SSE2
Please let me know if you need more details to help me! Thanks.
Shortly after posting this message, the whole plasma session crashed and the desktop was restarted. So I’m again in a situation similar to “shortly after logging in”. At this moment, systemsettings will start properly. kontact will not: it is still showing up on the task bar, but no window is displayed and the error message on the console is still the same. digikam still won’t budge.
Ok, the digikam issue is yet something else. If I wait long enough an error pops up that it fails to connect to its database… Yet another mystery to solve
I’ll make the digikam issue another thread (after searching for pre-existing topics)
The forum helpfully suggested a few related posts below and particularly this one was helpful: it suggested plasma on X11 can still be installed as a fallback on Fedora. I have done so and indeed my compositing troubles seem to be solved for now. I can even use hardware acceleration again in firefox.
So the pressure for me to get this fixed has been removed. But I would very much like to be able to use Plasma on Wayland eventually so if anyone has tips to debug or fix this, I’m all ears still!
When I tried the proprietary nvidia drivers under Wayland it was not a nice experience. I was getting most of what you described. Used both Fedora 41 and Tumbleweed. I got better desktop performance out of the Nouveau drivers, imagine that (and Nouveau works much better in Tumbleweed for some reason).
Have you tried this? sudo journalctl --no-pager | grep "Using legacy mode on GPU"
I got Dec 17 22:06:56 fedora kwin_wayland[2123]: kwin_wayland_drm: drmSetClientCap for Atomic Mode Setting failed. Using legacy mode on GPU "/dev/dri/card0" in each boot.
Maybe this is the cause but I’m not sure.
I am also having a plethora of issues on my upgraded Fedora system. Not the same as yours, but some in general. V-Sync or maybe explicit sync are completely broken across the board is the main one. The desktop feels sluggish and frame consistency, frame times and frame rates are completely broken in games that utilize V-Sync (most of the time). Drag and drop also doesn’t work in many if not most cases, although this could be generally lacking a proper implementation with a Wayland protocol (extension). But my desktop just feels off. Really off.
