Arch Linux

DanTheOrange

Member

Registered: 2024-03-08

Posts: 4

Plasma 6 post-upgrade issues.

The issue
After running `pacman -Syu` the other day I didn’t restart straight away and didn’t notice anything wrong. However today after turning the computer on I found some visual, graphical, and functional problems. Some things can't open anymore and the desktop environment is fairly broken.

I normally have a pretty standard Plasma desktop and three monitors. But this time I was greeted with a black screen and all the monitors were duplicated. Konsole was open by default. I found that if I take my mouse to the top left I can still open applications. There are visual glitches in the UI around these applications, some flickering and the black background flashes up icons in large oddly scaled formats for microseconds as I type in the search bar. I can't capture a good screenshot of this happening it's too quick. I still have 2 virtual desktops.

I wanted to open system settings to see if it was just a misconfiguration I’d made. But it doesn’t launch, so I tried to open it from the command line with `systemsettings`  but I got this error.

libEGL warning: MESA-LOADER: failed to open simpledrm: /usr/lib/dri/simple
drm_dri.so: cannot open shared object file: No such file or directory (sea
rch paths /usr/lib/dri, suffix _dri)

MESA: error: CreateSwapchainKHR failed with VK_ERROR_INITIALIZATION_FAILED
MESA: error: zink: could not create swapchain

I figured there was an issue with Plasma or KDE so I looked at the forum and did some searching. I found that there have been a lot of issues recently with KDE/Plasma going up to version 6 so I tried resetting the configs as I saw suggested somewhere. This didn’t seem to change anything. I also reinstalled Plasma and KDE in line with the arch wiki

I tried reinstalling the `nvidia` drivers and I tried both `nvidia` and `nvidia-dkms`. This seems to have made something worse… I now get a different error and the command hangs when I run `systemsettings`

libEGL warning: MESA-LOADER: failed to open simpledrm: /usr/lib/dri/simple
drm_dri.so: cannot open shared object file: No such file or directory (sea
rch paths /usr/lib/dri, suffix _dri)

MESA: error: CreateSwapchainKHR failed with VK_ERROR_INITIALIZATION_FAILED
MESA: error: zink: could not create swapchain
MESA: error: CreateSwapchainKHR failed with VK_ERROR_INITIALIZATION_FAILED
MESA: error: zink: could not create swapchain
qt.qml.typeresolution.cycle: Cyclic dependency detected between "qrc:/qt/q
ml/org/kde/desktop/private/TextFieldContextMenu.qml" and "qrc:/qt/qml/org/
kde/desktop/MenuItem.qml"
qt.qml.typeresolution.cycle: Cyclic dependency detected between "qrc:/qt/q
ml/org/kde/desktop/private/TextFieldContextMenu.qml" and "qrc:/qt/qml/org/
kde/desktop/MenuItem.qml"
MESA: error: CreateSwapchainKHR failed with VK_ERROR_INITIALIZATION_FAILED
MESA: error: zink: could not create swapchain

I then found this post: https://bbs.archlinux.org/viewtopic.php?id=293502
Followed the instructions here: https://wiki.archlinux.org/title/NVIDIA … de_setting
And the command to check still returns `N`

Latest `journalctl -b` output: https://0x0.st/HhKP.txt
Pacman log https://0x0.st/HhKT.log

I am a software engineer but I’m one of those front-end people and I’m trying this OS for my machine to try and better myself on Linux. I have reached out to a Slack group with no luck. I am the “skilled friend” at this stuff in most of my friend groups. So I feel like I need to reach out here.

I normally use the machine to play games. Or code on personal projects. I can launch Steam and some games work but the usability of it is quite poor at the moment so I’d like to fix it if I can.

Please let me know if there is any information I’ve omitted.
Thanks in advance.

DanTheOrange

Member

Registered: 2024-03-08

Posts: 4

Re: Plasma 6 post-upgrade issues.

I just had a read of this post, as it is newer than my searching. https://bbs.archlinux.org/viewtopic.php?id=293533

I will admit I am very new to all this and not entirely clear in my head about the separation of differences between KDE, Plasma, Wayland, or X11.

X11 never worked for me after installation. So I switched away from it and never touched it again. I was always using Wayland. I just tried the monitor suggestion with Wayland, to no avail. I thought I'd click the X11 option and give it a go. It has launched perfectly into a multi-monitor desktop where things seem to work. I think I will stick with X11 for now as long as it does work. Which I am currently testing.

DanTheOrange

Member

Registered: 2024-03-08

Posts: 4

Re: Plasma 6 post-upgrade issues.

Okay, X11 seems to be working and fairly Stable. I'm happy not needing to fix the Wayland side since everything seems in working order.

I wouldn't mind understanding the problem more but I can do that in my own time. Happy to close this.

Scimmia

Fellow

Registered: 2012-09-01

Posts: 13,654

Re: Plasma 6 post-upgrade issues.

I then found this post: https://bbs.archlinux.org/viewtopic.php?id=293502
Followed the instructions here: https://wiki.archlinux.org/title/NVIDIA … de_setting

Except you didn't. As the wiki says and as I said in that thread, you MUST do this on the kernel command line.

DanTheOrange

Member

Registered: 2024-03-08

Posts: 4

Re: Plasma 6 post-upgrade issues.

I then found this post: https://bbs.archlinux.org/viewtopic.php?id=293502
Followed the instructions here: https://wiki.archlinux.org/title/NVIDIA … de_setting

Except you didn't. As the wiki says and as I said in that thread, you MUST do this on the kernel command line.

It turns out I didn't apply them correctly and missed one command

grub-mkconfig -o /boot/grub/grub.cfg

Thanks for your reply everything is working now.

RhineRiver

Member

Registered: 2024-03-11

Posts: 1

Re: Plasma 6 post-upgrade issues.

Sorry for bumping up somebody elses thread but I had the exact same issue yesterday and was able to fix it by adding

nvidia_drm.modeset=1

to my kernel cmdline at

/etc/kernel/cmdline

Today I was also able to use my system normally but after installing updates through yay and restarting the issue has reappeared. I then checked my kernel cmdline again and the parameter I added yesterday was gone but now even after re-adding it the issue still persists. If there is any useful additional info I can provide I'd be happy to. Thanks a lot in advance!

Edit: I am using systemd for booting, not Grub

Edit2: I was able to fix it by running sudo reinstall-kernels

Last edited by RhineRiver (2024-03-12 12:39:13)