GNOME Bugzilla – Bug 440321
crash in Tasks: Using evolution to retri...
Last modified: 2007-06-11 11:53:44 UTC
What were you doing when the application crashed? Using evolution to retrieve my email 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.21-1.3167.fc7 #1 SMP Thu May 17 23:05:53 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: Permissive Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 108388352 vsize: 108388352 resident: 29007872 share: 18931712 rss: 29007872 rss_rlim: 4294967295 CPU usage: start_time: 1179793077 rtime: 293 utime: 269 stime: 24 cutime:0 cstime: 2 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 -1208797472 (LWP 3433)] [New Thread -1336456304 (LWP 3507)] [New Thread -1281811568 (LWP 3502)] (no debugging symbols found) 0x00740402 in __kernel_vsyscall ()
+ Trace 135433
Thread 1 (Thread -1208797472 (LWP 3433))
----------- .xsession-errors (11 sec old) --------------------- ** Message: GetValue variable 2 (2) ** Message: GetValue variable 1 (1) ** Message: GetValue variable 2 (2) ** Message: GetValue variable 1 (1) ** Message: GetValue variable 2 (2) ** Message: GetValue variable 1 (1) ** Message: GetValue variable 2 (2) ** Message: Found best visual for GL: 0x23 CalDAV Eplugin starting up ... ** (evolution:3433): DEBUG: mailto URL command: evolution --component=mail %s ** (evolution:3433): DEBUG: mailto URL program: evolution (evolution:3433): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0 (evolution:3433): e-data-server-ui-WARNING **: Key file does not have group 'Passwords-Mail' (evolution:3433): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0 --------------------------------------------------
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!
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 373699 ***