I just installed the ubuntu released version, and can reproduce the crash again.
Its a WPA Personal secured WiFi network which I connect to.
First of all, I have to disable networking, and kill nm-applet. This hopefully means I loose association on my WiFi, and the pass-phrase is not cached anywhere in network-manager.
I then open up gnome-keyring-manager, find the key for that network, and delete it.
Now reload nm-applet:
gdb --args nm-applet --sm-disable
(--sm-disable avoids you getting lots of copies next time you log on).
Once you've got the list of WiFi networks again, (having re-enabled networking), I click my home network - which I no-longer have a gnome-keyring key for.
Segfault. (No stack trace, as I don't know where to get a dbg package from).
So - I fetched the Ubuntu source and built it, running the un-stripped binary from the build-tree...
As before,
0x0805fafc in nmi_dbus_get_network_key_callback (
result=GNOME_KEYRING_RESULT_OK, found_list=0x0, data=0x83d3bc8)
at applet-dbus-info.c:117
117 nm_gconf_wso_set_key (gconf_wso, found->secret, strlen (found->secret));
(gdb) bt
#0 0x0805fafc in nmi_dbus_get_network_key_callback (
result=GNOME_KEYRING_RESULT_OK, found_list=0x0, data=0x83d3bc8)
at applet-dbus-info.c:117
#1 0x4d25ba28 in ?? () from /usr/lib/libgnome-keyring.so.0
#2 0x00000000 in ?? ()
(gdb)
If you can point me at where to find a -dbg package for network-manager-gnome, and / or libgnome-keyring, I'll try and get a better stack trace.
Obviously clearing out the gnome-keyring keys isn't a common thing for a user to do, but in the first instance, I hit this after an upgrade - having never touched the keys.
What version of libgnome-keyring0 do you have installed?
I just installed the ubuntu released version, and can reproduce the crash again.
Its a WPA Personal secured WiFi network which I connect to.
First of all, I have to disable networking, and kill nm-applet. This hopefully means I loose association on my WiFi, and the pass-phrase is not cached anywhere in network-manager.
I then open up gnome-keyring- manager, find the key for that network, and delete it.
Now reload nm-applet:
gdb --args nm-applet --sm-disable
(--sm-disable avoids you getting lots of copies next time you log on).
Once you've got the list of WiFi networks again, (having re-enabled networking), I click my home network - which I no-longer have a gnome-keyring key for.
Segfault. (No stack trace, as I don't know where to get a dbg package from).
So - I fetched the Ubuntu source and built it, running the un-stripped binary from the build-tree...
As before,
0x0805fafc in nmi_dbus_ get_network_ key_callback ( GNOME_KEYRING_ RESULT_ OK, found_list=0x0, data=0x83d3bc8) dbus-info. c:117 wso_set_ key (gconf_wso, found->secret, strlen (found->secret)); get_network_ key_callback ( GNOME_KEYRING_ RESULT_ OK, found_list=0x0, data=0x83d3bc8) dbus-info. c:117 libgnome- keyring. so.0
result=
at applet-
117 nm_gconf_
(gdb) bt
#0 0x0805fafc in nmi_dbus_
result=
at applet-
#1 0x4d25ba28 in ?? () from /usr/lib/
#2 0x00000000 in ?? ()
(gdb)
If you can point me at where to find a -dbg package for network- manager- gnome, and / or libgnome-keyring, I'll try and get a better stack trace.
Obviously clearing out the gnome-keyring keys isn't a common thing for a user to do, but in the first instance, I hit this after an upgrade - having never touched the keys.
What version of libgnome-keyring0 do you have installed?
Peter