GNOME Bugzilla – Bug 433543
crash in Tasks: Just started Evolution f...
Last modified: 2007-04-26 11:16:54 UTC
What were you doing when the application crashed? Just started Evolution from the menu. Distribution: Fedora release 6.93 (Rawhide) Gnome Release: 2.18.0 2007-03-23 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.20-1.3104.fc7 #1 SMP Sat Apr 21 22:20:43 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10299905 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 37621760 vsize: 37621760 resident: 11784192 share: 9678848 rss: 11784192 rss_rlim: 4294967295 CPU usage: start_time: 1177581096 rtime: 29 utime: 12 stime: 17 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/evolution' (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 -1208744224 (LWP 2687)] (no debugging symbols found) 0x00efb402 in __kernel_vsyscall ()
+ Trace 130654
Thread 1 (Thread -1208744224 (LWP 2687))
----------- .xsession-errors --------------------- (nm-vpn-properties:2653): Gtk-WARNING **: gtk_widget_size_allocate(): attempt to allocate widget with width -5 and height -7 (nm-vpn-properties:2653): Gtk-WARNING **: gtk_widget_size_allocate(): attempt to allocate widget with width -5 and height 1 (nm-vpn-properties:2653): Gtk-WARNING **: gtk_widget_size_allocate(): attempt to allocate widget with width -7 and height -2 (nm-vpn-properties:2653): Gtk-WARNING **: gtk_widget_size_allocate(): attempt to allocate widget with width -14 and height 1 (nm-vpn-properties:2653): Gtk-WARNING **: gtk_widget_size_allocate(): attempt to allocate widget with width -14 and height 1 (nm-vpn-properties:2653): Gtk-WARNING **: gtk_widget_size_allocate(): attempt to allocate widget with width -14 and height -2 (nm-vpn-properties:2653): Gtk-WARNING **: gtk_widget_size_allocate(): attempt to allocate widget with width -14 and height 1 CalDAV Eplugin starting up ... CalDAV Eplugin starting up ... --------------------------------------------------
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. Thanks in advance!
Here's the updated stacktrace. Hope it helps. Distribution: Fedora release 6.93 (Rawhide) Gnome Release: 2.18.0 2007-03-23 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.20-1.3104.fc7 #1 SMP Sat Apr 21 22:20:43 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10299905 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 37625856 vsize: 37625856 resident: 11780096 share: 9678848 rss: 11780096 rss_rlim: 4294967295 CPU usage: start_time: 1177585994 rtime: 27 utime: 9 stime: 18 cutime:0 cstime: 9 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/evolution' Using host libthread_db library "/lib/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread -1208564000 (LWP 3191)] 0x0080a402 in __kernel_vsyscall ()
+ Trace 130684
Thread 1 (Thread -1208564000 (LWP 3191))
----------- .xsession-errors (7 sec old) --------------------- (gnome-terminal:2694): Vte-WARNING **: Can not find appropiate font for character U+ac04. (gnome-terminal:2694): Vte-WARNING **: Can not find appropiate font for character U+ac08. (gnome-terminal:2694): Vte-WARNING **: Can not find appropiate font for character U+ac10. CalDAV Eplugin starting up ... CalDAV Eplugin starting up ... CalDAV Eplugin starting up ... CalDAV Eplugin starting up ... CalDAV Eplugin starting up ... --------------------------------------------------
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find. *** This bug has been marked as a duplicate of 427232 ***