After an update, I got a window with a new icon that warned me about being on software renderer saying that it was going to affect performance and giving me the choice to change to vulkan or openGL (a setting windoow I haven’t seen in my life), predicting that it might break I figured it wasn’t a big deal since I could just timeshift to yesterday’s backup and it would be ok (which ended up not being the case, the timeshift didn’t really change the situation)
After rebooting, the plasma bottom panel opened in vulkan (I can tell because it has the mangoud thing in it) and then crashed, trying to bring it back from the terminal has the same result, I’ve been trying to find a solution with the help of duck.ai but the model is from two years ago and I think there have been some big changes on how everything works lately.
I usually use x11 with the compositor disabled at startup, which has been stable and worked well for me for close to a year, but I’ve been trying to get into using wayland so I’m not entirely sure in which I was when that happened, regardless I think wayland is broken since it falls back to x11 regardless of what I choose at session start.
I am very lost, I’ve been on linux for a few years and recently nuked windows from my desktop, but I’m still not very knowledgeable and I don’t seem to be good at googling solutions to these problems, also I’m certain this is related to recent changes which I can’t find much discussion about yet.
In short, plasma is bunged, I’m on vulkan renderer, and I can’t find a way to revert. Also the whole system seems unstable, I have to open programs from the terminal and after a while, they start crashing randomly, for example at this moment I’m unable to open systemsettings (which I opened before) and get
QThreadStorage: Thread 0x5d1fe87968b0 exited after QThreadStorage 8 destroyed
QThreadStorage: Thread 0x5d1fe87968b0 exited after QThreadStorage 3 destroyed
QThreadStorage: Thread 0x5d1fe87968b0 exited after QThreadStorage 2 destroyed
You can adjust the renderer settings by typing plasma renderer into Krunner (which is opened with the Alt+Space shortcut).
Alternatively, you can open the renderer settings from the command line:
kcmshell6 kcm_qtquicksettings
The settings should be “Automatic” for the rendering backend & render loop, and leave “force” unchecked for GL Core Profile.
Reference:
Regarding using AI:
The first place Manjaro users should go to for advice when they experience issues with their system is the Manjaro Linux Forum. AI is just a high-end text predictor, and is usually trained on data that is at least a year old. As Manjaro is a frequently-updated rolling release, any advice from an AI LLM will almost certainly be out-of-date.
And you are correct - there were some very big changes last year, especially for Plasma (the Plasma 5 → Plasma 6 update).
Thanks a lot!! apparently it was originally in software and I changed it to automatic (I would expect automatic would switch up when something goes wrong enough to crash applications), I switched to software again and it’s all back to normal.
Offtopic, but I mentioned the bit about ai because it usually helps me find a solution (even if not always directly since it can straight up lie, at least it points me towards another route to find the solution) quickly in a back and forth that with real people involves a lot of time and misunderstandings, just that this time I didn’t even have that and was completely lost. Plus I don’t want to just be spoon-fed solutions every single time I have a problem, specially since I don’t really contribute to the community.