[plasmashell] [Bug 420635] Apps that autostart do not appear in the system tray, including DiscoverNotifier

2022-10-20 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=420635

Nate Graham  changed:

   What|Removed |Added

   See Also|https://bugs.kde.org/show_b |
   |ug.cgi?id=425315|

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 420635] Apps that autostart do not appear in the system tray, including DiscoverNotifier

2021-07-29 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=420635

Nate Graham  changed:

   What|Removed |Added

 Resolution|--- |DUPLICATE
 Status|REOPENED|RESOLVED

--- Comment #40 from Nate Graham  ---


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

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 420635] Apps that autostart do not appear in the system tray, including DiscoverNotifier

2021-03-06 Thread Aleksey Kontsevich
https://bugs.kde.org/show_bug.cgi?id=420635

Aleksey Kontsevich  changed:

   What|Removed |Added

 Resolution|WORKSFORME  |---
 Status|RESOLVED|REOPENED
 Ever confirmed|0   |1

--- Comment #39 from Aleksey Kontsevich  ---
This shit happens again, disk is new. Happens for KeePassXC and KShutdown. KDE
is newest.

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 420635] Apps that autostart do not appear in the system tray, including DiscoverNotifier

2020-08-21 Thread Andrey
https://bugs.kde.org/show_bug.cgi?id=420635

--- Comment #38 from Andrey  ---
Hi, please note the possible duplicate bug 425315 is not related with faulty
HDD.
So maybe we should reopen this.

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 420635] Apps that autostart do not appear in the system tray, including DiscoverNotifier

2020-08-21 Thread Andrey
https://bugs.kde.org/show_bug.cgi?id=420635

Andrey  changed:

   What|Removed |Added

   See Also||https://bugs.kde.org/show_b
   ||ug.cgi?id=425315

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 420635] Apps that autostart do not appear in the system tray, including DiscoverNotifier

2020-08-21 Thread Andrey
https://bugs.kde.org/show_bug.cgi?id=420635

Andrey  changed:

   What|Removed |Added

 CC||butir...@gmail.com

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 420635] Apps that autostart do not appear in the system tray, including DiscoverNotifier

2020-05-25 Thread Aleksey Kontsevich
https://bugs.kde.org/show_bug.cgi?id=420635

--- Comment #37 from Aleksey Kontsevich  ---
Yeah, thanks much!!! :)))

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 420635] Apps that autostart do not appear in the system tray, including DiscoverNotifier

2020-05-25 Thread Brian Wright
https://bugs.kde.org/show_bug.cgi?id=420635

--- Comment #36 from Brian Wright  ---
I'm 100% convinced that the hard drive was the issue.  I noticed all kinds of
strange behavior (KDE setting changes not saving), but when I started getting
SmartControl warnings about the hard drive, that was key.

Without the SmartControl warnings, I wouldn't have suspected the hard drive. 
It seems that this is the greatest common denominator for this issue since
Aleksey's experience was 100% identical to mine.

Many thanks for bearing with us, Konrad! :-)

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 420635] Apps that autostart do not appear in the system tray, including DiscoverNotifier

2020-05-24 Thread Konrad Materka
https://bugs.kde.org/show_bug.cgi?id=420635

--- Comment #35 from Konrad Materka  ---
(In reply to Aleksey Kontsevich from comment #34)
> Very interesting. So I had same thing solved by replacing HDD? Never were
> the cause for ancient software, strange.
It is possible that there is an underlying problem, that shows symptons only
when something is wrong with HDD or file system. Or maybe it is totally
unrelated and was "fixed" simply by reinstalling the system? I don't know, but
when no-one now can reproduce it, I closed this bug report.
Feel free to reopen in of you have more information that can pinpoint the root
cause or it happens again for you.

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 420635] Apps that autostart do not appear in the system tray, including DiscoverNotifier

2020-05-23 Thread Aleksey Kontsevich
https://bugs.kde.org/show_bug.cgi?id=420635

--- Comment #34 from Aleksey Kontsevich  ---
(In reply to Konrad Materka from comment #33)
> (In reply to Brian Wright from comment #32)
> > I think this issue may have been caused by a faulty hard drive.
> Faulty hard drive is plausible explanation, thank you for checking.

Very interesting. So I had same thing solved by replacing HDD? Never were the
cause for ancient software, strange.

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 420635] Apps that autostart do not appear in the system tray, including DiscoverNotifier

2020-05-23 Thread Konrad Materka
https://bugs.kde.org/show_bug.cgi?id=420635

Konrad Materka  changed:

   What|Removed |Added

 Status|REPORTED|RESOLVED
 Resolution|--- |WORKSFORME

--- Comment #33 from Konrad Materka  ---
(In reply to Brian Wright from comment #32)
> I think this issue may have been caused by a faulty hard drive.
Faulty hard drive is plausible explanation, thank you for checking.
I'm closing this report then.

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 420635] Apps that autostart do not appear in the system tray, including DiscoverNotifier

2020-05-20 Thread Brian Wright
https://bugs.kde.org/show_bug.cgi?id=420635

--- Comment #32 from Brian Wright  ---
My apologies for the delay in getting back to you. :)

I think this issue may have been caused by a faulty hard drive.  The KDE
SmartControl module was issuing warnings about sectors on the hard drive
becoming unreadable.

I ordered a replacement drive, then I used CloneZilla to clone the disk. 
Afterwards, everything was working as it should, even after reinstalling
NoMachine with the default settings:

Output of journalctl -b 0 | grep StatusNotifierHost:

May 20 11:47:40 bdw-desktop kded5[4950]: Registering
"org.kde.StatusNotifierHost-7801" as system tray


Output of listIcons.sh:

org.kde.StatusNotifierWatcher
pid,start,command:  4950 11:47:13 kded5

ITEMS:

ITEM:  :1.39/org/ayatana/NotificationItem/pasystray
PID STAT: 10242 11:47:17 /usr/bin/pasystray
ID:pasystray
TITLE: pasystray

ITEM:  :1.27/StatusNotifierItem
PID STAT:  8267 11:47:16 /usr/lib/x86_64-linux-gnu/libexec/DiscoverNotifier
ID:Discover Notifier_org.kde.DiscoverNotifier
TITLE: Updates

ITEM:  :1.40/StatusNotifierItem
PID STAT:  9544 11:47:16 /usr/bin/korgac
ID:KOrganizer Reminder Daemon
TITLE: KOrganizer Reminder Daemon

ITEM:  :1.57/StatusNotifierItem
PID STAT: 10310 11:47:17 /usr/bin/kmix --keepvisibility
ID:KMix
TITLE: Volume Control

ITEM:  :1.59/StatusNotifierItem
PID STAT:  8779 11:47:16 /usr/bin/keepassxc
ID:KeePassXC
TITLE: KeePassXC

ITEM:  :1.63/StatusNotifierItem
PID STAT:  7797 11:47:15 /usr/bin/xembedsniproxy
ID:Private Internet Access
TITLE: Private Internet Access

ITEM:  :1.64/StatusNotifierItem
PID STAT:  7797 11:47:15 /usr/bin/xembedsniproxy
ID:hp-systray
TITLE: hp-systray

ITEM:  :1.60/org/ayatana/NotificationItem/Skype1
PID STAT:  9376 11:47:16 /usr/share/skypeforlinux/skypeforlinux
--executed-from=/home/bdw --pid=
8999
ID:Skype1
TITLE: skypeforlinux

ITEM:  :1.53/org/ayatana/NotificationItem/Slack1
PID STAT: 10219 11:47:17 /usr/lib/slack/slack
ID:Slack1
TITLE: slack

ITEM:  :1.98/StatusNotifierItem
PID STAT: 20889 11:47:46 /usr/bin/kalarm --tray
ID:KAlarm
TITLE: KAlarm

