Bug with opening context menu in KDE system tray

[ghost]

Hi!

I experiencing just the same issue as was in closed #7373

Steps to reproduce

1. Click on additional (right) mouse btn when pointer is over system tray icon

Expected behaviour

Display context menu

Actual behaviour

No any action

Configuration

Operating system:

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-1-MANJARO
OS Type: 64-bit

Version of Telegram Desktop:
2.4.
Previuos 2.3.2-2 version was with the same lack.

Installation source (Linux Only) - the official website / GitHub releases / flatpak / snap / distribution package:
"Community" official Manjaro repo.

$ pacman -Qi telegram-desktop
Name            : telegram-desktop
Version         : 2.4.0-1
Description     : Official Telegram Desktop client
Architecture    : x86_64
URL             : https://desktop.telegram.org/
Licenses        : GPL3
Groups          : None
Provides        : None
Depends On      : hunspell  ffmpeg  hicolor-icon-theme  lz4  minizip  openal  qt5-imageformats  xxhash  libdbusmenu-qt5  qt5-wayland  gtk3
Optional Deps   : ttf-opensans: default Open Sans font family
Required By     : None
Optional For    : purpose
Conflicts With  : None
Replaces        : None
Installed Size  : 61.42 MiB
Packager        : Jiachen YANG <cutted here>
Build Date      : Thu 01 Oct 2020 03:28:50 UTC
Install Date    : Thu 01 Oct 2020 17:03:21 UTC
Install Reason  : Explicitly installed
Install Script  : No
Validated By    : Signature

Used theme:
Tinted

Additional info

Workaround is the same as in mentioned ticked above. After switch to Russian, Telegram restarts and can show menu, switch back to English, Telegram restarts and context menu now can work. Telegram was added in autostart with the option in it's settings menu.

After PC restart situation is the same: lack is present again.
Fixing.

Logs

1. log before telegram restarts (no icon context menu).txt

2. log after telegram restarts (icon context menu works).txt

[ilya-fedin]

Well, I have no idea what else is needed to fix this and I don't know if KDE has any logging that could help, sorry :(

[ilya-fedin]

1. log before telegram restarts (no icon context menu).txt

[2020.10.02 12:40:28] Using Qt tray icon.

Oh, that explains a lot

[ghost]

Hi, Ilya!

Thank you for taking part!

Thanks for your try of comparison of log files attached in initial post.

Do we now have a chance to to try to fix it?

If not:

Does Telegram client has some debugging CLI/TUI params to add while it starting to make Telegram logs to be more verbose?

What you can suggest to try? What to try to find first? KDE logging?

[ghost]

if to start Telegram manually after desktop workspace has been loaded, then the Telegram executes with SNI icon in log and has context menu.

[ghost]

As far I know KDE based on Qt.
Just in general interest purpose, could you explain a possible cause why to use some SNI icon but not originally closer/sort of native Qt icon?

[ilya-fedin]

We have custom SNI implementation to have a good tray icon on all zoo of desktop environments with static binary, since we can't add platform theme plugins for each DE (including KDE) to static build. And the plain QSystemTrayIcon implementation (without platform theme plugins) really sucks.

[ghost]

Understood. Thank you very much!
So SNI is like abstraction level... not level, but module dependency which can run on every DE, and provide the same API to use one definition on all DE. Abstraction layer.

Like the same web browser app tries to provide the same JS API on all OS plalforms making the single JS apps running near the same in all OSes. Again, as abstraction layer/library/module.

[ilya-fedin]

So SNI is like abstraction level...

Vice versa. SNI is a tray icon protocol, which tdesktop implements on its own. QSystemTrayIcon is an abstraction level for Qt's and platform themes' tray icon implementations (usually SNI&XEmbed)

Fallback to QSystemTrayIcon is used to not to implement the XEmbed protocol (which is a X11 mess)

[ghost]

No, If I got the idea right! ;)
I mean SNI is abstraction level you made and use it on every DE of Telegram app and that's is the answer why not to use Qt:

1. really "not good" as you wrote.
2. to do not implement the same icon independently for each DE.
   I mean it is Telegram's layer which used on every DE as universal module of abstraction/high level coding.

