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 569311 - Panel stuck in endless crash-restart loop after launching an app
Panel stuck in endless crash-restart loop after launching an app
Status: RESOLVED DUPLICATE of bug 569336
Product: libwnck
Classification: Core
Component: general
2.25.x
Other Linux
: Normal critical
: ---
Assigned To: libwnck maintainers
libwnck maintainers
Depends on:
Blocks:
 
 
Reported: 2009-01-27 09:54 UTC by Reinout van Schouwen
Modified: 2009-01-27 17:13 UTC
See Also:
GNOME target: ---
GNOME version: 2.25/2.26



Description Reinout van Schouwen 2009-01-27 09:54:59 UTC
My test system is Mandriva Cooker in Virtualbox.

After loading the Gnome desktop, the panel shows. However after launching a random application (say gnome-terminal), the panel crashes and ends up in an endless crash-restart loop. I've attached gdb to the process and it looks like libwnck is involved:

Program received signal SIGSEGV, Segmentation fault.
0x00000000 in ?? ()
(gdb) bt
  • #0 ??
  • #1 gtk_toggle_button_clicked
    at gtktogglebutton.c line 505
  • #2 IA__g_cclosure_marshal_VOID__VOID
    at gmarshal.c line 77
  • #3 g_type_class_meta_marshal
    at gclosure.c line 878
  • #4 IA__g_closure_invoke
    at gclosure.c line 767
  • #5 signal_emit_unlocked_R
    at gsignal.c line 3174
  • #6 IA__g_signal_emit_valist
    at gsignal.c line 2977
  • #7 IA__g_signal_emit
    at gsignal.c line 3034
  • #8 IA__gtk_button_clicked
    at gtkbutton.c line 1106
  • #9 wnck_tasklist_change_active_task
    at tasklist.c line 2405
  • #10 IA__g_cclosure_marshal_VOID__OBJECT
    at gmarshal.c line 636
  • #11 IA__g_closure_invoke
    at gclosure.c line 767
  • #12 signal_emit_unlocked_R
    at gsignal.c line 3244
  • #13 IA__g_signal_emit_valist
    at gsignal.c line 2977
  • #14 IA__g_signal_emit
    at gsignal.c line 3034
  • #15 do_update_now
    at screen.c line 2364
  • #16 update_idle
    at screen.c line 2337
  • #17 g_idle_dispatch
    at gmain.c line 3922
  • #18 IA__g_main_context_dispatch
    at gmain.c line 1814
  • #19 g_main_context_iterate
    at gmain.c line 2448
  • #20 IA__g_main_loop_run
    at gmain.c line 2656
  • #21 IA__gtk_main
    at gtkmain.c line 1205
  • #22 main
    at main.c line 111
The program is running.  Quit anyway (and detach it)? (y or n) y
Detaching from program: /usr/bin/gnome-panel, process 6680
Comment 1 Vincent Untz 2009-01-27 12:01:06 UTC
FWIW, this code in libwnck hasn't changed since quite some time, I think.

(In reply to comment #0)
> (gdb) bt
> #0  0x00000000 in ?? ()
> #1  0xb7c4f104 in gtk_toggle_button_clicked (button=0x85758d8)
>     at gtktogglebutton.c:505

Can I know which line this is? In trunk, the file has less than 505 lines :-)

And gtk_toggle_button_clicked looks like this:

static void
gtk_toggle_button_clicked (GtkButton *button)
{
  GtkToggleButton *toggle_button = GTK_TOGGLE_BUTTON (button);
  toggle_button->active = !toggle_button->active;

  gtk_toggle_button_toggled (toggle_button);

  gtk_toggle_button_update_state (button);

  g_object_notify (G_OBJECT (toggle_button), "active");
}
Comment 2 Vincent Untz 2009-01-27 12:55:05 UTC
Also, Seb thinks it might be an issue with GTK+ 2.15.2. Is this the version you're using?
Comment 3 Reinout van Schouwen 2009-01-27 17:02:43 UTC
Yes, my GTK+ version is 2.15.2.
Comment 4 Vincent Untz 2009-01-27 17:13:52 UTC
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.


*** This bug has been marked as a duplicate of 569336 ***