ITEM:  org.kde.StatusNotifierItem-20918-1/StatusNotifierItem
PID STAT: 20918 11:47:46 /usr/NX/bin/nxclient.bin --monitor --pid 4910
ID:NoMachineMonitor
TITLE: NoMachineMonitor

ITEM:  :1.118/StatusNotifierItem
PID STAT:  7801 11:47:15 /usr/bin/plasmashell
ID:Plasma_microphone
TITLE: Microphone

ITEM:  org.kde.StatusNotifierItem-30735-1/StatusNotifierItem
PID STAT: 30735 12:02:48 /opt/google/chrome/chrome
ID:Error: org.freedesktop.DBus.Error.UnknownMethod Method "Id" with
signature "" on inte
rface "org.kde.StatusNotifierItem" doesn't exist
TITLE: Error: org.freedesktop.DBus.Error.UnknownMethod Method "Title" with
signature "" on i
nterface "org.kde.StatusNotifierItem" doesn't exist


The above error is from the Google Hangouts Chrome extension so we can
disregard that.


I'm now convinced that it was a problem with data corruption on the hard drive
that was causing this behavior.  I had issues with KDE not saving my settings
and other oddities.  The fact that I had the same issues with test accounts
confirmed it, and there were zero problems with KDE Neon running on VirtualBox

Clonezilla ran fsck on the original hard drive before cloning and it corrected
some errors.  All the data on the new drive is from the original and there are
no problems whatsoever. :)

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 420635] Apps that autostart do not appear in the system tray, including DiscoverNotifier

2020-05-14 Thread Konrad Materka
https://bugs.kde.org/show_bug.cgi?id=420635

--- Comment #31 from Konrad Materka  ---
(In reply to Brian Wright from comment #30)
> I use NoMachine to access a remote Windows box at my workplace.  NoMachine
> appears to wreak havoc with KDE Plasma when you log in via SDDM.
> 
> To be fair to NoMachine, I may have configured it incorrectly.  The
> NoMachine server was always running in the background, and only by removing
> it and rebooting the machine, everything was AOK.
> 
> I suggest installing NoMachine on your system (local or virtual) and set it
> to run the server at startup, then reboot.  You should see the same thing I
> experienced.

I installed Neon User in VirtualBox, then NoMachine and can't reproduce this
issue. NoMachine starts with every login, it's tray icon is visible. Any
specific settings?

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 420635] Apps that autostart do not appear in the system tray, including DiscoverNotifier

2020-05-11 Thread Brian Wright
https://bugs.kde.org/show_bug.cgi?id=420635

--- Comment #30 from Brian Wright  ---
AHA :-)

It appears that I found the culprit - NoMachine!

Based on your feedback from my last test results, I started to suspect if
NoMachine was causing it.  So, I did an apt-get purge --autoremove NoMachine,
rebooted, and BINGO!!! Everything worked as it should - the autostarted icons
appeared, and the app windows opened. The Kmix and DiscoverNotify icons were
also present.

Here are the latest test results.

Output from journalctl -b 0 | grep StatusNotifierHost:

May 11 20:54:03 bdw-desktop kded5[26589]: Registering
"org.kde.StatusNotifierHost-27787" as system tray

Output from listIcons.sh:

org.kde.StatusNotifierWatcher
pid,start,command:  26589 20:52:23 kded5

ITEMS:

ITEM:  :1.38/org/ayatana/NotificationItem/pasystray
PID STAT:  350 20:52:32 /usr/bin/pasystray
ID:pasystray
TITLE: pasystray

ITEM:  :1.40/StatusNotifierItem
PID STAT: 32563 20:52:32 /usr/bin/korgac
ID:KOrganizer Reminder Daemon
TITLE: KOrganizer Reminder Daemon

ITEM:  :1.30/StatusNotifierItem
PID STAT: 30242 20:52:31 /usr/lib/x86_64-linux-gnu/libexec/DiscoverNotifier
ID:Discover Notifier_org.kde.DiscoverNotifier
TITLE: Updates

ITEM:  :1.53/StatusNotifierItem
PID STAT:  1728 20:52:35 /usr/bin/kmix --keepvisibility
ID:KMix
TITLE: Volume Control

ITEM:  :1.60/StatusNotifierItem
PID STAT: 31040 20:52:31 /usr/bin/keepassxc
ID:KeePassXC
TITLE: KeePassXC

ITEM:  :1.68/StatusNotifierItem
PID STAT: 27858 20:52:30 /usr/bin/xembedsniproxy
ID:hp-systray
TITLE: hp-systray

ITEM:  :1.55/org/ayatana/NotificationItem/Skype1
PID STAT:  1764 20:52:35 /usr/share/skypeforlinux/skypeforlinux
--executed-from=/home/bdw --pid=1714
ID:Skype1
TITLE: skypeforlinux

ITEM:  :1.63/org/ayatana/NotificationItem/Slack1
PID STAT:  1695 20:52:33 /usr/lib/slack/slack
ID:Slack1
TITLE: slack

ITEM:  :1.74/StatusNotifierItem
PID STAT:  9345 20:53:05 /usr/bin/kalarm --tray
ID:KAlarm
TITLE: KAlarm

ITEM:  :1.107/org/ayatana/NotificationItem/dropbox_client_1903
PID STAT:  1903 20:52:50
/home/bdw/.dropbox-dist/dropbox-lnx.x86_64-96.4.172/dropbox
ID:dropbox-client-1903
TITLE: dropbox


I use NoMachine to access a remote Windows box at my workplace.  NoMachine
appears to wreak havoc with KDE Plasma when you log in via SDDM.

To be fair to NoMachine, I may have configured it incorrectly.  The NoMachine
server was always running in the background, and only by removing it and
rebooting the machine, everything was AOK.

I suggest installing NoMachine on your system (local or virtual) and set it to
run the server at startup, then reboot.  You should see the same thing I
experienced.

It seems that the NoMachine server and client are intertwined, so more testing
will have to be done with the NoMachine server not running on startup.

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 420635] Apps that autostart do not appear in the system tray, including DiscoverNotifier

2020-05-11 Thread Konrad Materka
https://bugs.kde.org/show_bug.cgi?id=420635

