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 498592 - crash in Panel: kill beagled
crash in Panel: kill beagled
Status: RESOLVED DUPLICATE of bug 487049
Product: gnome-panel
Classification: Other
Component: general
2.20.x
Other All
: High critical
: ---
Assigned To: Panel Maintainers
Panel Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-11-20 20:06 UTC by Daniel van Eeden
Modified: 2008-01-11 07:00 UTC
See Also:
GNOME target: ---
GNOME version: 2.19/2.20



Description Daniel van Eeden 2007-11-20 20:06:42 UTC
Version: 2.20.1

What were you doing when the application crashed?
kill beagled


Distribution: Debian 3.1 (sarge)
Gnome Release: 2.20.1 2007-10-26 (Debian)
BugBuddy Version: 2.20.1

System: Linux 2.6.22-2-amd64 #1 SMP Thu Aug 30 23:43:59 UTC 2007 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10400000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: gnome

Memory status: size: 300331008 vsize: 300331008 resident: 22450176 share: 13135872 rss: 22450176 rss_rlim: 18446744073709551615
CPU usage: start_time: 1195389278 rtime: 3144 utime: 2794 stime: 350 cutime:0 cstime: 14 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 "/lib/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0x2b11c016a2e0 (LWP 783)]
[New Thread 0x40040950 (LWP 4852)]
(no debugging symbols found)
0x00002b11b9c78c7f in waitpid () from /lib/libpthread.so.0

Thread 1 (Thread 0x2b11c016a2e0 (LWP 783))

  • #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 g_slist_remove
    from /usr/lib/libglib-2.0.so.0
  • #6 ??
    from /usr/lib/gnome-panel/libclock-applet.so
  • #7 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #8 ??
    from /usr/lib/libgobject-2.0.so.0
  • #9 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #10 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #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/libedataserver-1.2.so.9
  • #16 ??
    from /usr/lib/libORBit-2.so.0
  • #17 ??
    from /usr/lib/libORBit-2.so.0
  • #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 ---------------------
Error: Invalid Font Weight
Error: Invalid Font Weight
Error: Invalid Font Weight
Error: Invalid Font Weight
Error: Illegal entry in bfchar block in ToUnicode CMap
Error: Invalid Font Weight
Error: Illegal entry in bfchar block in ToUnicode CMap
Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x3000003 (Evince Doc)
Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
** (gnome-panel:783): WARNING **: The calendar backend for file:///home/compukid/.evolution/tasks/local/system has crashed.
** (gnome-panel:783): WARNING **: The calendar backend for webcal://compukid.no-ip.org/webcalendar/publish.php/compukid.ics has crashed.
** (gnome-panel:783): WARNING **: The calendar backend for file:///home/compukid/.evolution/tasks/local/system has crashed.
--------------------------------------------------
Comment 1 Susana 2007-11-23 22:53:28 UTC
Thanks for taking the time to report this bug.
Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Can you get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so and reopen this bug or report a new one. Thanks in advance!
Comment 2 Philip Withnall 2008-01-11 07:00:38 UTC

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