Bug 511097 - org.kde.plasma.systemtray applet does not load in Debian 14
Summary: org.kde.plasma.systemtray applet does not load in Debian 14
Status: RESOLVED DOWNSTREAM
Alias: None
Product: plasmashell
Classification: Plasma
Component: System Tray widget (other bugs)
Version First Reported In: 6.5.0
Platform: Other Linux
: NOR normal
Target Milestone: 1.0
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2025-10-25 14:01 UTC by arjenbalfoort
Modified: 2025-10-26 08:47 UTC (History)
2 users (show)

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


Attachments
Output of journalctl /usr/bin/plasmashell (3.82 KB, text/x-log)
2025-10-25 14:01 UTC, arjenbalfoort
Details

Note You need to log in before you can comment on or make changes to this bug.
Description arjenbalfoort 2025-10-25 14:01:32 UTC
Created attachment 186135 [details]
Output of journalctl /usr/bin/plasmashell

SUMMARY
org.kde.plasma.systemtray applet does not load in Debian 14 (testing, Forky).


STEPS TO REPRODUCE
1. Add org.kde.plasma.systemtray to panel or desktop.
2. Error window shows: "Error loading applet: package does not exist".


OBSERVED RESULT
An error window (see above)

EXPECTED RESULT
System Tray applet loaded and usable.

SOFTWARE/OS VERSIONS
Operating System: SolydXK EE 14 (Debian testing)
KDE Plasma Version: 6.3.6
KDE Frameworks Version: 6.18.0
Qt Version: 6.9.2
Kernel Version: 6.16.12+deb14+1-amd64 (64-bit)
Graphics Platform: Wayland


ADDITIONAL INFORMATION
See log file.
Comment 1 arjenbalfoort 2025-10-25 14:03:17 UTC
Comment on attachment 186135 [details]
Output of journalctl /usr/bin/plasmashell

gdb plasmawindowed
set logging enabled on
set logging file org.kde.plasma.systemtray.log
run org.kde.plasma.systemtray

Did not add any new information.
Comment 2 Antonio Rojas 2025-10-25 14:06:25 UTC
This is a packaging issue that you need to report to your distribution
Comment 3 arjenbalfoort 2025-10-25 15:17:30 UTC
You are right.
I just installed plasma-workspace from unstable and that solved the issue. We now just have to wait until the package get into testing.