Perhaps try killing the process plasmashell and open it up again?
1 Like
People will need a lot more information than these pictures to try help you have a read of this and post some system information. https://discovery.endeavouros.com/forum-log-tool-options/how-to-include-systemlogs-in-your-post/2021/03/
5 Likes
Do you have an nvidia graphics card or a hybrid card with nvidia?
If so, you may need to add these kernel parameters:
nvidia-drm.modeset=1 nvidia-drm.fbdev=1
as shown here.
1 Like
I think this would only relate to boot issues but I’m not 100% sure. On my nvidia desktop i only have this in the grub command line.
GRUB_CMDLINE_LINUX_DEFAULT='nowatchdog nvme_load=YES nvidia-drm.modeset=1 loglevel=3'
I’m running KDE Plasma on Wayland with Nvidia. No issues.
1 Like
You are not the starter of this thread. Just because you don’t have issues on your system doesn’t mean it is that way for everyone. While the 1060 will work fine with wayland with some apps, omitting nvidia-drm.fbdev=1 could cause the eos-welcome dialog not to be displayed and other shananigans.
2 Likes
This doesn’t always work.
https://wiki.archlinux.org/title/Talk:NVIDIA#Framebuffer_consoles_experimental_support
I had similar issues after hibernation with my nvidia PC. For details take a look in this forum post
According to your logic: It works for me so how could anyone else have a problem?
2 Likes
I have Intel/Nvidia laptop and used nvidia-inst for drivers install, it generated nvidia-drm.modeset=1 and nvidia_drm.modeset=1
But I think without any further input from the OP there’s no reason to speculate on what he may have.
Different hardware!
1 Like