Your message dated Sat, 30 Mar 2013 18:53:09 +0000 with message-id <20130330185309.GA14961@desktop> and subject line Re: Bug#669092: cups: Connection to server is not reestablished when using BrowsePoll and connection is interrupted has caused the Debian Bug report #669092, regarding cups: Connection to server is not reestablished when using BrowsePoll and connection is interrupted 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 [email protected] immediately.) -- 669092: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=669092 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: cups Version: 1.5.2-5 Severity: normal -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 When using BrowsePoll to discover printers on a defined remote server, CUPS uses a TCP connection, which is fine but may in some cases break. One scenario is a client going to sleep (in terms of ACPI). When it comes back up, the conenction has timed out on the server side and following attempts by the client to poll are answered with a connection reset by the server. The client CUPS daemon should now try to re-establish the connection, but doesn't. No new connection is ever made until cupsd is restarted. Originally reported at (German): https://debianforum.de/forum/viewtopic.php?f=31&t=135777 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (GNU/Linux) iQHOBAEBAgA4BQJPjS6KMRpodHRwczovL3d3dy5kb21pbmlrLWdlb3JnZS5kZS9n cGctcG9saWN5LnR4dC5hc2MACgkQ2w6kvOIQdBKHPQv/V/OYetrhF4klz4zW56+J 75v6/y2n58vUP6UKu2GDl35o7Hn0Ptdu5hKd1L9JSnMAAcoIoRs+bJ9zYsILZShn k4c/eWZ4YVSOiM72DXeJATW9xczUZtGeBeKh1Ojw6dDMTjpVuf1+T7ByhjKwhOqy HP2slkIubq0oK5OIWc+1WPU8cU1xlPqjL93M7Jm0A8YWOqooFwRPM++X7CJVKoPj VQExZWtSS9NJ8upUucisM7ekjrR6/zjqkaeVAc2XcscmRcsEpMkYxP1bqoz3BtpY TBPkuJ6ejP8UtzilvTXhdw/l6tFo9ZNJZaQWcbpHfAMckvfNK/aHJRY5BLZe4y3a KxNZqBVu8SEHUInQYJEXCN1UBUaukNkOZnERS/PXKwVEAjF3KXqhvdMowAkEsl/B SOIGKgeKkzvI/oXAHX2tJhYT0lxKlrPlgx1bltxs5kFpodM8H+XHzyvRsbCA3+pZ MN3JL6TMIpGV6hCeon84wUmgyBhsSqhYd4eFigoqvVxY =Jy4V -----END PGP SIGNATURE-----
--- End Message ---
--- Begin Message ---found 669092 1.5.2-5 fixed 669092 1.5.2-9 thanks Thank you for your report, Dominik. On Tue 17 Apr 2012 at 10:49:15 +0200, Dominik George wrote: > When using BrowsePoll to discover printers on a defined remote server, CUPS > uses a TCP connection, > which is fine but may in some cases break. > > One scenario is a client going to sleep (in terms of ACPI). When it comes > back up, the conenction > has timed out on the server side and following attempts by the client to poll > are answered with > a connection reset by the server. > > The client CUPS daemon should now try to re-establish the connection, but > doesn't. No new connection > is ever made until cupsd is restarted. >From changelog.Debian cups (1.5.2-9) unstable; urgency=low [ Till Kamppeter ] * debian/patches/cups-polld-reconnect.patch: The CUPS polling daemon did not reinitialize its connection to the remote server on errors in all cases The patch was removed in cups (1.5.3-1) because upstream had included it. I have tested suspending with pm-suspend on unstable and the bug does not appear, so I can only assume it really is fixed. Hence closing. Regards, Brian.
--- End Message ---