Hm, but there are "SNI for Qt" (https://agateau.com/2011/statusnotifieritem-for-qt-applications/) and package name "sni-qt" (https://github.com/bilelmoussaoui/sni-qt) makes me feel that there are sni for unity, gnome, xfce, i3, etc... so SNI is not universal (not like abstraction layers of jQ, Angular, React, which for different browsers provides the same API and behavior).

Ok, my try to understand it on the fly crashed) But thank you for your explanation efforts.

[ilya-fedin]

I mean SNI is abstraction level you made and use it on every DE of Telegram ap

No, SNI is not an abstraction level, SNI stands for StatusNotifierItem, which is the name of the protocol that Telegram implements

"Using SNI tray icon" == using custom implementation of the StatusNotifierItem protocol
"Using Qt tray icon" == using QSystemTrayIcon

[ghost]

Protocol... so it should be sender and addressee... and may be there are built-in addressee in each DE: for KDE it is sni-qt, for gnome it is sort of gnome-qt, etc...
protocol...
like client and server?
publisher-observer pattern and events comes by protocol via some way?

Oh, StatusNotifierItem is not a receiver/base, but protocol itself...
Ok, can't interrupt you more on my mess in this, which purpose was just to know/to be aware just in case.

[ilya-fedin]

Protocol... so it should be sender and addressee... and may be there are built-in addressee in each DE: for KDE it is sni-qt, for gnome it is sort of gnome-qt, etc...

