RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Description of problem:
When CUPS backend checks connection to remote CUPS server, it calls ippPort() to get port to which it tries to connect. This is wrong since the remote server can have different port from the one defined locally.
This is similar problem to the one from the bug #909454 but it needs to have cups-browsed service active to cause a problem because browsing subsystem has changed since then (it uses DNSSD now).


Steps to Reproduce:
1. set sharing of printers on a remote server (RHEL6 preferably because it uses CUPS protocol for browsing) and use a non-standard port number
2. point your local /etc/cups/cup-browsed.conf to the server via BrowsePoll (the name of the remote CUPS server has to be resolvable)
3. try to select a printer from the server in gtk print dialog


Actual results:
"Getting printer information failed" and the 'Print' button is insensitive.


Expected results:
The dialog gets the information and the 'Print' button is sensitive.


Additional info:
possible duplicate is #1154038 (has to be confirmed yet)

Finally managed to setup a proper configuration for this issue internally and got a remote (port 63101) printer discovered via cups-browsed using the cups protocol. Printer is visible in local GTK3 print dialogs, information is available and Print button available. The issue appears to be fixed for GTK3 too.

With my setup, got issue reproduced on the older version of GTK3 and all is okay after update to gtk3-3.14.13-13.el7.x86_64. Verified.

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHBA-2015-2116.html