2006-04-14 19:44:05 |
Matthias Klose |
gnome-cups-manager: status |
Confirmed |
Needs Info |
|
2006-04-14 19:44:05 |
Matthias Klose |
gnome-cups-manager: statusexplanation |
Bugzilla status=ASSIGNED, product=Ubuntu, component=gnome-cups-manager |
1.2 rc2 packages available, needs testing
https://lists.ubuntu.com/archives/ubuntu-devel/2006-April/017211.html
|
|
2006-08-09 14:22:37 |
Martin Pitt |
gnome-cups-manager: status |
Needs Info |
Unconfirmed |
|
2006-08-09 14:22:37 |
Martin Pitt |
gnome-cups-manager: statusexplanation |
1.2 rc2 packages available, needs testing
https://lists.ubuntu.com/archives/ubuntu-devel/2006-April/017211.html
|
|
|
2006-12-22 15:56:17 |
Daniel Holbach |
gnome-cups-manager: status |
Unconfirmed |
Confirmed |
|
2007-04-26 15:57:34 |
yosefrow |
description |
I configured my network with shared printing. I found out that I had not opened
the right ports on my print server, but the real problem was that cups-manager
hanged and even crashed Firefox when I tried to print a page when the firewall
on the print server blocked the attempt to print from my computer (found out
later). When I opened the right port (631), it all worked fine. I followed this
guide when i configured shared network printing: http://occy.net/printing. |
When the CUPS system is not able to access port 631 of the client machine, programs dependent on CUPS (ie. cups manager, firefox print dialog) become unresponsive and or crash.
Steps to reproduce:
configured your network with shared printing.
Tips on doing that can be found here: http://occy.net/printing.
Edit your client machine's client.conf file to include the address/name of your Print Server
close the 631 port on your server machine.
Open the cups-manager on your client machine
Observe that cups-manager crashes
Attempt to print a page from Firefox from your client machine
Observe that Firefox hangs and or crashes
|
|
2007-04-26 15:59:28 |
yosefrow |
description |
When the CUPS system is not able to access port 631 of the client machine, programs dependent on CUPS (ie. cups manager, firefox print dialog) become unresponsive and or crash.
Steps to reproduce:
configured your network with shared printing.
Tips on doing that can be found here: http://occy.net/printing.
Edit your client machine's client.conf file to include the address/name of your Print Server
close the 631 port on your server machine.
Open the cups-manager on your client machine
Observe that cups-manager crashes
Attempt to print a page from Firefox from your client machine
Observe that Firefox hangs and or crashes
|
When a CUPS client system is not able to access port 631 of the server machine listed in client.conf, programs dependent on CUPS such as cups manager and firefox print dialog) become unresponsive and or crash.
Steps to reproduce:
configured your network with shared printing.
Tips on doing that can be found here: http://occy.net/printing.
Edit your client machine's client.conf file to include the address/name of your Print Server
close the 631 port on your server machine.
Open the cups-manager on your client machine
Observe that cups-manager crashes
Attempt to print a page from Firefox from your client machine
Observe that Firefox hangs and or crashes
|
|
2007-04-26 16:00:25 |
yosefrow |
description |
When a CUPS client system is not able to access port 631 of the server machine listed in client.conf, programs dependent on CUPS such as cups manager and firefox print dialog) become unresponsive and or crash.
Steps to reproduce:
configured your network with shared printing.
Tips on doing that can be found here: http://occy.net/printing.
Edit your client machine's client.conf file to include the address/name of your Print Server
close the 631 port on your server machine.
Open the cups-manager on your client machine
Observe that cups-manager crashes
Attempt to print a page from Firefox from your client machine
Observe that Firefox hangs and or crashes
|
When a CUPS client system is not able to access port 631 of the server machine listed in client.conf, programs dependent on CUPS such as cups manager and firefox print dialog, become unresponsive and or crash.
Steps to reproduce:
configured your network with shared printing.
Instructions on setting up shared printing can be found here: http://occy.net/printing.
Edit your client machine's client.conf file to include the address/name of your Print Server
close the 631 port on your server machine.
Open the cups-manager on your client machine
Observe that cups-manager crashes
Attempt to print a page from Firefox from your client machine
Observe that Firefox hangs and or crashes
|
|
2007-04-26 16:02:03 |
yosefrow |
description |
When a CUPS client system is not able to access port 631 of the server machine listed in client.conf, programs dependent on CUPS such as cups manager and firefox print dialog, become unresponsive and or crash.
Steps to reproduce:
configured your network with shared printing.
Instructions on setting up shared printing can be found here: http://occy.net/printing.
Edit your client machine's client.conf file to include the address/name of your Print Server
close the 631 port on your server machine.
Open the cups-manager on your client machine
Observe that cups-manager crashes
Attempt to print a page from Firefox from your client machine
Observe that Firefox hangs and or crashes
|
When a CUPS client system is not able to access port 631 of the server machine listed in client.conf, programs on the client machine, which dependent on CUPS such as cups manager and firefox print dialog, become unresponsive and crash.
Steps to reproduce:
configured your network with shared printing.
Instructions on setting up shared printing can be found here: http://occy.net/printing.
Edit your client machine's client.conf file to include the address/name of your Print Server
close the 631 port on your server machine.
Open the cups-manager on your client machine
Observe that cups-manager crashes
Attempt to print a page from Firefox from your client machine
Observe that Firefox hangs and or crashes
|
|
2007-04-26 16:02:53 |
yosefrow |
description |
When a CUPS client system is not able to access port 631 of the server machine listed in client.conf, programs on the client machine, which dependent on CUPS such as cups manager and firefox print dialog, become unresponsive and crash.
Steps to reproduce:
configured your network with shared printing.
Instructions on setting up shared printing can be found here: http://occy.net/printing.
Edit your client machine's client.conf file to include the address/name of your Print Server
close the 631 port on your server machine.
Open the cups-manager on your client machine
Observe that cups-manager crashes
Attempt to print a page from Firefox from your client machine
Observe that Firefox hangs and or crashes
|
When a CUPS client system is not able to access port 631 of the server machine listed in client.conf, programs on the client machine, which are dependent on CUPS such as gnome-cups-manager and firefox print dialog, become unresponsive and crash.
Steps to reproduce:
configured your network with shared printing.
Instructions on setting up shared printing can be found here: http://occy.net/printing.
Edit your client machine's client.conf file to include the address/name of your Print Server
close the 631 port on your server machine.
Open the cups-manager on your client machine
Observe that cups-manager crashes
Attempt to print a page from Firefox from your client machine
Observe that Firefox hangs and or crashes
|
|
2007-07-16 11:09:28 |
Martin Pitt |
gnome-cups-manager: assignee |
pitti |
|
|
2007-12-18 16:42:15 |
Henrik Nilsen Omma |
gnome-cups-manager: status |
Confirmed |
Won't Fix |
|