Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 444267 - Starting network in rescue mode aborts operation
Starting network in rescue mode aborts operation
Status: CLOSED DUPLICATE of bug 432162
Product: Fedora
Classification: Fedora
Component: anaconda (Show other bugs)
All Linux
low Severity high
: ---
: ---
Assigned To: Jeremy Katz
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2008-04-26 05:31 EDT by Johnny Ljunggren
Modified: 2008-06-02 13:02 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2008-06-02 13:02:05 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Johnny Ljunggren 2008-04-26 05:31:41 EDT
Description of problem:
I installed Fedora 9 preview and booted in rescue mode to change grub.conf. I
answered yes to start network but it fails and reboot is the only option.

Version-Release number of selected component (if applicable):

How reproducible:
Every time

Steps to Reproduce:
1. Boot in rescue mode with Fedora 9 preview
2. Answer yes to start network
Actual results:
Rescue mode aborts

Expected results:
Network is started and rescue mode continues

Additional info:
This is done on an IBM Thinkpad Z60m
Comment 1 Jeremy Katz 2008-04-28 22:56:09 EDT
How did it fail?
Comment 2 Johnny Ljunggren 2008-05-05 17:19:25 EDT
Sorry for the incomplete info and late reply. Here goes:
Anaconda stops instantly after selecting yes to start network.
This is the output:
../textw/network_text.py 615
  dev = self.chooseNetworkDevice(screen)
../textw/network_text.py 511
  UnicodeDecodeError='ascii' codec can't decode byte 0xc3 in position 4: ordinal
not in range (128)

And also, I selected norwegian language and keyboard before the network selection.
Comment 3 Bug Zapper 2008-05-14 06:12:13 EDT
Changing version to '9' as part of upcoming Fedora 9 GA.
More information and reason for this action is here:
Comment 4 Jeremy Katz 2008-05-29 16:27:04 EDT
I can't reproduce this with Fedora 9 and I believe that this would have had the
same root cause as bug 443040.  Are you still seeing this with Fedora 9 final?
Comment 5 Andy Lindeberg 2008-06-02 13:02:05 EDT

*** This bug has been marked as a duplicate of 432162 ***

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