Bug 388588 – crash in Evolution: E-mail ophalen

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 388588 - crash in Evolution: E-mail ophalen


Summary:	crash in Evolution: E-mail ophalen


Status:	RESOLVED INCOMPLETE

Product:	evolution
Classification:	Applications
Component:	general
Version:	2.8.x (obsolete)
Hardware:	Other All

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

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2006-12-22 11:49 UTC by lazowesterhof
Modified:	2007-02-19 12:36 UTC

See Also:
GNOME target:	---
GNOME version:	2.15/2.16

Description lazowesterhof 2006-12-22 11:49:07 UTC

What were you doing when the application crashed?
E-mail ophalen


Distribution: Ubuntu 6.10 (edgy)
Gnome Release: 2.16.1 2006-10-02 (Ubuntu)
BugBuddy Version: 2.16.0

Memory status: size: 265506816 vsize: 265506816 resident: 30511104 share: 18702336 rss: 30511104 rss_rlim: -1
CPU usage: start_time: 1166788121 rtime: 114 utime: 105 stime: 9 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/usr/bin/evolution-2.8'

(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 47391201111376 (LWP 16759)]
[New Thread 1115703632 (LWP 16781)]
[New Thread 1107310928 (LWP 16780)]
[New Thread 1098918224 (LWP 16779)]
[New Thread 1090525520 (LWP 16771)]
[New Thread 1082132816 (LWP 16768)]
(no debugging symbols found)
0x00002b1a1b6935cf in waitpid () from /lib/libc.so.6

+ Trace 96213

Thread 6 (Thread 1082132816 (LWP 16768))

#0 __lll_mutex_lock_wait
from /lib/libpthread.so.0
#1 default_attr
from /lib/libpthread.so.0
#2 ??

Thread 5 (Thread 1090525520 (LWP 16771))

#0 select
from /lib/libc.so.6
#1 e_msgport_wait
from /usr/lib64/libedataserver-1.2.so.7
#2 e_msgport_reply
from /usr/lib64/libedataserver-1.2.so.7
#3 start_thread
from /lib/libpthread.so.0
#4 clone
from /lib/libc.so.6
#5 ??

Thread 4 (Thread 1098918224 (LWP 16779))

#0 select
from /lib/libc.so.6
#1 e_msgport_wait
from /usr/lib64/libedataserver-1.2.so.7
#2 e_msgport_reply
from /usr/lib64/libedataserver-1.2.so.7
#3 start_thread
from /lib/libpthread.so.0
#4 clone
from /lib/libc.so.6
#5 ??

Thread 3 (Thread 1107310928 (LWP 16780))

#0 select
from /lib/libc.so.6
#1 e_msgport_wait
from /usr/lib64/libedataserver-1.2.so.7
#2 e_msgport_reply
from /usr/lib64/libedataserver-1.2.so.7
#3 start_thread
from /lib/libpthread.so.0
#4 clone
from /lib/libc.so.6
#5 ??

Thread 2 (Thread 1115703632 (LWP 16781))

#0 select
from /lib/libc.so.6
#1 e_msgport_wait
from /usr/lib64/libedataserver-1.2.so.7
#2 e_msgport_reply
from /usr/lib64/libedataserver-1.2.so.7
#3 start_thread
from /lib/libpthread.so.0
#4 clone
from /lib/libc.so.6
#5 ??

Comment 1 Kjartan Maraas 2007-01-16 12:06:53 UTC

Thanks for taking the time to report this bug.
Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Can you get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so. Thanks in advance!

Comment 2 Bruno Boaventura 2007-02-19 12:36:33 UTC

Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for.
Thanks!