Bug 421006 – crash in Evolution: opened gmail junk folder...

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 421006 - crash in Evolution: opened gmail junk folder...


Summary:	crash in Evolution: opened gmail junk folder...


Status:	RESOLVED DUPLICATE of bug 371586

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-03-21 13:41 UTC by dorrit.novel
Modified:	2007-08-18 15:26 UTC

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

Description dorrit.novel 2007-03-21 13:41:35 UTC

What were you doing when the application crashed?
opened gmail junk folder to see if junk was correctly registered. 25 correct junk mails were found.


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

Memory status: size: 143380480 vsize: 0 resident: 143380480 share: 0 rss: 25219072 rss_rlim: 0
CPU usage: start_time: 1174484310 rtime: 0 utime: 120 stime: 0 cutime:110 cstime: 0 timeout: 10 it_real_value: 0 frequency: 0

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

Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread -1232476496 (LWP 6587)]
[New Thread -1336906848 (LWP 6609)]
[New Thread -1279263840 (LWP 6604)]
[New Thread -1296049248 (LWP 6600)]
[New Thread -1287656544 (LWP 6599)]
[New Thread -1269212256 (LWP 6594)]
0xffffe410 in __kernel_vsyscall ()

+ Trace 120759

Thread 1 (Thread -1232476496 (LWP 6587))

#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 segv_redirect
at main.c line 426
#4 <signal handler called>
#5 g_slice_alloc
from /usr/lib/libglib-2.0.so.0
#6 g_slice_alloc0
from /usr/lib/libglib-2.0.so.0
#7 g_type_create_instance
from /usr/lib/libgobject-2.0.so.0
#8 g_object_set
from /usr/lib/libgobject-2.0.so.0
#9 g_object_newv
from /usr/lib/libgobject-2.0.so.0
#10 g_object_new_valist
from /usr/lib/libgobject-2.0.so.0
#11 g_object_new
from /usr/lib/libgobject-2.0.so.0
#12 e_list_iterator_new
from /usr/lib/libedataserver-1.2.so.7
#13 e_list_get_iterator
from /usr/lib/libedataserver-1.2.so.7
#14 mail_config_get_account_by_source_url
at mail-config.c line 642
#15 em_uri_from_camel
at em-utils.c line 1817
#16 mail_vfolder_add_uri
at mail-vfolder.c line 444
#17 real_flush_updates
at mail-folder-cache.c line 228
#18 do_async_event
at mail-mt.c line 676
#19 idle_async_event
at mail-mt.c line 687
#20 g_source_is_destroyed
from /usr/lib/libglib-2.0.so.0
#21 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#22 g_main_context_check
from /usr/lib/libglib-2.0.so.0
#23 g_main_loop_run
from /usr/lib/libglib-2.0.so.0
#24 bonobo_main
from /usr/lib/libbonobo-2.so.0
#25 main
at main.c line 615
#0 __kernel_vsyscall

Comment 1 palfrey 2007-04-26 13:54:46 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-05-30 14:25:05 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!

Comment 3 André Klapper 2007-08-18 15:26:34 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 371586 ***