Where to report nm-applet crashes to?

Liviu Andronic landronimirc at gmail.com
Fri Oct 7 08:50:03 CEST 2011


On Thu, Oct 6, 2011 at 10:51 PM, Clemens Eisserer <linuxhippy at gmail.com> wrote:
> Hi,
>
> I am using Fedora-15 and whenever I enable my wireless network,
> nm-applet crashes (stack-trace attached).
> As far as I know, nm-applet is not part of the xfce-project, so where
>
I don't think so. NM seems part of Gnome [1], so you would either
address the report to the Gnome or Fedora devs.

Liviu

[1] http://projects.gnome.org/NetworkManager/


> should I send my bug-report to?
>
> Thank you in advance, Clemens
>
> #0  0x47db35e2 in g_object_unref (_object=0x82df010) at gobject.c:2728
> #1  0x44bb7bed in nma_wireless_dialog_new (client=0x8101890,
> settings=0x80be910, connection=0x8119648, device=0x0, ap=0x0,
>    secrets_only=1) at nm-wireless-dialog.c:1312
> #2  0x080689dd in wireless_get_secrets (req=0x8200190,
> error=0xbfffef2c) at applet-device-wifi.c:1676
> #3  0x0805ea49 in get_existing_secrets_cb (agent=0x80be958,
> connection=0x8119648, secrets=0x814cc60, secrets_error=0x0,
>    user_data=0x8200190) at applet.c:2804
> #4  0x08060b64 in keyring_find_secrets_cb
> (result=GNOME_KEYRING_RESULT_NO_MATCH, list=0x0, user_data=0x813c808)
>    at applet-agent.c:426
> #5  0x488618d5 in gkr_callback_invoke_res (cb=0xb7401568,
> res=GNOME_KEYRING_RESULT_NO_MATCH) at gkr-callback.c:139
> #6  0x4886312d in on_complete (op=0x814cef0) at gkr-operation.c:212
> #7  0x4886bd68 in find_items_1_reply (data=0x8140e50, reply=0x81340e8,
> op=0x814cef0) at gnome-keyring.c:2281
> #8  find_items_1_reply (op=0x814cef0, reply=0x81340e8, data=0x8140e50)
> at gnome-keyring.c:2259
> #9  0x488615b0 in gkr_callback_invoke_op_msg (cb=0x812e650,
> msg=0x81340e8) at gkr-callback.c:69
> #10 0x48863a1c in callback_with_message (op=0x814cef0,
> message=0x81340e8) at gkr-operation.c:341
> #11 0x488640f1 in on_pending_call_notify (pending=0x80bcda8,
> user_data=0x814cef0) at gkr-operation.c:365
> #12 0x489a4442 in _dbus_pending_call_complete (pending=0x80bcda8) at
> dbus-pending-call.c:197
> #13 0x4898f288 in complete_pending_call_and_unlock
> (connection=0x8205378, pending=0x80bcda8, message=0x81340e8)
>    at dbus-connection.c:2308
> #14 0x48992b98 in dbus_connection_dispatch (connection=0x8205378) at
> dbus-connection.c:4593
> #15 0x4886fd9e in message_queue_dispatch (source=0x8200248,
> callback=0, user_data=0x0) at egg-dbus.c:75
> #16 0x47b365bf in g_main_dispatch (context=0x80c3648) at gmain.c:2441
> #17 g_main_context_dispatch (context=0x80c3648) at gmain.c:3014
> #18 0x47b36d30 in g_main_context_iterate (context=0x80c3648,
> block=1203001984, dispatch=1, self=0x80a8960) at gmain.c:3092
> #19 0x47b37457 in g_main_loop_run (loop=0x80c6c60) at gmain.c:3300
> #20 0x080577c6 in main (argc=1, argv=0xbffff414) at main.c:106
> _______________________________________________
> Xfce mailing list
> Xfce at xfce.org
> https://mail.xfce.org/mailman/listinfo/xfce
> http://www.xfce.org
>



-- 
Do you know how to read?
http://www.alienetworks.com/srtest.cfm
http://goodies.xfce.org/projects/applications/xfce4-dict#speed-reader
Do you know how to write?
http://garbl.home.comcast.net/~garbl/stylemanual/e.htm#e-mail


More information about the Xfce mailing list