GNOME Bugzilla – Bug 332979
Exchange storage crashed when autocompletion was enabled for GAL address book
Last modified: 2008-09-12 12:37:10 UTC
Steps to reproduce: 1. Configure exchange account , enable autocompletion for GAL address book 2. try composign a mail 3. Exchange crashes when we try to enter an email address Stack trace: Backtrace was generated from '/opt/gnome/libexec/evolution-exchange-storage' (no debugging symbols found) Using host libthread_db library "/lib/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1234762064 (LWP 27493)] [New Thread -1271932000 (LWP 27584)] [New Thread -1263539296 (LWP 27583)] [New Thread -1255146592 (LWP 27580)] [New Thread -1236018272 (LWP 27494)] 0xffffe410 in __kernel_vsyscall ()
+ Trace 66601
Thread 4 (Thread -1255146592 (LWP 27580))
Other information: This was consistently happening for sometime . ( was not happenign when i disabled the GAL contacts from autocompletion) rpm -qa | grep evo evolution-sharp-0.10.2-11 evolution-pilot-2.5.92-1 evolution-2.5.92-1 multisync-evolution-0.82+cvs-13 evolution-data-server-1.5.92-1 evolution-debuginfo-2.5.92-1 evolution-exchange-debuginfo-2.5.92-2 evolution-webcal-2.4.1-4 evolution-data-server-debuginfo-1.5.92-1 beagle-evolution-0.2.1-20 evolution-exchange-2.5.92-2
*** Bug 333094 has been marked as a duplicate of this bug. ***
same problem here (2.6.1), on ubuntu dapper and gentoo also
*** Bug 343520 has been marked as a duplicate of this bug. ***
*** Bug 319865 has been marked as a duplicate of this bug. ***
similar to LDAP backend bug http://bugzilla.gnome.org/show_bug.cgi?id=300157
*** Bug 344009 has been marked as a duplicate of this bug. ***
I see same thing. evolution 2.6.0 SuSE Linux 10.1
*** Bug 353646 has been marked as a duplicate of this bug. ***
last duplicate is version 2.7.x Thanks for the bug report. Unfortunately, that stack trace is not very useful in determining the cause of the crash. Can you get us one with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so.
*** Bug 353795 has been marked as a duplicate of this bug. ***
I got crash in 2.8.0 Backtrace was generated from '/opt/gnome/libexec/evolution-exchange' Using host libthread_db library "/lib/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread -1236891984 (LWP 29755)] [New Thread -1247380576 (LWP 5766)] [New Thread -1238987872 (LWP 5761)] [New Thread -1238238304 (LWP 29758)] 0xffffe410 in __kernel_vsyscall ()
+ Trace 71882
Thread 3 (Thread -1238987872 (LWP 5761))
*** Bug 357024 has been marked as a duplicate of this bug. ***
*** Bug 358371 has been marked as a duplicate of this bug. ***
*** Bug 362868 has been marked as a duplicate of this bug. ***
Created attachment 75661 [details] Error report (output from bugbuddy) Same here, using gentoo linux, kernel 2.6.18 on a intel dualcore gnome-extra/evolution-data-server-1.8.1 USE="ipv6 kerberos ldap ssl -debug -doc -keyring -krb4 -nntp" gnome-extra/evolution-exchange-2.8.1 USE="-debug -doc -static" mail-client/evolution-2.8.1.1 USE="bogofilter crypt dbus hal ipv6 kerberos ssl -debug -doc -krb4 -ldap -mono -nntp -pda -profile -spell"
unfortunately, the last trace is missing debugging symbols. 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!
Hi, Hope this new backtrace helps. Memory status: size: 69832704 vsize: 0 resident: 69832704 share: 0 rss: 18284544 rss_rlim: 0 CPU usage: start_time: 1162921072 rtime: 0 utime: 752 stime: 0 cutime:656 cstime: 0 timeout: 96 it_real_value: 0 frequency: 0 Backtrace was generated from '/usr/libexec/evolution-exchange' Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread -1234524496 (LWP 7690)] [New Thread -1269793888 (LWP 13757)] [New Thread -1235809376 (LWP 7691)] 0xffffe410 in __kernel_vsyscall ()
+ Trace 84098
Thread 1 (Thread -1234524496 (LWP 7690))
last trace differs from the original one but seems to be triggered by the same means
*** Bug 399502 has been marked as a duplicate of this bug. ***
Created attachment 82091 [details] Trace output after crash encountered when adding recipient in CC list Here's another way that I encountered this problem. 1. Open email message 2. Click Reply All 3. Try to add name of recipient in CC list I have attached the output of the trace output
Here's a new backtrace. This time the crash occurred while autocompleting from exchange contacts Memory status: size: 83386368 vsize: 0 resident: 83386368 share: 0 rss: 16240640 rss_rlim: 0 CPU usage: start_time: 1172162376 rtime: 0 utime: 515 stime: 0 cutime:453 cstime: 0 timeout: 62 it_real_value: 0 frequency: 0 Backtrace was generated from '/usr/libexec/evolution-exchange' Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread -1233705296 (LWP 5726)] [New Thread -1277830240 (LWP 14551)] [New Thread -1252193376 (LWP 14541)] [New Thread -1260586080 (LWP 14538)] [New Thread -1243718752 (LWP 14536)] [New Thread -1234981984 (LWP 5727)] 0xffffe410 in __kernel_vsyscall ()
+ Trace 113040
Thread 1 (Thread -1233705296 (LWP 5726))
last trace is good, thank you. confirming report.
*** Bug 383389 has been marked as a duplicate of this bug. ***
*** Bug 400195 has been marked as a duplicate of this bug. ***
*** Bug 430709 has been marked as a duplicate of this bug. ***
*** Bug 444737 has been marked as a duplicate of this bug. ***
*** Bug 462280 has been marked as a duplicate of this bug. ***
bug 415778 also looks like a duplicate
*** Bug 415778 has been marked as a duplicate of this bug. ***
Fixed to head. Sending ChangeLog Sending addressbook/e-book-backend-gal.c Transmitting file data .. Committed revision 1421.
*** Bug 471160 has been marked as a duplicate of this bug. ***
*** Bug 470640 has been marked as a duplicate of this bug. ***
*** Bug 361460 has been marked as a duplicate of this bug. ***
*** Bug 348258 has been marked as a duplicate of this bug. ***
*** Bug 474489 has been marked as a duplicate of this bug. ***
*** Bug 480924 has been marked as a duplicate of this bug. ***
*** Bug 508548 has been marked as a duplicate of this bug. ***