KDE Plasma weirdness after upgrade to 38

Ask Fedora
, ,
1

So, I’ve discovered a few annoyances after upgrading my machine from Fedora 37 Plasma to 38 Plasma.
First, and the most important, is that kwin randomly crashes. Most of the time it is just after I first login. Problem Reporting pops up with a kioslave5 crash. I’ve tried filing a bug without success (I think I am doing something wrong). However, I did notice some recent activity on this bug (Bug 2185282).
Has anyone ran into this issue and found a solution yet?
Second, for some reason, my mouse cursor arrow changes when I hover over a different portion of a window or on a empty desktop and I don’t know how to fix it. See screenshot animated gif below behavior.
Finally, (and I just discovered this while typing this post), Dolphin is really messed up and almost unusable in its color scheme. See screenshot animated gif below behavior.
Thoughts? Solutions? Is this something that should be filed with the KDE developers?

Peek 2023-07-02 10-38

By the way, I have an NVIDIA GPU and I wonder if that has anything to do with it.

2

Are you using the rpmfusion drivers? Check if they loaded.
Are you using X11 or wayland? If wayland does x11 work?

3

I am using rpmfusion drivers. I use X11.

4

Use lsmod to check if nvidia driver is loaded. What fo you find?
Did you try X11?

5

I’m sorry, I meant to state I use X11. I edited the post.

Here is my lsmod output:

lsmod | grep -i nvidia
nvidia_drm             94208  38
nvidia_modeset       1560576  84 nvidia_drm
nvidia_uvm           3493888  0
nvidia              62517248  4326 nvidia_uvm,nvidia_modeset
video                  73728  2 asus_wmi,nvidia_modeset
6

So, the intermittent is becoming almost persistent now. KDE and/or X11 seems to be crashing almost as soon as I login. It takes close to a minute before it crashes, but it crashes. The only way to get back in is to reboot remotely via ssh. I can’t even access the system console via Ctrl-Alt-F2 or F3 or F4.
Any thoughts? Recommendations?
I’ve been looking through journalctl but there is so much to view, so far I don’t know what to look for.

7

Which nvdia gpu do you have?
Check dmesg output, is there a kernel crash?
Check the journal for clues as well.

8

I have the GeForce GTX 970.
So, ironically, the one time I have journalctl -f running remotely to view real time logs it doesn’t crash.
I’ll have to keep monitoring, I guess.

By the way, just before this time around of not crashing I completed an update and it updated a bunch of pipewire packages. Not sure if that may have fixed anything related or not.

9

The GTX 970 should be able to use the 535.54.03 driver. Is that the one installed?
dnf list installed '*nvidia*'

Is the system fully updated? sudo dnf upgrade --refresh

Pipewire should not be related to the crashes, but the only way to tell for sure is to have it show in the logs.

10

So, I do have 535.54.03 installed. But I’m seeing two different versions: 535.54.03-1 & 535.54.03-2. Could there be a conflict?

[ed@edfed: ~]$ dnf list installed ‘nvidia’
Installed Packages
akmod-nvidia.x86_64 3:535.54.03-1.fc38 @rpmfusion-nonfree-updates
kmod-nvidia-6.3.11-200.fc38.x86_64.x86_64 3:535.54.03-1.fc38 @@commandline
kmod-nvidia-6.3.8-200.fc38.x86_64.x86_64 3:535.54.03-1.fc38 @@commandline
nvidia-gpu-firmware.noarch 20230625-151.fc38 @updates
nvidia-settings.x86_64 3:535.54.03-1.fc38 @rpmfusion-nonfree-updates
xorg-x11-drv-nvidia.x86_64 3:535.54.03-2.fc38 @rpmfusion-nonfree-updates
xorg-x11-drv-nvidia-cuda-libs.x86_64 3:535.54.03-2.fc38 @rpmfusion-nonfree-updates
xorg-x11-drv-nvidia-kmodsrc.x86_64 3:535.54.03-2.fc38 @rpmfusion-nonfree-updates
xorg-x11-drv-nvidia-libs.i686 3:535.54.03-2.fc38 @rpmfusion-nonfree-updates
xorg-x11-drv-nvidia-libs.x86_64 3:535.54.03-2.fc38 @rpmfusion-nonfree-updates
xorg-x11-drv-nvidia-power.x86_64 3:535.54.03-2.fc38 @rpmfusion-nonfree-updates

dnf upgrade --refresh just updated glib2 and ansible.

11

It is expected that you have one kmod RPM for each kernel you have installed.

12

That seems perfectly fine at present. I have the same.
Normally that is not the case but apparently the xorg packages had some updates that did not directly affect the driver.

13

So, just an update. I’m not sure what happened but the issue stopped.
Weird.