Summary: | mail/notmuch crashes when indexing new mail | ||
---|---|---|---|
Product: | Ports & Packages | Reporter: | 33n5ps+89brie9u1qz9g |
Component: | Individual Port(s) | Assignee: | freebsd-ports-bugs (Nobody) <ports-bugs> |
Status: | Closed FIXED | ||
Severity: | Affects Some People | CC: | bugs_freebsd_org, m5bere2, mp39590, robak, ross |
Priority: | --- | Flags: | 33n5ps+89brie9u1qz9g:
maintainer-feedback?
(ross) |
Version: | Latest | ||
Hardware: | amd64 | ||
OS: | Any | ||
Bug Depends on: | 201884 | ||
Bug Blocks: |
Description
33n5ps+89brie9u1qz9g
2014-09-21 13:17:09 UTC
Maintainer CC'd I observe the same behavior on a freshly installed FreeBSD 10.0 system and no matter whether notmuch is installed using pkg or using ports. PR timed out (no response from maintainer in 2 weeks) but there's no fix suggested so there's nothing to do... Move PR out of triage. I can confirm the same error on several of my machines (all running 10.1, either freshly installed or upgraded from older verssions). I tried compiling notmuch (and all of its dependencies) from ports and also installed the binary packages. The problem is also present when using the new notmuch 0.19 port (see patch by mp39590@gmail.com). I did some testing and posted a backtrace to the notmuch mailing list, apparently it is related to maildir flag syncing and xapian: http://notmuchmail.org/pipermail/notmuch/2015/020342.html As a (somewhat unsatisfying) workaround for now, you can disable maildir flag syncing by putting [maildir] synchronize_flags=false into ~/.notmuch-config Any idea what could be the problem here? Hello, can you check if latest notmuch is failing for you, if being compiled from the ports tree on 10.1? (In reply to mp39590 from comment #6) Hi, notmuch always worked well when compiled from ports. Only the binary package from pkgng repository had issues with new emails. They are still present in the newest version (0.20.2) on 10.1-RELEASE-p14. I've pushed bug #201884, which shall fix the issue. It will take some time for packages to get rebuild (~1 week I suppose) - testing will be appreciated. Can you guys report if the issue in this PR is now solved, after 201884 have been committed? (In reply to Bartek Rutkowski from comment #9) It works. Thanks a lot! |