GNOME Bugzilla – Bug 449518
crash in Email: Start evolution --compon...
Last modified: 2007-06-20 18:48:17 UTC
What were you doing when the application crashed? Start evolution --component=mail Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.0 2007-03-23 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.21-1.3194.fc7 #1 SMP Wed May 23 22:47:07 EDT 2007 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: Enforcing Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 462270464 vsize: 462270464 resident: 27787264 share: 16531456 rss: 27787264 rss_rlim: 18446744073709551615 CPU usage: start_time: 1182357121 rtime: 54 utime: 44 stime: 10 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 "/lib64/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 46912743963424 (LWP 5869)] (no debugging symbols found) 0x00002aaaad8bc865 in waitpid () from /lib64/libpthread.so.0
+ Trace 142457
Thread 1 (Thread 46912743963424 (LWP 5869))
----------- .xsession-errors --------------------- Xlib: extension "MIT-SCREEN-SAVER" missing on display ":0.0". CalDAV Eplugin starting up ... (evolution:5869): e-data-server-DEBUG: Loaded default categories ** (evolution:5869): DEBUG: mailto URL command: evolution --component=mail %s ** (evolution:5869): DEBUG: mailto URL program: evolution Xlib: extension "SHAPE" missing on display ":0.0". Xlib: extension "SHAPE" missing on display ":0.0". Xlib: extension "SHAPE" missing on display ":0.0". X Error: BadMatch (invalid parameter attributes) 8 Major opcode: 143 Minor opcode: 6 Resource id: 0x164 Xlib: extension "SHAPE" missing on display ":0.0". Xlib: extension "DPMS" missing on display ":0.0". Xlib: extension "MIT-SCREEN-SAVER" missing on display ":0.0". --------------------------------------------------
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 425129 ***