evolution crashed with SIGSEGV in pthread_mutex_lock()

[marco.pallotta]

Binary package hint: evolution

Evolution crashes after login (without launching it)

ProblemType: Crash
Architecture: amd64
Date: Mon May 25 23:27:23 2009
DistroRelease: Ubuntu 8.04
ExecutablePath: /usr/bin/evolution
Package: evolution 2.22.3.1-0ubuntu1
PackageArchitecture: amd64
ProcCmdline: evolution
ProcEnviron:
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=it_IT.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: evolution
StacktraceTop:
 pthread_mutex_lock () from /lib/libpthread.so.0
 PR_Lock () from /usr/lib/libnspr4.so.0d
 ?? () from /usr/lib/libnspr4.so.0d
 __nptl_deallocate_tsd () from /lib/libpthread.so.0
 start_thread () from /lib/libpthread.so.0
Title: evolution crashed with SIGSEGV in pthread_mutex_lock()
Uname: Linux 2.6.24-24-generic x86_64
UserGroups: adm admin audio cdrom dialout dip floppy fuse lpadmin plugdev vboxusers video

[Pedro Villavicencio (pedro)]

Thanks for your bug report. Please try to obtain a backtrace http://wiki.ubuntu.com/DebuggingProgramCrash and attach the file to the bug report. This will greatly help us in tracking down your problem.

[marco.pallotta (marco-pallotta)]

Pedro, I have no way to obtain a backtrace as evolution crashed at system login but it wasn't launched by me. After having inserted my gdm login e password I saw the crash that I reported (but, I say again, without launching evolution).
The only thing I can do is posting more info next time the issue happens.

[Pedro Villavicencio (pedro)]

Ok let's wait to happens again then, without a backtrace there's not too much we can do either, it would help to post a few steps in order to reproduce the issue but you said that it only happens when you login, which works fine here and not a lot of people seems to have the same issue, it could be that evolution-data-server is crashing for example, but anyways let's wait for it to happens again. thanks marco.

[Sebastien Bacher (seb128)]

We are closing this bug report as it lacks the information, described in the previous comments, we need to investigate the problem further. However, please reopen it if you can give us the missing information and don't hesitate to submit bug reports in the future.