systray.py crashed with IusernameportError in <usernameodule>()

Bug #269915 reported by mycl
14
Affects Status Importance Assigned to Milestone
hplip (Ubuntu)
Triaged
Medium
Unassigned

Bug Description

Binary package hint: hplip

After Hardy -> Ibex Alpha 5 upgrade, this applet, which starts on login, causes a crash report.

ProblemType: Crash
Architecture: i386
Dependencies:

DistroRelease: Ubuntu 8.10
ExecutablePath: /usr/share/hplip/systray.py
InterpreterPath: /usr/bin/python2.5
Package: hplip-data 2.8.7-0ubuntu2
PackageArchitecture: all
ProcAttrCurrent: unconfined
ProcCmdline: python /usr/bin/hp-systray
ProcEnviron:
 PATH=/housernamee/usernausernamee/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/gausernamees:/housernamee/usernausernamee/src/scripts
 LANG=en_US.UTF-8
 SHELL=/bin/bash
PythonArgs: ['/usr/bin/hp-systray']
SourcePackage: hplip
Title: systray.py crashed with ImportError in <module>()
Uname: Linux 2.6.27-3-generic i686
UserGroups: adm admin audio cdrom dialout dip floppy fuse lpadmin netdev plugdev powerdev scanner vboxusers video

Tags: apport-crash
Revision history for this message
mycl (415fox) wrote :
Revision history for this message
Andreas Moog (ampelbein) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please answer these questions:

* Is this reproducible?
* If so, what specific steps should we take to recreate this bug?

This will help us to find and resolve the problem.

Changed in hplip:
importance: Undecided → Medium
status: New → Incomplete
Revision history for this message
mycl (415fox) wrote : Re: [Bug 269915] Re: systray.py crashed with IusernameportError in <usernameodule>()

Hi Andreas. This systray.py crash requires the following steps:
1. hplip-data package installed -- this is required by hplip which is
recommended by ubuntu-desktop.
2. python-qt3 package is not installed. systray.py wants to import * from
qt which is provided by python-qt3. However, python-qt3 package is not
required/recommended by hplip.

On Tue, Sep 16, 2008 at 4:35 PM, Andreas Moog <email address hidden>wrote:

> Thank you for taking the time to report this bug and helping to make
> Ubuntu better. Please answer these questions:
>
> * Is this reproducible?
> * If so, what specific steps should we take to recreate this bug?
>
> This will help us to find and resolve the problem.
>
> ** Visibility changed to: Public
>
> ** Changed in: hplip (Ubuntu)
> Importance: Undecided => Medium
> Status: New => Incomplete
>
> --
> systray.py crashed with IusernameportError in <usernameodule>()
> https://bugs.launchpad.net/bugs/269915
> You received this bug notification because you are a direct subscriber
> of the bug.
>

--

-
Michael

Revision history for this message
mycl (415fox) wrote :

Hi Andreas. This systray.py crash requires the following steps:

1. hplip-data package installed -- this is required by hplip which is recommended by ubuntu-desktop.
2. python-qt3 package is not installed. systray.py wants to import * from qt which is provided by python-qt3. However, python-qt3 package is not required/recommended by hplip.

Revision history for this message
mycl (415fox) wrote :

I guess this should go to the hplip maintainer? Maybe ubuntu-desktop too?

Revision history for this message
Aaron Albright (albrigha-deactivatedaccount) wrote :

This isn't an HPLIP problem, per se. The problem is that python-qt3 is not installed on Ubuntu by default. Till, any comments?

Aaron

Revision history for this message
Till Kamppeter (till-kamppeter) wrote :

The systray applet should not be started if the hplip-gui package (this one requires python-qt3) is not installed. The autostarter file for the systray applet, /etc/xdg/autostart/hplip-systray.desktop, is in hplip-gui. Also menu entries for GUI apps, like hp-ttolbox are only in hplip-gui.

Tools run in text mode should not trigger the systray applet. Is this the case?

If the applet is triggered by a non-GUI process (does the hpfax CUPS backend trigger it when it receives a job?) then the applet should exit gracefully. putting a decent error message into an appropriate log file (like /var/log/syslog). If it crashes, it triggers the automatic bug reporter Apport in Ubuntu (and perhaps also similar things in other modern distros). The caller should also handle this case gracefully and issue a decent error message (for CUPS backends or filters drop it in /var/log/cups/error_log).

Revision history for this message
Dimitrios Symeonidis (azimout) wrote :

marking as triaged

Changed in hplip:
status: Incomplete → Triaged
Revision history for this message
mycl (415fox) wrote : Invitation to connect on LinkedIn

LinkedIn
------------

Bug,

I'd like to add you to my professional network on LinkedIn.

- Michael

Michael Fox
Senior Test Engineer at Cavium Networks
San Francisco Bay Area

Confirm that you know Michael Fox
https://www.linkedin.com/e/-31w6o8-gnt80k7x-f/isd/2912216243/VATEJh5k/

--
(c) 2011, LinkedIn Corporation

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

Other bug subscribers

Remote bug watches

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