Comment 6 for bug 21993

Thank you for working on this bug report, I appreciate it. I have been
testing my printserver again, running
Dapper on both server and client:

Scenario 1:
1. Added line "ServerName <IP to printserver>" into client.conf of the
non-server PC.
2. Try to print a page from Firefox without blocking port 631 on server.
Result: OK.
3. Port 631 of printserver blocked.
4. Starts sudo gnome-cups-manager in terminal. Result: Nothing starts. Error
message after about
   5-10 minutes: ** (gnome-printer-view:16910): WARNING **: IPP request
failed with status 1280
5. Try to print a page from openoffice.org 2.0.2. Result: Openoffice.org
2.0.2 crashes. Need to "force quit".
6. Try to print a page from Firefox 1.5.0.3. Result: Firefox
1.5.0.3crashes. Need to "force quit".

Comment: Basically the same result as last time with breezy. On the other
hand, I do not need to add "servername ipadress" to client.conf anymore, so
it is not an issue for me now. Looks like the Cups version of Ubuntu Dapper
detects network printers more easily.

Scenario 2:
1. Did not add anything to client.conf. Just started gnome-cups-manager.
Detected the LAN-printer automatically.
2. Print a page from Firefox and Openoffice.org without firewall blocking
port 631 on the server. Result: OK.
3. Print a page from Firefox and Openoffice.org when firewall blocking port
631 on the server. Result: No crash of Firefox and Openoffice.org. No error
message within 15 minutes, even if it failed to print.

Comment: It does not seem to crash Firefox and Openoffice.org when I did not
edit the client.conf by myself. On the
other hand it should, in a perfect world, have returned an error message.

On 10/05/06, Martin Pitt <email address hidden> wrote:
>
> Do you still have this problem in current dapper?
>
> --
> When Print-server not found on network, cups-manager crashes
> https://launchpad.net/bugs/21993
>