GNOME Bugzilla – Bug 573390
crash in Evolution Mail and Calendar: again printing; I think ...
Last modified: 2009-02-27 13:45:10 UTC
What were you doing when the application crashed? again printing; I think it is more complete now 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: 214691840 vsize: 214691840 resident: 36827136 share: 22261760 rss: 36827136 rss_rlim: 18446744073709551615 CPU usage: start_time: 1235739776 rtime: 798 utime: 700 stime: 98 cutime:5 cstime: 26 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/evolution' [Thread debugging using libthread_db enabled] [New Thread 0xb8045980 (LWP 19187)] [New Thread 0xb1e08b90 (LWP 19221)] [New Thread 0xb320eb90 (LWP 19219)] 0x0099f416 in __kernel_vsyscall ()
+ Trace 212958
Thread 1 (Thread 0xb8045980 (LWP 19187))
----------- .xsession-errors (44 sec old) --------------------- Starting playback... VDec: vo config request - 320 x 240 (preferred colorspace: Planar YV12) [PP] Using external postprocessing filter, max q = 6. VDec: using Planar YV12 as output csp (no 0) Movie-Aspect is undefined - no prescaling applied. [swscaler @ 0x8702b00]No accelerated colorspace conversion found. [swscaler @ 0x8702b00]using unscaled yuv420p -> rgb24 special converter VO: [x11] 320x240 => 320x240 Planar YV12 [zoom] Resizing to 320 x 240 ERROR: Failed to get value of property 'chapters'. ERROR: Failed to get value of property 'sub_demux'. [Mixer] No hardware mixing, inserting volume filter. Exiting... (Quit) Thread completing --------------------------------------------------
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 ***