Bug 597863 – crash in Evolution: Opened an email

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 597863 - crash in Evolution: Opened an email


Summary:	crash in Evolution: Opened an email


Status:	RESOLVED DUPLICATE of bug 569700

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

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

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2009-10-08 23:11 UTC by sailor49
Modified:	2009-10-09 03:54 UTC

See Also:
GNOME target:	---
GNOME version:	2.23/2.24

Description sailor49 2009-10-08 23:11:59 UTC

What were you doing when the application crashed?
Opened an email


Distribution: SUSE Linux Enterprise Desktop 11 (x86_64)
Gnome Release: 2.24.1 2009-06-27 (SUSE)
BugBuddy Version: 2.24.1

System: Linux 2.6.27.29-0.1-default #1 SMP 2009-08-15 17:53:59 +0200 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10502000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Gilouche
Icon Theme: Gilouche

Memory status: size: 741154816 vsize: 741154816 resident: 41865216 share: 24227840 rss: 41865216 rss_rlim: 18446744073709551615
CPU usage: start_time: 1255043093 rtime: 686 utime: 620 stime: 66 cutime:0 cstime: 2 timeout: 0 it_real_value: 0 frequency: 100

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

[?1034h[Thread debugging using libthread_db enabled]
[New Thread 0x7f5cdf316950 (LWP 5436)]
[New Thread 0x7f5cd3981950 (LWP 5320)]
[New Thread 0x7f5cde109950 (LWP 5319)]
[New Thread 0x7f5cce088950 (LWP 5304)]
[New Thread 0x7f5cd458d950 (LWP 5301)]
[New Thread 0x7f5cdd107950 (LWP 5300)]
[New Thread 0x7f5cdeb15950 (LWP 5293)]
[New Thread 0x7f5cdfb17950 (LWP 5290)]
0x00007f5cf3c8c5af in waitpid () from /lib64/libpthread.so.0

+ Trace 218166

Thread 2 (Thread 0x7f5cdf316950 (LWP 5436))

#0 __lll_lock_wait
from /lib64/libpthread.so.0
#1 _L_lock_102
from /lib64/libpthread.so.0
#2 pthread_mutex_lock
from /lib64/libpthread.so.0
#3 <signal handler called>
#4 camel_mime_parser_read
at camel-mime-parser.c line 655
#5 stream_read
at camel-http-stream.c line 487
#6 emfh_gethttp
at em-format-html.c line 529
#7 efh_format_exec
at em-format-html.c line 1302
#8 mail_msg_proxy
at mail-mt.c line 520
#9 ??
from /usr/lib64/libglib-2.0.so.0
#10 ??
from /usr/lib64/libglib-2.0.so.0
#11 start_thread
from /lib64/libpthread.so.0
#12 clone
from /lib64/libc.so.6
#13 ??



----------- .xsession-errors (2194 sec old) ---------------------
Initializing nautilus-open-terminal extension
** (nautilus:3669): WARNING **: Unable to add monitor: Not supported
Nautilus-Share-Message: REFRESHING SHARES
Nautilus-Share-Message: ------------------------------------------
Nautilus-Share-Message: spawn arg "net"
Nautilus-Share-Message: spawn arg "usershare"
Nautilus-Share-Message: spawn arg "info"
Nautilus-Share-Message: end of spawn args; SPAWNING
Nautilus-Share-Message: returned from spawn: SUCCESS: 
Nautilus-Share-Message: exit code 255
Nautilus-Share-Message: ------------------------------------------
Nautilus-Share-Message: Called "net usershare info" but it failed: 'net usershare' returned error 255: net usershare: usershares are currently disabled
--------------------------------------------------

Comment 1 Akhil Laddha 2009-10-09 03:54:39 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 bug 569700 ***