--- Comment #29 from Konrad Materka  ---
(In reply to Brian Wright from comment #28)
> Yes, I have.  Everything works as it should.  I backed up my personal home
> directory, nuked it, and then started fresh.  Everything worked OK, until I
> restored some of my app data.  With the test account, I will be keeping it
> pristine except for the apps that I need to autostart.
That should be enough to pinpoint the root cause. If clean account is working
fine and with restored setting it is not, then most probably something is wrong
with these settings.

> org.kde.StatusNotifierWatcher
> pid,start,command:  29782 13:36:26 kded5
> 
> ITEMS:
> 
> ITEM:  :1.40/org/ayatana/NotificationItem/pasystray
> PID STAT: 31350 13:36:27 /usr/bin/pasystray
> ID:pasystray
> TITLE: pasystray
> 
> ITEM:  :1.91/StatusNotifierItem
> PID STAT: 31134 13:36:27 /usr/bin/xembedsniproxy
> ID:pasystray
> TITLE: pasystray
> 
> ITEM:  :1.102/StatusNotifierItem
> PID STAT:  7545 13:36:58 /usr/bin/kalarm --tray
> ID:KAlarm
> TITLE: KAlarm
> 
> PasSystray duplicated.
One is a legacy icon (handled by xembedsniproxy). Probably PasSystray detects
that there is no SNI and configures legacy tray icon. Then detects that SNI is
configured and uses SNI, but legacy icon still there. Killing xembedsniproxy
should hide one of the duplicated icons.

> > * Please find in logs the time when StatusNotifierHost was registered. On my
> > system, I've run:
> > journalctl -b 0 | grep StatusNotifierHost
> 
> May 10 13:35:32 bdw-desktop kded5[4104]: Registering
> "org.kde.StatusNotifierHost-9430" as system tray
> May 10 13:37:18 bdw-desktop kded5[29782]: Registering
> "org.kde.StatusNotifierHost-31127" as system tray
This is strange, two registrations? Did you log out immediately after login,
then logged in again? If yes, then it is also strange, there is a big
difference between PIDs (9430, 31127)... 

The pids and start times are really strange:
13:36:26 kded started (PID 29782) - OK
13:36:27 pasystray started (PID 31350) - OK, one second later
13:36:27 xembedsniproxy started (PID 31134) - OK, one second later
13:36:58 kalarm started (PID 7545) - 30 seconds later... Maybe coincident...
13:37:18 StatusNotifierHost registered (PID 31127) - much, MUCH too late, on my
system StatusNotifierHost is registered 1-2 seconds after kded is started.

Is you Plasma Desktop taking long time to start?
Can you disable some of the apps starting and check if that helps?
I have no idea but to start with clean user profile and restore configuration
one app at a time.  

> Disabling all background services except for Status Notifier Manager:
OK, no change, dead end.

> That being said, startx always seems to work (though I do plan to run
> multiple tests with it to see if it's consistent).
OK, thanks.

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 420635] Apps that autostart do not appear in the system tray, including DiscoverNotifier

2020-05-10 Thread Brian Wright
https://bugs.kde.org/show_bug.cgi?id=420635

--- Comment #28 from Brian Wright  ---
(In reply to Konrad Materka from comment #27)


> Have you tried fresh user account on your local system?

Yes, I have.  Everything works as it should.  I backed up my personal home
directory, nuked it, and then started fresh.  Everything worked OK, until I
restored some of my app data.  With the test account, I will be keeping it
pristine except for the apps that I need to autostart.

> Thank you! Other people are/were affected, reinstall helped but IMO that's
> not a proper solution.

A reinstall should only take place if the system is not working, period. :-)

> 
> Let's investigate it further...
> 
> * I modified listIcons.sh script, now it outputs PID, path and start time.
> Can you run it again when icons are not registered?

org.kde.StatusNotifierWatcher
pid,start,command:  29782 13:36:26 kded5

ITEMS:

ITEM:  :1.40/org/ayatana/NotificationItem/pasystray
PID STAT: 31350 13:36:27 /usr/bin/pasystray
ID:pasystray
TITLE: pasystray

ITEM:  :1.91/StatusNotifierItem
PID STAT: 31134 13:36:27 /usr/bin/xembedsniproxy
ID:pasystray
TITLE: pasystray

ITEM:  :1.102/StatusNotifierItem
PID STAT:  7545 13:36:58 /usr/bin/kalarm --tray
ID:KAlarm
TITLE: KAlarm

Result - Kmix, DiscoverNotifer, Slack, Skype, KeepassXC, HP-Systray Dropbox
icons are not in the system tray.  PasSystray duplicated.


> * Please find in logs the time when StatusNotifierHost was registered. On my
> system, I've run:
> journalctl -b 0 | grep StatusNotifierHost

May 10 13:35:32 bdw-desktop kded5[4104]: Registering
"org.kde.StatusNotifierHost-9430" as system tray
May 10 13:37:18 bdw-desktop kded5[29782]: Registering
"org.kde.StatusNotifierHost-31127" as system tray


> 
> * In system settings, can you disable all background service and leave only
> one enabled: Status Notifier Manager? Then restart. Maybe something is
> blocking Status Notifier Manager service during startup.

Disabling all background services except for Status Notifier Manager:

Output from journalctl -b 0 | grep StatusNotifierHost:

May 10 17:13:59 bdw-desktop kded5[21295]: Registering
"org.kde.StatusNotifierHost-27235" as system tray
May 10 17:13:59 bdw-desktop kded5[11899]: Registering
"org.kde.StatusNotifierHost-12215" as system tray

Output from ./listIcons.sh:

org.kde.StatusNotifierWatcher
pid,start,command:  21295 17:12:32 kded5
-e 
ITEMS:
-e 
ITEM:  :1.38/StatusNotifierItem
PID STAT: 27336 17:12:36 /usr/bin/korgac
ID:KOrganizer Reminder Daemon
TITLE: KOrganizer Reminder Daemon
-e 
ITEM:  :1.35/StatusNotifierItem
PID STAT: 27274 17:12:36 /usr/lib/x86_64-linux-gnu/libexec/DiscoverNotifier
ID:Discover Notifier_org.kde.DiscoverNotifier
TITLE: Updates
-e 
ITEM:  :1.31/org/ayatana/NotificationItem/pasystray
PID STAT: 27295 17:12:36 /usr/bin/pasystray
ID:pasystray
TITLE: pasystray
-e 
ITEM:  :1.55/StatusNotifierItem
PID STAT: 27345 17:12:36 /usr/bin/kmix --keepvisibility
ID:KMix
TITLE: Volume Control
-e 
ITEM:  :1.39/org/ayatana/NotificationItem/Skype1
PID STAT: 27337 17:12:36 /usr/share/skypeforlinux/skypeforlinux
--executed-from=/home/bdw --pid=27328
ID:Skype1
TITLE: skypeforlinux
-e 
ITEM:  :1.63/StatusNotifierItem
PID STAT:  2517 17:13:07 /usr/bin/kalarm --tray
ID:KAlarm
TITLE: KAlarm
-e 
ITEM:  :1.98/org/ayatana/NotificationItem/dropbox_client_27390
PID STAT: 27390 17:12:36
/home/bdw/.dropbox-dist/dropbox-lnx.x86_64-96.4.172/dropbox
ID:dropbox-client-27390
TITLE: dropbox
-e 
ITEM:  :1.111/org/ayatana/NotificationItem/dropbox_client_24606
PID STAT: 24606 17:17:32
/home/bdw/.dropbox-dist/dropbox-lnx.x86_64-96.4.172/dropbox
ID:dropbox-client-24606
TITLE: dropbox

KeepassXC, Slack, and HP-SystemTray did not open their windows and their icons
did not appear in the system tray.


> 
> * In one of comments you wrote that problem occurs only when KDE is started
> from SDDM, but it is fine when started using startx command. I checked both,
> there is a difference is startup procedure:
> SDDM runs startplasma-x11 (using sddm-helper)
> startx runs plasma_session (using x-session-manager)
> I don't know if what is the difference, I will check with other Plasma
> developers.

I plan to run additonal tests to confirm this.  Either a background process is
messing this up, or something with sddm.  We just have to narrow things down.

That being said, startx always seems to work (though I do plan to run multiple
tests with it to see if it's consistent).

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 420635] Apps that autostart do not appear in the system tray, including DiscoverNotifier

2020-05-10 Thread Konrad Materka
https://bugs.kde.org/show_bug.cgi?id=420635

--- Comment #27 from Konrad Materka  ---
Created attachment 128332
  --> https://bugs.kde.org/attachment.cgi?id=128332=edit
Script to list all registered SNI

(In reply to Brian Wright from comment #26)
> Obviously, something is broken in my system.  Though, I'm reluctant to wipe
> the data and do a full reinstall unless it's absolutely necessary.
Have you tried fresh user account on your local system?

> I'm more inclined to look for the exact cause; only because this issue may
> be affecting others.
Thank you! Other people are/were affected, reinstall helped but IMO that's not
a proper solution.

Let's investigate it further...

* I modified listIcons.sh script, now it outputs PID, path and start time. Can
you run it again when icons are not registered?

* Please find in logs the time when StatusNotifierHost was registered. On my
system, I've run:
journalctl -b 0 | grep StatusNotifierHost

* In system settings, can you disable all background service and leave only one
enabled: Status Notifier Manager? Then restart. Maybe something is blocking
Status Notifier Manager service during startup.

* In one of comments you wrote that problem occurs only when KDE is started
from SDDM, but it is fine when started using startx command. I checked both,
there is a difference is startup procedure:
SDDM runs startplasma-x11 (using sddm-helper)
startx runs plasma_session (using x-session-manager)
I don't know if what is the difference, I will check with other Plasma
developers.

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 420635] Apps that autostart do not appear in the system tray, including DiscoverNotifier

2020-05-08 Thread Brian Wright
https://bugs.kde.org/show_bug.cgi?id=420635

--- Comment #26 from Brian Wright  ---
I've done multiple tests - both on my KDE Neon local system and KDE Neon
running in Virtualbox.

In Virtualbox, all the icons are displayed in the system tray after autostart,
and the autostarted app windows do open.

However, this is not the case with my local system.  The autostarted app
windows do not open and the autostarted app icons will not appear in the system
tray.  DiscoverNotifyer and Kmix are the only plasma apps that will not appear
in the system tray.

Obviously, something is broken in my system.  Though, I'm reluctant to wipe the
data and do a full reinstall unless it's absolutely necessary.

I'm more inclined to look for the exact cause; only because this issue may be
affecting others.

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 420635] Apps that autostart do not appear in the system tray, including DiscoverNotifier

