nm-connection-editor assert failure: ERROR:nm-connection-editor.c:207:connection_editor_validate: assertion failed: (s_con)
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
network-manager-applet (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
every time I call the nm-connection manager and try to edit my vodafone websession entry (ppp, 3g), I get this error: Failure while initialising the editor: Insufficiient user rights (I typed in the right super user password) or System policy prevents modifying the system configuration (then I cannot cancel or legitimate the action, even I typed in the correct password, the widget then does not take any action...just can close by the close button). I can repeat this and finally get into the configuration editor, but then passwords are missing for example and cannot be changed permanently...
In user rights I set membership to all groups possible...
Package: libnm-0.
ProblemType: Crash
Architecture: i386
AssertionMessage: ERROR:nm-
CRDA: Error: [Errno 2] No such file or directory
CrashCounter: 1
Date: Mon Oct 19 10:25:24 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/
Gconf:
IfupdownConfig:
auto lo
iface lo inet loopback
IpRoute:
10.64.64.64 dev ppp0 proto kernel scope link src 10.230.97.154
169.254.0.0/16 dev ppp0 scope link metric 1000
default via 10.64.64.64 dev ppp0 proto static
NonfreeKernelMo
Package: network-
ProcCmdline: /usr/bin/
ProcEnviron:
LANG=de_DE.UTF-8
SHELL=/bin/bash
ProcVersionSign
Signal: 6
SourcePackage: network-
StacktraceTop:
__kernel_vsyscall ()
raise () from /lib/tls/
abort () from /lib/tls/
g_assertion_
g_assertion_
Title: nm-connection-
Uname: Linux 2.6.31-14-generic i686
UserGroups: adm admin audio cdrom dialout dip fax fuse lpadmin netdev plugdev sambashare tape video
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.