Bug 486245 - Discord taskbar indicator missing despite libunity being installed
Summary: Discord taskbar indicator missing despite libunity being installed
Status: RESOLVED DOWNSTREAM
Alias: None
Product: plasmashell
Classification: Plasma
Component: Panel (show other bugs)
Version: 6.0.5
Platform: unspecified Linux
: NOR minor
Target Milestone: 1.0
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-04-28 11:32 UTC by Anya
Modified: 2024-08-28 12:13 UTC (History)
3 users (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Anya 2024-04-28 11:32:10 UTC
SUMMARY
Previously there would be a circled number on Discords taskbar button indicating how many new messages or pings there are, if there are any. This is similar to Windows. It seems like with updating to KDE/Plasma 6 this functionality broke. I posted the bug on Discord's bug megathread on Reddit but I don't have high hopes for them to fix it.

STEPS TO REPRODUCE
1. Install KDE/Plasma 6 or higher, install Discord
2. Receive a new message or friend request

OBSERVED RESULT
The taskbar button does not change in appearance at all.

EXPECTED RESULT
There should be a little circle with a number in it on the taskbar button.

SOFTWARE/OS VERSIONS
Linux: 6.8.7-arch1-2 (64-bit)
(available in About System)
KDE Plasma Version: 6.0.4
KDE Frameworks Version: 6.1.0
Qt Version: 6.7.0
Wayland session (but I heard this happens on X11 too)

Sorry if this might have been posted already somewhere else, but I searched this site and couldn't find any mention of it yet. For clarity, I'm talking about the panels "Task Manager", not the systray.
Comment 1 Kye 2024-06-14 07:13:30 UTC
Some info:
Up until recently this could be fixed by launching discord with `XDG_CURRENT_DESKTOP=KDE5` due to how electron interacts with libunity. Now this seems to no longer work. I assume a plasma update broke this workaround and I didnt notice. 

More reading: https://github.com/Vencord/Vesktop/issues/298
Comment 2 Niccolò Venerandi 2024-08-28 12:13:12 UTC
Even after reading that thread, this seems to be an issue that has to be addressed on Discord side of things. Is there something we can do here?