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 597816 - evolution crashed with SIGSEGV in vfprintf()
evolution crashed with SIGSEGV in vfprintf()
Status: RESOLVED FIXED
Product: evolution
Classification: Applications
Component: Mailer
2.28.x (obsolete)
Other Linux
: Normal critical
: ---
Assigned To: evolution-mail-maintainers
Evolution QA team
: 601544 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2009-10-08 14:57 UTC by Pedro Villavicencio
Modified: 2010-01-05 13:44 UTC
See Also:
GNOME target: ---
GNOME version: 2.27/2.28


Attachments
eds patch (1.64 KB, patch)
2010-01-04 14:04 UTC, Milan Crha
committed Details | Review
evo patch (2.01 KB, patch)
2010-01-05 13:39 UTC, Milan Crha
committed Details | Review

Description Pedro Villavicencio 2009-10-08 14:57:41 UTC
this report has been filed here:

https://bugs.edge.launchpad.net/ubuntu/+source/evolution/+bug/444177

"Evolution crashes after a minute of start up. I have two imap accounts configured."


"#0  0x040e24b1 in vfprintf () from /lib/tls/i686/cmov/libc.so.6
No symbol table info available.
  • #1 __vasprintf_chk
    from /lib/tls/i686/cmov/libc.so.6
  • #2 vasprintf
    at /usr/include/bits/stdio2.h line 199
  • #3 IA__g_vasprintf
    at /build/buildd/glib2.0-2.22.2/glib/gprintf.c line 315
  • #4 IA__g_strdup_vprintf
    at /build/buildd/glib2.0-2.22.2/glib/gstrfuncs.c line 244
  • #5 IA__g_strdup_printf
    at /build/buildd/glib2.0-2.22.2/glib/gstrfuncs.c line 270
  • #6 user_flag
    at camel-search-sql-sexp.c line 461
  • #7 e_sexp_term_eval
    at e-sexp.c line 718
  • #8 func_or
    at camel-search-sql-sexp.c line 126
  • #9 e_sexp_term_eval
    at e-sexp.c line 708
  • #10 match_all
    at camel-search-sql-sexp.c line 301
  • #11 e_sexp_term_eval
    at e-sexp.c line 708
  • #12 func_and
    at camel-search-sql-sexp.c line 93
  • #13 e_sexp_term_eval
    at e-sexp.c line 708
  • #14 e_sexp_eval
    at e-sexp.c line 1323
  • #15 camel_sexp_to_sql_sexp
  • #16 camel_folder_search_search
  • #17 imap_search_by_expression
  • #18 camel_folder_search_by_expression
  • #19 vee_rebuild_folder
    at camel-vee-folder.c line 1131
  • #20 vee_add_folder
    at camel-vee-folder.c line 1932
  • #21 camel_vee_folder_add_folder
    at camel-vee-folder.c line 225
  • #22 vfolder_adduri_exec
    at mail-vfolder.c line 273
  • #23 mail_msg_proxy
    at mail-mt.c line 522
  • #24 g_thread_pool_thread_proxy
    at /build/buildd/glib2.0-2.22.2/glib/gthreadpool.c line 265
  • #25 g_thread_create_proxy
    at /build/buildd/glib2.0-2.22.2/glib/gthread.c line 635
  • #26 start_thread
    from /lib/tls/i686/cmov/libpthread.so.0
  • #27 clone
    from /lib/tls/i686/cmov/libc.so.6

Comment 1 Milan Crha 2009-10-13 16:32:21 UTC
It is trying to build a search folder, which seems to be broken for some reason. Was this only an accidental crash of is it reproducible on the machine?
Comment 2 Akhil Laddha 2009-11-12 03:39:14 UTC
*** Bug 601544 has been marked as a duplicate of this bug. ***
Comment 3 Martin Mai 2009-11-23 17:30:42 UTC
Two comments from launchpad:

>>>
I'm unable to reproduce any errors as i've nuked my upgraded 9.10
install in favour of a clean install off the CD.

Sorry i can't help anymore; but this is a work machine and i coudn't
afford the downtime.
<<<

