Bug 23795 - HPLIP "no system tray detected" error with Gnome 3.30.0
Summary: HPLIP "no system tray detected" error with Gnome 3.30.0
Status: NEW
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: All Linux
Priority: High normal
Target Milestone: ---
Assignee: GNOME maintainers
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-11-01 07:32 CET by Sébastien Morin
Modified: 2018-12-10 21:35 CET (History)
4 users (show)

See Also:
Source RPM: hplip-3.18.9-1.mga7
CVE:
Status comment:


Attachments

Description Sébastien Morin 2018-11-01 07:32:59 CET
Description of problem:
When Gnome desktop environment is started, a pop-up error message says:
"HPLIP Status Service: No system tray detected on this system. Unable to start, exiting".

This is what I can find in journaltcl:
nov. 01 10:14:23 bifrost hplip-systray.desktop[8479]: error:  No system tray detected on this system.  Unable to start, exiting. 
nov. 01 10:14:23 bifrost /hp-systray[8479]: hp-systray(qt5)[8479]: error:  No system tray detected on this system.  Unable to start, exiting.
nov. 01 10:14:23 bifrost org.gnome.Shell.desktop[6444]: Window manager warning: Invalid WM_TRANSIENT_FOR window 0x1a00008 specified for 0x1a00006 (HPLIP Stat).

Version-Release number of selected component (if applicable):
$ rpm -qa | grep hplip
hplip-hpijs-ppds-3.18.9-1.mga7
hplip-3.18.9-1.mga7
hplip-hpijs-3.18.9-1.mga7
hplip-gui-3.18.9-1.mga7
hplip-model-data-3.18.9-1.mga7

and
gnome-3.30.0-2.mga7

How reproducible:
Always. Just open a session in Gnome desktop with your up-to-date Cauldron.

Please note: this message doesn't show up when opening a session in KDE Plasma.
Comment 1 Marja Van Waes 2018-11-01 07:53:14 CET
(In reply to Sébastien Morin from comment #0)

> 
> How reproducible:
> Always. Just open a session in Gnome desktop with your up-to-date Cauldron.
> 
> Please note: this message doesn't show up when opening a session in KDE
> Plasma.

Assigning to the Gnome maintainers, then.

Assignee: bugsquad => gnome
CC: (none) => marja11

Comment 2 Lewis Smith 2018-12-07 20:37:05 CET
Not sure whether this is the right place to complain, but testing M7beta1 Classic ISO Gnome desktop from GDM, there is no sign of Systray. Yet programs which leave launchers in it, work. Just that you cannot see them.
Gnome Systray used to be hidden in the bottom LH margin, popping out when hovered there. This does not happen now - unless it is hidden elsewhere, which I have not been able to find.
Comment 3 Frank Griffin 2018-12-07 21:35:54 CET
Reincarnation of https://bugs.mageia.org/show_bug.cgi?id=16946 ?

CC: (none) => ftg

Comment 4 Lewis Smith 2018-12-09 11:49:37 CET
Same problem testing M7beta1 Live Gnome installation. This must be fixed, because you think applications have not started when in reality they have - but remain inaccessible. Because the consequence is not trivial, I have raised the bug priority.

CC: (none) => lewyssmith
Priority: Normal => High

Comment 5 Martin Whitaker 2018-12-10 00:13:22 CET
The legacy tray has gone for good:

https://bugzilla.gnome.org/show_bug.cgi?id=785956

but there's a GNOME extension that may help:

https://extensions.gnome.org/extension/1031/topicons/

CC: (none) => mageia

Comment 6 Lewis Smith 2018-12-10 21:35:47 CET
(In reply to Martin Whitaker from comment #5)
> The legacy tray has gone for good:
> https://bugzilla.gnome.org/show_bug.cgi?id=785956
This is hopeless. Many applications (especially KDE, also Mageia network thingies) do not pop a window, but put themselves in Systray for activation on-demand. Not having it, one is not only unaware that they are running, but you have no access to them! Unless I have missed something...

> but there's a GNOME extension that may help:
> https://extensions.gnome.org/extension/1031/topicons/
"This extension moves legacy tray icons (bottom left of Gnome Shell) to the top panel."
This looks ideal, since it makes the Systray like for the other desktops. Can we not install it as standard? So many questions (which could become bugs) are caused by this loss of Gnome Systray.
Something for the Gnome maintainer(s).

Note You need to log in before you can comment on or make changes to this bug.