Plasma 6.5 taskbar not working
Hi all, I'm not familiar with reporting bugs here, so please be patient.
Since switching to Plasma 6.5 on Bazzite with the latest update, I've been confronted to really frustrating issues. The first was the infamous black screen with mouse after login, which seems to be fixed.
Since then, it's the taskbar which behaves erratically : my app launcher randomly cease to show the menu, either by clicking it or with the Super key.
The button indicator lits up, but no menu. I've tried resetting my Plasma configuration to defaults, either by using the gui or with the terminal, using :
mv ~/.config/plasma-org.kde.plasma.desktop-appletsrc ~/.config/plasma-org.kde.plasma.desktop-appletsrc.old rm -rf ~/.cache/plasma* rm -rf ~/.cache/icon-cache.kcache
which seems to temporarily fix the issue, until it randomly (or apparently so), reappears.
Same thing by switching to another app launcher plasmoid, and by recreating another taskbar.
Logging out and back also temporarily fixes the issue, but only for a short time.
I'm using a Wayland session, with latest Nvidia drivers provided.
I don't want to rollback to a previous release yet, and I've found no information about other people affected by this.
Am I missing something ? Is there something else I could try ?
I've submitted a bug report on Github, with the same text.
Thanks for the support, Bazzite's been a blast so far, but these issues lately are quite frustrating.
33 Replies
After some research, I tried running journalctl --user -xe | grep plasmashell, and found this error which could be the source of the bug: Need a window and a context ToolTipDialog(0x56059387a770, visibility=QWindow::Hidden, flags=QFlags<Qt::WindowType>(FramelessWindowHint|WindowStaysOnTopHint|WindowDoesNotAcceptFocus), transientParent=0x560593a10e80, geometry=437,944 296x232)
I’ve removed all custom widgets and switch the app launcher to the application dashboard (which I don’t like because fullscreen), and see if the problem persists.
I’m quite a newbie, so I don’t know how to further look for a fix. Does anyone have an idea ?
For anyone interested, while I can't find the bug report on Github, it's apparently a known problem with some popup menus not rendering. Some users on Reddit have the same problem. For the context, I'm also using my laptop connected to a monitor, with the internal screen disabled. That may be a factor. Using application dashboard seems to have fixed the problem, for now, while waiting for the bug to be ironed out.
can confirm this bug also happens for me.
3 monitors, but on any monitor the application launcher will randomly just stop showing up. i made a resetkde.sh that i can slap open a terminal and reset it with but its super annoying.
we have the same gpu, I'm guessing it has something to do with wayland not playing nice with Nvidia
it also happens with the systemtray popups not appearing. Looks like an issue with drawing popup menus
This is probably not a bazzite specific thing and if I had to guess probably affects kde in general. I will try to search it up later.
I assume it also has to do with Nvidia and wayland aswell.
Its a pretty bad bug to have, although the application dashboard is actually preferable to me over the launcher now that ive used it, but I frequently use the sound applet (constantly) so it randomly not appearing is the most frustrating thing possible.
Its a pretty bad bug to have, although the application dashboard is actually preferable to me over the launcher now that ive used it, but I frequently use the sound applet (constantly) so it randomly not appearing is the most frustrating thing possible.
I've been digging and found some mentions about issues with Wayland not drawing popup with nvidia drivers, but nothing conclusive really about how to fix it
https://bugs.kde.org/
Have you found a bug report here?
I haven't so I figured i would ask
I've posted one, but no answer. I found some stuff on Reddit, not directly related, but the common factors are Nvidia and Wayland, and often using multi monitors. I personnally use my laptop on a monitor or TV, with the main screen disabled. Multi screen seems to be another possible factor
ah my bad, that was on github
I'll try digging to see if there are similar issues on kde
Do you mind sending me the link to github? As this issue is near and dear to my heart I would like as many angles as possible to see a resolution
I myself have 2 monitors and a TV hooked up at all times
Bug 508321 this one on KDE is similar
What's weird is my wife has a similar setup but has never had this issue, which at first led me to believe it was something I had customized or changed (I have a lot more done to my pc softwarewise then her)
GitHub
Plasma 6.5 taskbar possible Wayland issue. · Issue #3447 · ublue-...
Hi all, I'm not familiar with reporting bugs here, so please be patient. Since switching to Plasma 6.5 on Bazzite with the latest update, I've been confronted to really frustrating issues. ...
what's infuriating is that most of the issues I have with Bazzite right now started after the latests Plasma versions shipped with system updates
508321 is an application bug, not a panel bug but I can see the similarity in it not appearing.
I fear noone has posted about this specific bug on the kde site
yeah, I'm far from being linux-savvy, but all the signs I've found point to wayland not playing nice
The command you are using
"mv ~/.config/plasma-org.kde.plasma.desktop-appletsrc ~/.config/plasma-org.kde.plasma.desktop-appletsrc.old rm -rf ~/.cache/plasma* rm -rf ~/.cache/icon-cache.kcache" does it reset everything as in, does everything blink out of existence for awhile and then it comes back? Or is this clearing the cache without closing and reopening everything?
From what I recall, it also restarts Plasma, but I'm not sure, as I've always used it with a restart command right after
Ah, rip.
The reason I asked, is because if this was able to fix the issue without the abrupt restarting of plasma (what ive been doing) I was gonna just get some python script going that would just auto reset the cache every 20min effectively slapping a bandage on it.
heh, that could've been nice, yeah
some people suggest switching to a x11 session
bazzite doesn't have that though
yeah, maybe I'll have to distro hop and wait for the kinks to be ironed out. I dont wanna go back to windows 😭
also are you on NVIDIA
alas, yes
might be an NVIDIA thing
indeed, looks like some fuckery between wayland and nvidia
yeeeeah
like always i guess
NVIDIA always had wayland issues
much less so nowadays though
this sucks, linux is SO close to being a replacement for windows, and more and more people are considering switching
what's also really grating is that I didn't have any trouble so far, these issues appeared with Plasma 6.5 for me
an open source driver for newer nvidia cards is in the works though
NVIDIA is even helping sort of
welp, as long as I can still play some games, I'm fine with some quirks
though I've spent a lot of time looking for fixes lately, instead of gaming
I'll try switching to garuda or cachy, and see if these issues persist
It'd be a pain to reformat and redo everything (I use this everyday for most things) so while distrohopping is an enticing idea, I will likely not consider that until I update my pc and im going amd next time anyway, so it'd be a moot point then, ill post here if I find any solution
Yeah, I dont want to reformat and reinstall everything, and since I'm on a laptop, switching to amd gpu is not an option... Let me know if you find anything worthy :)*
Just a bump to see if anyone has this issue, or even heard of it ? The problem is very much still happening, and it's annoying as ever.
It hasn't affected me as much since using dashboard, but every once in awhile thr volume menu wont come up and then its resetkde.sh time luckily.i have a system tray on my top monitor too.
It still.hasnt affected my wife's pc Which confuses me because also Nvidia.
Are we the only 2 humans in existence this happened to? and if so, which library did I sudo ostree that caused it? Hmm
haha, imagine we're the only two person alive having this bug xD
Seriously tho, I think maybe other ppl having this bug either didn't report it, or are having the same issue with other apps, or we didn't report the issue correctly.
I'm still reluctant on rolling back to a previous update, but I wonder if rollback then update again would change anything ?
If you do let me know how it goes.