After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 508905 - gnome-print dialog in evince, eog etc hangs for all network printers that can be resolved but not connected to
gnome-print dialog in evince, eog etc hangs for all network printers that can...
Status: RESOLVED DUPLICATE of bug 424041
Product: gtk+
Classification: Platform
Component: Printing
2.12.x
Other All
: Normal critical
: ---
Assigned To: gtk-bugs
Depends on:
Blocks:
 
 
Reported: 2008-01-12 08:32 UTC by bugreports
Modified: 2009-04-13 00:15 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22



Description bugreports 2008-01-12 08:32:03 UTC
Steps to reproduce:
1. configure cups to use 2 network printers one that is in the local network (ping'able and will print just fine) and one that somewhere far away but neither ping able nor connectable however the name of that remote printer must be DNS resolvable.
2. open a gnome application and open the print dialog
3. in the gnome print dialog select the remote network printer

-> the whole application will hang


Stack trace:
$5 = (GSource *) 0x84f0200
(gdb) p timeout_
$6 = (gint *) 0xbf9c4ce8
(gdb) p *timeout_
$7 = -1
(gdb) p *source
$8 = {callback_data = 0x83da268, callback_funcs = 0xb75499a8, source_funcs = 0xb5944860, ref_count = 2, context = 0x8105018, priority = 0, flags = 1, source_id = 529, poll_fds = 0x0, prev = 0x83b4900, 
  next = 0x83b4608, reserved1 = 0x0, reserved2 = 0x0}

Interestingly the default was 5 seconds!

(gdb) p timeout
$11 = 5

Looking at the code

static gboolean
cups_dispatch_watch_prepare (GSource *source,
			     gint    *timeout_)
{
  GtkPrintCupsDispatchWatch *dispatch;

  dispatch = (GtkPrintCupsDispatchWatch *) source;

  GTK_NOTE (PRINTING,
            g_print ("CUPS Backend: %s <source %p>\n", G_STRFUNC, source));

  *timeout_ = -1;
  
  return gtk_cups_request_read_write (dispatch->request);
}

timeout is set to -1


So to me it seems setting it to 5 seconds or so should do it?
Comment 1 bugreports 2008-03-25 08:31:44 UTC
Setting a different timeout did not help, unfortunately. So the bug is somewhere deep down in the gnome printing system as other apps like eog etc also hang.

I can basically not print any longer using a gnome application - great :(
Comment 2 Nickolay V. Shmyrev 2008-11-13 21:32:07 UTC
The same as http://bugzilla.gnome.org/show_bug.cgi?id=424041 ?
Comment 3 bugreports 2008-11-23 05:22:33 UTC
yes same issue. gtk print dialog hangs when the server cannot be reached (and is potentially firewalled)
Comment 4 Till Kamppeter 2008-12-06 14:50:50 UTC
Also here is a complaint by a Ubuntu user

https://bugs.launchpad.net/ubuntu/+source/cups/+bug/276531

I can reproduce it as described here:

http://www.cups.org/str.php?L3033

Best would be if the polling of information from remote CUPS servers gets somehow improved in the CUPS library, but probably in any case also changes in the printing GUIs are needed.

For me http://bugzilla.gnome.org/show_bug.cgi?id=424041 seems to be really a duplicate of this.
Comment 5 Matthias Clasen 2008-12-07 17:41:20 UTC
What version of gtk are you using ?

2.14 tries to work around some of the cups issues (as this is mostly just cups making it very hard to avoid blocking)
Comment 6 Matthias Clasen 2009-04-13 00:15:16 UTC

*** This bug has been marked as a duplicate of 424041 ***