Yeah. Applications on one side and a panel on another (there are no sni-qt and etc, sni-qt was a Canonical's SNI implementation for Qt4, Qt5 has SNI without additional plugins like sni-qt, but it still sucks for tdesktop)

[ghost]

Thank you for your patience to try to explain it in details! I should not take another your time anymore but start to read articles if I want to know it and its environment/ecosystem more exactly.

Danke!

[ghost]

@ilya-fedin , may be I distracted you from additional actions of fixing process but this lack, but I got 2.4.2 version, restarted PC but still have no context menu (app behavior is the same as was in initial post).

Tried to re-create autostart link via v2.4.2's setting menu and restart PC again. Not helped.

$ cat /var/log/pacman.log | grep -i telegram | tail -n3

[2020-10-01T17:03:21+0000] [ALPM] upgraded telegram-desktop (2.3.2-2 -> 2.4.0-1)
[2020-10-03T14:36:30+0000] [ALPM] upgraded telegram-desktop (2.4.0-1 -> 2.4.1-1)
[2020-10-04T06:38:58+0000] [ALPM] upgraded telegram-desktop (2.4.1-1 -> 2.4.2-1)

$ pacman -Qi telegram-desktop

Name            : telegram-desktop
Version         : 2.4.2-1
Description     : Official Telegram Desktop client
Architecture    : x86_64
URL             : https://desktop.telegram.org/
Licenses        : GPL3
Groups          : None
Provides        : None
Depends On      : hunspell  ffmpeg  hicolor-icon-theme  lz4  minizip  openal  qt5-imageformats  xxhash  libdbusmenu-qt5  qt5-wayland  gtk3
Optional Deps   : ttf-opensans: default Open Sans font family
Required By     : None
Optional For    : purpose
Conflicts With  : None
Replaces        : None
Installed Size  : 61.39 MiB
Packager        : Jiachen YANG <hidden>
Build Date      : Sat 03 Oct 2020 13:53:23 UTC
Install Date    : Sun 04 Oct 2020 06:38:58 UTC
Install Reason  : Explicitly installed
Install Script  : No
Validated By    : Signature

If to change GUI language to another, than Telegram app restarts and context menu on the system icon tray showing (in the general log last line is SNI icon).

If to remove Telegram from autostart and to add it via KDE's Settings app, than executable link will be slightly different (having some different params and lines order are not the same) but restarting PC with such made link via direct KDE functionality still does not make Telegram to show context menu (logged Qt icon).

I tried to remove Telegram from autostart and after PC restarted I executed Telegram manually: context menu works, logged SNI icon.

May be somehow Telegram loads "too earlier"

May be you have a condition in the app which checks SNI protocol "receiver" in OS if it is absent, then using compatibility mode of Qt icon. But may be such "receiver" is just not yet loaded at that early desktop initialization stage when Telegram came. May be it is not good idea when Telegram is too quick in all aspects including startup.

May be other reason of that issue.

May be I have damaged OS

Recently I tried 5.9rc7 kernel which issue ( https://gitlab.freedesktop.org/drm/intel/-/issues/2526 ) could broke my OS functionality, but I just did still not know about it.

May be to collect additional logs? What exactly?

Tried to open via TUI in GUI session

Telegram window opens, console output is:

$ telegram-desktop 

(process:4764): Telegram-WARNING **: 07:16:41.192: Unfortunately, GTK integration conflicts with qgtk2 platformtheme and style. Therefore, QT_QPA_PLATFORMTHEME and QT_STYLE_OVERRIDE will be unset.
Telegram-Message: 07:16:41.195: This can be ignored by setting TDESKTOP_I_KNOW_ABOUT_GTK_INCOMPATIBILITY environment variable to any value, however, if qgtk2 theme or style is used, this will lead to a crash.
Telegram-Message: 07:16:41.195: GTK integration can be disabled by setting TDESKTOP_DISABLE_GTK_INTEGRATION to any value. Keep in mind that this will lead to clipboard issues and tdesktop will be unable to get settings from GTK (such as decoration layout, dark mode & more).

(process:4764): Telegram-WARNING **: 07:16:41.195: Application was built without embedded fonts, this may lead to font issues.
Telegram-Message: 07:16:41.449: You can disable tray icon counter with TDESKTOP_DISABLE_TRAY_COUNTER and make it look better if it is monochrome.
error: : cannot open
error: : cannot open
error: : cannot open

and after exit from Telegram app via context menu on system ray icon, that the only one line adds to the console output:

QCoreApplication::postEvent: Unexpected null receiver

Qt... Platform themes...

What KDE theme do I use?

For 2 years it is the same "Breeze Dark":

[ilya-fedin]

May be somehow Telegram loads "too earlier"

Yeah, it's definitely so. KDE loads applications too earlier and that lead to bugs like that one and a bug with detection of notification daemon. But there is nothing that Telegram can do about that.

May be you have a condition in the app which checks SNI protocol "receiver" in OS if it is absent, then using compatibility mode of Qt icon.

Yeah, that exactly so. But tdesktop also registers a service watcher and it should detect SNI service as soon as it registers in dbus. Maybe KDE starts applications even before dbus 🤔, then there is nothing that Telegram can do about that :(

[ilya-fedin]

pacman -Qi telegram-desktop

hmm, looks like you are using a packaged version, can you check with binary from desktop.telegram.org?

[ghost]

You are lightning-fast on answers!

Now I will try different KDE themes. Will post results.

Lets collect logs which could be useful. In what garbage will we search payload? :) What to collect?

[ilya-fedin]

You are lightning-fast on answers!

GitHub has AJAX, it updates the page as soon as there are a new answer and indicates that in the tab title. And there are a email notification that fast as well.

In what garbage will we search payload?

I have no idea where KDE logs its boot process :(

[ghost]

Tried all 4 avail. themes which are pre-defined/pre-installed in the official ManjaroLinux KDE distro.
No luck: every time no any response by right click and every time logs Qt icon.

I even used layout from theme.

Also on the PC with i5-10210U CPU, DDR4-2400 dual channel, nvme ssd I wait for PC background load while was login screen and after about 20 seconds enter my user session, saw default theme's splash screen and still see no telegram's context menu and logged Qt icon.

[ilya-fedin]

hmm, looks like you are using a packaged version, can you check with binary from desktop.telegram.org?

@alven-a

[ghost]

Spent a 30-40 minutes in tries to read and to do that. I was never install somewhat from a file, always used repos. Will continue tries soon.

[ilya-fedin]

Spent a 30-40 minutes in tries to read and to do that.

🙁 Just unpack the archive and double click the binary

[ghost]

it is only executes binary, as I think we need to install package to add it into autostart, cause manual execution has no lack with context menu on packaged version too.
the problem is when telegram autostarts (it is the same bahavior before and after your commit)

[ghost]

I uninstalled package version and now search the ways to install it from file.
or errors with metadata is absent or archive format is wrong (while tried zstd compression as new pacman like) or saw how to make make package suggests...

[ilya-fedin]

You don't need to "install it from file", it is like portable applications on WIndows. Just double click and it will start (if you don't have an already launched instance)

[ghost]

started from file.
telegram window opens.
context menu working, [2020.10.04 09:22:31] Using SNI tray icon. logged

how it can help?

[ilya-fedin]

how it can help?

You can enable autostart in telegram settings. If it is already enabled, just disable and re-enable it.

[ghost]

About starting from file: hm, BTW, log is about 1.5 times longer (4.1 KB against prev. 2.8 KB from package version):

log from execution as file.txt

Autostart:
already was enabled.
turned off,
wait while typing this text
re-enabled with Launch minimised option which I always use.

Will restart PC now.

[ghost]

Report to KDE - ok, but before I believe we should understand what is that mean- how it is too early/ how it is normal - so the root what before what - that question will be for that KDE issue reporter, but I can't say that right order or what event to wait to start an App.

May be that component which did not start yet gererates system event "I am started, c'mon guys i am ready!" like DOMContetLoaded as BOM JS event in webbrowser, That the point how (subscribe to that event) and when many JS apps starts.

[ilya-fedin]

how it is too early/ how it is normal

"normal" in my opinion is when all KDE services are started: tray area, notification daemon, etc.

[ghost]

Grabbed PC loading journalctl log with portable version with autostart and minimise to tray options enabled.

manjaro-log-helper.logs.zip

log.zip

Note:
-) Between logon screen appears I waited 20 seconds before enter into user session;
-) During desktop loading the taskbar appears on the screen with 11:04:44 time on it and was already with Telegram system tray icon.

