Bug#543468: comment client.conf out if you're not using it
On 2009-09-05, at 07:19, Martin-Éric Racine wrote: I notice that several people reporting this bug have an /etc/cups/client.conf pointing to some bogus remote host. Please comment this out and see if it fixes it. I can't speak for the others, but mine actually points to a non-bogus host. I redacted the name to avoid exposing internal company network info. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#543468: comment client.conf out if you're not using it
On Sep 5, 2009, at 8:59, Martin-Éric Racine q-f...@iki.fi wrote: That's an interesting case. Are connecting only to remote printers or also to local printers? Only remote. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#543468: RIPCache
This happens to me, too, and I don't have a ~/.cups/client.conf . (I do, however, have ServerName printserver.company.invalid in the system-wide /etc/cups/client.conf .) I did ps axf while it was hung prompting for the password, and the command doing the prompting was: cupsctl RIPCache=3083788k As a workaround, I commented out the call to set_ripcache in the initscript. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