2020-05-06 Thread Konrad Materka
https://bugs.kde.org/show_bug.cgi?id=420635

--- Comment #25 from Konrad Materka  ---
(In reply to Brian Wright from comment #23)
> Started system - all plasma icons appeared in the system tray.  Autostarted,
> running, but missing from the system tray:
OK, so not working: Keepassxc, slack, skypeforlinux, dropbox, hp-systray
Icons that are fine: Discover Notifier (Updates), KOrganizer Reminder Daemon,
pasystray, KMix, KAlarm
All are using SNI, but some icons are missing... It is probably a coincident
that visible icons are mostly KDE apps, but maybe not.

> Stopped and restarted xembedsniproxy - no change
OK, no legacy icons used.

> I'll test with my virtualbox system, and another test user account on my
> local machine, unless there's something else that you'd like me to run.  I'm
Checking on different user or different machine (even virtual) is very much
welcomed! It is possible that something is unusual in your setup.
If possible, can you check logs of affected applications? That might be
difficult, these logs can be stored in different location. I know that Skype
stores them in:
~/.config/skypeforlinux/logs/skype-startup.log

> suspecting that non-plasma apps are not being picked up by the SNI when the
> system starts?
I don't know if that the rule that non-plasma (non-KDE in fact) apps are
affected, pasystray is app from Gnome world.

(In reply to Brian Wright from comment #24)
> Also - the windows did not open for Skype, Slack, and KeepassXC on both
> system startup and logout/login.  They were effectively running in the
> background.
This is unfortunate consequence, but expected. Applications are running but are
minimized by default to tray icon. As tray icon is not there, it is not
possible to show window...

My working idea is that during login application are restored to quickly,
before SNI service is started. That would be really strange, but I have no
other ideas.

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 420635] Apps that autostart do not appear in the system tray, including DiscoverNotifier

2020-05-05 Thread Brian Wright
https://bugs.kde.org/show_bug.cgi?id=420635

--- Comment #24 from Brian Wright  ---
Also - the windows did not open for Skype, Slack, and KeepassXC on both system
startup and logout/login.  They were effectively running in the background.

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 420635] Apps that autostart do not appear in the system tray, including DiscoverNotifier

2020-05-05 Thread Brian Wright
https://bugs.kde.org/show_bug.cgi?id=420635

--- Comment #23 from Brian Wright  ---
Started system - all plasma icons appeared in the system tray.  Autostarted,
running, but missing from the system tray:

Keepassxc
slack
skypeforlinux
dropbox
hp-systray

Ran listIcons.sh

:1.31/StatusNotifierItem
Discover Notifier_org.kde.DiscoverNotifier
Updates

:1.38/StatusNotifierItem
KOrganizer Reminder Daemon
KOrganizer Reminder Daemon

:1.40/org/ayatana/NotificationItem/pasystray
pasystray
pasystray

:1.56/StatusNotifierItem
KMix
Volume Control

:1.76/StatusNotifierItem
KAlarm
KAlarm

Stopped and restarted xembedsniproxy - no change

listIcon.sh output:

:1.31/StatusNotifierItem
Discover Notifier_org.kde.DiscoverNotifier
Updates

:1.38/StatusNotifierItem
KOrganizer Reminder Daemon
KOrganizer Reminder Daemon

:1.40/org/ayatana/NotificationItem/pasystray
pasystray
pasystray

:1.56/StatusNotifierItem
KMix
Volume Control

:1.76/StatusNotifierItem
KAlarm
KAlarm


Logged out, then logged back in.  No change, as seen by listIcons.sh

:1.198/org/ayatana/NotificationItem/pasystray
pasystray
pasystray

:1.191/StatusNotifierItem
Discover Notifier_org.kde.DiscoverNotifier
Updates

:1.195/StatusNotifierItem
KOrganizer Reminder Daemon
KOrganizer Reminder Daemon

:1.208/StatusNotifierItem
KMix
Volume Control

:1.226/StatusNotifierItem
KAlarm
KAlarm

I'll test with my virtualbox system, and another test user account on my local
machine, unless there's something else that you'd like me to run.  I'm
suspecting that non-plasma apps are not being picked up by the SNI when the
system starts?

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 420635] Apps that autostart do not appear in the system tray, including DiscoverNotifier

2020-05-05 Thread Brian Wright
https://bugs.kde.org/show_bug.cgi?id=420635

--- Comment #22 from Brian Wright  ---
Over the weekend, I discovered that my KDE user profile was corrupted.  Monitor
resolution changes weren't saving and SDDM was black-screening with the mouse
cursor.  I backed up all the user data and rebuild my home directory.

I'm going to re-run the testing as I don't trust the results with the corrupted
profile.

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 420635] Apps that autostart do not appear in the system tray, including DiscoverNotifier

2020-05-02 Thread Konrad Materka
https://bugs.kde.org/show_bug.cgi?id=420635

Konrad Materka  changed:

   What|Removed |Added

 CC||simonandr...@gmail.com

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 420635] Apps that autostart do not appear in the system tray, including DiscoverNotifier

2020-05-02 Thread Konrad Materka
https://bugs.kde.org/show_bug.cgi?id=420635

Konrad Materka  changed:

   What|Removed |Added

 CC||notux...@gmail.com

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 420635] Apps that autostart do not appear in the system tray, including DiscoverNotifier

2020-05-02 Thread Konrad Materka
https://bugs.kde.org/show_bug.cgi?id=420635

Konrad Materka  changed:

   What|Removed |Added

 CC||b...@briandwright.com

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 420635] Apps that autostart do not appear in the system tray, including DiscoverNotifier

2020-05-02 Thread Konrad Materka
https://bugs.kde.org/show_bug.cgi?id=420635

Konrad Materka  changed:

   What|Removed |Added

 CC||rdie...@gmail.com

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 420635] Apps that autostart do not appear in the system tray, including DiscoverNotifier

2020-05-02 Thread Konrad Materka
https://bugs.kde.org/show_bug.cgi?id=420635

Konrad Materka  changed:

   What|Removed |Added

 CC||bugsefor...@gmx.com

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 420635] Apps that autostart do not appear in the system tray, including DiscoverNotifier

2020-05-02 Thread Konrad Materka
https://bugs.kde.org/show_bug.cgi?id=420635

Konrad Materka  changed:

   What|Removed |Added

 CC||k...@davidedmundson.co.uk

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 420635] Apps that autostart do not appear in the system tray, including DiscoverNotifier

