https://bugzilla.redhat.com/show_bug.cgi?id=2069264
--- Comment #21 from Michael J Gruber <mjg(a)fedoraproject.org> ---
Thanks for reporting back, and happy new year to you, too!
thread:(null) 1970-01-01 [0/0] ; (null) ()
These lines should definitely not be there and indicate a database problem. No,
notmuch should not crash, but the root cause is a corrupt db.
Query string is:
thread:0000000000021c67
Exclude query is:
Query()
Final query is:
Query((Tmail AND 0 * G0000000000021c67))
Those are the queries for the individual result threads just before display,
not the original query. This indeed means that thread:0000000000021c67 should
be the (first) one causing the segfault, but parallism could fool us.
Did moving some messages away solve the issue?
I would in fact try the opposite approach: Use `notmuch dump` to backup all
tags, remove all xapian files (in `$(notmuch config get
database.path)/xapian)`), rescan your mail (I know this takes a bit), then
`notmuch restore` your tags.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2069264