>>>
It was not an accidental one, I could reproduce the problem everytime. As mentioned by upstream, I figured out that it was due to my search folders and managed to delete them (pressed delete immediately upon start). After deleting the search folders I could not reproduce the problem. Evolution was upgraded from Jaunty - I guess this could be reproducible if you try to upgrade from Jaunty to Karmic with search folders - but I have not verified it as this is the only system that I have. If no one has the problem, I guess this can be closed - but I would be great if evolution can add checks to prevent crashes like this though.
<<<


Seems like this is no problem with a clean install, but eventually caused by an upgrade.
Comment 4 Milan Crha 2010-01-04 12:50:43 UTC
I looked slightly more closely on the given backtrace and realized the problem is with labels. It seems to me that you had setup your own labels in Edit->Preferences->Mail Preferences, tab Labels, and these got lost on update, thus the search folder rule, though setup with correct label, didn't find its corresponding item in available labels, and then it began making troubles. Why your labels didn't survive upgrade is a question. I can reproduce this when I create a search folder with "Label is Work" and then edit the
~/.evolution/mail/vfolders.xml
file and change $Label... to other value, some which is not in a list of known labels there, say $LabelXXX. Then the SQL WHERE part is generated incorrectly.
I will add some checking in rule generation, but the real issue are lost user defined labels.

I do not know Ubuntu at all, what are exact versions we are talking about here, please? Karmic has 2.28.x I guess, but the older version is unknown to me.
Comment 5 Milan Crha 2010-01-04 14:04:43 UTC
Created attachment 150777 [details] [review]
eds patch

for evolution-data-server;

This is for the part about "not crashing on unknown label stored in a rule".
The part about "how the label got lost" is still opened. Maybe one other option is that the label was deleted intentionally, but the search folder was kept. Not that I think it's our case here, but it's another way how to reproduce this.
Comment 6 Milan Crha 2010-01-04 14:20:03 UTC
Created commit 3c901c5 in eds master (2.29.5+)
Created commit b7f31dc in eds gnome-2-28 (2.28.3+)
Comment 7 Martin Mai 2010-01-04 23:55:35 UTC
If you are still interested in the versions of evolution in Ubuntu:

Jaunty was released with evolution 2.26.1 and not synced from debian. The changelog for the Ubuntu package (2.26.1-0ubuntu1) was the following:
>>>
evolution (2.26.1-0ubuntu1) jaunty; urgency=low

  * New upstream version
  * debian/control:
    - updated evolution-data-server requirement
  * debian/patches/90_svn_update.patch,
    debian/patches/91_svn_change_fix_google_username.patch:
    - the changes are in the new version
  * debian/patches/92_incorrect_free_crasher.patch:
    - use upstream version
<<<

7 weeks later there has been a stable release update for evolution 2.26.1 in Ubuntu (2.26.1-0ubuntu2) to fix two launchpad bugs. Changelog was the following:
>>>
evolution (2.26.1-0ubuntu2) jaunty-proposed; urgency=low

  * debian/patches/90_git_change_fix_recurrent_event_edition.patch:
    - git change to make editing recurrent events work correctly
      (lp: #372503, #376110)
<<<
(You can find a diff at http://launchpadlibrarian.net/26721036/evolution_2.26.1-0ubuntu1_2.26.1-0ubuntu2.diff.gz)


Ubuntu 9.10 (karmic) shipped with evolution 2.28.1 (2.28.1-0ubuntu1). There were no changes made to the code by the Ubuntu packaging.


Given the date the launchpad reported submitted the bug, he updated from 2.26.1-0ubuntu2 to 2.28.1-0ubuntu1.

I hope this information will be helpful.
Comment 8 Milan Crha 2010-01-05 13:11:13 UTC
Thanks. I tried and I cannot reproduce this when moving from 2.26 to 2.28, but when I move to upcoming 2.29.5 then it fails to use the right labels in a search folders setup with labels. I'm going to fix it in master at least.
Comment 9 Milan Crha 2010-01-05 13:39:43 UTC
Created attachment 150839 [details] [review]
evo patch

for evolution;

For incorrectly read older search folders with labels.
Comment 10 Milan Crha 2010-01-05 13:41:51 UTC
Created commit ac07595 in evo master (2.29.5+)
Comment 11 Milan Crha 2010-01-05 13:44:49 UTC
Please reopen if you'll find some steps how to reproduce this with an update
from 2.26 to 2.28. I would like to fix it in 2.28 too, but as I'm unable to reproduce it, then it's hard to tell where the issue is.