GNOME Bugzilla – Bug 573388
crash in Evolution Mail and Calendar: printing
Last modified: 2009-02-27 13:46:10 UTC
What were you doing when the application crashed? printing Distribution: Fedora release 10 (Cambridge) Gnome Release: 2.24.3 2009-01-16 (Red Hat, Inc) BugBuddy Version: 2.24.2 System: Linux 2.6.27.15-170.2.24.fc10.i686 #1 SMP Wed Feb 11 23:58:12 EST 2009 i686 X Vendor: The X.Org Foundation X Vendor Release: 10503000 Selinux: Enforcing Accessibility: Disabled GTK+ Theme: Nodoka Icon Theme: oxygen Memory status: size: 191909888 vsize: 191909888 resident: 35713024 share: 22122496 rss: 35713024 rss_rlim: 18446744073709551615 CPU usage: start_time: 1235739642 rtime: 541 utime: 452 stime: 89 cutime:6 cstime: 23 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/evolution' [Thread debugging using libthread_db enabled] [New Thread 0xb7edd980 (LWP 18937)] [New Thread 0xb6fffb90 (LWP 18980)] 0x00dcb416 in __kernel_vsyscall ()
+ Trace 212957
Thread 1 (Thread 0xb7edd980 (LWP 18937))
----------- .xsession-errors (34 sec old) --------------------- [swscaler @ 0x8702b00]using unscaled yuv420p -> rgb24 special converter VO: [x11] 248x192 => 248x192 Planar YV12 [zoom] Resizing to 248 x 192 ERROR: Failed to get value of property 'chapters'. ERROR: Failed to get value of property 'sub_demux'. [Mixer] No hardware mixing, inserting volume filter. shutting down threadquery for /home/gcraciun/.cache/gnome-mplayer/plugin/gecko-mediaplayerfjaqdv since threaddata->done is TRUE Exiting... (Quit) Thread completing error : unterminated entity reference T error : unterminated entity reference SNR evolution-shell-Message: Killing old version of evolution-data-server... ** (evolution:18937): DEBUG: mailto URL command: evolution --component=mail %s ** (evolution:18937): DEBUG: mailto URL program: evolution --------------------------------------------------
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 569892 ***