NetworkManager connection editor crashed with add_done_cb: code should not be reached

[trbs]

Binary package hint: network-manager

The NetworkManager Connection-Editor crashes with the error below when trying to add a wired connection but then pressing cancel in the new-connection editing window.

Console messages:
{{{
$ nm-connection-editor

(nm-connection-editor:4696): GLib-CRITICAL **: g_hash_table_foreach: assertion `hash_table != NULL' failed

** (nm-connection-editor:4696): WARNING **: nm_connection_list_new: failed to load VPN plugins: Couldn't read VPN .name files directory /etc/NetworkManager/VPN.
**
ERROR:nm-connection-list.c:787:add_done_cb: code should not be reached
Aborted
}}}

Distributor ID: Ubuntu
Description: Ubuntu 9.04
Release: 9.04
Codename: jaunty

ii network-manager 0.7.1~rc4.1.cf199a964-0ubuntu2 network management framework daemon
ii network-manager-gnome 0.7.1~rc4.1-0ubuntu2 network management framework (GNOME frontend)

network-manager:
  Installed: 0.7.1~rc4.1.cf199a964-0ubuntu2
  Candidate: 0.7.1~rc4.1.cf199a964-0ubuntu2
  Version table:
 *** 0.7.1~rc4.1.cf199a964-0ubuntu2 0
        500 http://ftp.jaist.ac.jp jaunty/main Packages
        100 /var/lib/dpkg/status

network-manager-gnome:
  Installed: 0.7.1~rc4.1-0ubuntu2
  Candidate: 0.7.1~rc4.1-0ubuntu2
  Version table:
 *** 0.7.1~rc4.1-0ubuntu2 0
        500 http://ftp.jaist.ac.jp jaunty/main Packages
        100 /var/lib/dpkg/status

[Pedro Villavicencio (pedro)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. However, your crash report is either missing or challenging to deal with as a ".crash" file. Please follow these instructions to have apport report a new bug about your crash that can be dealt with by the automatic retracer.

If you are running the Ubuntu Stable Release you might need to enable apport in /etc/default/apport and restart.

If you are using Ubuntu with the Gnome desktop environment - launch nautilus and navigate to your /var/crash directory and double click on the crash report you wish to submit.

If you are using Kubuntu or Xubuntu you can file the crash using /usr/share/apport/apport-qt --crash-file=/var/crash/_my_crash_report.crash in a terminal - where _my_crash_report.crash is the crash you would like to report.

I'm closing this bug report since the process outlined above will automatically open a new bug report which can then dealt with more efficiently. Thanks in advance for your cooperation and understanding.

[trbs (trbs)]

That does not work :(

I enabled apport in /etc/default/apport and i restarted it, I even tried with "sudo force_start=1 /etc/init.d/apport start"

But I don't get a crash file in /var/crash when I reproduce the bug. Reproducing the bug is extremely easy btw with the above describing. It literary takes a couple of seconds (3 mouse clicks) to see the nm-connection-editor crash consistently, it's not an obscure bug.

Reproducing says:
{{{
ERROR:nm-connection-list.c:787:add_done_cb: code should not be reached
Aborted (core dumped)
}}}

But nothing in either /var/crash or the current directory. I get crash files for other applications but not for nm-connection-editor.

So the method described in the command that closes the ticket does not work.

Either reopen the ticket, so I help provide more information or keep it closed in which case I will not pursue the matter further.

Here is the backtrace output of gdb:
{{{
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[New Thread 0xb6484b90 (LWP 4001)]
**
ERROR:nm-connection-list.c:787:add_done_cb: code should not be reached

Program received signal SIGABRT, Aborted.
[Switching to Thread 0xb6ed2750 (LWP 3984)]
0xb7f9e430 in __kernel_vsyscall ()
(gdb) bt
#0 0xb7f9e430 in __kernel_vsyscall ()
#1 0xb726a6d0 in raise () from /lib/tls/i686/cmov/libc.so.6
#2 0xb726c098 in abort () from /lib/tls/i686/cmov/libc.so.6
#3 0xb741c263 in g_assertion_message () from /usr/lib/libglib-2.0.so.0
#4 0x0805948e in ?? ()
#5 0x08076313 in nma_marshal_VOID__INT_POINTER ()
#6 0xb7483c7b in g_closure_invoke () from /usr/lib/libgobject-2.0.so.0
#7 0xb7499e57 in ?? () from /usr/lib/libgobject-2.0.so.0
#8 0xb749b4b9 in g_signal_emit_valist () from /usr/lib/libgobject-2.0.so.0
#9 0xb749b936 in g_signal_emit () from /usr/lib/libgobject-2.0.so.0
#10 0x08057651 in ?? ()
#11 0xb74913a4 in g_cclosure_marshal_VOID__VOID ()
   from /usr/lib/libgobject-2.0.so.0
#12 0xb7483c7b in g_closure_invoke () from /usr/lib/libgobject-2.0.so.0
#13 0xb7499e57 in ?? () from /usr/lib/libgobject-2.0.so.0
#14 0xb749b4b9 in g_signal_emit_valist () from /usr/lib/libgobject-2.0.so.0
#15 0xb749b936 in g_signal_emit () from /usr/lib/libgobject-2.0.so.0
#16 0xb7886bda in gtk_button_clicked () from /usr/lib/libgtk-x11-2.0.so.0
#17 0xb78881f8 in ?? () from /usr/lib/libgtk-x11-2.0.so.0
#18 0xb74913a4 in g_cclosure_marshal_VOID__VOID ()
   from /usr/lib/libgobject-2.0.so.0
#19 0xb74823d9 in ?? () from /usr/lib/libgobject-2.0.so.0
#20 0xb7483c7b in g_closure_invoke () from /usr/lib/libgobject-2.0.so.0
---Type <return> to continue, or q <return> to quit---
#21 0xb74996c0 in ?? () from /usr/lib/libgobject-2.0.so.0
#22 0xb749b4b9 in g_signal_emit_valist () from /usr/lib/libgobject-2.0.so.0
#23 0xb749b936 in g_signal_emit () from /usr/lib/libgobject-2.0.so.0
#24 0xb7886c7a in gtk_button_released () from /usr/lib/libgtk-x11-2.0.so.0
#25 0xb7886cb3 in ?? () from /usr/lib/libgtk-x11-2.0.so.0
#26 0xb7941526 in ?? () from /usr/lib/libgtk-x11-2.0.so.0
#27 0xb74823d9 in ?? () from /usr/lib/libgobject-2.0.so.0
#28 0...