Hello Cédric,
On Tue, Oct 20, 2015 at 04:00:36PM +0200, Cedric 321 wrote:
> Hello Carsten,
>
> Thank you for your fast response.
>
> I have done:
> $ mv ~/.icedove ~/old_icedove
> I have configured my email address cedric...@gmx.fr after a new start of
> icedove.
>
> I have tried this two commands:
> $ strace -e file -f -s2048 -o /tmp/icedove_dbg.txt icedove
> $ NSPR_LOG_MODULES=IMAP:5,SMTP:5 NSPR_LOG_FILE=~/icedove-activity.log
> icedove
>
> To have the probem, i have closed it few times after start it (Icedove is
> still searching messages on email address).
> =>icedove-activity_problem.log
> =>icedove_dbg_problem.txt
>
> To have no probems, i let it make.
> =>icedove-activity_correct.log
> =>icedove_dbg_correct.txt
>
> I notice that it doesn't "
> unlink("/home/cedric/.icedove/q8n4qwsr.default/lock") = 0 " when the problem
> arrives.
I never have provoke Icedove to such a behavior, this looks like a race
condition in the locking part. But my (our) knowing about this specific
internal part is quite near zero.
This issue is likely a upstream related problem. You could test this
with the releases from Mozilla and report the result into the bug tracker
on Mozilla. A forwarded entry into this Debian report would keep us in
sync with the progress on the Mozilla bug tracker.
Would you please report that issue here upstream? If you don't know how
to forward the upstream bug report I'm surly can help.
Regards
Carsten
