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 505814 - crash in Panel: Push on clock to view th...
crash in Panel: Push on clock to view th...
Status: RESOLVED INCOMPLETE
Product: gnome-panel
Classification: Other
Component: general
unspecified
Other All
: High critical
: ---
Assigned To: Panel Maintainers
Panel Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-12-26 23:08 UTC by ogrobf
Modified: 2008-01-09 21:40 UTC
See Also:
GNOME target: ---
GNOME version: 2.19/2.20



Description ogrobf 2007-12-26 23:08:16 UTC
Version: 2.20.0.1

What were you doing when the application crashed?
Push on clock to view the calendar.


Distribution: Debian lenny/sid
Gnome Release: 2.20.2 2007-11-29 (Debian)
BugBuddy Version: 2.20.1

System: Linux 2.6.18.1 #1 Mon Oct 23 21:29:45 CEST 2006 i686
X Vendor: The X.Org Foundation
X Vendor Release: 70000000
Selinux: Permissive
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: gnome

Memory status: size: 33824768 vsize: 33824768 resident: 19574784 share: 13090816 rss: 19574784 rss_rlim: 4294967295
CPU usage: start_time: 1198663070 rtime: 6735 utime: 6217 stime: 518 cutime:0 cstime: 2 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/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1225271632 (LWP 2335)]
[New Thread -1236112496 (LWP 20140)]
(no debugging symbols found)
0xb7f77410 in ?? ()


----------- .xsession-errors ---------------------
** (nautilus:2334): WARNING **: Could not initialize hal context
Shutting down gnome-mount extension
** Message: failed to load session from /home/ogro/.nautilus/saved-session-DX1ZUT
Gtk-WARNING **: Failed to load module "libgnomebreakpad.so": libgnomebreakpad.so: no se puede abrir el fichero del objeto compartido: No existe el fichero o el directorio
Advertencia del gestor de ventanas: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x2800003 (Visor de d)
Advertencia del gestor de ventanas: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
Advertencia del gestor de ventanas: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x2000058 (Lista de a)
Advertencia del gestor de ventanas: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
Advertencia del gestor de ventanas: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x2000058 (Lista de a)
Advertencia del gestor de ventanas: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
Advertencia del gestor de ventanas: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x2000003 (Visor de d)
Advertencia del gestor de ventanas: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
Failed to read a valid object file image from memory.
--------------------------------------------------
Comment 1 Philip Withnall 2008-01-09 21:40:06 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!