Bug 517749 - System Tray settings for Discord and Discord PTB are linked. Changing one updates both.
Summary: System Tray settings for Discord and Discord PTB are linked. Changing one upd...
Status: RESOLVED DUPLICATE of bug 470840
Alias: None
Product: plasmashell
Classification: Plasma
Component: System Tray widget (other bugs)
Version First Reported In: 6.6.2
Platform: CachyOS Linux
: NOR normal
Target Milestone: 1.0
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2026-03-18 13:29 UTC by kde.stoop672
Modified: 2026-03-18 14:37 UTC (History)
2 users (show)

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

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description kde.stoop672 2026-03-18 13:29:02 UTC 
SUMMARY
System Tray settings for Discord and Discord PTB are linked. Changing one updates both.

STEPS TO REPRODUCE
1. Open Discord and Discord PTB so that they are visible in the system tray
2. Try to hide one in System Tray Settings > Entries.

OBSERVED RESULT
Both entries sync. If I hide PTB, Stable version hides too.

EXPECTED RESULT
They should be independent so i can hide/show them separately.


Operating System: CachyOS Linux 
KDE Plasma Version: 6.6.2
KDE Frameworks Version: 6.24.0
Qt Version: 6.10.2


ADDITIONAL INFORMATION
I am running a triple-monitor setup, my goal is to have Discord PTB pinned/shown on my left monitor's tray and Discord Stable shown only on my right monitor's tray. 
Because the settings are currently linked, I cannot isolate them to their respective screens. 
When I try to configure one for a specific monitor, the other app is updated as well in the Entries, making it impossible to manage my multi monitor workspace effectively.

❯ pacman -Qs discord
local/discord 1:0.0.129-1
    All-in-one voice and text chat for gamers
local/discord-ptb 0.0.182-1
    All-in-one voice and text chat for gamers - public test build
Comment 1 Nicolas Fella 2026-03-18 14:37:55 UTC 

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