GNOME Bugzilla – Bug 487506
crash in Evolution:
Last modified: 2007-10-22 22:23:55 UTC
What were you doing when the application crashed? Distribution: Mandriva Linux release 2007.1 (Official) for i586 Gnome Release: 2.18.0 2007-03-15 (Mandriva) BugBuddy Version: 2.18.0 System: Linux 2.6.17-13mdvlegacy #1 SMP Fri Mar 23 19:05:24 UTC 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 70200000 Selinux: No Accessibility: Disabled GTK+ Theme: Ia Ora Orange Icon Theme: gnome Memory status: size: 193630208 vsize: 193630208 resident: 24293376 share: 18087936 rss: 24293376 rss_rlim: 4294967295 CPU usage: start_time: 1192629567 rtime: 91 utime: 79 stime: 12 cutime:0 cstime: 3 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/i686/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1237137696 (LWP 8071)] [New Thread -1388913760 (LWP 8145)] [New Thread -1380521056 (LWP 8144)] [New Thread -1372128352 (LWP 8142)] [New Thread -1363514464 (LWP 8140)] [New Thread -1355121760 (LWP 8122)] [New Thread -1304478816 (LWP 8114)] [New Thread -1295692896 (LWP 8113)] [New Thread -1243341920 (LWP 8111)] (no debugging symbols found) 0xbfffe410 in __kernel_vsyscall ()
+ Trace 170849
Thread 1 (Thread -1237137696 (LWP 8071))
----------- .xsession-errors --------------------- evolution-shell-Message: Killing old version of evolution-data-server... ** (evolution:8071): DEBUG: mailto URL command: evolution %s ** (evolution:8071): DEBUG: mailto URL program: evolution X Error: BadMatch (invalid parameter attributes) 8 Major opcode: 157 Minor opcode: 6 Resource id: 0x5d X Error: BadMatch (invalid parameter attributes) 8 Major opcode: 157 Minor opcode: 6 Resource id: 0x5d X Error: BadMatch (invalid parameter attributes) 8 Major opcode: 157 Minor opcode: 6 Resource id: 0x5d --------------------------------------------------
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 364700 ***