https://bugzilla.novell.com/show_bug.cgi?id=755820
https://bugzilla.novell.com/show_bug.cgi?id=755820#c2
--- Comment #2 from Rainer Klier
Please attach your output of the hp-toolbox python script in your particular case as MIME type "text/plain"
i will try. but it is really a just simple text: /usr/lib64/python2.7/site-packages/gtk-2.0/gtk/__init__.py:127: RuntimeWarning: PyOS_InputHook is not available for interactive use of PyGTK set_interactive(1) error: Unable to communicate with device (code=12): hp:/net/HP_Color_LaserJet_2600n?ip=172.16.17.25 error: Device not found
But I assume it is better to simply drop my hp-toolbox.wrapper attempt to work around issues in HPLIP's hp-toolbox and file a bug report at HPLIP upstream via http://hplipopensource.com/hplip-web/support.html
i agree.
Those kind of workarounds never ever really work in all cases.
of course not. ;-)
For now you can avoid it by changing hp-toolbox.wrapper to ------------------------------------------------------------------------- ... if test -x "$( type -p hp-toolbox )" then hp-toolbox else $PopupProgram 'Cannot execute hp-toolbox.' fi ------------------------------------------------------------------------- Does it work for you after you changed hp-toolbox.wrapper this way?
I did it already this way, after i found out, where the problem came from. Just before i added this bug report. And yes, it works with this workaround. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.