Bug 504858 - System tray widget added to a panel using the "+" button without dragging is invisible until next login
Summary: System tray widget added to a panel using the "+" button without dragging is ...
Status: VERIFIED FIXED
Alias: None
Product: plasmashell
Classification: Plasma
Component: System Tray widget (other bugs)
Version First Reported In: 6.3.90
Platform: Other Linux
: NOR normal
Target Milestone: 1.0
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2025-05-27 11:58 UTC by altmail
Modified: 2025-06-23 22:23 UTC (History)
4 users (show)

See Also:
Latest Commit:
Version Fixed/Implemented In: 6.4.0
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description altmail 2025-05-27 11:58:50 UTC
SUMMARY
When adding a system tray using the "+" or "Add widgets..." button on an empty panel and simply clicking on the widget in the selection list instead of dragging it onto the panel, the system tray is added but remains invisible until the next login.

STEPS TO REPRODUCE
1. Create an empty panel.
2. Click on the "Add widgets..."/"+" button to open the widget selection.
3. Click on the System Tray widget (do not drag it onto the panel!)
4. Observe that the system tray is invisible.
5. Log out and log back in.
6. Observe that the system tray is now visible.

See https://youtu.be/OCOBXb8DzmI?si=5wObZ2cEkUPbSbKz for a video demonstrating the issue.

OBSERVED RESULT
The added system tray is invisible until the next login.

EXPECTED RESULT
The system tray should be visible immediately.

SOFTWARE/OS VERSIONS
Operating System: Fedora Linux 42
KDE Plasma Version: 6.3.90
KDE Frameworks Version: 6.14.0
Qt Version: 6.9.0
Kernel Version: 6.14.6-300.fc42.x86_64 (64-bit)
Graphics Platform: Wayland
Processors: 12 ร— AMD Ryzen 5 5600X 6-Core Processor
Memory: 16 GiB of RAM (15.5 GiB usable)
Graphics Processor: NVIDIA GeForce RTX 2070
Comment 1 Nate Graham 2025-05-27 18:09:26 UTC
Thanks for the video; that's helpful. However I cannot reproduce the issue on git master with those steps, including making sure that the new empty panel is vertical.

Does it happen in a new clean user account on the same machine?
Comment 2 TraceyC 2025-05-27 23:47:10 UTC
I'm also not able to reproduce the bug on git-master, or Plasma 6.3.5
Comment 3 altmail 2025-05-28 00:02:34 UTC
(In reply to Nate Graham from comment #1)
> Thanks for the video; that's helpful. However I cannot reproduce the issue
> on git master with those steps, including making sure that the new empty
> panel is vertical.
> 
> Does it happen in a new clean user account on the same machine?

I can reproduce it on an entirely separate Fedora 42 installation (also using the Plasma 6.4 Beta, of course) on the same machine with a clean user account. It also happens with the nouveau driver, so it doesn't seem to be specific to the proprietary NVIDIA driver.
Comment 4 Bug Janitor Service 2025-06-12 03:48:04 UTC
๐Ÿ›๐Ÿงน โš ๏ธ This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information, then set the bug status to REPORTED. If there is no change for at least 30 days, it will be automatically closed as RESOLVED WORKSFORME.

For more information about our bug triaging procedures, please read https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging.

Thank you for helping us make KDE software even better for everyone!
Comment 5 John Kizer 2025-06-22 19:16:18 UTC
I can't reproduce on a Fedora KDE 42 VM with Plasma 6.4.0, or on my Fedora KDE 42 desktop (NVIDIA proprietary graphics) with Plasma from git master.

If you open up a terminal and enter `sudo journalctl --follow`, and then reproduce this issue, could you let folks here know if there are any errors that show up?

Thanks!
Comment 6 altmail 2025-06-23 15:29:57 UTC
I can't seem to reproduce the issue on Plasma 6.4 anymore (neither on my main installation nor the other one I had reproduced it on previously), so I guess it was fixed by some other change.
Comment 7 TraceyC 2025-06-23 22:22:51 UTC
Let's call this fixed in 6.4 then. If the issue happens again, feel free to set this report to REOPENED. Thanks!