Bug 1440816

Summary:	Do not crash while leaving the panel during actualize_printers_list ()
Product:	Red Hat Enterprise Linux 7	Reporter:	Felipe Borges <feborges>
Component:	control-center	Assignee:	Felipe Borges <feborges>
Status:	CLOSED ERRATA	QA Contact:	Desktop QE <desktop-qa-list>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	7.4	CC:	mkasik, pgeorgie, tpelka
Target Milestone:	rc
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-08-01 22:38:29 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Felipe Borges 2017-04-10 14:19:28 UTC

Description of problem:
The Printers panel might crash while getting closed during the execution of the actualize_printers_list method.

This bug was filled initially against Fedora at https://bugzilla.redhat.com/show_bug.cgi?id=1432257

And it has been fixed upstream at https://bugzilla.gnome.org/show_bug.cgi?id=780299

Patch that applies to rhel-7.4 https://bug780299.bugzilla-attachments.gnome.org/attachment.cgi?id=349353

Comment 5 Pavlin Georgiev 2017-06-07 10:44:32 UTC

TEST SETUP
On VM running under RHEL 7.4 Workstation x86_64 with GNOME desktop environment.

Component version:
control-center-3.22.2-3.el7.x86_64

TEST PROCEDURE
1. Log in to GNOME session.
2. Edit CUPS config file: /etc/cups/client.conf
   Add a server which provokes a log waiting delay for printers:
    ServerName cups.nikhef.nl
3. Restart CUPS service.
4. Open control-center.
5. Open section "Printers". A long delay appears.
6. Close the window.

The bug does not appear. Control-center does not crash.

RESULTS
the bug does not exist in version:
    3.22.2-3.el7

Comment 7 errata-xmlrpc 2017-08-01 22:38:29 UTC

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://access.redhat.com/errata/RHBA-2017:2096