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 517545 - crash in Panel:
crash in Panel:
Status: RESOLVED DUPLICATE of bug 466845
Product: gnome-panel
Classification: Other
Component: general
2.18.x
Other All
: High critical
: ---
Assigned To: Panel Maintainers
Panel Maintainers
Depends on:
Blocks:
 
 
Reported: 2008-02-19 21:17 UTC by yunongqi
Modified: 2008-02-19 21:24 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description yunongqi 2008-02-19 21:17:30 UTC 
Version: 2.18.3

What were you doing when the application crashed?



Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.3 2007-07-02 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.22.4-65.fc7 #1 SMP Tue Aug 21 21:50:50 EDT 2007 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Enforcing
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 293830656 vsize: 293830656 resident: 23142400 share: 18964480 rss: 23142400 rss_rlim: 18446744073709551615
CPU usage: start_time: 1203455242 rtime: 15 utime: 12 stime: 3 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

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

(no debugging symbols found)
Using host libthread_db library "/lib64/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 46912679001632 (LWP 5459)]
(no debugging symbols found)
0x00002aaab07fd945 in waitpid () from /lib64/libpthread.so.0

+ Trace 189788

Thread 1 (Thread 46912679001632 (LWP 5459))

  • #0 waitpid
    from /lib64/libpthread.so.0
  • #1 g_cclosure_marshal_VOID__ENUM
    from /usr/lib64/libgnomeui-2.so.0
  • #2 <signal handler called>
  • #3 strcmp
    from /lib64/libc.so.6
  • #4 gnome_vfs_volume_compare
    from /usr/lib64/libgnomevfs-2.so.0
  • #5 g_cclosure_marshal_VOID__ENUM
    from /lib64/libglib-2.0.so.0
  • #6 g_cclosure_marshal_VOID__ENUM
    from /lib64/libglib-2.0.so.0
  • #7 g_cclosure_marshal_VOID__ENUM
    from /lib64/libglib-2.0.so.0
  • #8 ??
  • #9 ??
  • #10 panel_place_menu_item_new
  • #11 ??
  • #12 g_type_create_instance
    from /lib64/libgobject-2.0.so.0
  • #13 g_cclosure_marshal_VOID__ENUM
    from /lib64/libgobject-2.0.so.0
  • #14 g_object_newv
    from /lib64/libgobject-2.0.so.0
  • #15 g_object_new_valist
    from /lib64/libgobject-2.0.so.0
  • #16 g_object_new
    from /lib64/libgobject-2.0.so.0
  • #17 panel_menu_bar_load_from_gconf
  • #18 ??
  • #19 g_main_context_dispatch
    from /lib64/libglib-2.0.so.0
  • #20 g_cclosure_marshal_VOID__ENUM
    from /lib64/libglib-2.0.so.0
  • #21 g_main_loop_run
    from /lib64/libglib-2.0.so.0
  • #22 gtk_main
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #23 main
  • #0 waitpid
    from /lib64/libpthread.so.0 


----------- .xsession-errors ---------------------
(bug-buddy:5369): GLib-GObject-WARNING **: invalid uninstantiatable type `unmap-event' in cast to `GObject'
(bug-buddy:5369): GLib-GObject-CRITICAL **: g_object_get_data: assertion `G_IS_OBJECT (object)' failed
(bug-buddy:5369): GLib-CRITICAL **: g_hash_table_destroy: assertion `hash_table->ref_count > 0' failed
(bug-buddy:5369): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed
(bug-buddy:5410): GLib-GObject-WARNING **: invalid uninstantiatable type `motion-notify-event' in cast to `GObject'
(bug-buddy:5410): GLib-GObject-CRITICAL **: g_object_get_data: assertion `G_IS_OBJECT (object)' failed
(bug-buddy:5410): GLib-CRITICAL **: g_hash_table_destroy: assertion `hash_table->ref_count > 0' failed
(bug-buddy:5410): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed
--------------------------------------------------
Comment 1 Philip Withnall 2008-02-19 21:24:38 UTC 
Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers?


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