May be that log could help.

Anyway thank you so much for trying to solve it.

[ilya-fedin]

manjaro-log-helper.logs.zip

Telegram start:
Oct 04 11:04:41.703526 plasma_session[866]: org.kde.plasma.session: Starting autostart service "/home/_user_/.config/autostart/appimagekit_cb64cc1587d501854854642ccd911a56-Telegram_Desktop.desktop" ("/home/_user_/Desktop/Telegram/Telegra_user_", "-autostart")

System tray registration (happens after Telegram start):
Oct 04 11:04:43.834475 kded5[898]: Registering "org.kde.StatusNotifierHost-961" as system tray

And even some KDE service reports lack of the tray: Oct 04 11:04:40.462713 kded5[898]: kf.notifications: env says KDE is running but SNI unavailable -- check KDE_FULL_SESSION and XDG_CURRENT_DESKTOP

Something is really wrong with the system or KDE 🙈

[ghost]

Ok, got it. Thanks!

after a few complete hangs while was running 5.9rc7 kernel (mentioned in this topic earlier) my "OS sample" should not be a litmus test.

[ghost]

after such conversation with developer that label linux looks like "it is not bug, it is linux feature" Sadly for now :|

[ilya-fedin]

label linux looks like "it is not bug, it is linux feature"

What are you talking about?

[ghost]

What are you talking about?

#8708 (comment)
If I understood correctly, than this label marks this ticket as persistent linux issue, so actual lack of environment became persistent, so looks like "not a bug, it is feature"

[ghost]

I did not catch this: portable version can show menu, the same version number prepared by another man and installed as package can't show context menu after autostart.
Any thoughts why? Or may be it is question to packager?

[ilya-fedin]

If I understood correctly, than this label marks this ticket as persistent linux issue

It marks any linux issue, I just called Aokromes to mark it since I feel that there wouldn't be fix for much time, so that it would be handy to have the issue in linux to not to forget about it

Any thoughts why?

I already explained that in this thread

[ghost]

Saw it in #8708 (comment)

it only tries to open a menu that inside of it: ...

Still can't understand why only Telegram can't show menu. Telegram needs only custom click handler or custom looking menu? Is it not good idea to show context menu as other icons do?
manjaro settings manager, KDE Media Player, Octopi, Pamac, Notifications, qBittorrent, Clipboard, Audio Volume, Device Notifier, Keyboard, Keyboard layouts, Network - all of them shows context menu. They behave abnormal or use "bad-looking" Qt icons? They are also installed as packages.

When you're using static binary, Qt's QSystemTrayIcon implementation calls Telegram handler on right click. When you're using packaged version, kde platformtheme plugin is used and it doesn't support calling custom handlers on right click

Also fact that if to start installed Telegram package manually not via autostart, then it's context menu works, adds some mess in that explanation above, there effect of showing and not showing context menu depends on package origin.

[ilya-fedin]

Still can't understand why only Telegram can't show menu.

Because only our implementation is affected by that race condition on autostart for some reason

[ghost]

