New install Fedora 40 KDE found two bugs already

Hello everyone,

Glad I am being allowed to even make a post from a Fedora installation. To my misfortune however, I have been unable to enjoy and discover this operating system; due to first log in I have already found problems. For the sake of giving you all troubleshooting data and results and have someone else not go through this I decided to just have the system run for a few of days while you guys walk me through getting logs and possibly a solution. Instead of running to the next OS unbothered.

Keep in mind this is a completely fresh Fedora 40 KDE installation on bare metal.

System is
CPU AMD 3900x
Nvidia 3090
32GB ram
3 screens far left 1440p 144hz, middle 1440p 165hz, far right 1080p 60hz

Issue #1
Mouse pointer disappears when jumping from monitor to monitor, except on the primary monitor. Restarting plasma as I have seen in the internet with killall plasmashell && kstart5 plasmashell does nothing to change it. I’ll up you one more head scratcher on this one. When I am at the login screen, if I choose to login to the far left monitor, then the far left monitor will have no issues with the mouse whatsoever. The rest will present this issue. If I login to the monitor in the middle, then it will be the monitors on the sides which will present the problem. Neat ain’t it?
Rebooting does nothing to resolve this issue. I can kind of figure out where my mouse is, if I right click then the “configure desktop and wall paper” menu will come up. I can see by the UI where the mouse is hovering thru. For whatever reason I was able to sometimes make it show up again by clicking the main monitor in an empty part of the desktop and move between monitors back and forth again; however I am having little luck replicating this last part. It is unreliable.

Issue #2
The discover bar shows constantly “click to restart device Computer needs to restart”. I have applied sudo dnf update, sudo dnf upgrade, and I have rebooted several times through terminal, through the discover button requesting it and through manual means, but it just won’t go away. And I mean, it is a BRAND NEW fresh install, I do not think this should be the case specially after I updated and upgraded through terminal.

Issue #3
Left the system alone as I said I would for troubleshooting. Well, when I came back to after a good night of sleep, was the inability to wake the system up. My keyboard would show sings of being awake. My system LEDs show it woke up to me tapping on the keyboard, but the screens were black/blank. I forced rebooted and I get this error when I came back into the desktop
“Unexpected system error, the system has encountered a problem and recovered.
A kernel problem occurred, but your kernel has been tainted (flags:GW). Explanation:
W - Kernel issued warning.
Kernel maintainers are unable to diagnose tainted reports.”

Since this is a second day of not getting anywhere, and in fact finding more bugs as time goes on. I give up. I do not feel this is the experience I was expecting as a new user on a brand new system before I even modify nothing.

Thank you everyone, maybe in another life.

Best regards.

f40 has plasma 6 and fixes for plasma 5 may well not work.
I do not have a multi-screen setup to test with, other will need to comment.

If you do as asked, “click on restart”, does that resolve the issue?
(I know that does not explain why its prompt for a restart).

Thank you for your fast response. Yes I can do as asked and reboot, I have several times. Via directly on the discover taskbar, terminal, and manually rebooting. All of them to no solution. When it comes back up, requests for it again.

Also I do see it reboots and brings up the desktop when I apply the plasmashell fix. So it seems to do it, just won’t solve the problem with the mouse.

Thanks.

Try this: Go into Discover and tell it to do an update.
As you have already updated with dnf it should find nothing needs updating.

Plasma 6 is a new code base, I’m not surprised a work around for the old code does not work.

1 Like

Discover says up to date; Taskbar disagrees still.

I’d agree with the statement plasmakill is not fixing it, seems correct old code doesn’t work.

Cheers.