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 318035 - Evolution crashed when asked to find mail containing the string '99' in the message
Evolution crashed when asked to find mail containing the string '99' in the ...
Status: RESOLVED DUPLICATE of bug 236778
Product: evolution
Classification: Applications
Component: Mailer
unspecified
Other other
: Normal normal
: ---
Assigned To: evolution-mail-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2005-10-05 16:39 UTC by fede_m
Modified: 2006-01-09 15:06 UTC
See Also:
GNOME target: ---
GNOME version: 2.7/2.8



Description fede_m 2005-10-05 16:39:46 UTC
Distribution: Fedora Core release 3 (Heidelberg)
Package: Evolution
Severity: normal
Version: GNOME2.8.0 unspecified
Gnome-Distributor: Red Hat, Inc
Synopsis: Evolution crashed when asked to find mail containing the string '99'  in the message
Bugzilla-Product: Evolution
Bugzilla-Component: Mailer
Bugzilla-Version: unspecified
BugBuddy-GnomeVersion: 2.0 (2.8.0)
Description:
Description of the crash:
"Evolution died unexpectedly' - restarting in any way puts it right back
at the crashing spot, with '99' in the search bar and 'Updating
vFolders...' and 'Generating message list (...)' in the taskbar (and
crashing instantly again)

Steps to reproduce the crash:
1. Set search  field to 'Message'
2. Type '99' in the search bar
3. click on 'Find Now'

Expected Results:
A filtered list of messages... And, most certainly, a restart from
scratch when closed and reopened - not an immdiate return to the
crashing situation.

How often does this happen?


Additional Information:



Debugging Information:

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

(no debugging symbols found)...Using host libthread_db library
"/lib/tls/libthread_db.so.1".
(no debugging symbols found)...`shared object read from target memory'
has disappeared; keeping its symbols.
(no debugging symbols found)...(no debugging symbols found)...(no
debugging symbols found)...(no debugging symbols found)...(no debugging
symbols found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...[Thread debugging using libthread_db enabled]
[New Thread -1209104160 (LWP 5450)]
[New Thread -1234191440 (LWP 5455)]
[Thread debugging using libthread_db enabled]
[New Thread -1209104160 (LWP 5450)]
[New Thread -1234191440 (LWP 5455)]
[New Thread -1225786448 (LWP 5453)]
[New Thread -1215558736 (LWP 5452)]
(no debugging symbols found)...[Thread debugging using libthread_db
enabled]
[New Thread -1209104160 (LWP 5450)]
[New Thread -1234191440 (LWP 5455)]
(no debugging symbols found)...(no debugging symbols found)...(no
debugging symbols found)...(no debugging symbols found)...(no debugging
symbols found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...0xffffe410 in __kernel_vsyscall ()

Thread 2 (Thread -1234191440 (LWP 5455))

  • #0 __kernel_vsyscall
  • #1 __waitpid_nocancel
    from /lib/tls/libpthread.so.0
  • #2 libgnomeui_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 __kernel_vsyscall
  • #5 raise
    from /lib/tls/libc.so.6
  • #6 abort
    from /lib/tls/libc.so.6
  • #7 g_logv
    from /usr/lib/libglib-2.0.so.0
  • #8 g_log
    from /usr/lib/libglib-2.0.so.0
  • #9 camel_key_table_lookup
    from /usr/lib/evolution/2.0/libcamel.so.0
  • #10 camel_text_index_name_new
    from /usr/lib/evolution/2.0/libcamel.so.0
  • #11 camel_index_cursor_next
    from /usr/lib/evolution/2.0/libcamel.so.0
  • #12 camel_folder_search_free_result
    from /usr/lib/evolution/2.0/libcamel.so.0
  • #13 camel_folder_search_free_result
    from /usr/lib/evolution/2.0/libcamel.so.0
  • #14 e_sexp_term_eval
    from /usr/lib/evolution/2.0/libeutil.so.0
  • #15 e_sexp_term_eval
    from /usr/lib/evolution/2.0/libeutil.so.0
  • #16 e_sexp_term_eval
    from /usr/lib/evolution/2.0/libeutil.so.0
  • #17 e_sexp_term_eval
    from /usr/lib/evolution/2.0/libeutil.so.0
  • #18 e_sexp_term_eval
    from /usr/lib/evolution/2.0/libeutil.so.0
  • #19 e_sexp_eval
    from /usr/lib/evolution/2.0/libeutil.so.0
  • #20 camel_folder_search_search
    from /usr/lib/evolution/2.0/libcamel.so.0
  • #21 camel_local_folder_lock
    from /usr/lib/evolution/2.0/camel-providers/libcamellocal.so
  • #22 camel_folder_search_by_expression
    from /usr/lib/evolution/2.0/libcamel.so.0
  • #23 message_list_save_state
    from /usr/lib/evolution/2.0/components/libevolution-mail.so
  • #24 mail_enable_stop
    from /usr/lib/evolution/2.0/components/libevolution-mail.so
  • #25 e_thread_busy
    from /usr/lib/evolution/2.0/libeutil.so.0
  • #26 start_thread
    from /lib/tls/libpthread.so.0
  • #27 clone
    from /lib/tls/libc.so.6




------- Bug moved to this database by unknown@gnome.bugs 2005-10-05 16:39 UTC -------

Comment 1 André Klapper 2005-10-06 12:05:37 UTC
fede_m, which evolution version is this?
Comment 2 C Shilpa 2005-10-18 07:04:23 UTC
marking as needinfo. Not able to replicate the issue with
evolution-2.4.1.0.200510090310-0.snap.novell.0.1. Which version of evolution do
you use?
Comment 3 André Klapper 2006-01-09 15:06:25 UTC
same stacktrace as bug 270822 which is a dup of bug 236778

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