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

[Oliver Gerlich]

In the dialog for adding new Wireless connections, I clicked Add, and looked through the config window (but didn't change anything). Went to IPv4 Settings tab, clicked the Routes... button; then the system was busy for several seconds, then the crash dialog appeared.

This is in a Virtualbox system, with Intrepid alpha4 plus all updates. The crash is easily reproducible (crashes every time I try it).

ProblemType: Crash
Architecture: i386
DistroRelease: Ubuntu 8.10
ExecutablePath: /usr/bin/nm-connection-editor
Package: network-manager-gnome 0.7~~svn20080817t183748-0ubuntu1
ProcAttrCurrent: unconfined
ProcCmdline: /usr/bin/nm-connection-editor --type vpn
ProcEnviron:
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: network-manager-applet
StacktraceTop:
 ?? ()
 g_cclosure_marshal_VOID__VOID ()
 g_closure_invoke () from /usr/lib/libgobject-2.0.so.0
 ?? () from /usr/lib/libgobject-2.0.so.0
 g_signal_emit_valist () from /usr/lib/libgobject-2.0.so.0
Title: nm-connection-editor crashed with SIGSEGV in g_cclosure_marshal_VOID__VOID()
Uname: Linux 2.6.27-2-generic i686
UserGroups: adm admin cdrom dialout fuse lpadmin plugdev sambashare

[Apport retracing service (apport)]

StacktraceTop:IA__g_cclosure_marshal_VOID__VOID (closure=0x9d19ae8,
IA__g_closure_invoke (closure=0x9d19ae8, return_value=0x0,
signal_emit_unlocked_R (node=0x96a2a90, detail=0,
IA__g_signal_emit_valist (instance=0x9cd1338, signal_id=156,
IA__g_signal_emit (instance=0x9cd1338, signal_id=156,

[Chuck Renner (chuckrenner)]

Whenever making changes in the connection editor from Network Manager, the connection manager seems to crash, and to not apply the changes.

I am very happy to see all the options that have been added to the connection manager, but none of them seem to work!

I am particularly happy to see options to set MAC addresses, BSSIDs, system-wide wireless connections, wireless broadband, etc., but none of these new settings seem to work!!!

[Kamil Páral (kamil.paral)]

I can confirm this bug.

[heillig (iosifsubiac-deactivatedaccount)]

I can confirm this bug - runing livecd

[Viorel Cernăţeanu (vrilutza)]

Hi, me to confirm this bug - Intrepid Ibex Alpha 6 with the last update.

[Ralf Nieuwenhuijsen (ralf-nieuwenhuijsen)]

Confirm on Ubuntu Intrepid (the one with the ugly background) Beta..

[C Anthony Risinger (extofme)]

affirmative same result.

although i was trying to open/configure custom routes for a NOT YET SAVED pptp connection.

nm-applet crashes with sigseg

intrepid beta i386 full updated as of 10/6

[Alexander Sack (asac)]

Please test the intrepid packages in https://edge.launchpad.net/~network-manager/+archive.

[Oliver Gerlich (ogerlich)]

Dunno if this helps, but I tried again with a fairly up-to-date Intrepid system, and the crash doesn't happen any more (the Routes window is opened as expected, both for the existing eth0 connection and for a new, not yet saved Wifi connection).
So for me, the bug is already fixed even without using the packages from https://edge.launchpad.net/~network-manager/+archive.

[Liam O'Reilly (aliam13-2)]

Same here, I do not get the same behaviour now running 8.10 (fully updated as of today)

[Liam O'Reilly (aliam13-2)]

Same here, I do not get the same behavior now running 8.10 (fully updated as of today)

[Alexander Sack (asac)]

no duplicates for quite some time. closing.

[DougEdey (doug-edey)]

This is now occuring in 9.10 alpha 6.

[Herber (bdj9999)]

Bug apparent in 9.10 Alpha 6 on a Vaio system, crashes everytime Network manager tries to connect to a wireless network.

[Makoto (makotothedragon)]

Confirming bug as per DougEdey and Herber. Seems to occur whenever I connect to a wireless network.

Running Karmic Alpha 6.

[Kamil Páral (kamil.paral)]

There are people reporting it on Ubuntu 9.10 so I am reopening the bug.

[Omegamormegil (omegamormegil)]

I'm marking this bug invalid because I can no longer duplicate the original bug I reported. Please open a new bug report detailing the specific problems you are reporting, and post a link to the new bug in these comments.