When logging into a KDE Plasma session, desktop icons appear on the left monitor (secondary monitor - not where they are supposed to be) and the desktop icons become unresponsive.
Right-clicking works, but dragging does not show the multi-select highlight, and icons are unresponsive.
Restarting plasmashell using “systemctl --user restart plasma-plasmashell.service” fixes this problem, but the issue returns upon each login. The icons even return to their proper positions on my right monitor (primary monitor).
I suspect a recent update may have been the cause, but I do not know where to begin looking to troubleshoot this particular issue without reinstalling my OS.
I’m a bit new to making posts as I usually rely upon what I can find on the internet, so please let me know if there is etiquette that I am lacking or additional information I should provide. Please go easy on me.
Operating System: Fedora Linux 44
KDE Plasma Version: 6.7.5
KDE Frameworks Version: 6.31.0
Qt Version: 6.11.2
Kernel Version: 7.2.11-200.fc44.x86_64 (64-bit)
Graphics Platform: Wayland
Processors: 8 × Intel® Core™ i7-7700K CPU @ 4.20GHz
Memory: 32 GiB of RAM (31.3 GiB usable)
Graphics Processor: NVIDIA GeForce GTX 1080 Ti
Monitor Count: 2 (2560x1440-primary, 1920x1080-secondary)
Check the system and user journals for errors when this happens.
In particular see if there are logs from kwin and plamashell.
I use this command to check the user journal:
journalctl --user -b 0 -g 'kwin|plasmashell'
Are you using the RPMfusion nvidia drivers for your GPU?
You can check with inxi (you may need to install inxi):
inxi -G
It is almost never needed to reinstall the OS to work on an issue like this.
Hiya, thanks for the reply. I also forgot to mention that my shell is frozen upon logging in for about a minute or two before I can use my taskbar or anything.
Output from command: journalctl --user -b 0 -g ‘kwin|plasmashell’
Oct 27 13:42:47 meower-supply systemd[1657]: Starting plasma-kwin_wayland.service - KDE Wayland Compositor…
Oct 27 13:42:47 meower-supply systemd[1657]: Started plasma-kwin_wayland.service - KDE Wayland Compositor.
Oct 27 13:42:49 meower-supply systemd[1657]: Starting plasma-plasmashell.service - KDE Plasma Workspace…
Oct 27 13:42:49 meower-supply systemd[1657]: Started plasma-plasmashell.service - KDE Plasma Workspace.
Oct 27 13:43:51 meower-supply drkonqi-coredump-launcher[5662]: Unable to find file for pid 2105 expected at “kcrash-metadata/plasmashell.c840a10cfe644db0932050fdcda7f0ac.2105.ini”
Oct 27 13:43:52 meower-supply drkonqi-coredump-launcher[5695]: Unable to find file for pid 2135 expected at “kcrash-metadata/plasmashell.1708fc22d623483c8785b794674419a7.2135.ini”
Oct 27 13:43:52 meower-supply drkonqi-coredump-launcher[5702]: Unable to find file for pid 2277 expected at “kcrash-metadata/plasmashell.7719dbb4b2b44afb8620f3160bb0b15f.2277.ini”
Output from command: inxi -G
Graphics:
Device-1: NVIDIA GP102 [GeForce GTX 1080 Ti] driver: nvidia v: 580.178.04
Device-2: Logitech C920 HD Pro Webcam driver: snd-usb-audio,uvcvideo
type: USB
Device-3: MacroSilicon USB Video
driver: hid-generic,snd-usb-audio,usbhid,uvcvideo type: USB
Display: wayland server: X .org v: 1.21.1.25 with: Xwayland v: 24.1.14
compositor: kwin_wayland driver: X: loaded: nvidia unloaded: modesetting
gpu: nvidia,nvidia-nvswitch resolution: 1: 2560x1440~144Hz
2: 1920x1080~60Hz
API: EGL v: 1.5 drivers: nvidia,swrast
platforms: gbm,wayland,x11,surfaceless,device
API: OpenGL v: 4.6.0 compat-v: 4.6 vendor: nvidia mesa v: 580.178.04
renderer: NVIDIA GeForce GTX 1080 Ti/PCIe/SSE2
API: Vulkan v: 1.4.341 drivers: nvidia,llvmpipe surfaces: N/A
Info: Tools: api: clinfo, eglinfo, glxinfo, vulkaninfo
de: kscreen-console,kscreen-doctor gpu: lact, nvidia-settings, nvidia-smi
wl: wayland-info,wlr-randr x11: xdriinfo, xdpyinfo, xprop, xrandr
You have plasmashell crashing.
Does coredumpctl list have an entry for plasmashell?
If so try coredumpctl dump plasmashell.
What do you see?
Also can you confirm if you have the RPMfusion drivers for the nvidia card installed?
Ah, sorry I thought RPMFusion would be in the output of that command. I’m pretty sure I’m using the RPMFusion drivers. If they’re the proprietary ones, then yes. I have the newest that my GPU supports which is 580.178.04 (my GPU lost support at the beginning of this year).
There are entries for plasmashell in coredumpctl list, however trying “coredumpctl dump plasmashell” gives an incredibly long output ending with (in red):
Refusing to dump core to tty (use shell redirection or specify --output).
I also tried coredumpctl dump --output plasmashell in response to that, which also had a crazy long output ending with (in blue)
More than one entry matches, ignoring rest.
As I’m not quite sure how to make sense of the output nor how to provide it here in a small enough package here is at least what the end of it looks like before the blue text
Stack trace of thread 2945:
#0 0x00007f4cdf682352 \__syscall_cancel_arch (libc.so.6 + 0x7b352)
#1 0x00007f4cdf67654c \__internal_syscall_cancel (libc.so.6 + 0x6f54c)
#2 0x00007f4cdf676594 \__syscall_cancel (libc.so.6 + 0x6f594)
#3 0x00007f4cdf6f0466 ppoll (libc.so.6 + 0xe9466)
#4 0x00007f4cde571165 g_main_context_iterate_unlocked.isra.0 (libglib-2.0.so.0 + 0x48165)
#5 0x00007f4cde571223 g_main_context_iteration (libglib-2.0.so.0 + 0x48223)
#6 0x00007f4ce005defd \_ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt6Core.so.6 + 0x45defd)
#7 0x00007f4cdfd1a78b \_ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt6Core.so.6 + 0x11a78b)
#8 0x00007f4cdfe4b34a \_ZN7QThread4execEv (libQt6Core.so.6 + 0x24b34a)
#9 0x00007f4ce1af4e5a \_ZN18QQuickPixmapReader3runEv (libQt6Quick.so.6 + 0x2f4e5a)
#10 0x00007f4cdff0788f \_ZN14QThreadPrivate5startEPv (libQt6Core.so.6 + 0x30788f)
#11 0x00007f4cdf679c42 start_thread (libc.so.6 + 0x72c42)
#12 0x00007f4cdf6fd5ac \__clone3 (libc.so.6 + 0xf65ac)
ELF object binary architecture: AMD x86-64
You should raise a bug in the kde bug tracker with the full output of the coredumpctl command. It says redirect to a file to get the full output.
You can add that to the bug report. Then a plasmashell maintainer can comment on why it’s crashing.
Understood. I am in the process of making an account there, and posting a bug report (I searched the current bugs and did not find anything that matches this issue).
They closed it as duplicate but what they linked it to didn’t seem very similar. I hope they plan on fixing this. They say they fixed it, but didn’t say which version fixes it. All I know is I don’t have the fix yet am I’m on the newest version that Fedora KDE gets.
6.8.1 or .2 will be in fedora 45 on release.
Thanks, I didn’t know that. Is it possible to downgrade KDE Plasma versions in the meantime? This and a few other problems I hadn’t even mentioned occurred after an update.
You can try downgrading plasma shell and see if that helps.
sudo dnf downgrade plasmashell
Ahh sadly I was met with the following output:
Updating and loading repositories:
Fedora 44 - x86_64 - Updates 100% | 62.1 KiB/s | 20.9 KiB | 00m00s
Repositories loaded.
Failed to resolve the transaction:
Problem: problem with installed package
- installed package kf6-kmime-6.31.0-1.fc44.x86_64 requires libQt6Core.so.6(Qt_6.11)(64bit), but none of the providers can be installed
- package kf6-kmime-6.31.0-1.fc44.x86_64 from updates requires libQt6Core.so.6(Qt_6.11)(64bit), but none of the providers can be installed
- cannot install both qt6-qtbase-6.10.2-2.fc44.x86_64 from fedora and qt6-qtbase-6.11.2-3.fc44.x86_64 from @System
- cannot install both qt6-qtbase-6.11.2-3.fc44.x86_64 from updates and qt6-qtbase-6.10.2-2.fc44.x86_64 from fedora
- package plasma-desktop-6.6.4-1.fc44.x86_64 from fedora requires libQt6Core.so.6(Qt_6.10_PRIVATE_API)(64bit), but none of the providers can be installed
- conflicting requests
You can try to add to command line:
–skip-broken to skip uninstallable packages
looks like downgrade will not work.
That’s alright. My “systemctl --user restart plasma-plasmashell.service” temporary fix has been suitable in the meantime.
I’ve also recently learned how soon the new Fedora update is coming so I’m hoping this, and all of my other issues that seemed to be caused by an update are resolved in this upcoming update.
I’ll update this thread with the results.
Here’s hoping the 6.8.x fixes your issues.
My OS has not updated to Fedora 45 but I got the Plasma 6.8.2 update. It appears the update did not fix any of the bugs I’ve been dealing with. Is it possible to uninstall and reinstall KDE Plasma without having to reinstall my entire OS?
search your package manager for “plasma-desktop” and reinstall it.
I ran the reinstall argument for the dnf command since the remove argument just told me it was a protected package.
Sadly, this did not work. Whatever a previous update did to break things, it seems to still persist through the reinstall. Although the reinstall did keep settings and such.