https://bugs.kde.org/show_bug.cgi?id=425315
--- Comment #85 from Aleksandr Beliaev <[email protected]> --- (In reply to Ilya Fedin from comment #84) > Wait, I thought you're running Plasma? If you're not running Plasma then > your tray daemon is unlikely to be from Plasma... Sorry for late reply. I was several days away from Internet. Yep, definitely. It's native Awesome wibox.widget.systray I could only speculate what might cause crash. I start telegram automatically immediately after login. I tried to run various KDE applications, however only dolphin triggers the issue. After some tests... It's enough to open any file in Dolphin (e.g. text file with Kate, or picture with Gwenview) to destroy Telegram icon. Trace with journalctl shown the following sequence (# - my comments): === # starting dolphin Jul 15 20:20:07 systemd[1580]: Starting KActivityManager Activity manager Service... ..... Jul 15 20:20:07 systemd[1580]: Started KActivityManager Activity manager Service. ..... Jul 15 20:20:36 systemd[1580]: Started dbus-:[email protected]. # Open text file with Kate Jul 15 20:20:46 systemd[1580]: Started dbus-:[email protected]. Jul 15 20:20:46 telegram-desktop[1620473]: QDBusTrayIcon encountered a D-Bus error: QDBusError("org.freedesktop.DBus.Error.UnknownObject", "No such object path '/StatusNotifierWatcher'") Jul 15 20:20:46 systemd[1580]: Started Kate - Advanced Text Editor. === If I stop dbus-:[email protected] (systemctl --user stop dbus-:[email protected]), then restart telegram, tray icon has appearing. If I start dolphin again and open file, there a new instance of dbus-:[email protected] starts (where Y is a next number) and telegram icon crashes again. -- You are receiving this mail because: You are watching all bug changes.