2020-05-01 Thread Brian Wright
https://bugs.kde.org/show_bug.cgi?id=420635

--- Comment #21 from Brian Wright  ---
(In reply to Konrad Materka from comment #20)

> > Conditions:  PrivateInternetAccess not running.  Booted KDE Neon @ Runlevel
> > 3.  Started KDE via "exec startx"
> Why did you change runlevel? Just to perform this test? That's usual :)

SDDM was broken, and I temporarily set my system to runlevel 3 until I fixed
SDDM. :)

> 
> > Results:  All icons displayed except Slack, hp-systray and DiscoverNotifer 
> > ((confirmed that they were running via ps aux).  Odd effect:  pasystray,
> > indicator-sound-switcher, and skype are duplicated.
> 
> * You have 3 icons missing and 3 duplicated - this is probably be a
> coincidence, but can you perform more tests?

Yes - I plan to do more tests this weekend.

> * Are this duplicated icons behaving the same? For example, if you
> left/right click on Skype icon, to you have the same behavior?

Yes, the duplicated icons behave the same.

> * Duplicated icons does not look the same - maybe one is new SNI and second
> old legacy? What happens if you kill xembedsniproxy? Do duplicated icons
> dissappear? What happens when you run xembedsniproxy again (after kill)?

Duplicated icons don't disappear.  When I ran xembedsniproxy, the command
seemed to hang.  I did not get a message about the container.  So I had to
re-run xembedsniproxy as a background process.

> * For missing icons, what happens when you kill app and run it again? For
> example, kill Slack and run it again - do you have proper tray icon?

Yes, that happens with all the affected apps.  Once I kill the apps and restart
them, they work perfectly.  This is the only way to resolve the issue.

> * The indicator-sound-switcher is not in a default repository, it requires
> ppa. Do you have many ppa configured? Did you do many changes into default
> installation and configuration? My point is, maybe on fresh system (or just
> fresh user) problem does not occur?

I installed Neon on Virtualbox, and then created a test user account. 
Everything worked as it should with the affected apps.  I'm beginning to
strongly suspect that my KDE Plasma profile was corrupted.  I'm going to see
about doing a "factory reset" on the KDE Plasma profile and run more tests.  As
far as changes to the configuration, I can't recall specifics.

> * Are you using snap or flatpack for any of affected application?

No, they were all .deb packages.

> 
> > listIcons.sh output:
> I see duplicated entries for indicator-sound-switcher, pasystray and skype.
> Skype is particularly interesting because it has different names in output.
> My guess is on icon is SNI, second legacy icon translated by xembedsniproxy.

Interesting!

> > org.kde.StatusNotifierItem-19688-1/StatusNotifierItem
> > ..
> > The error is probably being caused by the Google Hangouts extension in
> > Chrome.  I had NetworkManager run via systemd, but the NetworkManager icon
> > was disabled in the system tray.
> NetworkManager icon is an applet to show and manipulate NetworkManager
> daemon, disabling it should not affect anything.
> Error is interesting, but probably this is unrelated - it might be a
> separate issue.

Agreed.

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 420635] Apps that autostart do not appear in the system tray, including DiscoverNotifier

2020-05-01 Thread Konrad Materka
https://bugs.kde.org/show_bug.cgi?id=420635

--- Comment #20 from Konrad Materka  ---
> I had also uninstalled libayatana-appindicator3-1 and associated dependencies
You didn't need to do that, but probably it was not used anyway and it has no
influence.

> Conditions:  PrivateInternetAccess not running.  Booted KDE Neon @ Runlevel
> 3.  Started KDE via "exec startx"
Why did you change runlevel? Just to perform this test? That's usual :)

> Results:  All icons displayed except Slack, hp-systray and DiscoverNotifer 
> ((confirmed that they were running via ps aux).  Odd effect:  pasystray,
> indicator-sound-switcher, and skype are duplicated.

* You have 3 icons missing and 3 duplicated - this is probably be a
coincidence, but can you perform more tests?
* Are this duplicated icons behaving the same? For example, if you left/right
click on Skype icon, to you have the same behavior?
* Duplicated icons does not look the same - maybe one is new SNI and second old
legacy? What happens if you kill xembedsniproxy? Do duplicated icons
dissappear? What happens when you run xembedsniproxy again (after kill)?
* For missing icons, what happens when you kill app and run it again? For
example, kill Slack and run it again - do you have proper tray icon?
* The indicator-sound-switcher is not in a default repository, it requires ppa.
Do you have many ppa configured? Did you do many changes into default
installation and configuration? My point is, maybe on fresh system (or just
fresh user) problem does not occur?
* Are you using snap or flatpack for any of affected application?

> listIcons.sh output:
I see duplicated entries for indicator-sound-switcher, pasystray and skype.
Skype is particularly interesting because it has different names in output. My
guess is on icon is SNI, second legacy icon translated by xembedsniproxy.

> org.kde.StatusNotifierItem-19688-1/StatusNotifierItem
> ..
> The error is probably being caused by the Google Hangouts extension in
> Chrome.  I had NetworkManager run via systemd, but the NetworkManager icon
> was disabled in the system tray.
NetworkManager icon is an applet to show and manipulate NetworkManager daemon,
disabling it should not affect anything.
Error is interesting, but probably this is unrelated - it might be a separate
issue.

> See "Latest Test" attachment for a visual on the current system tray.
Thanks! Images always help :)

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 420635] Apps that autostart do not appear in the system tray, including DiscoverNotifier

2020-05-01 Thread Brian Wright
https://bugs.kde.org/show_bug.cgi?id=420635

--- Comment #19 from Brian Wright  ---
(Neglected to put in the previous comment)

I had also uninstalled libayatana-appindicator3-1 and associated dependencies.

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 420635] Apps that autostart do not appear in the system tray, including DiscoverNotifier

2020-05-01 Thread Brian Wright
https://bugs.kde.org/show_bug.cgi?id=420635

--- Comment #18 from Brian Wright  ---
Latest test:

Conditions:  PrivateInternetAccess not running.  Booted KDE Neon @ Runlevel 3. 
Started KDE via "exec startx"

Results:  All icons displayed except Slack, hp-systray and DiscoverNotifer 
((confirmed that they were running via ps aux).  Odd effect:  pasystray,
indicator-sound-switcher, and skype are duplicated.

Windows did not open for Slack and hp-systray.  DiscoverNotifer did not appear
on the system tray

listIcons.sh output:

:1.37/org/ayatana/NotificationItem/pasystray
pasystray
pasystray

:1.43/org/ayatana/NotificationItem/indicator_sound_switcher
indicator-sound-switcher
indicator-sound-switcher

:1.50/org/ayatana/NotificationItem/Skype1
Skype1
skypeforlinux

:1.67/StatusNotifierItem
pasystray
pasystray

:1.74/StatusNotifierItem
indicator-sound-switcher
indicator-sound-switcher

:1.102/StatusNotifierItem
skypeforlinux
skypeforlinux

:1.111/org/ayatana/NotificationItem/dropbox_client_10415
dropbox-client-10415
dropbox

:1.113/StatusNotifierItem
KAlarm
KAlarm

org.kde.StatusNotifierItem-19688-1/StatusNotifierItem
Error: org.freedesktop.DBus.Error.UnknownMethod
Method "Id" with signature "" on interface "org.kde.StatusNotifierItem" doesn't
exist

Error: org.freedesktop.DBus.Error.UnknownMethod
Method "Title" with signature "" on interface "org.kde.StatusNotifierItem"
doesn't exist

The error is probably being caused by the Google Hangouts extension in Chrome. 
I had NetworkManager run via systemd, but the NetworkManager icon was disabled
in the system tray.

See "Latest Test" attachment for a visual on the current system tray.

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 420635] Apps that autostart do not appear in the system tray, including DiscoverNotifier

