Bug 117232 – Gnome panel crashes if trying to add a starter

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 117232 - Gnome panel crashes if trying to add a starter


Summary:	Gnome panel crashes if trying to add a starter


Status:	RESOLVED DUPLICATE of bug 106166

Product:	gnome-panel
Classification:	Other
Component:	panel
Version:	unspecified
Hardware:	Other other

Importance:	Normal normal
Target Milestone:	---
Assigned To:	Panel Maintainers
QA Contact:	Panel Maintainers

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2003-07-11 19:34 UTC by chhahn
Modified:	2004-12-22 21:47 UTC

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

Description chhahn 2003-07-11 19:34:32 UTC

Package: gnome-panel
Severity: normal
Version: GNOME2.2.0 2.2.0.1
os_details: Gnome.Org
Synopsis: Gnome panel crashes if trying to add a starter
Bugzilla-Product: gnome-panel
Bugzilla-Component: Panel
BugBuddy-GnomeVersion: 2.0 (2.2.0.1)
Description:
Description of Problem:
Every time I try to add a starter to an existing folder on the panel,
the gnome panel crashes.

Steps to reproduce the problem:
1. 
2. 
3. 

Actual Results:


Expected Results:


How often does this happen?


Additional Information:



Debugging Information:

Backtrace was generated from '/opt/gnome2/bin/gnome-panel'

(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)...[New
Thread 16384 (LWP 2375)]

(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)...
0x40a9b387 in waitpid () from /lib/libpthread.so.0

+ Trace 38632

Thread 1 (Thread 16384 (LWP 2375))

#0 waitpid
from /lib/libpthread.so.0
#1 libgnomeui_module_info_get
from /opt/gnome2/lib/libgnomeui-2.so.0
#2 __pthread_sighandler
from /lib/libpthread.so.0
#3 <signal handler called>
#4 strcmp
from /lib/libc.so.6
#5 transcmp
from /lib/libc.so.6
#6 tfind
from /lib/libc.so.6
#7 __dcigettext
from /lib/libc.so.6
#8 dcgettext
from /lib/libc.so.6
#9 gtk_dialog_get_type
from /usr/lib/libgtk-x11-2.0.so.0
#10 type_class_init_Wm
from /usr/lib/libgobject-2.0.so.0
#11 g_type_class_ref
from /usr/lib/libgobject-2.0.so.0
#12 g_object_newv
from /usr/lib/libgobject-2.0.so.0
#13 g_object_new_valist
from /usr/lib/libgobject-2.0.so.0
#14 g_object_new
from /usr/lib/libgobject-2.0.so.0
#15 gtk_dialog_new
from /usr/lib/libgtk-x11-2.0.so.0
#16 gtk_dialog_new_with_buttons
from /usr/lib/libgtk-x11-2.0.so.0
#17 ask_about_launcher
#18 ask_about_launcher_cb
#19 g_cclosure_marshal_VOID__VOID
from /usr/lib/libgobject-2.0.so.0
#20 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#21 signal_emit_unlocked_R
from /usr/lib/libgobject-2.0.so.0
#22 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#23 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#24 gtk_widget_activate
from /usr/lib/libgtk-x11-2.0.so.0
#25 gtk_menu_shell_activate_item
from /usr/lib/libgtk-x11-2.0.so.0
#26 gtk_menu_shell_deactivate
from /usr/lib/libgtk-x11-2.0.so.0
#27 gtk_menu_reorder_child
from /usr/lib/libgtk-x11-2.0.so.0
#28 gtk_propagate_event
from /usr/lib/libgtk-x11-2.0.so.0
#29 g_type_class_meta_marshal
from /usr/lib/libgobject-2.0.so.0
#30 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#31 signal_emit_unlocked_R
from /usr/lib/libgobject-2.0.so.0
#32 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#33 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#34 gtk_widget_send_expose
from /usr/lib/libgtk-x11-2.0.so.0
#35 gtk_propagate_event
from /usr/lib/libgtk-x11-2.0.so.0
#36 gtk_main_do_event
from /usr/lib/libgtk-x11-2.0.so.0
#37 gdk_add_client_message_filter
from /usr/lib/libgdk-x11-2.0.so.0
#38 g_main_dispatch
from /usr/lib/libglib-2.0.so.0
#39 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#40 g_main_context_iterate
from /usr/lib/libglib-2.0.so.0
#41 g_main_loop_run
from /usr/lib/libglib-2.0.so.0
#42 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#43 main
#44 __libc_start_main
from /lib/libc.so.6
#0 waitpid
from /lib/libpthread.so.0





------- Bug moved to this database by unknown@bugzilla.gnome.org 2003-07-11 15:34 -------

The original reporter (chhahn@gmx.net) of this bug does not have an account here.
Reassigning to the exporter, unknown@bugzilla.gnome.org.
Reassigning to the default owner of the component, gnome-panel-maint@bugzilla.gnome.org.

Comment 1 Elijah Newren 2003-07-11 23:33:25 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 106166 ***