This one is weird: It was triggered by just wanting to right-click on the networking icon in the upper right corner and selecting Edit Connections

[Kalumba]

I'm running Karmic Beta and since upgrading network-manager has been impossible to configure. Another curious fact is that now there are 2 ethernet cards listed: eth0 and eth3. Configuration and deletion of either is not possible as both options are greyed out.

ProblemType: Crash
Architecture: i386
AssertionMessage: ERROR:nm-connection-editor.c:207:connection_editor_validate: assertion failed: (s_con)
CRDA: Error: [Errno 2] No such file or directory
Date: Mon Oct 19 16:44:08 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/nm-connection-editor
IpRoute:
 117.83.112.1 dev ppp0 proto kernel scope link src 117.83.122.101
 default dev ppp0 scope link
NonfreeKernelModules: nvidia
Package: network-manager-gnome 0.8~a~git.20091014t134532.4033e62-0ubuntu1
ProcCmdline: /usr/bin/nm-connection-editor
ProcEnviron:
 LANGUAGE=en_US.UTF-8
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
RfKill:
 0: phy0: Wireless LAN
  Soft blocked: no
  Hard blocked: no
Signal: 6
SourcePackage: network-manager-applet
StacktraceTop:
 __kernel_vsyscall ()
 raise () from /lib/tls/i686/cmov/libc.so.6
 abort () from /lib/tls/i686/cmov/libc.so.6
 g_assertion_message () from /lib/libglib-2.0.so.0
 g_assertion_message_expr () from /lib/libglib-2.0.so.0
Title: nm-connection-editor assert failure: ERROR:nm-connection-editor.c:207:connection_editor_validate: assertion failed: (s_con)
Uname: Linux 2.6.31-14-generic i686
UserGroups: adm admin audio cdrom dialout dip floppy fuse lpadmin plugdev video
WpaSupplicantLog:

[Apport retracing service (apport)]

Thank you for taking the time to report this crash and helping to make Ubuntu better. This particular crash has already been reported and is a duplicate of bug #445951, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.