Bug 362716 – Error in deleting messages/viewing in Trash folder. Causes crash. (and (match-all (not (system-flag "junk"))) )

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 362716 - Error in deleting messages/viewing in Trash folder. Causes crash. (and (match-all (not (system-flag "junk"))) )


Summary:	Error in deleting messages/viewing in Trash folder. Causes crash. (and (match...


Status:	RESOLVED DUPLICATE of bug 360237

Product:	evolution
Classification:	Applications
Component:	Mailer
Version:	2.8.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:	2006-10-16 21:17 UTC by Choose to remain Anonymous
Modified:	2006-10-17 10:35 UTC

See Also:
GNOME target:	---
GNOME version:	2.15/2.16

Description Choose to remain Anonymous 2006-10-16 21:17:54 UTC

Error executing search expression: Unknown type in parse tree: 138686936:
(and (match-all (not (system-flag "junk"))))

This error is reported in an info box. Afterwards, evo will crash.

Specific steps on a clean evo install.

Setup a pop account
Retrieve mail
Delete message in inbox
Message NOT displayed in Trash although trash shows a count of 1
Click back to Inbox, dialog message shown.
Clicking on Hide deleted messages will cause an immediate abort.

Using Garnome 2.16.1 on
Slackware 11.0
Evo 2.8.1 et al.
Kernel, 2.6.17 beyond patchset.

Sorry, no usable stack trace. Don't have the time to recompile all of gnome.

If this is of any use. It occurs right after clicking hide deleted messages.

Distribution: Slackware Slackware 11.0.0
Gnome Release: 2.16.1 2006-10-04 (GARNOME)
BugBuddy Version: 2.16.0

Memory status: size: 78123008 vsize: 0 resident: 78123008 share: 0 rss: 21004288 rss_rlim: 0
CPU usage: start_time: 1161032708 rtime: 0 utime: 151 stime: 0 cutime:142 cstime: 0 timeout: 9 it_real_value: 0 frequency: 0

Backtrace was generated from '/opt/gnome/2.16.1/bin/evolution-2.8'

Using host libthread_db library "/lib/tls/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread -1230330176 (LWP 25758)]
[New Thread -1281201232 (LWP 26104)]
[New Thread -1263248464 (LWP 25790)]
[New Thread -1244365904 (LWP 25789)]
[New Thread -1252791376 (LWP 25773)]
[New Thread -1235977296 (LWP 25770)]
0xb758c071 in __waitpid_nocancel () from /lib/tls/libpthread.so.0

+ Trace 76676

Thread 4 (Thread -1244365904 (LWP 25789))

#0 __lll_mutex_lock_wait
from /lib/tls/libpthread.so.0
#1 _L_mutex_lock_33
from /lib/tls/libpthread.so.0
#2 ??
#3 segv_redirect
#4 <signal handler called>
#5 memset
from /lib/tls/libc.so.6
#6 e_memchunk_alloc0
from /opt/gnome/2.16.1/lib/libedataserver-1.2.so.7
#7 parse_term_new
from /opt/gnome/2.16.1/lib/libedataserver-1.2.so.7
#8 parse_value
from /opt/gnome/2.16.1/lib/libedataserver-1.2.so.7
#9 parse_values
from /opt/gnome/2.16.1/lib/libedataserver-1.2.so.7
#10 parse_value
from /opt/gnome/2.16.1/lib/libedataserver-1.2.so.7
#11 e_sexp_parse
from /opt/gnome/2.16.1/lib/libedataserver-1.2.so.7
#12 camel_folder_search_search
from /opt/gnome/2.16.1/lib/libcamel-provider-1.2.so.8
#13 local_search_by_expression
from /opt/gnome/2.16.1/lib/evolution-data-server-1.2/camel-providers/libcamellocal.so
#14 camel_folder_search_by_expression
from /opt/gnome/2.16.1/lib/libcamel-provider-1.2.so.8
#15 regen_list_regen
from /opt/gnome/2.16.1/lib/evolution/2.8/components/libevolution-mail.so
#16 mail_msg_received
from /opt/gnome/2.16.1/lib/evolution/2.8/components/libevolution-mail.so
#17 thread_dispatch
from /opt/gnome/2.16.1/lib/libedataserver-1.2.so.7
#18 start_thread
from /lib/tls/libpthread.so.0
#19 clone
from /lib/tls/libc.so.6

Comment 1 André Klapper 2006-10-17 10:18:01 UTC

Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.


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

Comment 2 Choose to remain Anonymous 2006-10-17 10:35:56 UTC

(In reply to comment #1)
> Thanks for the bug report. This particular bug has already been reported into
> our bug tracking system, but please feel free to report any further bugs you
> find.
> 
> 
> *** This bug has been marked as a duplicate of 360237 ***
> 

Arggggh. I'm sorry. I am SO bad at searching. I suppose there were so many critical open bugs I must have missed it. Thanks for correcting me.