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 315197 - Opening "Add to Panel" dialog multiple times crashes
Opening "Add to Panel" dialog multiple times crashes
Status: RESOLVED NOTGNOME
Product: gnome-panel
Classification: Other
Component: panel
2.11.x
Other All
: High critical
: ---
Assigned To: Panel Maintainers
Panel Maintainers
Depends on:
Blocks:
 
 
Reported: 2005-09-03 21:34 UTC by Peter Shinners
Modified: 2005-09-09 22:45 UTC
See Also:
GNOME target: ---
GNOME version: 2.11/2.12


Attachments
Bug fix (1.11 KB, patch)
2005-09-09 14:05 UTC, Manu Cornet
none Details | Review
Better bug fix (1.07 KB, patch)
2005-09-09 22:45 UTC, Manu Cornet
none Details | Review

Description Peter Shinners 2005-09-03 21:34:13 UTC
Steps to reproduce:
1. Choose "Add to Panel..." from the right mouse menu.
2. Choose "Add to Panel..." again
3. crash


Stack trace:

Backtrace was generated from '/usr/bin/gnome-panel'

(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
`system-supplied DSO at 0xffffe000' has disappeared; keeping its
symbols.
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1224059200 (LWP 8494)]
[New Thread -1231713360 (LWP 8495)]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

Thread 1 (Thread -1224059200 (LWP 8494))

  • #0 __kernel_vsyscall
  • #1 __waitpid_nocancel
    from /lib/tls/i686/cmov/libpthread.so.0
  • #2 libgnomeui_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 panel_addto_present
  • #5 g_cclosure_marshal_VOID__VOID
    from /usr/lib/libgobject-2.0.so.0
  • #6 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #7 g_signal_stop_emission
    from /usr/lib/libgobject-2.0.so.0
  • #8 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #9 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #10 gtk_widget_activate
    from /usr/lib/libgtk-x11-2.0.so.0
  • #11 gtk_menu_shell_activate_item
    from /usr/lib/libgtk-x11-2.0.so.0
  • #12 gtk_menu_shell_activate_item
    from /usr/lib/libgtk-x11-2.0.so.0
  • #13 gtk_menu_reorder_child
    from /usr/lib/libgtk-x11-2.0.so.0
  • #14 _gtk_marshal_BOOLEAN__BOXED
    from /usr/lib/libgtk-x11-2.0.so.0
  • #15 g_cclosure_new_swap
    from /usr/lib/libgobject-2.0.so.0
  • #16 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #17 g_signal_stop_emission
    from /usr/lib/libgobject-2.0.so.0
  • #18 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #19 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #20 gtk_widget_activate
    from /usr/lib/libgtk-x11-2.0.so.0
  • #21 gtk_propagate_event
    from /usr/lib/libgtk-x11-2.0.so.0
  • #22 gtk_main_do_event
    from /usr/lib/libgtk-x11-2.0.so.0
  • #23 _gdk_events_queue
    from /usr/lib/libgdk-x11-2.0.so.0
  • #24 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #25 g_main_context_check
    from /usr/lib/libglib-2.0.so.0
  • #26 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #27 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #28 main
  • #0 __kernel_vsyscall




Other information:
Not using any applets that didn't come from a Ubuntu package. The only
non-standard applets in use is "Tomboy". This is on a prerelease Ubuntu Breezy
Badger. Gnome version is 2.11.4, Panels version is 2.11.92
Comment 1 Alessio Spadaro 2005-09-06 11:15:26 UTC
Not able to reproduce on stock ubuntu (Breezy Badger) packages (2.11.92 nor
2.12.0-ubuntu1)Could you please upgrade via upgrade-manager and see if it still
happens?
Comment 2 Christian Kirbach 2005-09-06 12:55:05 UTC
unique stack trace.
Comment 3 Peter Shinners 2005-09-06 14:55:40 UTC
Updated everything, it seems most of the gnome packages are 2.12.0-ubuntu1 now.
This still has the same crash for me. I created a new user account to test and
also saw the same problem.

I checked the stack trace and it looks similar. Each thread has the same three
functions right before <signal handler called>. I've saved it, but won't post it
unless asked for. 

I am downloading a daily live snapshot today and will test with that tonight (12
hours from posting time, I am in PST).

Bug buddy says I am now running version: GNOME2.12.0 2.12.x
Apt says my gnome-panel is version: 2.12.0-0ubuntu1
Comment 4 Alessio Spadaro 2005-09-06 16:19:27 UTC
Ok, able to reproduce on 2.12.0-ubuntu1, here's the stack trace:

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 16384 (LWP 19682)]
panel_addto_present (item=0x82e3df0, panel_widget=0x8145b18)
    at panel-addto.c:1488
1488    panel-addto.c: No such file or directory.
        in panel-addto.c
(gdb) thread apply all bt

Thread 1 (Thread 16384 (LWP 19682))

  • #0 panel_addto_present
    at panel-addto.c line 1488
  • #1 IA__g_cclosure_marshal_VOID__VOID
    at gmarshal.c line 77
  • #2 IA__g_closure_invoke
    at gclosure.c line 492
  • #3 signal_emit_unlocked_R
    at gsignal.c line 2485
  • #4 IA__g_signal_emit_valist
    at gsignal.c line 2244
  • #5 IA__g_signal_emit
    at gsignal.c line 2288
  • #6 IA__gtk_widget_activate
    at gtkwidget.c line 3766
  • #7 IA__gtk_menu_shell_activate_item
    at gtkmenushell.c line 1057
  • #8 gtk_menu_shell_button_release
    at gtkmenushell.c line 663
  • #9 gtk_menu_button_release
    at gtkmenu.c line 2571
  • #10 _gtk_marshal_BOOLEAN__BOXED
    at gtkmarshalers.c line 83
  • #11 g_type_class_meta_marshal
    at gclosure.c line 569
  • #12 IA__g_closure_invoke
    at gclosure.c line 492
  • #13 signal_emit_unlocked_R
    at gsignal.c line 2523
  • #14 IA__g_signal_emit_valist
    at gsignal.c line 2254
  • #15 IA__g_signal_emit
    at gsignal.c line 2288
  • #16 gtk_widget_event_internal
    at gtkwidget.c line 3735
  • #17 IA__gtk_propagate_event
    at gtkmain.c line 2160
  • #18 IA__gtk_main_do_event
    at gtkmain.c line 1397
  • #19 gdk_event_dispatch
    at gdkevents-x11.c line 2291
  • #20 IA__g_main_context_dispatch
    at gmain.c line 1934
  • #21 g_main_context_iterate
  • #22 IA__g_main_loop_run
    at gmain.c line 2769
  • #23 IA__gtk_main
    at gtkmain.c line 976
  • #24 main
    at main.c line 90

Comment 5 Sebastien Bacher 2005-09-06 22:36:03 UTC
this dialog is an ubuntu patch, the uptream code doesn't crash. Ccing Emmanuel
who work on that
Comment 6 Manu Cornet 2005-09-09 14:05:47 UTC
Created attachment 52015 [details] [review]
Bug fix

This patch solves the bug by displaying a small GtkMessageDialog (with just a
"Close" button) saying that another instance of the "add to panel" dialog is
already open.
Comment 7 Vincent Untz 2005-09-09 21:17:30 UTC
Manu: this is clearly wrong. Look at how this is done in the current panel code
(in panel-addto.c): we just present the window again.
Comment 8 Manu Cornet 2005-09-09 22:45:45 UTC
Created attachment 52037 [details] [review]
Better bug fix

Right :) Then it's even simpler ! Here's a new patch.