Bug 336933 – nm-applet exits when the GNOME panel crashes

After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.

Bug 336933 - nm-applet exits when the GNOME panel crashes


Summary:	nm-applet exits when the GNOME panel crashes


Status:	RESOLVED FIXED

Product:	NetworkManager
Classification:	Platform
Component:	nm-applet
Version:	git master
Hardware:	Other Linux

Importance:	Normal major
Target Milestone:	---
Assigned To:	Dan Williams
QA Contact:	Dan Williams

URL:
Whiteboard:

Duplicates:	331634 463495 (view as bug list)
Depends on:
Blocks:

Reported:	2006-04-02 15:37 UTC by Diego González
Modified:	2007-12-31 15:41 UTC

See Also:
GNOME target:	---
GNOME version:	---

Description Diego González 2006-04-02 15:37:57 UTC

backtrace:

0xb75f4963 in IA__g_object_unref (_object=0x0) at gobject.c:1721
1721      old_ref = g_atomic_int_get (&object->ref_count);
(gdb) bt

+ Trace 67402

#0 IA__g_object_unref
at gobject.c line 1721
#1 nma_destroy
at applet.c line 2543
#2 IA__g_cclosure_marshal_VOID__VOID
at gmarshal.c line 77
#3 IA__g_closure_invoke
at gclosure.c line 490
#4 signal_emit_unlocked_R
at gsignal.c line 2438
#5 IA__g_signal_emit_valist
at gsignal.c line 2197
#6 IA__g_signal_emit
at gsignal.c line 2241
#7 gtk_object_dispose
at gtkobject.c line 418
#8 gtk_widget_dispose
at gtkwidget.c line 6709
#9 gtk_window_dispose
at gtkwindow.c line 1790
#10 IA__g_object_run_dispose
at gobject.c line 571
#11 IA__gtk_object_destroy
at gtkobject.c line 403
#12 IA__gtk_widget_destroy
at gtkwidget.c line 2039
#13 _gtk_plug_send_delete_event
at gtkplug.c line 282
#14 _gtk_plug_windowing_filter_func
at gtkplug-x11.c line 280
#15 gdk_event_apply_filters
at gdkevents-x11.c line 345
#16 gdk_event_translate
at gdkevents-x11.c line 982
#17 _gdk_events_queue
at gdkevents-x11.c line 2245
#18 gdk_event_dispatch
at gdkevents-x11.c line 2305
#19 g_main_dispatch
at gmain.c line 1916
#20 IA__g_main_context_dispatch
at gmain.c line 2466
#21 g_main_context_iterate
at gmain.c line 2547
#22 IA__g_main_loop_run
at gmain.c line 2751
#23 IA__gtk_main
at gtkmain.c line 1002
#24 main
at main.c line 67

Comment 1 Robert Love 2006-05-25 20:35:21 UTC

*** Bug 331634 has been marked as a duplicate of this bug. ***

Comment 2 Dan Williams 2006-07-09 22:15:12 UTC

Hmm.  How do other applets detect and recover from panel crashes?

Comment 3 Bartek Kostrzewa 2007-06-17 00:52:14 UTC

This bug is confirmed on launchpad (ubuntu bugtracker)

https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/20176

note that the process also stops when the notification area is removed from the panel, it does not require a panel crash see the bug below:

https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/114580


As for the detection, you might want to check out the ubuntu update manager or gnome power manager, both of which have icons in the notification area and both of which do not suffer from this bug.

Comment 4 Alexander “weej” Jones 2007-06-17 01:10:36 UTC

From my own use of GtkStatusIcon, you don't need any detection. It's actually more work to quit when the icon unmaps.

Comment 5 Bartek Kostrzewa 2007-06-19 16:41:27 UTC

I think we should also mention here that Alex did not observe a crash but exit status 0. Alex, can you comment whether you crashed the panel to observe this or whether you simply killed the panel process?

Comment 6 Alexander “weej” Jones 2007-06-19 16:56:32 UTC

I killed the panel process. You can also simply remove the notification area.

Comment 7 Christopher Aillon 2007-08-07 15:06:43 UTC

*** Bug 463495 has been marked as a duplicate of this bug. ***

Comment 8 Sam Morris 2007-11-15 00:16:30 UTC

Should this be retitled to something like 'nm-applet exits when the system tray disappears'?

Comment 9 Alexander “weej” Jones 2007-11-15 00:35:49 UTC

Yes.

Comment 10 Christopher Aillon 2007-12-31 15:41:26 UTC

This was fixed by bug 379914, only on HEAD.