Bug 460907

Summary: System tray sometimes overlaps the clock until plasmashell is restarted or screen layout is changed
Product: [Plasma] plasmashell Reporter: Oded Arbel <oded>
Component: PanelAssignee: Plasma Bugs List <plasma-bugs>
Status: RESOLVED DUPLICATE    
Severity: normal CC: materka, nate, niccolo.venerandi
Priority: NOR    
Version: master   
Target Milestone: 1.0   
Platform: Other   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:
Attachments: Screenshot showing the problem
How it looks today after a plasmashell restart
How it looks in Plasma 6 - I think it is worse than before?
how it looks in Plasma 6 on the vertical screen

Description Oded Arbel 2022-10-23 20:17:52 UTC
SUMMARY
Running on Neon unstable, under wayland, when plasmashell starts, the system tray icons get squished under the clock, so it is not possible to access the system tray overflow menu and often the network manager menu is not accessible. See screenshot.

I am not sure when it started - I started using Neon unstable when the work on moving to Jammy started, and tried the wayland and it immediately start like this.

The problem can be worked around by entering "edit mode" and then dismissing it,  which fixes the rendering until next time the shell starts.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: 
KDE Plasma Version: 5.26.80
KDE Frameworks Version: 5.100.0
Qt Version: 5.15.6
Comment 1 Oded Arbel 2022-10-23 20:18:27 UTC
Created attachment 153153 [details]
Screenshot showing the problem
Comment 2 Nate Graham 2022-10-24 20:26:13 UTC
the heck
Comment 3 Oded Arbel 2022-11-08 19:26:55 UTC
Just got back to X11 to check something, and it happens there as well.
Comment 4 Nate Graham 2023-05-16 20:59:12 UTC
Are you able to reproduce this in Plasma 5.27 at all?
Comment 5 Oded Arbel 2023-05-16 23:11:10 UTC
(In reply to Nate Graham from comment #4)
> Are you able to reproduce this in Plasma 5.27 at all?

I still have this issue after restarting the shell (`systemctl restart --user plasma-plasmashell.service`).

Changing the primary display (to an external screen and back) fixes it, the same as getting into edit mode and changing switching display configurations: I've been going to the office a lot more lately - which involves changing the display configurations a few times a day, and not restarting plasmashell too often - as I'm not on the development branch anymore, so this problem had been bothering me a lot less, but I can still repro it.
Comment 6 Oded Arbel 2023-05-16 23:12:37 UTC
Created attachment 159020 [details]
How it looks today after a plasmashell restart
Comment 7 Nate Graham 2023-05-17 14:11:39 UTC
How bizarre. I'm at a loss regarding how this would be happening, and why changing the display layout fixes it.
Comment 8 Oded Arbel 2023-05-25 13:03:14 UTC
(In reply to Nate Graham from comment #7)
> How bizarre. I'm at a loss regarding how this would be happening, and why
> changing the display layout fixes it.

Actually, changing the screen configuration does not fix it - I was incorrect in stating that. Changing on which screen the panel appears (the primary screen) did fix the problem. The other screen is in a vertical orientation so the size of the panel actually changes.

I can reproduce the problem using plasma-desktop built from git master using kdesrc-build, and in this setup - changing the primary screen does not solve the problem - on the vertical screen the display is still messed up and when setting it back to the laptop's built-in screen it is also messed up.
Comment 9 Oded Arbel 2023-05-25 13:04:08 UTC
Created attachment 159248 [details]
How it looks in Plasma 6 - I think it is worse than before?
Comment 10 Oded Arbel 2023-05-25 13:04:31 UTC
Created attachment 159249 [details]
how it looks in Plasma 6 on the vertical screen
Comment 11 Oded Arbel 2023-05-25 13:25:41 UTC
I can no longer reproduce the problem, after I messed around with manually editing the configuration in the ~/.config/plasma-org.kde.plasma.desktop-appletsrc file, several restarts and org.kde.plasma.systemtray rewriting its configuration - it now looks fine and I cannot reproduce the issue.

I can't figure out anything significant that has changed - comparing the old configuration to the new one (I keep backups), the only thing changed around the panel's configuration is that I kicked the org.kde.plasma.systemtray configuration by changing its `SystrayContainmentId` value to something that was obviously incorrect and so it regenerated the `org.kde.plasma.private.systemtray` containment with a new (yet unused) ID. I see no other noticeable changes.
Comment 12 Oded Arbel 2024-05-11 13:39:13 UTC

*** This bug has been marked as a duplicate of bug 482098 ***