2020-05-01 Thread Brian Wright
https://bugs.kde.org/show_bug.cgi?id=420635

--- Comment #17 from Brian Wright  ---
Created attachment 128062
  --> https://bugs.kde.org/attachment.cgi?id=128062=edit
Latest Test

System tray right after KDE starts from system bootup.

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 420635] Apps that autostart do not appear in the system tray, including DiscoverNotifier

2020-05-01 Thread Brian Wright
https://bugs.kde.org/show_bug.cgi?id=420635

--- Comment #16 from Brian Wright  ---
I do run PrivateInternetAccess and it's set to run at startup.  I'll set it so
it won't run at startup to see if that affects the issue.

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 420635] Apps that autostart do not appear in the system tray, including DiscoverNotifier

2020-05-01 Thread Konrad Materka
https://bugs.kde.org/show_bug.cgi?id=420635

Konrad Materka  changed:

   What|Removed |Added

 CC||akontsev...@gmail.com

--- Comment #15 from Konrad Materka  ---
*** Bug 385828 has been marked as a duplicate of this bug. ***

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 420635] Apps that autostart do not appear in the system tray, including DiscoverNotifier

2020-04-30 Thread Konrad Materka
https://bugs.kde.org/show_bug.cgi?id=420635

--- Comment #14 from Konrad Materka  ---
> Maybe something is happening when SDDM launches Plasma?
It may be that KDE is started in a different way, but I'm not an expert in this
area.

I was not able to reproduce this issue, I'm using exactly the same
distribution. KDE Neon is popular among KDE developers, someone else would
notice already, so it seems that this problem is very rare. We have another
similar Bug 385828, so it is not that rare that you are the only one affected
:)

In that context, I would like to ask you for more help, but firstly I need to
explain few technical aspects so that we will get as useful data as possible.

System tray contains two type of items:
* Plasmoids - these are not real applications, but embedded widgets, for
example: Bluetooth, Network, Volume etc. You can recognize them by two things:
in setting of System Tray they have disabled option and usually on click they
show some panel, instead of menu.
* SNI (Status Notifier Item) icons - all external applications like Skype,
Dropbox, Discord, Telegram etc.

It looks that the problem is with SNI icons - plasmoids are working fine.

There is also a special case for SNI icons: legacy tray icons used by some old
old application like KeePass2, Pidgin, xchat and all Windows application run
with wine. The xembedsniproxy is used to translate legacy icons to SNI
protocol.

SNI icons are register in DBus service named "org.kde.StatusNotifierWatcher" -
that's why I asked you to run "qdbus org.kde.StatusNotifierWatcher
/StatusNotifierWatcher RegisteredStatusNotifierItems" - to list all icons IDs
registered in that DBus service. The listIcons.sh scripts uses these IDs and
just prints more information.

In the situation you have, when icons are missing entirely but corresponding
applications are running in the background, DBus service should not have them
as well. This is the most important information to confirm first: is DBus
service running and if it has or not icons registered.

In your second comment, after running listIcons.sh, you received this error:
"org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes
include: the remote application did not send a reply, the message bus security
policy blocked the reply, the reply timeout expired, or the network connection
was broken.". This is especially worrying and strange...

You then posted this: "The error message is from NetworkManager. I accidentally
had it disabled when". Can you give more details how did you disable
NetworkManager? Can you reproduce the same situation again? Disabling Network
Manager should not affect DBus, did you do anything else? Maybe it is related
to your VPN configuration? I found this:
https://www.privateinternetaccess.com/forum/discussion/33328/no-tray-icon-after-update-to-v80-on-ubuntu-17-10

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 420635] Apps that autostart do not appear in the system tray, including DiscoverNotifier

2020-04-30 Thread Brian Wright
https://bugs.kde.org/show_bug.cgi?id=420635

--- Comment #13 from Brian Wright  ---
Hi, Konrad -

I did some additional testing that may help out.

When I start KDE via "startx", all the autostarted programs opened up their
windows and appeared in the system tray.  I did this repeatedly and it worked
consistently.

This issue only seems to happen when logging in via SDDM.  All the programs
autostart, but windows don't open and they don't appear in the taskbar.

The only programs that seem to be affected are any program that isn't QT or
Plasma-based.  When I start Google Chrome, the Hangouts extension will open up
in the system tray.

Maybe something is happening when SDDM launches Plasma?

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 420635] Apps that autostart do not appear in the system tray, including DiscoverNotifier

2020-04-29 Thread Brian Wright
https://bugs.kde.org/show_bug.cgi?id=420635

--- Comment #12 from Brian Wright  ---
After a reboot, the icons did not appear when I disabled the Networkmanager
status icon in the system tray:

:1.35/StatusNotifierItem
KOrganizer Reminder Daemon
KOrganizer Reminder Daemon

:1.36/StatusNotifierItem
Discover Notifier_org.kde.DiscoverNotifier
Updates

:1.38/org/ayatana/NotificationItem/pasystray
pasystray
pasystray

:1.96/StatusNotifierItem
KAlarm
KAlarm

org.kde.StatusNotifierItem-21682-1/StatusNotifierItem
Error: org.freedesktop.DBus.Error.UnknownMethod
Method "Id" with signature "" on interface "org.kde.StatusNotifierItem" doesn't
exist

Error: org.freedesktop.DBus.Error.UnknownMethod
Method "Title" with signature "" on interface "org.kde.StatusNotifierItem"
doesn't exist


The above error seems to be with the Google Hangouts extension with Chrome.  It
does appear in the system tray after I start Google Chrome.  Maybe this has
something to do with the autostart system if the programs set to autostart are
not opening windows and creating icons in the system tray?

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 420635] Apps that autostart do not appear in the system tray, including DiscoverNotifier

2020-04-29 Thread Brian Wright
https://bugs.kde.org/show_bug.cgi?id=420635

--- Comment #11 from Brian Wright  ---
(In reply to Konrad Materka from comment #10)
> > The error message is from NetworkManager.  I accidentally had it disabled
> That's might be it! Can you run:
> qdbus org.kde.StatusNotifierWatcher /StatusNotifierWatcher
> RegisteredStatusNotifierItems
> When Network Manager is disabled? If icons are not visible, it might be the
> root cause. Icons are fetched from DBus service, maybe Network Manager is
> disabling DBus?

Here it is with the NetworkManager disabled:

:1.1103/StatusNotifierItem
hp-systray
hp-systray

:1.1095/org/ayatana/NotificationItem/pasystray
pasystray
pasystray

:1.1104/org/ayatana/NotificationItem/indicator_sound_switcher
indicator-sound-switcher
indicator-sound-switcher

:1.1091/StatusNotifierItem
Discover Notifier_org.kde.DiscoverNotifier
Updates

:1.1092/StatusNotifierItem
KOrganizer Reminder Daemon
KOrganizer Reminder Daemon

:1./StatusNotifierItem
KeePassXC
KeePassXC

:1.1123/org/ayatana/NotificationItem/dropbox_client_25827
dropbox-client-25827
dropbox

org.kde.StatusNotifierItem-25792-1/StatusNotifierItem
privateinternetaccess
privateinternetaccess

:1.1161/StatusNotifierItem
KAlarm
KAlarm

:1.1177/org/ayatana/NotificationItem/Slack1
Slack1
slack

org.kde.StatusNotifierItem-9237-1/StatusNotifierItem
Error: org.freedesktop.DBus.Error.UnknownMethod
Method "Id" with signature "" on interface "org.kde.StatusNotifierItem" doesn't
exist

Error: org.freedesktop.DBus.Error.UnknownMethod
Method "Title" with signature "" on interface "org.kde.StatusNotifierItem"
doesn't exist

I'm not sure about those two errors.  However, the icons did display and the
windows opened. :)

