Mailinglist Archive: opensuse-bugs (6606 mails)

< Previous Next >
[Bug 528819] New: HPLIP version upgrade from 3.9.6b to 3.9.8
  • From: bugzilla_noreply@xxxxxxxxxx
  • Date: Thu, 6 Aug 2009 06:44:20 -0600
  • Message-id: <bug-528819-21960@xxxxxxxxxxxxxxxxxxxxxxxx/>

Summary: HPLIP version upgrade from 3.9.6b to 3.9.8
Classification: openSUSE
Product: openSUSE 11.2
Version: Factory
Platform: All
OS/Version: SuSE Other
Severity: Enhancement
Priority: P5 - None
Component: Printing
AssignedTo: coolo@xxxxxxxxxx
ReportedBy: jsmeix@xxxxxxxxxx
QAContact: jsmeix@xxxxxxxxxx
CC: lnussel@xxxxxxxxxx, jsmeix@xxxxxxxxxx
Found By: Development

Today HPLIP version 3.9.8 was released.
I would like to have HPLIP 3.9.8 in openSUSE 11.2.

There are many bug fixies and
many more supported printers and all-in-one devices.

The main new feature is mDNS/Bonjour support
for which I provide
to open UDP ports 5353(mdns) and 427(svrloc)
which are required for mDNS support in HPLIP
according to the init-suse-firewall file in the tar ball
(there is no init-suse-firewall in the RPM).
do you like to have a look at the firewall stuff here?

For details see

As far as I see there is no backward incompatibility.
It works for me on my openSUSE 11.1 i386 workstation
with a HP LaserJet 1220 printer+scanner at the USB.

But I am no usual "desktop user" (I run neither KDE nor Gnome
but plain X with fvwm2) so that someone else who is a typical
"desktop user" should carefully and thoroughly test if there are
regressions regarding HPLIP integration into our desktops.
In particular if hp-toolbox together with hp-systray work well and
regarding normal user access for HP devices via our udev/HAL magic
(in particular if hp-toolbox can show the device state and if scanners
in HP all-in-one devices are accessible by the desktop user).

hplip-3.9.8 and hplip-hpijs-3.9.8 RPMs for testing
will appear after several hours at

if you agree I will submit HPLIP 3.9.8 to openSUSE:Factory.

Configure bugmail:
------- You are receiving this mail because: -------
You are on the CC list for the bug.

< Previous Next >