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 108603 - When deleting the top level panel I get a seg fault massage.
When deleting the top level panel I get a seg fault massage.
Status: RESOLVED FIXED
Product: gnome-panel
Classification: Other
Component: panel
2.2.x
Other Linux
: High critical
: ---
Assigned To: Panel Maintainers
Panel Maintainers
: 110185 111109 111567 112219 115032 119576 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2003-03-17 14:52 UTC by Regan Burke
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: 2.1/2.2



Description Regan Burke 2003-03-17 14:52:15 UTC
Description of Problem:
when deleting the top level panel error message
"apllication 'gnome-panel' has crashed due to a
fatal error : segmentation fault

Steps to reproduce the problem:
1. Right mouse, delete panel
2. Confirm by pressing delete at prompt
3. 

Actual Results:
Error message as above


Expected Results:
Panel deletion


How often does this happen?
each time


Additional Information:
Comment 1 Elijah Newren 2003-03-17 17:52:19 UTC
Thanks for the bug report. Without a stack trace from the crash it's
very hard to determine what caused the crash. Please see
http://bugzilla.gnome.org/getting-traces.cgi for more information
about getting a useful stack trace.  It would also be helpful to know
which version of the gnome-panel (and/or which distribution of linux)
you are using.
Comment 2 Raul Acevedo 2003-03-18 22:48:22 UTC
I get this too, here's my Bug Buddy report including stack trace:

(This bug report was generated by Bug Buddy 2.2.103)
Description of Problem:
If I try to remove the menu bar created by default at the top of the
screen, the panel will crash after confirming the delete.

Steps to reproduce the problem:
1. Remove all GNOME configuration files, or start with a new user.
2. Login to GNOME.
3. Right click on menu bar across top of screen, select Delete Panel.

Actual Results:
Panel crashes.

Expected Results:
It should delete the menu panel.

How often does this happen?
Every time.

Additional Information:
Using GARNOME 0.22.0 build (and thus latest GNOME 2.2.1), on Red Hat
8.0.


Debugging Information:

Backtrace was generated from
'/home/garnome/0.22.0/install/bin/gnome-panel'

[New Thread 8192 (LWP 7579)]
0x420ae169 in wait4 () from /lib/i686/libc.so.6

Thread 1 (Thread 8192 (LWP 7579))

  • #0 wait4
    from /lib/i686/libc.so.6
  • #1 __DTOR_END__
    from /lib/i686/libc.so.6
  • #2 waitpid
    from /lib/i686/libpthread.so.0
  • #3 libgnomeui_segv_handle
    at gnome-ui-init.c line 646
  • #4 __pthread_sighandler
    from /lib/i686/libpthread.so.0
  • #5 <signal handler called>
  • #6 g_type_check_instance_cast
    at gtype.c line 2771
  • #7 panel_delete_without_query
    at panel.c line 2820
  • #8 remove_panel_accept
    at panel.c line 2866
  • #9 g_cclosure_marshal_VOID__INT
    at gmarshal.c line 216
  • #10 g_closure_invoke
    at gclosure.c line 437
  • #11 signal_emit_unlocked_R
    at gsignal.c line 2822
  • #12 g_signal_emit_valist
  • #13 g_signal_emit
    at gsignal.c line 2612
  • #14 gtk_dialog_response
    at gtkdialog.c line 826
  • #15 action_widget_activated
    at gtkdialog.c line 533
  • #16 g_cclosure_marshal_VOID__VOID
    at gmarshal.c line 77
  • #17 g_closure_invoke
    at gclosure.c line 437
  • #18 signal_emit_unlocked_R
    at gsignal.c line 2822
  • #19 g_signal_emit_valist
    at gsignal.c line 2554
  • #20 g_signal_emit
    at gsignal.c line 2612
  • #21 gtk_button_clicked
    at gtkbutton.c line 555
  • #22 gtk_real_button_released
    at gtkbutton.c line 1044
  • #23 g_cclosure_marshal_VOID__VOID
    at gmarshal.c line 77
  • #24 g_type_class_meta_marshal
    at gclosure.c line 514
  • #25 g_closure_invoke
    at gclosure.c line 437
  • #26 signal_emit_unlocked_R
    at gsignal.c line 2752
  • #27 g_signal_emit_valist
    at gsignal.c line 2554
  • #28 g_signal_emit
    at gsignal.c line 2612
  • #29 gtk_button_released
    at gtkbutton.c line 547
  • #30 gtk_button_button_release
    at gtkbutton.c line 960
  • #31 _gtk_marshal_BOOLEAN__BOXED
    at gtkmarshalers.c line 82
  • #32 g_type_class_meta_marshal
    at gclosure.c line 514
  • #33 g_closure_invoke
    at gclosure.c line 437
  • #34 signal_emit_unlocked_R
    at gsignal.c line 2860
  • #36 g_signal_emit
    at gsignal.c line 2612
  • #37 gtk_widget_event_internal
    at gtkwidget.c line 3143
  • #38 gtk_propagate_event
    at gtkmain.c line 2267
  • #39 gtk_main_do_event
    at gtkmain.c line 1502
  • #40 gdk_event_dispatch
    at gdkevents-x11.c line 2018
  • #41 g_main_dispatch
    at gmain.c line 1653
  • #42 g_main_context_dispatch
    at gmain.c line 2197
  • #43 g_main_context_iterate
    at gmain.c line 2278
  • #44 g_main_loop_run
    at gmain.c line 2498
  • #45 gtk_main
    at gtkmain.c line 1092
  • #46 main
    at main.c line 216
  • #47 __libc_start_main
    from /lib/i686/libc.so.6
  • #0 wait4
    from /lib/i686/libc.so.6


Comment 3 Elijah Newren 2003-03-18 23:17:28 UTC
Appears to be a unique stack trace, according to the
simple-dup-finder.  Setting version->2.2.x, marking priority->high
(it's a crasher), changing GNOMEVER2.0->GNOMEVER2.2, adding bugsquad
keyword, and reopening.
Comment 4 Arvind S N 2003-03-19 17:00:05 UTC
Thanks guys for tracking this guys!

2003-03-19  Arvind Samptur <arvind.samptur@wipro.com>

       Don't forget, FOOBAR_WIDGET still exists for 2.2. :/

       * panel.c: (remove_panel_accept) (panel_delete_without_query) :
        Get the casting right when deleting the menu panel.
        Fixes #108603
Comment 5 Arvind S N 2003-03-19 17:01:33 UTC
Ah, I am off to sleep, before  I type some more "guys" ;-)
Comment 6 Mark McLoughlin 2003-04-12 23:44:54 UTC
*** Bug 110185 has been marked as a duplicate of this bug. ***
Comment 7 Charles McLaughlin 2003-04-25 08:16:48 UTC
Same thing happens on my system (debian unstable).
Comment 8 Arvind S N 2003-04-26 11:47:37 UTC
*** Bug 111109 has been marked as a duplicate of this bug. ***
Comment 9 Arvind S N 2003-04-26 12:08:14 UTC
*** Bug 111567 has been marked as a duplicate of this bug. ***
Comment 10 Arvind S N 2003-04-28 03:24:06 UTC
*** Bug 111567 has been marked as a duplicate of this bug. ***
Comment 11 Elijah Newren 2003-05-25 14:24:25 UTC
*** Bug 112219 has been marked as a duplicate of this bug. ***
Comment 12 Elijah Newren 2003-06-12 16:17:25 UTC
*** Bug 115032 has been marked as a duplicate of this bug. ***
Comment 13 Elijah Newren 2003-08-11 01:41:41 UTC
*** Bug 119576 has been marked as a duplicate of this bug. ***