Red Hat Bugzilla – Bug 220311
Printing in openoffice, evince causes application to hang.
Last modified: 2008-05-06 13:12:59 EDT
Description of problem:
Printing in openoffice, evince causes application to hang. This happens when I
have more than 227 printers (using CUPS). If I reduce the number of CUPS
printers to below 227, there is NO problem.
Version-Release number of selected component (if applicable): GA version for
How reproducible: every time
Steps to Reproduce:
1. In oowriter (or evince), go to file -> print
2. If we have more than 227 printers (I am using CUPS for printing), the
print dialog box comes up, but it is blank, and the whole application
hangs (freezes). The only way to proceed is to kill the application.
print dialog comes up but is blank and the whole application hangs.
I expect the print dialog to come up with all the printers listed in the
I have reported this bug to openoffice (as I noticed it in
openoffice initially), but on further investigation, it seems to happen in
evince as well. It seems to be a problem with the gtk2 print dialog (as both
these applications uses this for the printing dialog).
Created attachment 155118 [details]
Evince crash traces
I can confirm... It makes impossible to print anything with OOo or Evince. I do
not know whether others GTK applications are impacted but Gedit works without
any problems for instance.
A workaround for the "many printers lock up the cups backend" problem has been
included in 2.10.12, which I will build as an FC6 update once F7 is released.
Fedora apologizes that these issues have not been resolved yet. We're
sorry it's taken so long for your bug to be properly triaged and acted
on. We appreciate the time you took to report this issue and want to
make sure no important bugs slip through the cracks.
If you're currently running a version of Fedora Core between 1 and 6,
please note that Fedora no longer maintains these releases. We strongly
encourage you to upgrade to a current Fedora release. In order to
refocus our efforts as a project we are flagging all of the open bugs
for releases which are no longer maintained and closing them.
If this bug is still open against Fedora Core 1 through 6, thirty days
from now, it will be closed 'WONTFIX'. If you can reporduce this bug in
the latest Fedora version, please change to the respective version. If
you are unable to do this, please add a comment to this bug requesting
Thanks for your help, and we apologize again that we haven't handled
these issues to this point.
The process we are following is outlined here:
We will be following the process here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping to ensure this
doesn't happen again.
And if you'd like to join the bug triage team to help make things
better, check out http://fedoraproject.org/wiki/BugZappers
This bug is open for a Fedora version that is no longer maintained and
will not be fixed by Fedora. Therefore we are closing this bug.
If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen thus bug against that version.
Thank you for reporting this bug and we are sorry it could not be fixed.