Bug 465220

Summary: system-config-network crashes on PS3
Product: [Fedora] Fedora Reporter: Kazunori Asayama <asayama>
Component: system-config-networkAssignee: Harald Hoyer <harald>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: medium    
Version: rawhideCC: dchapman, harald, jmoskovc, mclasen
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2008-10-25 03:47:05 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
error message by system-config-netwrok-cmd
none
tree /sys
none
Fix crash with getVendor() == None none

Description Kazunori Asayama 2008-10-02 09:03:56 UTC
Created attachment 319202 [details]
error message by system-config-netwrok-cmd

Description of problem:

The system-config-network crashes on PLAYSTATION 3 because of unhandled exception.

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

Fedora 10 (Beta, rawhide)
system-config-network-1.5.10-1.fc9.noarch.rpm
system-config-network-tui-1.5.10-1.fc9.noarch.rpm

How reproducible:

Every time.

Steps to Reproduce:
1. Run system-config-network-cmd on PS3.

  
Actual results:

The system-config-network crashes with unhandled exception. See the attached log.


Expected results:

The system-config-network starts correctly.


Additional info:

The system-config-network works on Mac G5 and x86 PC.

Comment 1 Kazunori Asayama 2008-10-02 09:06:35 UTC
Created attachment 319203 [details]
tree /sys

Comment 2 Kazunori Asayama 2008-10-24 12:43:54 UTC
Created attachment 321403 [details]
Fix crash with getVendor() == None

NCBackendHal.getDevices() doesn't seem to consider getVendor() may return 'None'. Attached patch should fix this problem.

Is there any chance to apply this fix to F10?

Comment 3 Doug Chapman 2008-10-24 19:30:56 UTC
I ran into this as well and the patch in comment #2 resolves the issue for me.  I second the request to get this into F10.

Comment 4 Matthias Clasen 2008-10-25 03:47:05 UTC

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