First encounter with Plasma6 - several applications unusable

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 :frowning:
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, fedora’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.

can you try this in X11?

fedora is generally pretty good with their implementation of plasma, but your upgrade might have left some things behind.

recently upgraded from kubuntu 24.04 (plasma 5) to 24.10 (plasma 6) and there are plenty of things that have issues or are incomplete

but 24.10 is a development branch and i would expect fedora to have a better handle on things for their next version (it is a rolling distro tho, so there’s that).

Try with X11 as already stated
Try with a new user
Try cleaning the cache and read more troubleshooting from there.

I thought Plasma 6 dropped X11 support. However after some searching on the Fedora forum I found Fedora still maintains a plasma-workspace-x11 package. Not officially supported by KDE but whatever.

I have installed that one and my first impression is that this does fix most of my issues. Thanks for the hint.

That reduces the urgency of fixing a broken wayland for me. Yay!

I still would like to dig into the actual issues I have on Wayland as it may help find solutions uncover bugs that still need fixing. So if anyone has more experience or insight in this, I’m interested to read about it.

Your wayland issues could be very much related to what kind of nvidia driver you are running, if it is nouveau you can forget wayland, if it is the proprietary, anything less than 565.x is not optimal.

Thanks for the suggestion.

The nvidia-settings tool shows me I’m using driver version 565.57.01 so it’s likely something else.

Note I’m documenting everything on my journey here hoping it may help others as well if they run into the same issues.

So the digikam issue. This is somewhat odd in itself. While still on Wayland, I waited a bit longer after a fresh startup and after a while it showed an failure to connect to its database (an internal mysqldb server). I tried several times but it would not connect.

Now that I’m back on X11 I retried digikam and this time it only popped up a warning about a change in character set (from utf8 to utf8mb3). A quick search on the internet showed this is to be expected and harmless. So I just let it continue and on X11 it works just fine. So apparently under Wayland this has additional issues to be solved.

X11 is still there, the default was changed to wayland is all.