"NameError: name 'systray' is not defined" While trying to install HPlip

Bug #1793040 reported by Stimbus
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
HPLIP
In Progress
Undecided
Unassigned

Bug Description

Trying to install hplip 3.18.7 on Debian 9.5 and getting this error.

Traceback (most recent call last):
  File "/usr/bin/hp-systray", line 118, in <module>
    systray.run(r1)
NameError: name 'systray' is not defined

The printer was added to CUPS but doesn't print. Gives "Filter failed" error.

Revision history for this message
srinivas (srinivas5) wrote :

Hi,

Please share the printer details.

For the filter issue,
Run sudo hp-logcapture and do print job. It will generate logs, Please share the logs.

Thanks,
Srinivas Teja.

Changed in hplip:
status: New → In Progress
Revision history for this message
Pierre (plindenbaum) wrote :

Hi,
four years later, I've got the same problem with hplip-3.22.10 + XUbuntu 22.04.

The command ended with:

```
(...)
RE-STARTING HP_SYSTRAY
----------------------

HP Linux Imaging and Printing System (ver. 3.22.10)
System Tray Status Service ver. 2.0

Copyright (c) 2001-18 HP Development Company, LP
This software comes with ABSOLUTELY NO WARRANTY.
This is free software, and you are welcome to distribute it
under certain conditions. See COPYING file for more details.

Traceback (most recent call last):
  File "/usr/bin/hp-systray", line 118, in <module>
    systray.run(r1)
NameError: name 'systray' is not defined
Error in sys.excepthook:
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/apport_python_hook.py", line 153, in apport_excepthook
    with os.fdopen(os.open(pr_filename,
PermissionError: [Errno 13] Permission denied: '/var/crash/_usr_share_hplip_systray.py.1000.crash'

Original exception was:
Traceback (most recent call last):
  File "/usr/bin/hp-systray", line 118, in <module>
    systray.run(r1)
NameError: name 'systray' is not defined

```

Revision history for this message
Pierre (plindenbaum) wrote :

and enalbling gui seems to fix the problem.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Bug attachments

Remote bug watches

Bug watches keep track of this bug in other bug trackers.