Bug 427326

Summary:	Telegram app system tray icon can't show it's right click context menu if was autostarted by KDE
Product:	[Plasma] plasmashell	Reporter:	pveax <pveax>
Component:	System Tray widget	Assignee:	Plasma Bugs List <plasma-bugs-null>
Status:	RESOLVED DUPLICATE
Severity:	normal	CC:	materka, nate
Priority:	NOR
Version First Reported In:	5.19.5
Target Milestone:	1.0
Platform:	Manjaro
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description pveax 2020-10-04 12:47:25 UTC

SUMMARY


STEPS TO REPRODUCE
1. Install Telegram app as package of official Manjaro Linux repo.
2. Set it up to loads automatically with OS (autostart).
3. reboot PC.
4. Right click on Telegram Icon in System Tray.

OBSERVED RESULT
No context menu appears.

EXPECTED RESULT
Show context menu (usually 4 items/lines).

Additional
But if to start Telegram manually after OS loads, than context menu available.

Sort of investigation was in Telegram's thread https://github.com/telegramdesktop/tdesktop/issues/8708

Key post could be this: 
https://github.com/telegramdesktop/tdesktop/issues/8708#issuecomment-703222635

We came to idea to call KDE developers to help to understand what's going on while KDE loads user session: why applications starts when no system tray or SNI is not available (yet not loaded).

Please take part in investigation of effect where context menu of system tray icon of Telegram does not shows when app starts via autostart versus context menu shows when the app starts manually.


SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: 
Operating System: Manjaro Linux
KDE Plasma Version: 5.19.5
KDE Frameworks Version: 5.74.0
Qt Version: 5.15.1
Kernel Version: 5.8.13-3-MANJARO
OS Type: 64-bit

ADDITIONAL INFORMATION
Please see Telegram thread.

May be I can gather KDE additional logs. What to try to do?

Thank you!

Comment 1 Konrad Materka 2020-10-08 17:38:03 UTC

Thank you for you report. I checked Telegram's thread, this is definitely a duplicate of Bug 425315 - please check it, there are some instructions how to get some logs and more info.

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