GNOME Bugzilla – Bug 459463
crash in Tasks: Creating a new signature
Last modified: 2007-07-23 16:31:05 UTC
Version: 2.10 What were you doing when the application crashed? Creating a new signature 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.21-1.3228.fc7 #1 SMP Tue Jun 12 14:56:37 EDT 2007 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks_Cairo-Etiquette Icon Theme: nuoveXT.2.1 Memory status: size: 675442688 vsize: 675442688 resident: 59211776 share: 31232000 rss: 59211776 rss_rlim: 18446744073709551615 CPU usage: start_time: 1185181111 rtime: 431 utime: 399 stime: 32 cutime:2 cstime: 4 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/evolution' (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 46912499015984 (LWP 4564)] [New Thread 1084229968 (LWP 4659)] [New Thread 1105209680 (LWP 4658)] [New Thread 1115699536 (LWP 4657)] [New Thread 1094719824 (LWP 4600)] (no debugging symbols found) 0x00000036e980d97f in waitpid () from /lib64/libpthread.so.0
+ Trace 149906
Thread 1 (Thread 46912499015984 (LWP 4564))
----------- .xsession-errors --------------------- (bug-buddy:4661): Gtk-WARNING **: Theme directory 32x32/filesystems of theme nuoveXT.2.1 has no size field (bug-buddy:4661): Gtk-WARNING **: Theme directory 48x48/filesystems of theme nuoveXT.2.1 has no size field (bug-buddy:4661): Gtk-WARNING **: Theme directory 64x64/filesystems of theme nuoveXT.2.1 has no size field (bug-buddy:4661): Gtk-WARNING **: Theme directory 72x72/filesystems of theme nuoveXT.2.1 has no size field (bug-buddy:4661): Gtk-WARNING **: Theme directory 96x96/filesystems of theme nuoveXT.2.1 has no size field --------------------------------------------------
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 430817 ***