nm-connection-editor crashed with SIGSEGV in glade_xml_get_widget()

[BlueT - Matthew Lien - 練喆明]

On a newly installed 9.10 beta, nm-applet doesn't work correctly with pppoe even after upgrading system.
I can setup a new setting in DSL tab, but dialup/connect always failed.
After sing pppoeconf to connect with Success, I try to edit DSL setting in nm-applet but keep showing error and ask for password. And Crashed when I try to delete the setting.

ProblemType: Crash
Architecture: amd64
CRDA: Error: [Errno 2] 沒有此一檔案或目錄
CrashCounter: 1
Date: Wed Oct 21 13:03:58 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/nm-connection-editor
IpRoute:
 118.170.192.254 dev ppp0 proto kernel scope link src 118.170.214.32
 192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1
 default dev ppp0 scope link
NonfreeKernelModules: nvidia
Package: network-manager-gnome 0.8~a~git.20091014t134532.4033e62-0ubuntu1
PciNetwork:

ProcCmdline: /usr/bin/nm-connection-editor
ProcEnviron:
 LANGUAGE=zh_TW.UTF-8
 LANG=zh_TW.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
RfKill:

SegvAnalysis:
 Segfault happened at: 0x7f1215342e8e <glade_xml_get_widget+14>: mov 0x20(%rdi),%rax
 PC (0x7f1215342e8e) ok
 source "0x20(%rdi)" (0x300000020) not located in a known VMA region (needed readable region)!
 destination "%rax" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: network-manager-applet
StacktraceTop:
 glade_xml_get_widget ()
 ?? ()
 g_closure_invoke ()
 ?? () from /usr/lib/libgobject-2.0.so.0
 g_signal_emit_valist ()
Title: nm-connection-editor crashed with SIGSEGV in glade_xml_get_widget()
Uname: Linux 2.6.31-14-generic x86_64
UserGroups: adm admin cdrom dialout libvirtd lpadmin plugdev sambashare

[Apport retracing service (apport)]

StacktraceTop:glade_xml_get_widget (self=0x300000000, name=0x44fdf6 "notebook")
page_initialized (page=0xbfe280,
g_closure_invoke ()
?? () from /usr/lib/libgobject-2.0.so.0
g_signal_emit_valist ()

[Timothy Arceri (t-fridey)]

Marking as invalid:

Looking at the report date this bug appears to have been reported against a development version of Ubuntu 9.10. Ubuntu 9.10 has since reached end of life and there have been no further reports on this bug.