Wrote description as understand it: https://bugs.kde.org/show_bug.cgi?id=427326
Can't see System tray component itself there, so general was selected as target section.

[kmaterka]

Hi, it might be a race condition in KDE/Plasma startup:
https://bugs.kde.org/show_bug.cgi?id=425315
It affected few users already, but it is rare and very hard to reproduce. It is even hard to tell if this is a distribution issue or something with KDE startup process.

The additional question is, why there is no context menu when legacy XEmbed protocol is used?

[ilya-fedin]

The additional question is, why there is no context menu when legacy XEmbed protocol is used?

I already explained that in this thread

[ilya-fedin]

@alven-a just wondering, is this really fixed after the last attempt to fix?

[ghost]

Hi, Ilya! Thank you for your msg! I get some troubles with PC's hardware. No! Not cause Telegram app :) Some UEFI settings triggered constant black screen and it is no video signal from NUC10. I exchanged it in shop to another model. It is raw currently, no hardware, software installed yet. And currently I am on another old desktop machine (i3-550) on the freash installation of Manjaro Linux from scratch. I have something to say about 2.4.3-1 packaged version. Will post details in 1-2 days.

[ghost]

On completely different PC hardware I installed fresh copy of Manjaro Linux OS (KDE official edition) made in Oct-2020.

I got all latest updates on freshest update branch of the OS.

Operating System: Manjaro Linux
KDE Plasma Version: 5.19.5
KDE Frameworks Version: 5.75.0
Qt Version: 5.15.1
Kernel Version: 5.8.14-1-MANJARO
OS Type: 64-bit
Processors: 2 × Intel® Core™ i3 CPU 550 @ 3.20GHz
Memory: 7.5 GiB of RAM
Graphics Processor: Mesa DRI Intel® HD Graphics

$ uname -r
5.8.14-1-MANJARO

Installed the app:

$ pacman -Qi telegram-desktop
Name            : telegram-desktop
Version         : 2.4.3-1
Description     : Official Telegram Desktop client
Architecture    : x86_64
URL             : https://desktop.telegram.org/
Licenses        : GPL3
Groups          : None
Provides        : None
Depends On      : hunspell  ffmpeg  hicolor-icon-theme  lz4  minizip  openal  qt5-imageformats  xxhash  libdbusmenu-qt5  qt5-wayland  gtk3
Optional Deps   : ttf-opensans: default Open Sans font family
Required By     : None
Optional For    : purpose
Conflicts With  : None
Replaces        : None
Installed Size  : 61.39 MiB
Packager        : Jiachen YANG <hidden>
Build Date      : Wed 07 Oct 2020 15:54:40 UTC
Install Date    : Fri 09 Oct 2020 22:11:00 UTC
Install Reason  : Explicitly installed
Install Script  : No
Validated By    : Signature

Setup it to autostart via the app settings menu.

Rebooted PC several times: results are the same:

$ pidof telegram-desktop
$

$ telegram-desktop

(process:2269): Telegram-WARNING **: 23:50:13.143: Unfortunately, GTK integration conflicts with qgtk2 platformtheme and style. Therefore, QT_QPA_PLATFORMTHEME and QT_STYLE_OVERRIDE will be unset.
Telegram-Message: 23:50:13.145: This can be ignored by setting TDESKTOP_I_KNOW_ABOUT_GTK_INCOMPATIBILITY environment variable to any value, however, if qgtk2 theme or style is used, this will lead to a crash.
Telegram-Message: 23:50:13.145: GTK integration can be disabled by setting TDESKTOP_DISABLE_GTK_INTEGRATION to any value. Keep in mind that this will lead to clipboard issues and tdesktop will be unable to get settings from GTK (such as decoration layout, dark mode & more).

(process:2269): Telegram-WARNING **: 23:50:13.145: Application was built without embedded fonts, this may lead to font issues.
Telegram-Message: 23:50:13.357: You can disable tray icon counter with TDESKTOP_DISABLE_TRAY_COUNTER and make it look better if it is monochrome.
error: : cannot open
error: : cannot open
error: : cannot open

and now:

$ pidof telegram-desktop 
2269

It is on the current boot.

Before previous boot the app was added in autostart via Telegram settings menu.
Logs of that boot (storing for 14 days only): https://dropmefiles.com/9uwv9

One more 'effect' discovered:

$ telegram-desktop 

