Bug 436199 – Crash when moving a message between IMAP folders

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 436199 - Crash when moving a message between IMAP folders


Summary:	Crash when moving a message between IMAP folders


Status:	RESOLVED DUPLICATE of bug 481699

Product:	evolution
Classification:	Applications
Component:	Mailer
Version:	2.10.x (obsolete)
Hardware:	Other Linux

Importance:	Normal critical
Target Milestone:	---
Assigned To:	evolution-mail-maintainers
QA Contact:	Evolution QA team

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2007-05-05 20:53 UTC by Milan Bouchet-Valat
Modified:	2007-09-30 13:38 UTC

See Also:
GNOME target:	---
GNOME version:	2.17/2.18

Description Milan Bouchet-Valat 2007-05-05 20:53:19 UTC

Steps to reproduce:
Drag and Drop a message from a folder to another on the same IMAP account.

Stack trace:
Program received signal SIGSEGV, Segmentation fault.

+ Trace 132614

Thread NaN (LWP 17340)

#0 imap_uid_array_free
from /usr/lib/evolution-data-server-1.2/camel-providers-10/libcamelimap.so
#1 ??
from /usr/lib/evolution-data-server-1.2/camel-providers-10/libcamelimap.so
#2 ??
#0 __kernel_vsyscall
#1 poll
from /lib/tls/i686/cmov/libc.so.6
#2 ??
from /usr/lib/libglib-2.0.so.0
#3 ??
#4 ??
#5 ??
#6 ??
#7 ??
#8 pthread_mutex_unlock
from /lib/tls/i686/cmov/libpthread.so.0
#9 g_main_loop_run
from /usr/lib/libglib-2.0.so.0
#10 bonobo_main
from /usr/lib/libbonobo-2.so.0
#11 main
#0 imap_uid_array_free
from /usr/lib/evolution-data-server-1.2/camel-providers-10/libcamelimap.so
#1 ??
from /usr/lib/evolution-data-server-1.2/camel-providers-10/libcamelimap.so
#2 ??
#0 __kernel_vsyscall
#1 pthread_cond_wait
from /lib/tls/i686/cmov/libpthread.so.0
#2 pthread_cond_wait
from /lib/tls/i686/cmov/libc.so.6
#3 ??
from /usr/lib/libglib-2.0.so.0
#4 ??
#5 ??
#6 ??
#7 g_async_queue_pop_unlocked
from /usr/lib/libglib-2.0.so.0
#8 e_msgport_wait
from /usr/lib/libedataserver-1.2.so.9
#9 ??
from /usr/lib/libedataserver-1.2.so.9
#10 ??
#11 ??
#12 ??
#0 __kernel_vsyscall
#1 poll
from /lib/tls/i686/cmov/libc.so.6
#2 ??
from /usr/lib/libglib-2.0.so.0
#3 ??
#4 ??
#5 ??
#6 ??
#7 ??
#8 pthread_mutex_unlock
from /lib/tls/i686/cmov/libpthread.so.0
#9 g_main_loop_run
from /usr/lib/libglib-2.0.so.0
#10 ??
from /usr/lib/libnm_glib.so.0
#11 ??
#12 pthread_mutex_unlock
from /lib/tls/i686/cmov/libpthread.so.0
#13 ??
from /usr/lib/libglib-2.0.so.0
#14 ??
#15 ??
#16 ??
#17 ??
#18 ??
from /lib/tls/i686/cmov/libc.so.6
#19 ??
from /lib/tls/i686/cmov/libpthread.so.0
#20 ??
from /lib/tls/i686/cmov/libc.so.6
#21 ??
from /lib/tls/i686/cmov/libpthread.so.0
#22 ??
#0 __kernel_vsyscall
#1 pthread_cond_wait
from /lib/tls/i686/cmov/libpthread.so.0
#2 pthread_cond_wait
from /lib/tls/i686/cmov/libc.so.6
#3 ??
from /usr/lib/libglib-2.0.so.0
#4 ??
#5 ??
#6 ??
#7 g_async_queue_pop_unlocked
from /usr/lib/libglib-2.0.so.0
#8 e_msgport_wait
from /usr/lib/libedataserver-1.2.so.9
#9 ??
from /usr/lib/libedataserver-1.2.so.9
#10 ??
#11 ??
#12 ??
#0 __kernel_vsyscall
#1 pthread_cond_wait
from /lib/tls/i686/cmov/libpthread.so.0
#2 pthread_cond_wait
from /lib/tls/i686/cmov/libc.so.6
#3 ??
from /usr/lib/libglib-2.0.so.0
#4 ??
#5 ??
#6 ??
#7 g_async_queue_pop_unlocked
from /usr/lib/libglib-2.0.so.0
#8 e_msgport_wait
from /usr/lib/libedataserver-1.2.so.9
#9 ??
from /usr/lib/libedataserver-1.2.so.9
#10 ??
#11 ??
#12 ??
#0 __kernel_vsyscall
#1 pthread_cond_wait
from /lib/tls/i686/cmov/libpthread.so.0
#2 pthread_cond_wait
from /lib/tls/i686/cmov/libc.so.6
#3 ??
from /usr/lib/libglib-2.0.so.0
#4 ??
#5 ??
#6 ??
#7 g_async_queue_pop_unlocked
from /usr/lib/libglib-2.0.so.0
#8 e_msgport_wait
from /usr/lib/libedataserver-1.2.so.9
#9 ??
from /usr/lib/libedataserver-1.2.so.9
#10 ??
#11 ??
#12 ??



Other information:
Note *the message is rightly copied to the destination folder*, but not removed from source.

Log using LC_ALL=C CAMEL_DEBUG=all CAMEL_IMAP_BRAINDAMAGED=1 evolution &> evo.log:
sending : A00044 UID COPY 37876 Sent
received: A00044 OK [COPYUID 1 38466] COPY completed

(evolution-2.10:17556): camel-imap-provider-WARNING **: Invalid uid set COPY com
pleted

Please feel free to ask for more infos...

Comment 1 Milan Bouchet-Valat 2007-05-06 09:45:50 UTC

Here is a more complete stacktrace:

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread -1332352112 (LWP 31353)]
imap_uid_array_free (arr=0x0) at camel-imap-utils.c:1284
1284    camel-imap-utils.c: No such file or directory.
        in camel-imap-utils.c
(gdb) thread apply all bt

+ Trace 132685

Thread 7 (Thread -1332352112 (LWP 31353))

#0 imap_uid_array_free
at camel-imap-utils.c line 1284
#1 do_copy
at camel-imap-folder.c line 1512
#2 imap_transfer_online
at camel-imap-folder.c line 1567
#3 disco_transfer_messages_to
at camel-disco-folder.c line 394
#4 camel_folder_transfer_messages_to
at camel-folder.c line 1453
#5 em_utils_selection_get_uidlist
at em-utils.c line 1062
#6 emft_drop_async_drop
at em-folder-tree.c line 912
#7 mail_msg_received
at mail-mt.c line 582
#8 thread_dispatch
at e-msgport.c line 1005
#9 start_thread
from /lib/tls/i686/cmov/libpthread.so.0
#10 clone
from /lib/tls/i686/cmov/libc.so.6

Comment 2 Milan Bouchet-Valat 2007-09-30 13:38:14 UTC


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