Bug 513469 – crash in Tasks:

After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.

Bug 513469 - crash in Tasks:


Summary:	crash in Tasks:


Status:	RESOLVED DUPLICATE of bug 445309

Product:	evolution
Classification:	Applications
Component:	BugBuddyBugs
Version:	2.10.x (obsolete)
Hardware:	Other All

Importance:	High critical
Target Milestone:	---
Assigned To:	Evolution Triage Team
QA Contact:	Evolution QA team

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2008-01-31 15:57 UTC by booger
Modified:	2008-02-01 14:38 UTC

See Also:
GNOME target:	---
GNOME version:	2.17/2.18

Description booger 2008-01-31 15:57:47 UTC

Version: 2.10

What were you doing when the application crashed?



Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.3 2007-11-13 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.23.12-52.fc7 #1 SMP Tue Dec 18 21:18:02 EST 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Bluecurve-Lime
Icon Theme: Crux

Memory status: size: 140660736 vsize: 140660736 resident: 53358592 share: 34086912 rss: 53358592 rss_rlim: 4294967295
CPU usage: start_time: 1201763419 rtime: 3631 utime: 2910 stime: 721 cutime:259 cstime: 30 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/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1208498464 (LWP 378)]
[New Thread -1305244784 (LWP 2759)]
[New Thread -1315734640 (LWP 2626)]
[New Thread -1276425328 (LWP 413)]
(no debugging symbols found)
0x00110402 in __kernel_vsyscall ()

+ Trace 187605

Thread 2 (Thread -1305244784 (LWP 2759))

#0 __kernel_vsyscall
#1 __lll_mutex_lock_wait
from /lib/libpthread.so.0
#2 _L_mutex_lock_79
from /lib/libpthread.so.0
#3 pthread_mutex_lock
from /lib/libpthread.so.0
#4 ??
#5 <signal handler called>
#6 pthread_mutex_lock
from /lib/libpthread.so.0
#7 PR_Lock
from /usr/lib/libnspr4.so
#8 ??
from /usr/lib/libnspr4.so
#9 __nptl_deallocate_tsd
from /lib/libpthread.so.0
#10 start_thread
from /lib/libpthread.so.0
#11 clone
from /lib/libc.so.6



----------- .xsession-errors (858391 sec old) ---------------------
Selected video codec: [ffwmv1] vfm: ffmpeg (FFmpeg M$ WMV1/WMV7)
==========================================================================
==========================================================================
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: [alsa] 48000Hz 2ch s16le (2 bytes per sample)
Starting playback...
VDec: vo config request - 320 x 240 (preferred colorspace: Planar YV12)
VDec: using Planar YV12 as output csp (no 0)
Movie-Aspect is undefined - no prescaling applied.
VO: [xv] 320x240 => 320x240 Planar YV12 
A:   3.3 V:   3.0 A-V:  0.272 ct:  0.000   1/  1 ??% ??% ??,?% 0 0              
A:   3.3 V:   3.0 A-V:  0.223 ct: -0.004   2/  2 ??% ??% ??,?% 1 0              
A:   3.3 V:   3.1 A-V:  0.185 ct: -0.0
...Too much output, ignoring rest...
--------------------------------------------------

Comment 1 Tobias Mueller 2008-02-01 14:38:56 UTC

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 445309 ***