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 537219 - crash in Panel:
crash in Panel:
Status: RESOLVED DUPLICATE of bug 466845
Product: gnome-panel
Classification: Other
Component: general
2.20.x
Other All
: High critical
: ---
Assigned To: Panel Maintainers
Panel Maintainers
Depends on:
Blocks:
 
 
Reported: 2008-06-08 09:06 UTC by bugbuddy
Modified: 2008-06-08 10:50 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22



Description bugbuddy 2008-06-08 09:06:30 UTC
Version: 2.20.3

What were you doing when the application crashed?



Distribution: Debian lenny/sid
Gnome Release: 2.22.2 2008-05-29 (Debian)
BugBuddy Version: 2.22.0

System: Linux 2.6.23-1-amd64 #1 SMP Fri Dec 21 12:00:17 UTC 2007 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10400090
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: gnome

Memory status: size: 288030720 vsize: 288030720 resident: 25915392 share: 14598144 rss: 25915392 rss_rlim: 18446744073709551615
CPU usage: start_time: 1212809913 rtime: 12015 utime: 11429 stime: 586 cutime:0 cstime: 6 timeout: 0 it_real_value: 0 frequency: 100

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

(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0x2b053b206200 (LWP 3914)]
(no debugging symbols found)
0x00002b0534b785b5 in waitpid () from /lib/libpthread.so.0

Thread 1 (Thread 0x2b053b206200 (LWP 3914))

  • #0 waitpid
    from /lib/libpthread.so.0
  • #1 g_spawn_sync
    from /usr/lib/libglib-2.0.so.0
  • #2 g_spawn_command_line_sync
    from /usr/lib/libglib-2.0.so.0
  • #3 ??
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #4 <signal handler called>
  • #5 strcmp
    from /lib/libc.so.6
  • #6 gnome_vfs_volume_compare
    from /usr/lib/libgnomevfs-2.so.0
  • #7 ??
    from /usr/lib/libglib-2.0.so.0
  • #8 ??
  • #9 ??
  • #10 ??
  • #11 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #12 ??
    from /usr/lib/libgobject-2.0.so.0
  • #13 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #14 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #15 ??
    from /usr/lib/libgnomevfs-2.so.0
  • #16 dbus_connection_dispatch
    from /usr/lib/libdbus-1.so.3
  • #17 ??
    from /usr/lib/libdbus-glib-1.so.2
  • #18 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #19 ??
    from /usr/lib/libglib-2.0.so.0
  • #20 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #21 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #22 main
  • #0 waitpid
    from /lib/libpthread.so.0


----------- .xsession-errors (80543 sec old) ---------------------
(xchat:4102): Gtk-CRITICAL **: gtk_progress_set_percentage: assertion `percentage >= 0 && percentage <= 1.0' failed
(xchat:4102): Gtk-CRITICAL **: gtk_progress_set_percentage: assertion `percentage >= 0 && percentage <= 1.0' failed
(xchat:4102): Gtk-CRITICAL **: gtk_progress_set_percentage: assertion `percentage >= 0 && percentage <= 1.0' failed
(xchat:4102): Gtk-CRITICAL **: gtk_progress_set_percentage: assertion `percentage >= 0 && percentage <= 1.0' failed
(xchat:4102): Gtk-CRITICAL **: gtk_progress_set_percentage: assertion `percentage >= 0 && percentage <= 1.0' failed
(xchat:4102): Gtk-CRITICAL **: gtk_progress_set_percentage: assertion `percentage >= 0 && percentage <= 1.0' failed
(xchat:4102): Gtk-CRITICAL **: gtk_progress_set_percentage: assertion `percentage >= 0 && percentage <= 1.0' failed
...Too much output, ignoring rest...
--------------------------------------------------
Comment 1 Philip Withnall 2008-06-08 10:50:30 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 ***