GNOME Bugzilla – Bug 486024
crash in Evolution: kde gestartet
Last modified: 2007-11-18 20:41:00 UTC
What were you doing when the application crashed? kde gestartet 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-14mdv #1 SMP Wed May 9 21:11:43 MDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 70200000 Selinux: No Accessibility: Disabled GTK+ Theme: Ia Ora Blue Icon Theme: gnome Memory status: size: 59940864 vsize: 59940864 resident: 5881856 share: 4710400 rss: 5881856 rss_rlim: 4294967295 CPU usage: start_time: 1192197431 rtime: 4 utime: 4 stime: 0 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/lib/evolution-data-server-1.10' (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 -1222371648 (LWP 4740)] [New Thread -1243182176 (LWP 4748)] [New Thread -1234789472 (LWP 4747)] [New Thread -1226130528 (LWP 4741)] (no debugging symbols found) 0xbfffe410 in __kernel_vsyscall ()
+ Trace 169730
Thread 1 (Thread -1222371648 (LWP 4740))
----------- .xsession-errors --------------------- SIOCETHTOOL: Die Operation ist nicht erlaubt SIOCETHTOOL: Die Operation ist nicht erlaubt CalDAV Eplugin starting up ... evolution-alarm-notify-Message: Setting timeout for 28969 1192226400 1192197431 evolution-alarm-notify-Message: Sat Oct 13 00:00:00 2007 evolution-alarm-notify-Message: Fri Oct 12 15:57:11 2007 evolution-shell-Message: Killing old version of evolution-data-server... ** (evolution:4698): DEBUG: mailto URL command: evolution %s ** (evolution:4698): DEBUG: mailto URL program: evolution X Error: BadMatch (invalid parameter attributes) 8 Major opcode: 159 Minor opcode: 6 Resource id: 0x84 --------------------------------------------------
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 426237 ***