GNOME Bugzilla – Bug 456433
crash in Evolution: starting evolution mail
Last modified: 2007-07-17 00:42:38 UTC
What were you doing when the application crashed? starting evolution mail 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: 129241088 vsize: 129241088 resident: 22769664 share: 16334848 rss: 22769664 rss_rlim: 4294967295 CPU usage: start_time: 1184285661 rtime: 91 utime: 81 stime: 10 cutime:2 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 -1237408032 (LWP 4510)] [New Thread -1324385376 (LWP 4557)] [New Thread -1297101920 (LWP 4556)] [New Thread -1271923808 (LWP 4554)] [New Thread -1288709216 (LWP 4535)] [New Thread -1280316512 (LWP 4532)] [New Thread -1261708384 (LWP 4530)] (no debugging symbols found) 0xbfffe410 in __kernel_vsyscall ()
+ Trace 147664
Thread 1 (Thread -1237408032 (LWP 4510))
----------- .xsession-errors --------------------- SIOCETHTOOL: Operation not permitted SIOCETHTOOL: Operation not permitted getting exclusive lock on urpmi unlocking urpmi database medium "update_source" is up-to-date medium "update_source2" is up-to-date medium "update_source3" is up-to-date X Error: BadWindow (invalid Window parameter) 3 Major opcode: 20 Minor opcode: 0 Resource id: 0x2600077 CalDAV Eplugin starting up ... evolution-shell-Message: Killing old version of evolution-data-server... ** (evolution:4510): DEBUG: mailto URL command: evolution %s ** (evolution:4510): DEBUG: mailto URL program: evolution --------------------------------------------------
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 431459 ***