Hey!
I just updated my system and am encountering an issue–my taskbar is completely extremely laggy to the point of it being unusable. The other parts of my system are fully functional (I can alt-tab, open system monitor, open settings, open a terminal, etc…), but the taskbar is unresponsive. Additionally, right clicking my wallpaper to open up options does nothing. I have found something interesting: Unplugging my second monitor and executing killall plasmashell && kstart plasmashell
seems to fix it, but when I replug in my second monitor the issue reappears. Unplugging my second monitor then restarting also fixes it (I have to keep it unplugged or the issue reappears.) If I execute killall plasmashell && kstart plasmashell
with my second monitor plugged in, the issue persists. This only happened after I updated my system. I would revert my packages, but it’s 100 of them. I am using wayland and a nvidia gpu. Logs:
System information - https://0x0.st/8oKK.txt
Boot log - https://0x0.st/8oKN.txt
If anyone has any ideas, please help.
Thanks!
I am going to suggest what I suggest to most and try the different kernels out and see if that helps. Upon boot using the LTS kernel the taskbar remains inactive for about 2 to 3 minutes after boot but on Zen and mainline it is responsive within about 30 seconds
Over the past week I’ve been experiencing some issues too @Hypnoshell and I’m fairly sure it was after an update. I had tried downgrading mesa
but that proved unhelpful.
The LTS kernel likewise proved unhelpful. I typically use Zen.
Try logging with which ever session type you’re not currently using (X11 / Wayland) and see if you get better results. This is currently my only real workaround.
In your ~/.config/kdeglobals
file, what setting is specified under [QtQuickRendererSettings]
? You can also view that setting by opening Plasma Renderer. I’d caution adjusting anything just yet though.
I am going to suggest what I suggest to most and try the different kernels out and see if that helps. Upon boot using the LTS kernel the taskbar remains inactive for about 2 to 3 minutes after boot but on Zen and mainline it is responsive within about 30 seconds
@smokey Thanks for your idea, but it doesn’t seem to have worked. I tried the LTS kernel but it seems to still be happening. (I mainly use mainline kernel.)
Try logging with which ever session type you’re not currently using (X11 / Wayland) and see if you get better results. This is currently my only real workaround.
I tried x11, but the problem remains. Not really a difference.
In your
~/.config/kdeglobals
file, what setting is specified under[QtQuickRendererSettings]
?
Interestingly enough, the [QtQuickRendererSettings]
is missing from the ~/.config/kdeglobals
file. I attached an image of what it says in the Plasma Renderer executable.
A few notes:
- Before the issue started, text would appear on both of my monitors when booting up my computer. Now, however, text only appears on my second monitor when I’m booting.
- Sometimes my sound icon says it’s muted, even though it’s not. No clue why
- When I try to shutdown my computer, it gets stuck on “a stop job is running for User Manager for UID 1000” It goes until it reaches the maximum alloted time of 1 minute and 49 seconds. It also sometimes blinks.
More logs that could be useful:
Pacman log - https://pastebin.com/py66eUNt (Using pastebin because I wanted to just show the latest update lol)
Journalctl log - https://0x0.st/8oqw.txt
dmesg - https://0x0.st/8oq3.txt
I just thought of something I would normally suggest but don’t think I did, does the same occur with a new user/account?
Have not tried that… but I just changed where I put my cable into my monitor and put it back into it’s normal place… and now it’s fixed (???). I would NOT close this post until I’m certain, but yeah.
Journalctl log: https://0x0.st/8oq6.txt
Turns out, nope! This was not the fix. I restarted my computer to change to the arch kernel, and it happened again. What I found out during testing: It seems like having more than one applications menu bar and default panel causes the crash. What I was seeing when I plugged in my second monitor was because I had a default panel on both monitors. So yeah, remove one and it is fixed. No clue why. I’ll make an additional post/edit to include more information later today. @Bink @smokey
Update: It fixed itself. For more details, check the related post I created: https://discuss.kde.org/t/having-1-application-launcher-crashes-plasmashell/28453/5
This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.