Bug 495984 - nm-system-settings: update: assertion 'context != NULL' failed
Summary: nm-system-settings: update: assertion 'context != NULL' failed
Keywords:
Status: CLOSED DUPLICATE of bug 495884
Alias: None
Product: Fedora
Classification: Fedora
Component: NetworkManager
Version: rawhide
Hardware: powerpc
OS: Linux
medium
high
Target Milestone: ---
Assignee: Dan Williams
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-04-15 20:20 UTC by Geoff Levand
Modified: 2009-04-16 16:35 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2009-04-16 16:35:48 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
screen shot (421.00 KB, image/jpeg)
2009-04-15 22:13 UTC, Geoff Levand 		no flags Details
View All

Description Geoff Levand 2009-04-15 20:20:08 UTC 
Description of problem:

Anaconda startup fails with 'there was an error configuring your network interface".

Last system message seen is:
nm-system-settings: update: assertion 'context != NULL' failed

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

Todays build (15-Apr-2009 06:22)

sha1sum ppc/os/ppc/ppc64/{ramdisk.image.gz,vmlinuz}
669767e3c3b0831a347f54f098cb096bce5cb54a  ppc/os/ppc/ppc64/ramdisk.image.gz
1f89181aa261a4be7d18ab9e0772304cea6299c6  ppc/os/ppc/ppc64/vmlinuz

This worked OK yesterday.

How reproducible:

always, 100%

Additional info:

Tested on PS3 game console and Mac G5, 'text' and 'graphical' installs.

Couldn't get a dump.

-Geoff
Comment 1 Geoff Levand 2009-04-15 22:13:42 UTC 
Created attachment 339753 [details]
screen shot
Comment 2 Joe Orton 2009-04-16 07:34:35 UTC 
I'm seing the same on a x86_64 kickstart, only a wired r8169 ethernet device present - last message logged is the

  "device state change 2 -> 3"

kickstart was working fine, modulo anaconda borkage, in the previous day's spin.
Comment 3 Geoff Levand 2009-04-16 16:35:48 UTC 

*** This bug has been marked as a duplicate of bug 495884 ***
Note You need to log in before you can comment on or make changes to this bug.