> 
> This item also looks suspicious, are you using VPN?
> > org.kde.StatusNotifierItem-20771-1/StatusNotifierItem
> > privateinternetaccess
> > privateinternetaccess

Yes, I'm running a VPN.

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 420635] Apps that autostart do not appear in the system tray, including DiscoverNotifier

2020-04-29 Thread Konrad Materka
https://bugs.kde.org/show_bug.cgi?id=420635

Konrad Materka  changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |---
 Status|NEEDSINFO   |REPORTED

--- Comment #10 from Konrad Materka  ---
> The error message is from NetworkManager.  I accidentally had it disabled
That's might be it! Can you run:
qdbus org.kde.StatusNotifierWatcher /StatusNotifierWatcher
RegisteredStatusNotifierItems
When Network Manager is disabled? If icons are not visible, it might be the
root cause. Icons are fetched from DBus service, maybe Network Manager is
disabling DBus?

This item also looks suspicious, are you using VPN?
> org.kde.StatusNotifierItem-20771-1/StatusNotifierItem
> privateinternetaccess
> privateinternetaccess

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 420635] Apps that autostart do not appear in the system tray, including DiscoverNotifier

2020-04-28 Thread Brian Wright
https://bugs.kde.org/show_bug.cgi?id=420635

--- Comment #9 from Brian Wright  ---
cat ~/.local/share/sddm/xorg-session.log | grep SNI



-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 420635] Apps that autostart do not appear in the system tray, including DiscoverNotifier

2020-04-28 Thread Brian Wright
https://bugs.kde.org/show_bug.cgi?id=420635

--- Comment #8 from Brian Wright  ---
After restarting xembedsniproxy, the icons did not appear.

Output from qdbus org.kde.StatusNotifierWatcher /StatusNotifierWatcher
RegisteredStatusNotifierItems after running listIcons.sh:

:1.337/org/ayatana/NotificationItem/pasystray
:1.462/StatusNotifierItem
org.kde.StatusNotifierItem-3009-1/StatusNotifierItem
:1.540/StatusNotifierItem

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 420635] Apps that autostart do not appear in the system tray, including DiscoverNotifier

2020-04-28 Thread Brian Wright
https://bugs.kde.org/show_bug.cgi?id=420635

--- Comment #7 from Brian Wright  ---
After changing xembedsniproxy.desktop to use X-KDE-autostart-phase=1, I logged
out and then logged back in.  The programs Skype, Slack, Dropbox, KeepassXC, HP
System Tray, and PrivateInternetAccess launched.  DiscoverNotify is running,
but the icon was not in the system tray.

With the exception of Dropbox, all the other apps that autostarted did not open
windows and are running in the background.  Stoppening xembed

listIcons.sh output after logging back in:

:1.337/org/ayatana/NotificationItem/pasystray
pasystray
pasystray

:1.462/StatusNotifierItem
KAlarm
KAlarm

org.kde.StatusNotifierItem-3009-1/StatusNotifierItem
Error: org.freedesktop.DBus.Error.UnknownMethod
Method "Id" with signature "" on interface "org.kde.StatusNotifierItem" doesn't
exist

Error: org.freedesktop.DBus.Error.UnknownMethod
Method "Title" with signature "" on interface "org.kde.StatusNotifierItem"
doesn't exist


:1.508/StatusNotifierItem
pasystray
pasystray

bdw@bdw-desktop:~/Downloads$ sh listIcons.sh 
:1.337/org/ayatana/NotificationItem/pasystray
pasystray
pasystray

:1.462/StatusNotifierItem
KAlarm
KAlarm

org.kde.StatusNotifierItem-3009-1/StatusNotifierItem
Error: org.freedesktop.DBus.Error.UnknownMethod
Method "Id" with signature "" on interface "org.kde.StatusNotifierItem" doesn't
exist

Error: org.freedesktop.DBus.Error.UnknownMethod
Method "Title" with signature "" on interface "org.kde.StatusNotifierItem"
doesn't exist


:1.508/StatusNotifierItem
pasystray
pasystray

bdw@bdw-desktop:~/Downloads$ sh listIcons.sh 
:1.337/org/ayatana/NotificationItem/pasystray
pasystray
pasystray

:1.462/StatusNotifierItem
KAlarm
KAlarm

org.kde.StatusNotifierItem-3009-1/StatusNotifierItem
Error: org.freedesktop.DBus.Error.UnknownMethod
Method "Id" with signature "" on interface "org.kde.StatusNotifierItem" doesn't
exist

Error: org.freedesktop.DBus.Error.UnknownMethod
Method "Title" with signature "" on interface "org.kde.StatusNotifierItem"
doesn't exist


:1.508/StatusNotifierItem
pasystray
pasystray


:1.337/org/ayatana/NotificationItem/pasystray
pasystray
pasystray

:1.462/StatusNotifierItem
KAlarm
KAlarm

org.kde.StatusNotifierItem-3009-1/StatusNotifierItem
Error: org.freedesktop.DBus.Error.UnknownMethod
Method "Id" with signature "" on interface "org.kde.StatusNotifierItem" doesn't
exist

Error: org.freedesktop.DBus.Error.UnknownMethod
Method "Title" with signature "" on interface "org.kde.StatusNotifierItem"
doesn't exist


:1.508/StatusNotifierItem
pasystray
pasystray

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 420635] Apps that autostart do not appear in the system tray, including DiscoverNotifier

2020-04-28 Thread Brian Wright
https://bugs.kde.org/show_bug.cgi?id=420635

--- Comment #6 from Brian Wright  ---
I've reviewed #385828.  I did check /etc/xdg/autostart/xembedsniproxy.desktop,
and changed X-KDE-autostart-phase to 1.  I'll logout, log back in and see what
happens, along with a reboot.

Here's additional information - Not all the apps that are set to autostart will
actually launch.  This seems to be hit-or-miss.  The apps that are set to
autolaunch will not even launch.  When they do start, they are running and no
icon appears.

However, when they autostart properly, the app windows will be open.  The only
exception is dropbox.

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 420635] Apps that autostart do not appear in the system tray, including DiscoverNotifier

2020-04-28 Thread Brian Wright
https://bugs.kde.org/show_bug.cgi?id=420635

--- Comment #5 from Brian Wright  ---
When all icons are available.  The error message is from NetworkManager.  I
accidentally had it disabled when 

:1.28/StatusNotifierItem
Discover Notifier_org.kde.DiscoverNotifier
Updates

:1.35/StatusNotifierItem
KOrganizer Reminder Daemon
KOrganizer Reminder Daemon

:1.42/org/ayatana/NotificationItem/pasystray
pasystray
pasystray

:1.95/StatusNotifierItem
KAlarm
KAlarm

org.kde.StatusNotifierItem-3341-1/StatusNotifierItem
NoMachineMonitor
NoMachineMonitor

org.kde.StatusNotifierItem-17098-1/StatusNotifierItem
Error: org.freedesktop.DBus.Error.UnknownMethod
Method "Id" with signature "" on interface "org.kde.StatusNotifierItem" doesn't
exist

Error: org.freedesktop.DBus.Error.UnknownMethod
Method "Title" with signature "" on interface "org.kde.StatusNotifierItem"
doesn't exist


:1.164/StatusNotifierItem
strawberry
strawberry

org.kde.StatusNotifierItem-20771-1/StatusNotifierItem
privateinternetaccess
privateinternetaccess

:1.178/org/ayatana/NotificationItem/dropbox_client_23929
dropbox-client-23929
dropbox

:1.184/StatusNotifierItem
hp-systray
hp-systray

:1.186/org/ayatana/NotificationItem/Skype1
Skype1
skypeforlinux

:1.192/org/ayatana/NotificationItem/Slack1
Slack1
slack

