GNOME Bugzilla – Bug 616188
crash in Evolution Mail: Reviewing a patch in a p...
Last modified: 2010-04-19 23:38:07 UTC
What were you doing when the application crashed? Reviewing a patch in a preview, the "checking for new mail" started too. Distribution: Debian squeeze/sid Gnome Release: 2.28.2 2009-12-18 (Debian) BugBuddy Version: 2.28.0 System: Linux 2.6.32-trunk-amd64 #1 SMP Sun Jan 10 07:51:13 UTC 2010 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10705000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: gnome GTK+ Modules: gnomebreakpad, canberra-gtk-module Memory status: size: 808140800 vsize: 808140800 resident: 392560640 share: 15179776 rss: 392560640 rss_rlim: 18446744073709551615 CPU usage: start_time: 1269610961 rtime: 438701 utime: 391968 stime: 46733 cutime:3 cstime: 108 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/evolution' [Thread debugging using libthread_db enabled] [New Thread 0xdc2f3b70 (LWP 5699)] [New Thread 0xde2f7b70 (LWP 5691)] [New Thread 0xeb6feb70 (LWP 14755)] [New Thread 0xe64fbb70 (LWP 14754)] [New Thread 0xef8c6b70 (LWP 19766)] [New Thread 0xee68fb70 (LWP 19765)] [New Thread 0xf047fb70 (LWP 19701)] [New Thread 0xf26fdb70 (LWP 19698)] [New Thread 0xf2efeb70 (LWP 19696)] [New Thread 0xf36ffb70 (LWP 19695)] [New Thread 0xf4854b70 (LWP 19693)] [New Thread 0xf5055b70 (LWP 19692)] 0xf77b1425 in __kernel_vsyscall ()
+ Trace 221453
Thread 3 (Thread 0xde2f7b70 (LWP 5691))
Inferior 1 [process 19685] will be detached. Quit anyway? (y or n) [answered Y; input not from terminal] ---- Critical and fatal warnings logged during execution ---- ** GLib-GObject **: g_signal_emit_valist: assertion `G_TYPE_CHECK_INSTANCE (instance)' failed ** GLib-GObject **: g_object_unref: assertion `G_IS_OBJECT (object)' failed ** GLib-GObject **: g_object_unref: assertion `G_IS_OBJECT (object)' failed ** GLib-GObject **: g_object_ref: assertion `G_IS_OBJECT (object)' failed ** GLib-GObject **: g_signal_emit_valist: assertion `G_TYPE_CHECK_INSTANCE (instance)' failed ** GLib-GObject **: g_object_unref: assertion `G_IS_OBJECT (object)' failed ** GLib-GObject **: g_object_unref: assertion `G_IS_OBJECT (object)' failed ** GLib-GObject **: g_object_ref: assertion `G_IS_OBJECT (object)' failed ** GLib-GObject **: g_signal_emit_valist: assertion `G_TYPE_CHECK_INSTANCE (instance)' failed ** GLib-GObject **: g_object_unref: assertion `G_IS_OBJECT (object)' failed ** GLib-GObject **: g_object_unref: assertion `G_IS_OBJECT (object)' failed ** GLib-GObject **: g_object_ref: assertion `G_IS_OBJECT (object)' failed ** GLib-GObject **: g_signal_emit_valist: assertion `G_TYPE_CHECK_INSTANCE (instance)' failed ** GLib-GObject **: g_object_unref: assertion `G_IS_OBJECT (object)' failed ** GLib-GObject **: g_object_unref: assertion `G_IS_OBJECT (object)' failed ----------- .xsession-errors (1609004 sec old) --------------------- Opening video decoder: [ffmpeg] FFmpeg's libavcodec codec family Selected video codec: [ffwmv2] vfm: ffmpeg (FFmpeg WMV2/WMV8) ========================================================================== ========================================================================== Opening audio decoder: [ffmpeg] FFmpeg/libavcodec audio decoders AUDIO: 32000 Hz, 2 ch, s16le, 32.0 kbit/3.12% (ratio: 4000->128000) Selected audio codec: [ffwmav2] afm: ffmpeg (DivX audio v2 (FFmpeg)) ========================================================================== [AO OSS] audio_setup: Can't open audio device /dev/dsp: Device or resource busy AO: [alsa] 48000Hz 2ch s16le (2 bytes per sample) Starting playback... Movie-Aspect is undefined - no prescaling applied. VO: [xvidix] 320x240 => 320x240 Planar YV12 A: 3.3 V: 3.0 A-V: 0.277 ct: 0.000 1/ 1 ??% ??% ??,?% 0 0 A: 3.3 V: 3.1 A-V: 0.205 ct: -0.006 2/ 2 ??% ??% ??,?% 1 0 A: 3.4 V: 3.9 A-V: -0.505 ct: -0.0 ...Too much output, ignoring rest... --------------------------------------------------
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 bug 600322 ***