Kde Plasma 6.5 taskbar bug

Bazzite
1

Hi all,
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 also posted the same topic as a bug report on Github. Github Report

2

Can you replicate the issue with Fedora live USB stick? That will indicate if its a Fedora issue upstream or a problem with Bazzite (or your setup with something like a corrupted cache file or something). I don’t think the live USB has the nvidia drivers though, so that variable can’t be replicated.

Whenever I have a problem on Bazzite, Aurora or Bluefin with the desktop, first thing I do is see if it’s the same on Fedora upstream.

3

Thanks for the suggestion, alas, I can’t test that as I don’t have any stick at hand (and it’ll be some days before I buy & receive one.)
If it’s a corrupted cache file, are there other files Plasma uses than the ones I’ve already deleted ?
I’ll order a stick, but I do want to try and fix it in the meantime. Rollback would be a huge pain in the a** at this moment, and while I can still us my machine, this issue is grating my nerves :grin:

4

Why would the rollback be an issue? How did you load bazzite on the machine its running on (initial install) did you use a usb then? I haven’t had to delete KDE cache files recently, so I’ll be of no hope there unfortunately.

5

Rollback would be an issue because if anything goes wrong, I’d lose even more time trying to fix it.
A previous rollback a few weeks ago (using rpm-ostree) didn’t go well, system would not boot, and I had to reinstall Bazzite to zero. I’m really anxious about going through that again :sweat_smile: And since I’m also currently working, I can’t afford that time and effort right now.
As for the stick, yeah, I had one when installing Bazzite a few months ago, but I lost it since :sweat_smile:
edit : no worries, thanks for your suggestions anyway :wink:

6

Thats really weird that a rollback did that. All the rollback would do is use a prior working image. if rolling back is causing issues….

Do you have packages layered?

7

I had some layered packages back then, maybe that was causing the issue. I can’t remember precisely what happened and didn’t try to search, I just reinstalled everything and went on my way rather than spending time searching for a solution.
Right now, I only have two layered packages, Coolercontrol and liquidctl.
The system worked without any issue until latest update shipping Plasma 6.5.

8

after some research, I tried running journalctl --user -xe | grep plasmashell, and got 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 ?

9

yea, those two packages you have layered shouldn’t cause an issue. At this point, testing in Fedora live is your best bet sans doing a re-install.

10

You might try to re-base to Aurora and test to see if the issue is just a bazzite issue or if its an issue that shows in both Aurora and Bazzite.

11

I can’t really find the exact issue on Github, but I’ve found some users on Reddit (on other distros using Wayland + Plasma) afflicted with the same problem. Apparently, it’s a known bug with Wayland and Plasma not drawing some popup, be it the app launcher, or when clicking some systemtray icons. For the context, I’m using my laptop with an external monitor and internal screen disabled, so that may be another factor. Switching to a full screen app launcher resolved this so far, until the bug is fixed.