Package: icedove
Version: 31.8.0-1~deb8u1
Severity: serious

icedove is just not working any more

The host was shutdown yesterday (5 August) and when started up again, I
could only see messages up to 27 July

Normally at startup it asks for the master password, this prompt is not
appearing

I enabled debugging:


    NSPR_LOG_MODULE=IMAP:5 NSPR_LOG_FILE=~/icedove-issue.log icedove


and in the log file I see:

 1115800:th3:NA:CreateNewLineFromSocket: * OK [CAPABILITY IMAP4rev1
LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE IDLE AUTH=PLAIN] Dovecot ready.
 try to log in
 IMAP auth: server caps 0x4085425, pref 0x1006, failed 0x0, avail caps
0x1004
 (GSSAPI = 0x1000000, CRAM = 0x20000, NTLM = 0x100000, MSN =  0x200000,
PLAIN = 0x1000, LOGIN = 0x2, old-style IMAP login = 0x4)auth external
IMAP login = 0x20000000
 trying auth method 0x1000
 IMAP: password prompt failed or user canceled it
 login failed entirely



The mail server log shows that there was a connection and no attempt to
authenticate

There was no password prompt on the client, either for the account
password or the master password

I stopped the process and went into the profile directory and did

$ sqlite3 signons.sqlite
SQLite version 3.8.7.1 2014-10-29 13:59:56
Enter ".help" for usage hints.
sqlite> PRAGMA integrity_check;
Error: database is locked
sqlite>


so it appears the sqlite file was corrupted at shutdown.  Why doesn't
icedove inform me that the file is corrupt, why does it just sit there
showing me old messages and giving no feedback there is a problem?

I tried to work around this by moving the ~/.icedove directory to a
backup location, shutting down icedove on my laptop and then copying the
~/.icedove directory from laptop to desktop home directory

Upon starting up, it still isn't prompting me for the master password.

I also tried starting up in safe made, it still doesn't resolve the issue.

Does it depend on some other (potentially corrupt) file outside
~/.icedove?  Why doesn't it display an error to tell me what is wrong
and where to look?


--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Reply via email to