(process:2536): Telegram-WARNING **: 23:56:38.776: Unfortunately, GTK integration conflicts with qgtk2 platformtheme and style. Therefore, QT_QPA_PLATFORMTHEME and QT_STYLE_OVERRIDE will be unset.
Telegram-Message: 23:56:38.778: This can be ignored by setting TDESKTOP_I_KNOW_ABOUT_GTK_INCOMPATIBILITY environment variable to any value, however, if qgtk2 theme or style is used, this will lead to a crash.
Telegram-Message: 23:56:38.778: GTK integration can be disabled by setting TDESKTOP_DISABLE_GTK_INTEGRATION to any value. Keep in mind that this will lead to clipboard issues and tdesktop will be unable to get settings from GTK (such as decoration layout, dark mode & more).

(process:2536): Telegram-WARNING **: 23:56:38.778: Application was built without embedded fonts, this may lead to font issues.
Telegram-Message: 23:56:38.982: You can disable tray icon counter with TDESKTOP_DISABLE_TRAY_COUNTER and make it look better if it is monochrome.
error: : cannot open
error: : cannot open
error: : cannot open
QCoreApplication::postEvent: Unexpected null receiver
$

all lines appears at the app's startup except last one - it logs if to quit the app via item in sys. tray context menu. May be it is usual line, may be could be a key for investigation.

[ilya-fedin]

Rebooted PC several times: results are the same

What do you mean? As I can see in the log you provided, tdesktop correctly switches to SNI now

[ghost]

What do you mean? As I can see in the log you provided, tdesktop correctly switches to SNI now

May be correctly switches and then probably immediately gone from memory.

$ pidof telegram-desktop
$

Rebooted PC several times: results are the same

tried several times to reboot PC, but the same

$ pidof telegram-desktop
$

[ilya-fedin]

May be correctly switches and then probably immediately gone from memory.

I guess it crashes, you should reproduce that with official binary since arch and manjaro packages don't have a crash reporter nor debug symbols in repositories.

[ghost]

with packaged version (Manjaro OS):
-) removed from autostart
-) quit the app
-) uninstalled

with the site version:
-) downloaded
-) executed
-) added to autostart via the app settings menu

Tried 2 reboots.
The app loads and context menu lines looks compact (not Qt-like) in 2 times of 2 tries. Visually looks like working perfect.

Gathered logs: https://dropmefiles.com/lmxll
(storing for 14 days)

Thank you so much for your efforts and hitting target result! The site 2.4.3 "portable" version works well.
"- Enemy down!..

• Roger that!"

Could I ask you more? Again)
May be you have something to suggest to packager to make a packaged version to work the same as the site version? What to pay attention on or to try?

[ilya-fedin]

May be you have something to suggest to packager to make a packaged version to work the same as the site version?

I have no idea, debugging is needed, but manjaro doesn't provide debug symbols and getting them is a complicated process: https://wiki.archlinux.org/index.php/Debug_-_Getting_Traces

[ghost]

Somehow the

$ pacman -Qi telegram-desktop 
Name            : telegram-desktop
Version         : 2.4.4-1
Description     : Official Telegram Desktop client
Architecture    : x86_64
URL             : https://desktop.telegram.org/
Licenses        : GPL3
Groups          : None
Provides        : None
Depends On      : hunspell  ffmpeg  hicolor-icon-theme  lz4  minizip  openal  qt5-imageformats  xxhash  libdbusmenu-qt5  qt5-wayland  gtk3
Optional Deps   : ttf-opensans: default Open Sans font family [installed]
Required By     : None
Optional For    : purpose
Conflicts With  : None
Replaces        : None
Installed Size  : 61.44 MiB
Packager        : Jiachen YANG <hidden data>
Build Date      : Sat 24 Oct 2020 11:27:53 UTC
Install Date    : Sun 25 Oct 2020 00:08:26 UTC
Install Reason  : Explicitly installed
Install Script  : No
Validated By    : Signature

packaged version able to autostart w/o crashing at the start. Context menu on the system tray icon works well also.

Tested 4 re-boots on the

Operating System: Manjaro Linux
KDE Plasma Version: 5.20.1
KDE Frameworks Version: 5.75.0
Qt Version: 5.15.1
Kernel Version: 5.8.16-2-MANJARO
OS Type: 64-bit

with 4 times of success autostart.

[github-actions]

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.