| Summary: | Race condition between Unity counter service and autostarted apps, causing them to sometimes lose their Task Manager notification badges until they're restarted | ||
|---|---|---|---|
| Product: | [Plasma] plasmashell | Reporter: | Salvatore <sannythebest95> |
| Component: | Startup process | Assignee: | Salvatore <sannythebest95> |
| Status: | CONFIRMED --- | ||
| Severity: | normal | CC: | fedin-ilja2010, kde, kde, nate, postix, sannythebest95 |
| Priority: | NOR | ||
| Version: | master | ||
| Target Milestone: | 1.0 | ||
| Platform: | Other | ||
| OS: | Linux | ||
| See Also: |
https://bugs.kde.org/show_bug.cgi?id=323151 https://bugs.kde.org/show_bug.cgi?id=473860 |
||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
| Attachments: |
On the left, Telegram started automatically when the system started, on the right, the app after closing and restarting it
Log without badge log with badge |
||
IIRC this is a Qt issue of some sort. Ilya, do you remember which one? That Qt issue is about system tray icon, the icon on screenshot is the taskbar one, i.e. it seems to be a different issue, with the com.canonical.Unity.LauncherEntry API An issue with the API itself, not its implementation in Plasma or Telegram? Somewhere in its implementation I believe, whether in Plasma or Telegram it's a question though. Telegram does a simple NameHasOwner check (and then logs the result to its log.txt) on launch, maybe there's a similar race condition. If that's the case, the fix on Telegram side would be as easy as removing the check, it probably won't hurt if the signal is always emitted. But that would likely also mean Plasma doesn't accept requests to the API in first seconds applications are auto-started, so the issue will be harder to reproduce, but it won't disappear (e.g. in case Telegram or some other application sets the counter on start and there's no new messages for a long time, so no new requests to the API are made). Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! Salvatore, I believe you need to provide Telegram's log.txt to validate the assumption Created attachment 154801 [details]
Log without badge
Created attachment 154802 [details]
log with badge
Indeed, I see "Not using Unity launcher counter." line in the log without counter (In reply to Ilya Fedin from comment #10) > Indeed, I see "Not using Unity launcher counter." line in the log without > counter Excuse my ignorance, is this a package I didn't install? This means Plasma launches Telegram earlier than it starts the Unity counter service |
Created attachment 154385 [details] On the left, Telegram started automatically when the system started, on the right, the app after closing and restarting it SUMMARY When Telegram is launched at system startup, the badge is not shown. If you close and reopen the app, the badge returns STEPS TO REPRODUCE 1. Telegram autostart - unread messages but no badge 2. close telegram and restart it, the badge return Operating System: Arch Linux KDE Plasma Version: 5.26.4 KDE Frameworks Version: 5.100.0 Qt Version: 5.15.7 Kde Gear: 22.08.3