Bug#587737: [hplip-gui] hp-systray fails to start

2010-11-28 Thread Matthias Heinz
Hi,

well, I found out something new.

I'm using gtk-qt-engine and even though hp-systray uses PyQt there seems 
to be a connection.

If I deactivate the usage of the gtk style engine hp-systray works fine. 
If I activate it, it hangs like I mentioned before.


Regards,
Matthias



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#587737: [hplip-gui] hp-systray fails to start

2010-08-07 Thread Matthias Heinz
Hi,

If found some time to dig in a bit.

It looks like it has something to do with python-qt4, because the 
app.exec_() in /usr/share/hplip/ui4/systemtray.py:725 fails/locks it up.

This is a call for QApplication to start, so it looks like something 
goes wrong here.


Regards,
Matthias

PS: Not being able to kill PyQt-apps has this reason:
http://www.mail-archive.com/p...@riverbankcomputing.com/msg13757.html



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#587737: [Pkg-hpijs-devel] Bug#587737: [hplip-gui] hp-systray fails to start

2010-07-02 Thread Mark Purcell
On Thursday 01 July 2010 19:55:02 Matthias Heinz wrote:
 since yesterday, iirc, hp-systray fails to start and leaves a python 
 process behind, which consumes 100% cpu time.

Matthais,

Could you please forward a copy of the output from `hpcheck -r`.

Also things appear to be quite muddled with the python transition, so if you 
could provide some details of your current python configuration that would also 
assist.


Thanks,
Mark


signature.asc
Description: This is a digitally signed message part.


Bug#587737: [hplip-gui] hp-systray fails to start

2010-07-01 Thread Matthias Heinz
Package: hplip-gui
Version: 3.10.5-3.2
Severity: serious

--- Please enter the report below this line. ---

Hi,

since yesterday, iirc, hp-systray fails to start and leaves a python 
process behind, which consumes 100% cpu time.

This is all I can get as debug output:

# hp-systray -l debug

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

Copyright (c) 2001-9 Hewlett-Packard 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.

hp-systray[16680]: debug: Locking: /home/xts/.hplip/hp-systray.lock
hp-systray[16680]: debug: Creating pipe: hpssd (6) == systemtray (5)
hp-systray[16680]: debug: Creating pipe: hpssd (7) == hpdio (5)
hp-systray[16680]: debug: Creating pipe: hpdio (9) == hpssd (8)
hp-systray(hpdio)[16682]: debug: PID=16682
hp-systray(hpssd)[16681]: debug: PID=16681
hp-systray(hpssd)[16681]: debug: Entering main dbus loop...
/usr/lib/pymodules/python2.6/gtk-2.0/gtk/__init__.py:127: 
RuntimeWarning: PyOS_InputHook is not available for interactive use of 
PyGTK
  set_interactive(1)
hp-systray(qt4)[16680]: debug: PID=16680
hp-systray(qt4)[16680]: debug: Loading user settings...
hp-systray(qt4)[16680]: debug: FAB command: /usr/bin/hp-fab 
hp-systray(qt4)[16680]: debug: Scan command: /usr/bin/xsane -V 
%SANE_URI%
hp-systray(qt4)[16680]: debug: Auto refresh: False
hp-systray(qt4)[16680]: debug: Auto refresh rate: 30
hp-systray(qt4)[16680]: debug: Auto refresh type: 1
hp-systray(qt4)[16680]: debug: Systray visible: 1
hp-systray(qt4)[16680]: debug: Systray messages: 0
hp-systray(qt4)[16680]: debug: Last used device URI: 
hpfax:/net/HP_Color_LaserJet_2840?ip=192.168.1.20
hp-systray(qt4)[16680]: debug: Last used printer: 
HP_Color_LaserJet_2840_fax
hp-systray(qt4)[16680]: debug: Working directory: .
hp-systray(qt4)[16680]: debug: 
hp:/net/HP_Color_LaserJet_2840?ip=192.168.1.20: back_end:hp is_hp:True 
bus:net model:HP_Color_LaserJet_2840 serial: dev_file: host:192.168.1.20 
zc: port:1  

   
hp-systray(qt4)[16680]: debug: Cache miss: hp_color_laserjet_2840
hp-systray(qt4)[16680]: debug: Reading file: 
/usr/share/hplip/data/models/models.dat
hp-systray(qt4)[16680]: debug: Searching for section 
[hp_color_laserjet_2840] in file /usr/share/hplip/data/models/models.dat
hp-systray(qt4)[16680]: debug: Found section [hp_color_laserjet_2840] in 
file /usr/share/hplip/data/models/models.dat
hp-systray(qt4)[16680]: debug: 
hpfax:/net/HP_Color_LaserJet_2840?ip=192.168.1.20: back_end:hpfax 
is_hp:True bus:net model:HP_Color_LaserJet_2840 serial: dev_file: 
host:192.168.1.20 zc: port:1

   
hp-systray(qt4)[16680]: debug: Device URI cups-pdf:/ is invalid/unknown
hp-systray(qt4)[16680]: debug: Exception: 4 (Unknown/invalid device-uri 
field)
hp-systray(qt4)[16680]: debug: Device URI cups-pdf:/ is invalid/unknown
hp-systray(qt4)[16680]: debug: Exception: 4 (Unknown/invalid device-uri 
field)
hp-systray(qt4)[16680]: debug: Device URI hal:// is invalid/unknown
hp-systray(qt4)[16680]: debug: Exception: 4 (Unknown/invalid device-uri 
field)
hp-systray(qt4)[16680]: debug: 
hpfax:/net/HP_Color_LaserJet_2840?ip=192.168.1.20: back_end:hpfax 
is_hp:True bus:net model:HP_Color_LaserJet_2840 serial: dev_file: 
host:192.168.1.20 zc: port:1

   
hp-systray(qt4)[16680]: debug: 
hpfax:/net/HP_Color_LaserJet_2840?ip=192.168.1.20: back_end:hpfax 
is_hp:True bus:net model:HP_Color_LaserJet_2840 serial: dev_file: 
host:192.168.1.20 zc: port:1

   
hp-systray(qt4)[16680]: debug: 
hp:/net/HP_Color_LaserJet_2840?ip=192.168.1.20: back_end:hp is_hp:True 
bus:net model:HP_Color_LaserJet_2840 serial: dev_file: host:192.168.1.20 
zc: port:1  

   
hp-systray(qt4)[16680]: debug: 
hp:/net/HP_Color_LaserJet_2840?ip=192.168.1.20: back_end:hp is_hp:True 
bus:net model:HP_Color_LaserJet_2840 serial: dev_file: host:192.168.1.20 
zc: port:1  

   
^Chp-systray(hpssd)[16681]: debug: Ctrl-C: Exiting...