Description of problem: After upgrade of xapian-core and notmuch in F28, notmuch crashes. Version-Release number of selected component (if applicable): notmuch-0.26-1.fc28.x86_64 xapian-core-libs-1.4.5-1.fc28.x86_64 xapian-core-1.4.5-1.fc28.x86_64 How reproducible: always Steps to Reproduce: 1. notmuch count tag:unread Actual results: $ notmuch count tag:unread /usr/include/c++/8/bits/stl_vector.h:1010: std::vector<_Tp, _Alloc>::reference std::vector<_Tp, _Alloc>::front() [with _Tp = Xapian::Internal::MSetItem; _Alloc = std::allocator<Xapian::Internal::MSetItem>; std::vector<_Tp, _Alloc>::reference = Xapian::Internal::MSetItem&]: Assertion '__builtin_expect(!this->empty(), true)' failed. [1] 23358 abort (core dumped) notmuch count tag:unread Expected results: notmuch should not crash Additional info: crash was reported to FAF: https://retrace.fedoraproject.org/faf/reports/2031953/
This bug appears to have been reported against 'rawhide' during the Fedora 28 development cycle. Changing version to '28'.
I was able to reproduce this on rawhide and reported it to the xapian irc channel. A fix has been pushed and will be available in the next minor release, 1.4.6 from commit log: > Fix bug with get_mset(0, 0, X) when X > 0 > This was causing us to try to access an element in an empty vector. ( https://github.com/xapian/xapian/commit/f92e2a936c159209398bb85a61ee1ae7d0bc635a ) from irc: > <olly> sielicki: bremner: i've just pushed a fix for that get_mset(0, 0, X) bug - it'll be fixed in 1.4.6
This bug also affects neomutt users that use notmuch. neomutt is a fork of mutt, with native notmuch support: https://github.com/neomutt/neomutt https://copr.fedorainfracloud.org/coprs/flatcap/neomutt/ David Bremner (notmuch maintainer) has created a temporary workaround for notmuch: https://paste.debian.net/1018993/ If any notmuch users need a quick fix, I've bundled a patched version: F28 version: notmuch-0.25-6.fc28.src.rpm COPR version: notmuch-0.25-7.fc28.src.rpm dnf copr enable flatcap/neomutt dnf update
I can confirm that the patched version in the flatcap copr solves the issue for me ('notmuch count' and the emacs notmuch UI have resumed working), after upgrading to the Fedora 28 beta today resulted in breakage here.
Same here, notmuch new works again after using (force install ignoring deps) over my Fedora version. NeoMutt is tracking this at: https://github.com/neomutt/neomutt/issues/1126 Setting urgent/urgent as notmuch is unusable at the moment in F28 After the install command exits normally: Processed 9165 total files in 49s (185 files/sec.). Added 8429 new messages to the database. Removed 5117 messages. Detected 95 file renames.
This bug seems no longer present in notmuch 0.26.2.
This is pretty serious bug, can the provided patch please be applied? The bug makes notmuch next to useless on Fedora 28. And (no offense) but this has been reported in February, the fix is a few months overdue.
0.27-1.fc{27/28/29} is now available in Fedora repositories, which has all relevant fixes. This ticket can be closed.
This message is a reminder that Fedora 28 is nearing its end of life. On 2019-May-28 Fedora will stop maintaining and issuing updates for Fedora 28. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '28'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 28 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 28 changed to end-of-life (EOL) status on 2019-05-28. Fedora 28 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days