Finally found my problem,

I install notmuch into custom dir, and the declared PATH point to an old binary in the wrong /bin folder.

I works now.

Sorry for that, and thanks David for your help.

Sébastien Rey-Coyrehourcq

Research Engineer UMR IDEES

02.35.14.69.30

{Stronger security for your email, follow EFF tutorial : https://ssd.eff.org/}

Le mardi 28 mai 2019 à 09:59 -0300, David Bremner a écrit :

<pre>sebastien rey-coyrehourcq <sebastien.rey-coyrehourcq@univ-rouen.fr></pre><pre>writes:</pre><pre>
</pre><pre>(gdb) backtrace</pre><pre>#0 0x00007ffff6969410 in g_mime_stream_construct () at /usr/lib/x86_64-linux-gnu/libgmime-3.0.so.0</pre><pre>#1 0x00007ffff696d124 in g_mime_stream_fs_new_with_bounds () at /usr/lib/x86_64-linux-gnu/libgmime-3.0.so.0</pre><pre>#2 0x00007ffff7bc6f3f in g_mime_stream_gzfile_open (filename=<optimized out>) at util/gmime-extra.c:54</pre><pre>#3 0x00007ffff7bb0b51 in _notmuch_message_file_open_ctx (notmuch=notmuch@entry=0x5555557b67d0, ctx=ctx@entry=0x0, filename=filename@entry=0x5555557eceb0 "/home/reyman/Mail/unthinkingdepths/0_InfoLabos/.mbsyncstate") at lib/message-file.c:73</pre><pre>
</pre><pre>1) What can you tell me about .mbsyncstate? Is it a dangling symlink?</pre><pre>An empty file? very large?</pre><pre>
</pre><pre>2) what happens if you add .mbsyncstate to new.ignore with 'notmuch config'?</pre><pre>
</pre>

</body></html>