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 1305060 - Test case failure: Install fonts automatically using PackageKit
Summary: Test case failure: Install fonts automatically using PackageKit
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: PackageKit
Version: 6.8
Hardware: Unspecified
OS: Linux
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Richard Hughes
QA Contact: Desktop QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-02-05 13:50 UTC by Ladislav Kolacek
Modified: 2017-12-06 11:38 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 11:38:20 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
GLASS.txt (9.91 KB, text/plain)
2016-02-05 13:50 UTC, Ladislav Kolacek
no flags Details

Description Ladislav Kolacek 2016-02-05 13:50:30 UTC
Created attachment 1121386 [details]
GLASS.txt

Description of problem:
Test case failure: https://tcms.engineering.redhat.com/case/515481/?from_plan=19769

Version-Release number of selected component (if applicable):
PackageKit-gtk-module-0.5.8-26.el6
kernel-2.6.32-604.el6
PackageKit-0.5.8-26.el6

How reproducible:
always

Steps to Reproduce:
1. Install PackageKit-gtk-module
2. Make sure that lohit fonts are not installed 
   yum remove lohit-*-fonts 
3. Download attached testing file (GLASS.txt).
4. Using gedit open attached file GLASS.txt

Actual results:
Nothing happened.

Expected results:
Packagekit should find missing fonts (in this case Hindi, Bengali, Tamil). These fonts should be propperly installed. And application should use them immediately (no restart needed).

Additional info:
Problem appeared on s390x and ppc64. I tested on VM.

Comment 2 Jan Kurik 2017-12-06 11:38:20 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.