Bug 427828 – crash in Evolution: JE NE SAIS PAS

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 427828 - crash in Evolution: JE NE SAIS PAS


Summary:	crash in Evolution: JE NE SAIS PAS


Status:	RESOLVED DUPLICATE of bug 352284

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:	2007-04-09 11:10 UTC by alainseiller44
Modified:	2007-04-09 13:07 UTC

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

Description alainseiller44 2007-04-09 11:10:26 UTC

What were you doing when the application crashed?
JE NE SAIS PAS


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

Memory status: size: 749920256 vsize: 0 resident: 749920256 share: 0 rss: 35594240 rss_rlim: 0
CPU usage: start_time: 1176107582 rtime: 0 utime: 9092 stime: 0 cutime:4543 cstime: 0 timeout: 4549 it_real_value: 0 frequency: 0

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

(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1233221968 (LWP 4715)]
[New Thread -1348527200 (LWP 10534)]
[New Thread -1340134496 (LWP 10533)]
[New Thread -1356919904 (LWP 10516)]
[New Thread -1373807712 (LWP 10385)]
[New Thread -1330005088 (LWP 4729)]
[New Thread -1321612384 (LWP 4728)]
[New Thread -1313219680 (LWP 4727)]
[New Thread -1271657568 (LWP 4723)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 126246

Thread 8 (Thread -1313219680 (LWP 4727))

#0 __kernel_vsyscall
#1 waitpid
from /lib/tls/i686/cmov/libc.so.6
#2 gnome_gtk_module_info_get
from /usr/lib/libgnomeui-2.so.0
#3 <signal handler called>
#4 __kernel_vsyscall
#5 raise
from /lib/tls/i686/cmov/libc.so.6
#6 abort
from /lib/tls/i686/cmov/libc.so.6
#7 g_logv
from /usr/lib/libglib-2.0.so.0
#8 g_log
from /usr/lib/libglib-2.0.so.0
#9 g_realloc
from /usr/lib/libglib-2.0.so.0
#10 g_ptr_array_new
from /usr/lib/libglib-2.0.so.0
#11 g_array_append_vals
from /usr/lib/libglib-2.0.so.0
#12 g_byte_array_append
from /usr/lib/libglib-2.0.so.0
#13 camel_mime_part_construct_content_from_parser
from /usr/lib/libcamel-1.2.so.8
#14 camel_mime_part_construct_from_parser
from /usr/lib/libcamel-1.2.so.8
#15 camel_mime_part_construct_from_parser
from /usr/lib/libcamel-1.2.so.8
#16 camel_multipart_new
from /usr/lib/libcamel-1.2.so.8
#17 camel_multipart_construct_from_parser
from /usr/lib/libcamel-1.2.so.8
#18 camel_mime_part_construct_content_from_parser
from /usr/lib/libcamel-1.2.so.8
#19 camel_mime_part_construct_from_parser
from /usr/lib/libcamel-1.2.so.8
#20 camel_mime_message_new
from /usr/lib/libcamel-1.2.so.8
#21 camel_mime_part_construct_from_parser
from /usr/lib/libcamel-1.2.so.8
#22 camel_mbox_folder_new
from /usr/lib/evolution-data-server-1.2/camel-providers-8/libcamellocal.so
#23 camel_folder_get_message
from /usr/lib/libcamel-provider-1.2.so.8
#24 camel_folder_append_message
from /usr/lib/libcamel-provider-1.2.so.8
#25 camel_folder_transfer_messages_to
from /usr/lib/libcamel-provider-1.2.so.8
#26 em_utils_selection_get_uidlist
from /usr/lib/evolution/2.8/components/libevolution-mail.so
#27 em_folder_tree_set_multiselect
from /usr/lib/evolution/2.8/components/libevolution-mail.so
#28 mail_enable_stop
from /usr/lib/evolution/2.8/components/libevolution-mail.so
#29 e_msgport_reply
from /usr/lib/libedataserver-1.2.so.7
#30 start_thread
from /lib/tls/i686/cmov/libpthread.so.0
#31 clone
from /lib/tls/i686/cmov/libc.so.6

Comment 1 Pedro Villavicencio 2007-04-09 13:07:41 UTC

Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.


*** This bug has been marked as a duplicate of 352284 ***