:1.196/StatusNotifierItem
KeePassXC
KeePassXC

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 420635] Apps that autostart do not appear in the system tray, including DiscoverNotifier

2020-04-28 Thread Konrad Materka
https://bugs.kde.org/show_bug.cgi?id=420635

Konrad Materka  changed:

   What|Removed |Added

 Resolution|--- |WAITINGFORINFO
 Status|REPORTED|NEEDSINFO

--- Comment #4 from Konrad Materka  ---
Hmm, error... Can you run just this command?

qdbus org.kde.StatusNotifierWatcher /StatusNotifierWatcher
RegisteredStatusNotifierItems

In addition, Check "System Settings" -> "Startup and Shutdown" -> "Background
Services" and in section "Startup Service" check if "Status Notifier Manager"
is in "Running" status (it should be).

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 420635] Apps that autostart do not appear in the system tray, including DiscoverNotifier

2020-04-28 Thread Brian Wright
https://bugs.kde.org/show_bug.cgi?id=420635

--- Comment #3 from Brian Wright  ---
First, run with the missing icons - this error was generated:

Error:
Service 'Error:' is not a valid name.
Service 'Error:' is not a valid name.

org.freedesktop.DBus.Error.NoReply
Path 'org.kde.StatusNotifierItem.Id' is not a valid path name.
Path 'org.kde.StatusNotifierItem.Title' is not a valid path name.

Did
Path 'org.kde.StatusNotifierItem.Id' is not a valid path name.
Path 'org.kde.StatusNotifierItem.Title' is not a valid path name.

not
Path 'org.kde.StatusNotifierItem.Id' is not a valid path name.
Path 'org.kde.StatusNotifierItem.Title' is not a valid path name.

receive
Path 'org.kde.StatusNotifierItem.Id' is not a valid path name.
Path 'org.kde.StatusNotifierItem.Title' is not a valid path name.

a
Path 'org.kde.StatusNotifierItem.Id' is not a valid path name.
Path 'org.kde.StatusNotifierItem.Title' is not a valid path name.

reply.
Service 'reply.' is not a valid name.
Service 'reply.' is not a valid name.

Possible
Path 'org.kde.StatusNotifierItem.Id' is not a valid path name.
Path 'org.kde.StatusNotifierItem.Title' is not a valid path name.

causes
Path 'org.kde.StatusNotifierItem.Id' is not a valid path name.
Path 'org.kde.StatusNotifierItem.Title' is not a valid path name.

include:
Service 'include:' is not a valid name.
Service 'include:' is not a valid name.

the
Path 'org.kde.StatusNotifierItem.Id' is not a valid path name.
Path 'org.kde.StatusNotifierItem.Title' is not a valid path name.

remote
Path 'org.kde.StatusNotifierItem.Id' is not a valid path name.
Path 'org.kde.StatusNotifierItem.Title' is not a valid path name.

application
Path 'org.kde.StatusNotifierItem.Id' is not a valid path name.
Path 'org.kde.StatusNotifierItem.Title' is not a valid path name.

did
Path 'org.kde.StatusNotifierItem.Id' is not a valid path name.
Path 'org.kde.StatusNotifierItem.Title' is not a valid path name.

not
Path 'org.kde.StatusNotifierItem.Id' is not a valid path name.
Path 'org.kde.StatusNotifierItem.Title' is not a valid path name.

send
Path 'org.kde.StatusNotifierItem.Id' is not a valid path name.
Path 'org.kde.StatusNotifierItem.Title' is not a valid path name.

a
Path 'org.kde.StatusNotifierItem.Id' is not a valid path name.
Path 'org.kde.StatusNotifierItem.Title' is not a valid path name.

reply,
Service 'reply,' is not a valid name.
Service 'reply,' is not a valid name.

the
Path 'org.kde.StatusNotifierItem.Id' is not a valid path name.
Path 'org.kde.StatusNotifierItem.Title' is not a valid path name.

message
Path 'org.kde.StatusNotifierItem.Id' is not a valid path name.
Path 'org.kde.StatusNotifierItem.Title' is not a valid path name.

bus
Path 'org.kde.StatusNotifierItem.Id' is not a valid path name.
Path 'org.kde.StatusNotifierItem.Title' is not a valid path name.

security
Path 'org.kde.StatusNotifierItem.Id' is not a valid path name.
Path 'org.kde.StatusNotifierItem.Title' is not a valid path name.

policy
Path 'org.kde.StatusNotifierItem.Id' is not a valid path name.
Path 'org.kde.StatusNotifierItem.Title' is not a valid path name.

blocked
Path 'org.kde.StatusNotifierItem.Id' is not a valid path name.
Path 'org.kde.StatusNotifierItem.Title' is not a valid path name.

the
Path 'org.kde.StatusNotifierItem.Id' is not a valid path name.
Path 'org.kde.StatusNotifierItem.Title' is not a valid path name.

reply,
Service 'reply,' is not a valid name.
Service 'reply,' is not a valid name.

the
Path 'org.kde.StatusNotifierItem.Id' is not a valid path name.
Path 'org.kde.StatusNotifierItem.Title' is not a valid path name.

reply
Path 'org.kde.StatusNotifierItem.Id' is not a valid path name.
Path 'org.kde.StatusNotifierItem.Title' is not a valid path name.

timeout
Path 'org.kde.StatusNotifierItem.Id' is not a valid path name.
Path 'org.kde.StatusNotifierItem.Title' is not a valid path name.

expired,
Service 'expired,' is not a valid name.
Service 'expired,' is not a valid name.

or
Path 'org.kde.StatusNotifierItem.Id' is not a valid path name.
Path 'org.kde.StatusNotifierItem.Title' is not a valid path name.

the
Path 'org.kde.StatusNotifierItem.Id' is not a valid path name.
Path 'org.kde.StatusNotifierItem.Title' is not a valid path name.

network
Path 'org.kde.StatusNotifierItem.Id' is not a valid path name.
Path 'org.kde.StatusNotifierItem.Title' is not a valid path name.

connection
Path 'org.kde.StatusNotifierItem.Id' is not a valid path name.
Path 'org.kde.StatusNotifierItem.Title' is not a valid path name.

was
Path 'org.kde.StatusNotifierItem.Id' is not a valid path name.
Path 'org.kde.StatusNotifierItem.Title' is not a valid path name.

broken.
Service 'broken.' is not a valid name.
Service 'broken.' is not a valid name.

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 420635] Apps that autostart do not appear in the system tray, including DiscoverNotifier

2020-04-28 Thread Konrad Materka
https://bugs.kde.org/show_bug.cgi?id=420635

--- Comment #2 from Konrad Materka  ---
Possible a duplicate of Bug 385828.
Brian, can you check Bug 385828, especially attached "List SNI icons" script
(https://bugs.kde.org/attachment.cgi?id=123376). Run it when all icons are
visible and where icons are missing. With that output I will be able to
identify if this is a duplicate.

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 420635] Apps that autostart do not appear in the system tray, including DiscoverNotifier

2020-04-28 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=420635

Nate Graham  changed:

   What|Removed |Added

 CC||mate...@gmail.com,
   ||n...@kde.org

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 420635] Apps that autostart do not appear in the system tray, including DiscoverNotifier

2020-04-26 Thread Brian Wright
https://bugs.kde.org/show_bug.cgi?id=420635

--- Comment #1 from Brian Wright  ---
Deleting plasma-org.kde.plasma.desktop-appletsrc does not resolve the issue.

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 420635] Apps that autostart do not appear in the system tray, including DiscoverNotifier

2020-04-26 Thread Brian Wright
https://bugs.kde.org/show_bug.cgi?id=420635

Brian Wright  changed:

   What|Removed |Added

   Platform|Other   |Neon Packages

-- 
You are receiving this mail because:
You are watching all bug changes.