Bug 466248 - Discover's Notifier Tray Icon does not show
Summary: Discover's Notifier Tray Icon does not show
Status: RESOLVED DUPLICATE of bug 425315
Alias: None
Product: Discover
Classification: Applications
Component: Notifier (show other bugs)
Version: 5.27.1
Platform: Neon Linux
: NOR normal
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-02-22 16:37 UTC by John
Modified: 2023-09-25 20:29 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments
Tray Elements config (141.66 KB, image/png)
2023-02-22 16:37 UTC, John
Details
Tray (35.73 KB, image/png)
2023-02-22 16:38 UTC, John
Details

Note You need to log in before you can comment on or make changes to this bug.
Description John 2023-02-22 16:37:59 UTC
Created attachment 156606 [details]
Tray Elements config

SUMMARY
Discover's Notifier Tray Icon - sometimes - does not show (even when it's configured to be always visible on taskbar)

I actually don't have steps to reproduce it, because it's apparently random.

With the default configuration it sometimes shows up, sometimes it doesn't.
I original though it depended on whether there was updates or not (even with it completely invisible from the tray popup), but then - when it showed up - i configured it to be always visible and still sometimes it shows and then sometimes it doesn't.


EXPECTED RESULT:
Should be visible


SOFTWARE/OS VERSIONS
Operating System: KDE neon 5.27
KDE Plasma Version: 5.27.1
KDE Frameworks Version: 5.103.0
Qt Version: 5.15.8
Kernel Version: 5.19.0-32-generic (64-bit)
Graphics Platform: Wayland


ADDITIONAL INFORMATION
This is not a new problem. It happened on 5.26, on 5.102 and on x.org (if it helps...)
Comment 1 John 2023-02-22 16:38:48 UTC
Created attachment 156607 [details]
Tray

Sometimes it shows here as well
Comment 2 Nate Graham 2023-03-20 08:05:15 UTC
On a login when it's failed to appear in either the active area of the tray (on the panel) or the popup, can you paste the output of running `systemctl status --user app-org.kde.discover.notifier@autostart.service` in a terminal window?
Comment 3 John 2023-03-20 12:45:09 UTC
(In reply to Nate Graham from comment #2)
> On a login when it's failed to appear in either the active area of the tray
> (on the panel) or the popup, can you paste the output of running `systemctl
> status --user app-org.kde.discover.notifier@autostart.service` in a terminal
> window?

Hi Nate

This gets reeeeealy long... So, i'll post the last two chunks (because they look 'sort of' the same)...

But... if you want the whole thing... i can post it :)

~
lines 1-15/15 (END)...skipping...
● app-org.kde.discover.notifier@autostart.service - Discover
● app-org.kde.discover.notifier@autostart.service - Discover
● app-org.kde.discover.notifier@autostart.service - Discover
● app-org.kde.discover.notifier@autostart.service - Discover
     Loaded: loaded (/etc/xdg/autostart/org.kde.discover.notifier.desktop; generated)
● app-org.kde.discover.notifier@autostart.service - Discover
● app-org.kde.discover.notifier@autostart.service - Discover
● app-org.kde.discover.notifier@autostart.service - Discover
● app-org.kde.discover.notifier@autostart.service - Discover
● app-org.kde.discover.notifier@autostart.service - Discover
● app-org.kde.discover.notifier@autostart.service - Discover
     Loaded: loaded (/etc/xdg/autostart/org.kde.discover.notifier.desktop; generated)
     Active: active (running) since Mon 2023-03-20 12:25:48 WET; 3min 26s ago
       Docs: man:systemd-xdg-autostart-generator(8)
    Process: 1365 ExecCondition=/lib/systemd/systemd-xdg-autostart-condition KDE  (code=exited, status=0/SUCCESS)
   Main PID: 1382 (DiscoverNotifie)
      Tasks: 10 (limit: 9384)
     Memory: 42.2M
        CPU: 1.108s
     CGroup: /user.slice/user-1000.slice/user@1000.service/app.slice/app-org.kde.discover.notifier@autostart.service
             └─1382 /usr/lib/x86_64-linux-gnu/libexec/DiscoverNotifier

mar 20 12:25:48 escritorio systemd[1135]: Starting Discover...
mar 20 12:25:48 escritorio systemd[1135]: Started Discover.
mar 20 12:26:14 escritorio DiscoverNotifier[1382]: kf.notifications: env says KDE is running but SNI unavailable -- check KDE_FULL_SESSION a>
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
lines 1-15/15 (END)...skipping...
● app-org.kde.discover.notifier@autostart.service - Discover
     Loaded: loaded (/etc/xdg/autostart/org.kde.discover.notifier.desktop; generated)
     Active: active (running) since Mon 2023-03-20 12:25:48 WET; 3min 26s ago
       Docs: man:systemd-xdg-autostart-generator(8)
    Process: 1365 ExecCondition=/lib/systemd/systemd-xdg-autostart-condition KDE  (code=exited, status=0/SUCCESS)
   Main PID: 1382 (DiscoverNotifie)
      Tasks: 10 (limit: 9384)
     Memory: 42.2M
        CPU: 1.108s
     CGroup: /user.slice/user-1000.slice/user@1000.service/app.slice/app-org.kde.discover.notifier@autostart.service
             └─1382 /usr/lib/x86_64-linux-gnu/libexec/DiscoverNotifier

mar 20 12:25:48 escritorio systemd[1135]: Starting Discover...
mar 20 12:25:48 escritorio systemd[1135]: Started Discover.
mar 20 12:26:14 escritorio DiscoverNotifier[1382]: kf.notifications: env says KDE is running but SNI unavailable -- check KDE_FULL_SESSION and XDG_CURRENT_DESKTOP
Comment 4 Nate Graham 2023-03-27 18:23:30 UTC
> kf.notifications: env says KDE is running but SNI unavailable -- check KDE_FULL_SESSION and XDG_CURRENT_DESKTOP
This looks very relevant indeed.

Perhaps a race condition on boot. I bet this will be fixed by https://invent.kde.org/plasma/plasma-workspace/-/merge_requests/1343.
Comment 5 Kevin Kofler 2023-03-27 19:00:14 UTC
I do not see how that merge request can possibly fix this issue, because Discover uses native SNI, not xembedsniproxy.
Comment 6 John 2023-03-28 09:11:37 UTC
Well, whatever the reason, in the last few days I've been starting Discover manually every day to check for updates, because it simply hasn't been starting. It shows up on the notifications, but not the icon on the taskbar.

(maybe it went on a holiday break or something... lucky one... i know i surely needed one!)
Comment 7 Nate Graham 2023-03-28 16:58:47 UTC
(In reply to Kevin Kofler from comment #5)
> I do not see how that merge request can possibly fix this issue, because
> Discover uses native SNI, not xembedsniproxy.
Oops, my mistake. Perhaps a similar issue though.
Comment 8 John 2023-05-08 14:35:19 UTC
Might be relevant that:

- Last week, the icon "glimpsed" once at startup and vanished (discover did have updates!)
- Beside that it's now about two weeks i don't see it ever showing up!
- Notifications of new updates do show up, however...

(hope this helps)
Comment 9 Nate Graham 2023-09-25 20:29:47 UTC

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