Bug 440508 – crash in Panel:

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 440508 - crash in Panel:


Summary:	crash in Panel:


Status:	RESOLVED DUPLICATE of bug 413921

Product:	gnome-panel
Classification:	Other
Component:	general
Version:	2.18.x
Hardware:	Other All

Importance:	High critical
Target Milestone:	---
Assigned To:	Panel Maintainers
QA Contact:	Panel Maintainers

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2007-05-22 17:33 UTC by oliveirjallois
Modified:	2007-05-22 19:26 UTC

See Also:
GNOME target:	---
GNOME version:	2.17/2.18

Description oliveirjallois 2007-05-22 17:33:46 UTC

Version: 2.18.0

What were you doing when the application crashed?



Distribution: Unknown
Gnome Release: 2.18.0 2007-03-19 (Archlinux)
BugBuddy Version: 2.18.0

System: Linux 2.6.20.4 #3 SMP Thu Apr 12 17:36:47 CLT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 70200000
Selinux: No
Accessibility: Enabled
GTK+ Theme: Glider
Icon Theme: Crux

Memory status: size: 31899648 vsize: 31899648 resident: 20873216 share: 12886016 rss: 20873216 rss_rlim: 4294967295
CPU usage: start_time: 1179855005 rtime: 184 utime: 167 stime: 17 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

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

(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1225304384 (LWP 2782)]
(no debugging symbols found)
0xb7fa1822 in _dl_sysinfo_int80 () from /lib/ld-linux.so.2

+ Trace 135552

Thread 1 (Thread -1225304384 (LWP 2782))

#0 _dl_sysinfo_int80
from /lib/ld-linux.so.2
#1 __waitpid_nocancel
from /lib/libpthread.so.0
#2 libgnomeui_segv_handle
from /opt/gnome/lib/libgnomeui-2.so.0
#3 <signal handler called>
#4 strlen
from /lib/libc.so.6
#5 g_strdup
from /usr/lib/libglib-2.0.so.0
#6 ??
#7 ??
#8 ??
from /opt/gnome/lib/libORBit-2.so.0
#9 ??
#10 _int_free
from /lib/libc.so.6
#11 g_cclosure_marshal_VOID__OBJECT
from /usr/lib/libgobject-2.0.so.0
#12 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#13 signal_emit_unlocked_R
from /usr/lib/libgobject-2.0.so.0
#14 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#15 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#16 do_screen_change
from /usr/lib/libgtk-x11-2.0.so.0
#17 gtk_widget_propagate_hierarchy_changed_recurse
from /usr/lib/libgtk-x11-2.0.so.0
#18 gtk_bin_forall
from /usr/lib/libgtk-x11-2.0.so.0
#19 gtk_container_forall
from /usr/lib/libgtk-x11-2.0.so.0
#20 gtk_widget_propagate_hierarchy_changed_recurse
from /usr/lib/libgtk-x11-2.0.so.0
#21 gtk_box_forall
from /usr/lib/libgtk-x11-2.0.so.0
#22 gtk_container_forall
from /usr/lib/libgtk-x11-2.0.so.0
#23 gtk_widget_propagate_hierarchy_changed_recurse
from /usr/lib/libgtk-x11-2.0.so.0
#24 gtk_box_forall
from /usr/lib/libgtk-x11-2.0.so.0
#25 gtk_container_forall
from /usr/lib/libgtk-x11-2.0.so.0
#26 gtk_widget_propagate_hierarchy_changed_recurse
from /usr/lib/libgtk-x11-2.0.so.0
#27 gtk_box_forall
from /usr/lib/libgtk-x11-2.0.so.0
#28 gtk_container_forall
from /usr/lib/libgtk-x11-2.0.so.0
#29 gtk_widget_propagate_hierarchy_changed_recurse
from /usr/lib/libgtk-x11-2.0.so.0
#30 _gtk_widget_propagate_hierarchy_changed
from /usr/lib/libgtk-x11-2.0.so.0
#31 gtk_widget_unparent
from /usr/lib/libgtk-x11-2.0.so.0
#32 gtk_bin_remove
from /usr/lib/libgtk-x11-2.0.so.0
#33 g_cclosure_marshal_VOID__OBJECT
from /usr/lib/libgobject-2.0.so.0
#34 g_type_class_meta_marshal
from /usr/lib/libgobject-2.0.so.0
#35 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#36 signal_emit_unlocked_R
from /usr/lib/libgobject-2.0.so.0
#37 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#38 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#39 gtk_container_remove
from /usr/lib/libgtk-x11-2.0.so.0
#40 gtk_widget_dispose
from /usr/lib/libgtk-x11-2.0.so.0
#41 g_object_run_dispose
from /usr/lib/libgobject-2.0.so.0
#42 gtk_object_destroy
from /usr/lib/libgtk-x11-2.0.so.0
#43 gtk_widget_destroy
from /usr/lib/libgtk-x11-2.0.so.0
#44 gtk_bin_forall
from /usr/lib/libgtk-x11-2.0.so.0
#45 gtk_container_foreach
from /usr/lib/libgtk-x11-2.0.so.0
#46 gtk_container_destroy
from /usr/lib/libgtk-x11-2.0.so.0
#47 gtk_window_destroy
from /usr/lib/libgtk-x11-2.0.so.0
#48 g_cclosure_marshal_VOID__VOID
from /usr/lib/libgobject-2.0.so.0
#49 g_type_class_meta_marshal
from /usr/lib/libgobject-2.0.so.0
#50 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#51 signal_emit_unlocked_R
from /usr/lib/libgobject-2.0.so.0
#52 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#53 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#54 gtk_object_dispose
from /usr/lib/libgtk-x11-2.0.so.0
#55 gtk_widget_dispose
from /usr/lib/libgtk-x11-2.0.so.0
#56 gtk_window_dispose
from /usr/lib/libgtk-x11-2.0.so.0
#57 g_object_run_dispose
from /usr/lib/libgobject-2.0.so.0
#58 gtk_object_destroy
from /usr/lib/libgtk-x11-2.0.so.0
#59 gtk_widget_destroy
from /usr/lib/libgtk-x11-2.0.so.0
#60 ??
#61 ??
#62 ??
#63 ??
#64 ??
#0 _dl_sysinfo_int80
from /lib/ld-linux.so.2



----------- .xsession-errors ---------------------
  Resource id:  0x1c00561
X Error: BadWindow (invalid Window parameter) 3
  Major opcode:  20
  Minor opcode:  0
  Resource id:  0x1c00561
X Error: BadWindow (invalid Window parameter) 3
  Major opcode:  18
  Minor opcode:  0
  Resource id:  0x1c00561
GTK Accessibility Module initialized
Bonobo accessibility support initialized
GTK Accessibility Module initialized
Bonobo accessibility support initialized
** (bug-buddy:2914): WARNING **: Failed to initialize inotify: Función no implementada
--------------------------------------------------

Comment 1 Pedro Villavicencio 2007-05-22 19:26:18 UTC

Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.


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