Bug 794918 - cups printers don't show up in gtk apps, e.g. firefox & seamonkey (mozilla builds), evince, gimp
Summary: cups printers don't show up in gtk apps, e.g. firefox & seamonkey (mozilla bu...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: gtk2
Version: 6.2
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: rc
: ---
Assignee: Benjamin Otte
QA Contact: Desktop QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-02-17 22:20 UTC by csb sysadmin
Modified: 2017-12-06 12:16 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-12-06 12:16:19 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description csb sysadmin 2012-02-17 22:20:22 UTC
Description of problem:

CUPS printers which show up in the output of "lpstat -a" and which work with lp and lpr commands, and which also show up in the print dialogs in Adobe Acrobat, Openoffice, and LibreOffice, don't show up in GTK print dialogs in apps such as firefox & seamonkey (mozilla builds but probably also RHEL builds), evince, and gimp.

Version-Release number of selected component (if applicable):

CentOS release 6.2 (Final)

% rpm -qa | grep ^gtk
gtk2-engines-2.18.4-5.el6.centos.i686
gtk2-devel-2.18.9-6.el6.centos.x86_64
gtkspell-2.0.16-1.el6.x86_64
gtksourceview2-2.8.2-4.el6.x86_64
gtkhtml3-3.28.3-3.el6.x86_64
gtk2-engines-devel-2.18.4-5.el6.centos.x86_64
gtk2-engines-2.18.4-5.el6.centos.x86_64
gtk2-2.18.9-6.el6.centos.i686
gtk2-immodule-xim-2.18.9-6.el6.centos.x86_64
gtk2-2.18.9-6.el6.centos.x86_64
gtkmm24-2.18.2-1.el6.x86_64
gtk-doc-1.11-5.1.el6.noarch
gtk2-devel-docs-2.18.9-6.el6.centos.x86_64
gtk2-engines-devel-2.18.4-5.el6.centos.i686

How reproducible:

Everytime

Steps to Reproduce:
1. Make sure you have some printers installed via the cups http://localhost:631 interface and that these show up via "lpstat -a".
2. Open up evince, go to the print dialog, no printers available

Actual results:

No printers shown

Expected results:

Show all printers also available through cups and in the output of "lpstat -a"

Additional info:

Works fine under centos 5.

Comment 2 csb sysadmin 2012-03-26 22:19:20 UTC
Well, looks like we probably copied cupsd.conf from a centos5 system, and even though the printers showed up in lpstat and worked fine with the lp commands, they wouldn't show up in gtk apps. We copied the default cupsd.conf from a fresh centos6 install and the printers now show up without problems.

Comment 3 RHEL Program Management 2012-05-03 05:40:13 UTC
Since RHEL 6.3 External Beta has begun, and this bug remains
unresolved, it has been rejected as it is not proposed as
exception or blocker.

Red Hat invites you to ask your support representative to
propose this request, if appropriate and relevant, in the
next release of Red Hat Enterprise Linux.

Comment 6 RHEL Program Management 2013-10-14 05:06:35 UTC
This request was not resolved in time for the current release.
Red Hat invites you to ask your support representative to
propose this request, if still desired, for consideration in
the next release of Red Hat Enterprise Linux.

Comment 7 Jan Kurik 2017-12-06 12:16:19 UTC
Red Hat Enterprise Linux 6 is in the Production 3 Phase. During the Production 3 Phase, Critical impact Security Advisories (RHSAs) and selected Urgent Priority Bug Fix Advisories (RHBAs) may be released as they become available.

The official life cycle policy can be reviewed here:

http://redhat.com/rhel/lifecycle

This issue does not meet the inclusion criteria for the Production 3 Phase and will be marked as CLOSED/WONTFIX. If this remains a critical requirement, please contact Red Hat Customer Support to request a re-evaluation of the issue, citing a clear business justification. Note that a strong business justification will be required for re-evaluation. Red Hat Customer Support can be contacted via the Red Hat Customer Portal at the following URL:

https://access.redhat.com/


Note You need to log in before you can comment on or make changes to this bug.