nm-connection-editor assert failure: ERROR:nm-connection-editor.c:207:connection_editor_validate: assertion failed: (s_con)

[Syed S. Rahman]

Error while trying to edit connections. Also, can't connect with my 3G usb anymore using nm-applet. wvdial works fine.

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
CheckboxSubmission: eb703f512fa55f5fd2edd40195cd36a8
CheckboxSystem: 0ad41cb8883434b5c220c4fac21bbf74
CrashCounter: 1
Date: Wed Nov 4 14:59:47 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/nm-connection-editor
IfupdownConfig:
 auto lo
 iface lo inet loopback
InterestingModules: b44
IpRoute:
 192.168.1.0/24 dev wlan0 proto kernel scope link src 192.168.1.12 metric 2
 169.254.0.0/16 dev wlan0 scope link metric 1000
 default via 192.168.1.1 dev wlan0 proto static
Package: network-manager-gnome 0.8~a~git.20091014t134532.4033e62-0ubuntu1
ProcCmdline: /usr/bin/nm-connection-editor
ProcEnviron:
 LANGUAGE=en_IN.UTF-8
 LANG=en_IN.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
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
Tags: driver-b44
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 cdrom dialout lpadmin plugdev sambashare
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.