StatusNotifierHostRegistered DBus signal is not allowed, thus broken tray support on KDE Plasma

bam · August 18, 2021, 5:50pm

Hi @review-team, seems we need the desktop-legacy slot access to solve an issue with Telegram tray icon when it’s snap is autostarted by KDE Plasma desktop:

keshavnrj · August 19, 2021, 6:41am

Telegram desktop sanp if built and published from their github repository (https://github.com/telegramdesktop/tdesktop/blob/dev/snap/snapcraft.yaml)? already contains the desktop-legacy slot, which gets auto connected to the core. Hence, the issue has nothing to do with it.

bam · August 19, 2021, 10:28am

Sorry I put it wrong. The root of the problem is StatusNotifierHostRegistered DBus signal can’t be passed to snap, despite desktop-legacy slot, so changes to snapd seem needed:

github.com/telegramdesktop/tdesktop

No systray icon if autostarted by KDE Plasma

opened 11:25AM - 18 Aug 21 UTC

closed 01:36PM - 19 Aug 21 UTC

bam80

Cross-linked from downstream issue: https://bugs.kde.org/show_bug.cgi?id=425315… The bug was closed in KDE as UPSTREAM, please reopen if we are wrong: https://bugs.kde.org/show_bug.cgi?id=425315#c28 > From the logs: > > :1.230 is telegram > It makes a DBus call to kded asking if we have any SNI hosts (i.e the system tray) > KDED is up and ready and available and the call to the SNI watcher works. > But there are no hosts as plasma isn't up yet so it returns false > We later emit that a host is registered, but at this point telegram doesn't care. > > From a plasma side that looks like everything is working correctly. Other than moving app restore until after plasma is fully up, there's not much we can do.

tdesktop already has desktop-legacy slot. The problem is it doesn’t allow StatusNotifierHostRegistered signal. I.e. we need slot to be changed in snapd source code, not to be connected.