nm-system-settings crashed with SIGSEGV in g_type_check_instance_cast()

StacktraceTop:find_by_uuid (key=0x933d910, data=0x932af40, user_data=0xbfa78ab0) at plugin.c:86
IA__g_hash_table_foreach (hash_table=0x9315bb8, func=0xb8055db0 <find_by_uuid>, user_data=0xbfa78ab0)
dir_changed (monitor=0x931d0b0, file=0x932b630, other_file=0x0,
_gio_marshal_VOID__OBJECT_OBJECT_ENUM (closure=0x9318950, return_value=0x0, n_param_values=4,
IA__g_closure_invoke (closure=0x9318950, return_value=0x0, n_param_values=4, param_values=0x933c5f0,

can you reproduce this?

it seems like the last network-manager fixed the crash. I can't reproduce it anymore. Still, my network-manager cannot memorize the dsl login password, and there is no option to do that. I remember that after upgrading to intrepid alpha 5 the network-manager prompted me to accept the stored password in the gnome keyring. No I can't do that anymore, so I enter my dsl password everytime I login.
if this can help you:

mihai@mihai-desktop:~$ ifconfig -a
eth0 Link encap:Ethernet HWaddr 00:16:e6:11:da:93
          inet6 addr: fe80::216:e6ff:fe11:da93/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
          RX packets:194421 errors:0 dropped:0 overruns:0 frame:0
          TX packets:95276 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:171100281 (171.1 MB) TX bytes:9316452 (9.3 MB)
          Interrupt:23 Base address:0x6000

lo Link encap:Local Loopback
          inet addr:127.0.0.1 Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING MTU:16436 Metric:1
          RX packets:3522 errors:0 dropped:0 overruns:0 frame:0
          TX packets:3522 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:178036 (178.0 KB) TX bytes:178036 (178.0 KB)

ppp0 Link encap:Point-to-Point Protocol
          inet addr:86.104.255.64 P-t-P:86.104.254.1 Mask:255.255.255.255
          UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1492 Metric:1
          RX packets:25 errors:0 dropped:0 overruns:0 frame:0
          TX packets:26 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:3
          RX bytes:8522 (8.5 KB) TX bytes:1538 (1.5 KB)

I've tracked this down to a case of the wrong pointer being dereferenced in the keyfile plugin. Patch to follow shortly.

Here's the patch. Alexander, let me know if you'd like to upload.

fix committed to lp:~network-manager/network-manager/ubuntu.0.7 and forwarded upstream (to nm list).

This bug was fixed in the package network-manager - 0.7~~svn20080908t183521+eni0-0ubuntu3

---------------
network-manager (0.7~~svn20080908t183521+eni0-0ubuntu3) intrepid; urgency=low

  [ Antti "Wellark" Kaijanmäki ]
  * Fix LP: #268095 - MASTER Network Manager should probe for GSM and CDMA command
    sets; we probe all modems tagged as v.250 in hal that otherwise dont specify a
    GSM or CDMA command set.
    - added debian/patches/add_probe_for_v250_modems.patch
    - modified debian/patches/series

  [ Alexander Sack <email address hidden> ]
  * point Vcs-Bzr to right source tree
    - update debian/control
  * Fix LP: #269755 - "network manager always crashes on resume"; these crashes
    are a regression introduced by fix for LP: #259503 which was first
    released in 0.7~~svn20080908t183521+eni0-0ubuntu1. To fix we redo the patch
    in a way that will eliminate any idle callbacks as soon as they
    become irrelevant.
    - update debian/patches/80_lp259503_access_to_freed_device_struct.patch

  [ Steve Langasek <email address hidden> ]
  * system-settings/plugins/keyfile/plugin.c: it might be better if we were
    casting the data from the hash to a gobject, instead of the key which is
    a filename... fixes a crash whenever trying to handle system-level secrets.
    LP: #269010.
    - add debian/patches/lp269010_keyfile_secrets_crash.patch
    - update debian/patches/series

 -- Alexander Sack <email address hidden> Wed, 17 Sep 2008 02:54:56 +0200

Until 7 August ..all OK with my network.
Then after upgrade - network Manager won't work at all ( upgrade was for Karmic - on 7/8 August )

my connection is DSL - so, fortunatelly I can connect using pppoeconf utility.

But the point is ..network manager is unusable and this is bad. This kind of problems should be history now..

For example I use Karmic Koala now and this bug is alive again.

What should I do to repair my problem ?

..my Apport submit this bug - maybe is useful to see the command line responses ..

---------------------------------------------------------

ion@SQ2:~$ nm-applet

** (nm-applet:4917): WARNING **: <WARN> request_name(): Could not acquire the session service as it is already taken. Return: 3

** (nm-applet:4917): WARNING **: <WARN> constructor(): Couldn't initialize the D-Bus manager.

ion@SQ2:~$ killall nm-applet
ion@SQ2:~$ nm-applet

** (nm-applet:4993): WARNING **: Could not retrieve dbus connections: The name org.freedesktop.NetworkManagerSystemSettings was not provided by any .service files.

------------------------------------------------------------------

I'll wait for an useble answer (this bug force me to stay and to work under XP)