Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 1596863 - Installation of font file causes fatal error and abortion of install. [NEEDINFO]
Summary: Installation of font file causes fatal error and abortion of install.
Status: NEW
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: 28
Hardware: x86_64
OS: Linux
Target Milestone: ---
Assignee: Anaconda Maintenance Team
QA Contact: Fedora Extras Quality Assurance
Depends On:
TreeView+ depends on / blocked
Reported: 2018-06-29 20:11 UTC by Hprgvnv.nvus1
Modified: 2018-07-02 07:43 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed:
jkonecny: needinfo? (Hprgvnv.nvus1)

Attachments (Terms of Use)

Description Hprgvnv.nvus1 2018-06-29 20:11:46 UTC
Description of problem: Installation of Fedora 28 to laptop computer using  Fedora-Workstation-netinst-x86_64-28-1.1.iso file from Fedora Download website. Burned iso image to Dvd. Restarted system and system began downloading components for install (Software Catalog). Once Software catalog downloading was completed, I chose my drives and began the installing of the 1501 files recommended by Anaconda installer. The install went fine up to the point when the following error message appeared, at file (1440/1501) - "The following error occurred while installing. This is a fatal error and installation will be aborted. DNF error: Error unpacking rpm package dejavu-sans-fonts-2.35-6.fc28.noarch" Once error occurred system no longer responded, lost all mouse and keyboard use. Had to do a hard power shutdown.

Version-Release number of selected component (if applicable):2.35-6.fc28.noarch

How reproducible: Not reproducible by me.

Steps to Reproduce:

Actual results:

Expected results:

Additional info:

Comment 1 Jiri Konecny 2018-07-02 07:43:13 UTC

You have specified that you are not able to reproduce this. Does it mean that this happened just once and the installation went fine for the second run?

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