Bug 341334 – Evolution Crashes - New mail with no/blank subject - Connecting to Exchange

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 341334 - Evolution Crashes - New mail with no/blank subject - Connecting to Exchange


Summary:	Evolution Crashes - New mail with no/blank subject - Connecting to Exchange


Status:	RESOLVED DUPLICATE of bug 321352

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

Importance:	High critical
Target Milestone:	---
Assigned To:	Harish Krishnaswamy
QA Contact:	Evolution QA team

URL:
Whiteboard:

Duplicates:	329536 (view as bug list)
Depends on:
Blocks:

Reported:	2006-05-10 21:11 UTC by Luke Hewitt
Modified:	2006-07-28 13:10 UTC

See Also:
GNOME target:	---
GNOME version:	2.11/2.12

Attachments
Proposed patch (1.32 KB, patch) 2006-05-25 06:10 UTC, Srinivasa Ragavan	none	Details \| Review

Description Luke Hewitt 2006-05-10 21:11:31 UTC

Steps to reproduce:
Whenever Evolution gets mail with a blank subject line from our Exchange server
it quits unexpectedly. Eventually it resolves them and opens correctly,
sometimes after several attempts to reload the application.


Stack trace:


Other information:

Comment 1 André Klapper 2006-05-11 09:14:36 UTC

Thanks for the bug report. Without a stack trace from the crash it's very hard to determine what caused it.
Can you provide us with one? Please see http://live.gnome.org/GettingTraces for more information on how to do so.

Comment 2 Luke Hewitt 2006-05-11 22:10:09 UTC

(In reply to comment #1)
> Thanks for the bug report. Without a stack trace from the crash it's very hard
> to determine what caused it.
> Can you provide us with one? Please see http://live.gnome.org/GettingTraces for
> more information on how to do so.
> 
Is this good?

(gdb) run evolution
Starting program: /usr/bin/evolution evolution
[Thread debugging using libthread_db enabled]
[New Thread -1208162624 (LWP 13124)]
CalDAV Eplugin starting up ...
[New Thread 27941808 (LWP 13137)]
[Thread 27941808 (LWP 13137) exited]
Detaching after fork from child process 13140.

(evolution-2.6:13124): camel-WARNING **: camel_exception_get_id called with NULL parameter.
[New Thread 27941808 (LWP 13141)]
[New Thread 45054896 (LWP 13148)]
[Thread 45054896 (LWP 13148) exited]
[New Thread 45054896 (LWP 13149)]
[New Thread 55774128 (LWP 13150)]

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread -1208162624 (LWP 13124)]
0x00af43d8 in strcmp () from /lib/tls/libc.so.6
(gdb)

Comment 3 Luke Hewitt 2006-05-11 22:12:21 UTC

+ Trace 68177

Thread 6 (Thread 55774128 (LWP 13150))

#0 _dl_sysinfo_int80
from /lib/ld-linux.so.2
#1 pthread_cond_wait
from /lib/tls/libpthread.so.0
#2 e_mutex_lock
at e-msgport.c line 1229
#3 camel_service_connect
at camel-service.c line 349
#4 camel_exchange_store_connected
at camel-exchange-store.c line 179
#5 exchange_get_folder_info
at camel-exchange-store.c line 704
#6 camel_store_get_folder_info
at camel-store.c line 788
#7 emft_get_folder_info__get
at em-folder-tree.c line 1694
#8 mail_msg_received
at mail-mt.c line 570
#9 thread_dispatch
at e-msgport.c line 974
#10 start_thread
from /lib/tls/libpthread.so.0
#11 clone
from /lib/tls/libc.so.6

Thread 5 (Thread 45054896 (LWP 13149))

#0 _dl_sysinfo_int80
from /lib/ld-linux.so.2
#1 __read_nocancel
from /lib/tls/libpthread.so.0
#2 do_read
at camel-stub-marshal.c line 90
#3 marshal_read
at camel-stub-marshal.c line 117
#4 decode_uint32
at camel-stub-marshal.c line 149
#5 camel_stub_marshal_decode_uint32
at camel-stub-marshal.c line 262
#6 status_main
at camel-stub.c line 109
#7 start_thread
from /lib/tls/libpthread.so.0
#8 clone
from /lib/tls/libc.so.6

Thread 3 (Thread 27941808 (LWP 13141))

