Bug 1608320 - pyanaconda.modules.common.errors.DBusError: 'ascii' codec can't decode byte 0xc2 in position 12865: ordinal not in range(128)
Summary: pyanaconda.modules.common.errors.DBusError: 'ascii' codec can't decode byte 0...
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: 28
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Anaconda Maintenance Team
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-07-25 10:09 UTC by young.kim
Modified: 2018-07-25 10:13 UTC (History)
6 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2018-07-25 10:13:39 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)
The custom Fedora 28 ISO file (11.61 KB, text/plain)
2018-07-25 10:09 UTC, young.kim 		no flags Details
View All

Description young.kim 2018-07-25 10:09:02 UTC 
Created attachment 1470493 [details]
The custom Fedora 28 ISO file

Description of problem:
live image creation is failing with this traceback see "Actual results".

Version-Release number of selected component (if applicable):
anaconda 28.22.10-1.fc28

How reproducible:



Steps to Reproduce:
1. The custom Fedora 28 ISO file is generated with fedora-live-base.ks
2. My test ISO file is generated with 
3.

Actual results:


Expected results:


Additional info:
Comment 1 young.kim 2018-07-25 10:13:39 UTC 
(In reply to young.kim from comment #0)
> Created attachment 1470493 [details]
> The custom Fedora 28 ISO file
> 
> Description of problem:
> live image creation is failing with this traceback see "Actual results".
> 
> Version-Release number of selected component (if applicable):
> anaconda 28.22.10-1.fc28
> 
> How reproducible:
> 
> 
> 
> Steps to Reproduce:
> 1. The custom Fedora 28 ISO file is generated with fedora-live-base.ks
> 2. My test ISO file is generated with 
> 3.
> 
> Actual results:
> 
> 
> Expected results:
> 
> 
> Additional info:
Note You need to log in before you can comment on or make changes to this bug.