[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#995322: marked as done (ipp-usb: prevents hp-toolbox and libsane-hpaio from working)



Your message dated Wed, 29 Sep 2021 19:30:16 +0100
with message-id <29092021191432.de2261d9a6d8@desktop.copernicus.org.uk>
and subject line Re: Bug#995322: ipp-usb: prevents hp-toolbox and libsane-hpaio from working
has caused the Debian Bug report #995322,
regarding ipp-usb: prevents hp-toolbox and libsane-hpaio from working
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
995322: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995322
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: ipp-usb
Version: 0.9.17-3+b4
Severity: normal

Dear Maintainer,

Upon upgrading a computer to bullseye, I discovered that the 
multifunction scanner/printer/fax HP Officejet Pro 8620 became 
unusable as a scanner, and could not any more be accessed and managed
via hp-toolbox. The system did detect the printer to be connected
via USB, but was then unable to connect to it, be it via xsane (or 
any other scanning software) or hp-toolbox. This very effectively
made the scanner unusable from the computer.
Upon perusing strace and going through the system logs (I suspected some
apparmor problem, I had to fix some after the upgrade), I found out instead 
that the device was already in use by ipp-usb, which prevented xsane and/or 
hp-toolbox to use it. Upon stopping ipp-usb, I was able to correctly
use the multifunction flawlessly.

Please, either fix this incompatibility or document it properly, so that
users of such USB-connected devices do not get them partially blocked 
without any clue as to why. I actually did not explicitly select ipp-usb for 
installation, it was carried over by the overall upgrade from buster
to bullseye (don't know exactly by what dependency/recommends).
Getting a message upon installation that this might cause problems
with xsane would have spared me a few hours of troubleshooting at the 
moment I really needed the scanner to work (as it always did before).

Thanks in advance, best regards
Giacomo Mulas

--- End Message ---
--- Begin Message ---
On Wed 29 Sep 2021 at 18:33:04 +0200, Giacomo Mulas wrote:

> Package: ipp-usb
> Version: 0.9.17-3+b4
> Severity: normal
> 
> Dear Maintainer,
> 
> Upon upgrading a computer to bullseye, I discovered that the 
> multifunction scanner/printer/fax HP Officejet Pro 8620 became 
> unusable as a scanner, and could not any more be accessed and managed
> via hp-toolbox. The system did detect the printer to be connected
> via USB, but was then unable to connect to it, be it via xsane (or 
> any other scanning software) or hp-toolbox. This very effectively
> made the scanner unusable from the computer.
> Upon perusing strace and going through the system logs (I suspected some
> apparmor problem, I had to fix some after the upgrade), I found out instead 
> that the device was already in use by ipp-usb, which prevented xsane and/or 
> hp-toolbox to use it. Upon stopping ipp-usb, I was able to correctly
> use the multifunction flawlessly.
> 
> Please, either fix this incompatibility or document it properly, so that
> users of such USB-connected devices do not get them partially blocked 
> without any clue as to why. I actually did not explicitly select ipp-usb for 
> installation, it was carried over by the overall upgrade from buster
> to bullseye (don't know exactly by what dependency/recommends).
> Getting a message upon installation that this might cause problems
> with xsane would have spared me a few hours of troubleshooting at the 
> moment I really needed the scanner to work (as it always did before).

Thank you for your report, Giacomo.

Much of your time would have been saved by reading the Release
Notes. Please submit another report if you feel the documentation
is inadequate.

Cheers,

Brian.

--- End Message ---

Reply to: