Bug 1221157 – CUPS backend checks wrong port for remote printers

Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.

Bug 1221157 - CUPS backend checks wrong port for remote printers

Summary:	CUPS backend checks wrong port for remote printers

Status:	CLOSED ERRATA

Aliases:	None

Product:	Red Hat Enterprise Linux 7
Classification:	Red Hat
Component:	gtk3 (Show other bugs)
Sub Component:
Version:	7.2
Hardware:	Unspecified Unspecified

Priority	unspecified Severity unspecified
Target Milestone:	rc
Target Release:	---
Assigned To:	Marek Kašík
QA Contact:	Desktop QE
Docs Contact:	Jana Heves

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2015-05-13 07:48 EDT by Marek Kašík
Modified:	2015-11-19 03:18 EST (History)
CC List:	3 users (show)

See Also:
Fixed In Version:	gtk3-3.14.13-7.el7
Doc Type:	Bug Fix
Doc Text:	Previously, the CUPS backend checked incorrect port to connect to remote printers. Consequently, getting printer information failed and the "Print" button became insensitive. A patch has been provided to fix this bug, making sure CUPS checks the correct port. As a result, the "Printers" dialog displays the information and the "Print" button is sensitive as expected
Story Points:	---
Clone Of:
Environment:
Last Closed:	2015-11-19 03:18:22 EST
Type:	Bug
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

External Trackers
Tracker	ID	Priority	Status	Summary	Last Updated
GNOME Bugzilla	693738	None	None	None	Never
Red Hat Product Errata	RHBA-2015:2116	normal	SHIPPED_LIVE	GTK+ bug fix and enhancement update	2015-11-19 03:39:32 EST

Groups: None (edit)

Description Marek Kašík 2015-05-13 07:48:48 EDT

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)

Comment 2 Vitezslav Humpa 2015-08-13 10:07:01 EDT

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.

Comment 3 Vitezslav Humpa 2015-08-14 05:10:18 EDT

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.

Comment 4 errata-xmlrpc 2015-11-19 03:18:22 EST

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

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