Bug 203874 - loader gets SIGSEGV while setting up wireless networking
Summary: loader gets SIGSEGV while setting up wireless networking
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda   
(Show other bugs)
Version: 6
Hardware: powerpc
OS: Linux
Target Milestone: ---
Assignee: David Cantrell
QA Contact: Mike McLean
Depends On:
TreeView+ depends on / blocked
Reported: 2006-08-24 06:15 UTC by Dave Vasilevsky
Modified: 2007-11-30 22:11 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2006-08-25 02:44:54 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

Description Dave Vasilevsky 2006-08-24 06:15:35 UTC
Description of problem:
During installation, 'loader' asks for the ESSID and WEP password for my
wireless network. When I give an answer, loader receives a SIGSEGV and
installation is aborted.

How reproducible: Always

Steps to Reproduce:
1.Boot FC6test2 boot.iso CD.
2.Proceed through yaboot, and language selection.
3. When asked for installation method, choose HTTP.
4. When asked which network interface to configure, choose eth1 for my Airport card.
5. When asked for ESSID and WEP key, enter actual ESSID--no key is used as
network is open.

Actual results:
'loader' crashes, with text:

loader recieved SIGSEGV! Backtrace:
install exited abnormally ...

System then reboots.

Expected results:
Installer detects network, proceeds to DHCP vs. static.

Additional info:
- Crash occurs regardless of ESSID given.
- I also experience bug 186601, no idea if it's relevant.
- My hardware is a Mac G4/733 Quicksilver:

 with Apple Airport card and 896 MB RAM.

Comment 1 Dave Vasilevsky 2006-08-25 01:03:51 UTC
I tried out Rawhide, and this bug does not appear in Rawhide for 24 Aug 2006.

Comment 2 David Cantrell 2006-08-25 02:44:54 UTC
Great, thanks for testing that out.

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