GNOME Bugzilla – Bug 494803
crash in Tasks: Just started the applica...
Last modified: 2007-11-11 12:08:10 UTC
Version: 2.10 What were you doing when the application crashed? Just started the application. It was going to get my new e-mail. 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.22.9-91.fc7 #1 SMP Thu Sep 27 23:10:59 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: Enforcing Accessibility: Disabled GTK+ Theme: Bluecurve Icon Theme: Bluecurve Memory status: size: 154107904 vsize: 154107904 resident: 40660992 share: 32088064 rss: 40660992 rss_rlim: 4294967295 CPU usage: start_time: 1194481055 rtime: 111 utime: 99 stime: 12 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 -1208613152 (LWP 26435)] [New Thread -1291867248 (LWP 26458)] [New Thread -1270887536 (LWP 26447)] [New Thread -1249907824 (LWP 26444)] [New Thread -1227265136 (LWP 26442)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 176190
Thread 1 (Thread -1208613152 (LWP 26435))
----------- .xsession-errors --------------------- Minor opcode: 0 Resource id: 0x1c0000e WARNING: DCOPReply<>: cast to 'QStringList' error WARNING: DCOPReply<>: cast to 'QString' error CalDAV Eplugin starting up ... ** (evolution:26435): DEBUG: mailto URL command: evolution --component=mail %s ** (evolution:26435): DEBUG: mailto URL program: evolution X Error: BadMatch (invalid parameter attributes) 8 Major opcode: 157 Minor opcode: 6 Resource id: 0x3f X Error: BadMatch (invalid parameter attributes) 8 Major opcode: 157 Minor opcode: 6 Resource id: 0x3f --------------------------------------------------
Thanks for taking the time to report this bug. This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade. *** This bug has been marked as a duplicate of 431459 ***