Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
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.

Bug 1559431

Summary: system-config-printer freezes on 'Find Network Printer' [rhel-7.9.z]
Product: Red Hat Enterprise Linux 7 Reporter: Piyush Bhoot <pbhoot>
Component: control-centerAssignee: Marek Kašík <mkasik>
Status: CLOSED ERRATA QA Contact: Desktop QE <desktop-qa-list>
Severity: high Docs Contact:
Priority: unspecified    
Version: 7.4CC: cgarnach, jraising, jreznik, jwright, mboisver, mkasik, modehnal, pbhoot, pzhukov, sbarcomb, tpelka, tpopela, zdohnal
Target Milestone: rcKeywords: OtherQA, Reopened, Triaged, ZStream
Target Release: ---Flags: tpopela: mirror+
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: control-center-3.28.1-8.el7_9 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2021-04-27 11:31:59 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:
Bug Depends On:    
Bug Blocks: 1630905, 1709724, 1757052, 1780662    
Attachments:
Description Flags
output of system-config-printer --debug &
none
new strace
none
gcore at the time of issue none

Description Piyush Bhoot 2018-03-22 14:28:06 UTC
Description of problem:
system-config-printer freezes on 'Find Network Printer'


Version-Release number of selected component (if applicable):
cups-1.6.3-29.el7.x86_64
system-config-printer-1.4.1-19.el7.x86_64
gnome-shell-3.22.3-17.el7.x86_64

How reproducible:
deterministic

Steps to Reproduce:
1. Take X11 forwarded session to latest rhel7.4
2. start cups
3. start system-config-printer
4. Network printer > Find Network printer > click 'find'

Actual results:
it freezes, gui doesn't respond

Expected results:
I can add network printer

Additional info:
Issue happens only on ssh forwarded session

Comment 2 Piyush Bhoot 2018-03-23 06:31:32 UTC
I missed mention of libtdb, issue reproduceable with latst libtdb-1.3.12-2.el7

Comment 7 Piyush Bhoot 2018-03-23 10:13:13 UTC
Created attachment 1412036 [details]
output of system-config-printer --debug &

Comment 38 Joe Wright 2019-11-26 13:42:25 UTC
Created attachment 1639805 [details]
new strace

 After selecting the 'Add Network Printer' line and the triangle turning, I left it sitting for ~30-45 seconds (I think) before cancelling out.

Comment 39 Piyush Bhoot 2019-12-19 16:22:12 UTC
Created attachment 1646586 [details]
gcore at the time of issue

Comment 63 Chris Williams 2020-11-11 21:56:55 UTC
Red Hat Enterprise Linux 7 shipped it's final minor release on September 29th, 2020. 7.9 was the last minor releases scheduled for RHEL 7.
From intial triage it does not appear the remaining Bugzillas meet the inclusion criteria for Maintenance Phase 2 and will now be closed. 

From the RHEL life cycle page:
https://access.redhat.com/support/policy/updates/errata#Maintenance_Support_2_Phase
"During Maintenance Support 2 Phase for Red Hat Enterprise Linux version 7,Red Hat defined Critical and Important impact Security Advisories (RHSAs) and selected (at Red Hat discretion) Urgent Priority Bug Fix Advisories (RHBAs) may be released as they become available."

If this BZ was closed in error and meets the above criteria please re-open it flag for 7.9.z, provide suitable business and technical justifications, and follow the process for Accelerated Fixes:
https://source.redhat.com/groups/public/pnt-cxno/pnt_customer_experience_and_operations_wiki/support_delivery_accelerated_fix_release_handbook  

Feature Requests can re-opened and moved to RHEL 8 if the desired functionality is not already present in the product. 

Please reach out to the applicable Product Experience Engineer[0] if you have any questions or concerns.  

[0] https://bugzilla.redhat.com/page.cgi?id=agile_component_mapping.html&product=Red+Hat+Enterprise+Linux+7

Comment 64 Chris Williams 2020-11-11 23:18:27 UTC
Apologies for the inadvertent closure.

Comment 82 Michael Boisvert 2021-03-19 12:57:16 UTC
Jigar, any news from the customer?

Comment 96 errata-xmlrpc 2021-04-27 11:31:59 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 (control-center bug fix update), 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-2021:1387

Comment 97 Red Hat Bugzilla 2023-09-15 00:07:04 UTC
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 500 days