#0 _dl_sysinfo_int80
from /lib/ld-linux.so.2
#1 pthread_cond_wait
from /lib/tls/libpthread.so.0
#2 e_msgport_wait
at e-msgport.c line 660
#3 ep_msg_send
at e-passwords.c line 182
#4 e_passwords_get_password
#5 get_password
at mail-session.c line 188
#6 camel_session_get_password
at camel-session.c line 369
#7 exchange_connect
at camel-exchange-store.c line 354
#8 camel_service_connect
at camel-service.c line 369
#9 camel_exchange_store_connected
at camel-exchange-store.c line 179
#10 exchange_get_folder_info
at camel-exchange-store.c line 704
#11 camel_store_get_folder_info
at camel-store.c line 788
#12 get_folderinfo_get
at mail-ops.c line 1070
#13 mail_msg_received
at mail-mt.c line 570
#14 thread_dispatch
at e-msgport.c line 974
#15 start_thread
from /lib/tls/libpthread.so.0
#16 clone
from /lib/tls/libc.so.6

Thread 1 (Thread -1208162624 (LWP 13124))

#0 strcmp
from /lib/tls/libc.so.6
#1 e_component_registry_peek_info
at e-component-registry.c line 321
#2 impl_Shell_handleURI
at e-shell.c line 272
#3 _ORBIT_skel_small_GNOME_Evolution_Shell_handleURI
at Evolution-common.c line 88
#4 ORBit_c_stub_invoke
from /usr/lib/libORBit-2.so.0
#5 GNOME_Evolution_Shell_handleURI
at Evolution-stubs.c line 111
#6 open_uris
at main.c line 312
#7 idle_cb
at main.c line 379
#8 g_idle_dispatch
at gmain.c line 3796
#9 IA__g_main_context_dispatch
at gmain.c line 1916
#10 g_main_context_iterate
at gmain.c line 2547
#11 IA__g_main_loop_run
at gmain.c line 2751
#12 bonobo_main
from /usr/lib/libbonobo-2.so.0
#13 main

Comment 4 Poornima 2006-05-12 10:00:13 UTC

This bug has been reported already in bugzilla.novell.com, and is fixed by sragavan@novell.com. Fix should be available in 2.7.x

Comment 5 André Klapper 2006-05-12 10:14:28 UTC

poornima: novell bug id? so if it is fixed, *is* it available in 2.7? why hasn't it been also committed to 2.6?

reopening, sorry. this isn't enough info for me. :-)

Comment 6 Harish Krishnaswamy 2006-05-19 08:02:21 UTC

Poornima, can you please provide the bug number here if it is publicly accessible. If it is not, capture the information here.
This bug (and the likes) must not be closed unless the upstream commits on the HEAD and gnome-2-14 branch are done.

Comment 7 Poornima 2006-05-19 08:18:19 UTC

Novell bug id is https://bugzilla.novell.com/show_bug.cgi?id=171489
Based on stack traces in novell bugzilla bug, this bug was marked as 'Resolved fixed'. 
Srini can comment on for rest of the required information.

Comment 8 Srinivasa Ragavan 2006-05-22 05:59:25 UTC

+ Trace 68361

#0 strcmp
from /lib/tls/libc.so.6
#1 e_component_registry_peek_info
at e-component-registry.c line 321



I have fixed this. I dont think this is yet committed. It will be there in the next release.

Comment 9 Srinivasa Ragavan 2006-05-25 06:10:44 UTC

Created attachment 66166 [details] [review]
Proposed patch

Comment 10 Srinivasa Ragavan 2006-05-25 06:11:42 UTC

The above patch would fix the issue, by checking for NULL before comparing. They can be null, since exchange component wont have a button any more and is null.

Comment 11 David Hill 2006-06-17 03:49:27 UTC

I can confirm the problem with the blank subject.... based on this bug I used the web mail interface, found the offending email, and deleted it. After that, evolution ceased to spin forever, and merly crashed once before getting back to being reasonably usefull.

Comment 12 Poornima 2006-06-21 09:32:29 UTC

David: Is the crash you are observing now has same stack trace as mentioned in this bug ?

Comment 13 Poornima 2006-06-21 10:08:00 UTC

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

Comment 14 André Klapper 2006-07-28 13:10:16 UTC

*** Bug 329536 has been marked as a duplicate of this bug. ***

Comment 15 André Klapper 2006-07-28 13:10:29 UTC

*** Bug 337632 has been marked as a duplicate of this bug. ***