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

Bug#1017973: cups-browsed: Unable to print after resume from suspend



tags 1017973 upstream
thanks




On Tue 23 Aug 2022 at 19:14:46 +0930, Josh Heidenreich wrote:

> Package: cups-browsed
> Version: 1.28.7-1+deb11u1
> Severity: important
> X-Debbugs-Cc: josh.sickmate@gmail.com

Thank you for your report, Josh

> Dear Maintainer,
>
> When resuming from suspend (such as re-opening the lid of my laptop), printing
> over the network no longer works. I receive the following error:
> 
>     No destination host name supplied by cups-browsed for printer "name",
>     is cups-browsed running?

This is a message that crops up in other bug reports but not necessarily
involving suspend. See

 https://github.com/OpenPrinting/cups-filters/issues/97

> Restarting the service (i.e. sudo service cups-browsed restart) resolves the
> issue and printing then works. Attempting other fixes does not work; I've
> tried starting and stopping the printer within the CUPS web interface for
> example.
> 
> Note that my device needs to re-connect network after a resume. I of course
> wait for this to finish before attempting printing.
> 
> The printer devices do show up within applications. I don't have any printers
> "installed" as such, only using auto-detection. I regurally switch networks
> between home and office. Device is a Dell XPS 13 model 9370.

Which application? You could try purging (or stopping) cups-browse. The
printers should still show up, even after resuming from suspend.
 
> I've examined the debian changelog an did not see any notable package changes
> between 'stable' and 'unstable' versions of this package.
> 
> I have also examined the upstream changes for each of the versions, and have
> found one possible fix, released in v1.28.9:
> 
>     https://github.com/OpenPrinting/cups-filters/pull/360
>     "utils/cups-browsed.service: Add network-online.target"
> 
> This change alters the SystemD configuration to depend on the network being
> online.

AFAICT, #360 involves the legacy CUPS protocol, which I doubt very much
you are using.
 
> I've logged this bug report as I consider both printing and suspend/resume
> to be important features. Futhermore, new users would consider printing to
> be "broken" if they had closed the lid of their laptop even a single time
> prior to printing.

TBH, I think your best course of action is to take this upstream.

 https://github.com/OpenPrinting/cups-filters/issues

Regards,

Brian.


Reply to: