I have the following very frustrating symptoms:
1) Thunderbird will frequently decide that it does not have the headers for a particular folder, and will reload them. Th… (మరింత చదవండి)
I have the following very frustrating symptoms:
1) Thunderbird will frequently decide that it does not have the headers for a particular folder, and will reload them. This is in spite of the fact that I had all the headers the last time that I used the program, and I have not restarted Thunderbird or the computer (although I may have put it to sleep).
In one specific case, I clicked on my Inbox, and TB started a "compact" operation, and then it started to download *all* of the headers. Eventually it produced an error message for the compaction:
" The folder ‘Inbox on williamatwood41@gmail.com’ could not be compacted because writing to folder failed. Verify that you have enough disk space, and that you have write privileges to the file system, then try again."
2) Thunderbird will often state that a summary file cannot be opened:
"Unable to open the summary file for Drafts on william.atwood@concordia.ca. Perhaps there was an error on disk, or the full path is too long."
I have seen this for the Drafts folder, for the Inbox folder, for the Sent folder, and for arbitrary folders that I had previously opened successfully.
3) One day, I clicked on a folder that contained 6116 messages. I saw it download all of the headers. Then the right panel declared "No message found."
The next day, I clicked on the same folder. While downloading the headers, TB listed the low-numbered messages on the right side (upper panel), and then switched to the most recent message once all the headers had been downloaded. So, the behavior changed from one day to the next.
All of this seems to have started when I placed a restriction on the length of time that messages are synchronized. This was done because I was running out of disk space on my 250 GB disk. I subsequently replaced this disk with a 500 GB disk, but have not (yet) relaxed the constraint, because I wanted to get to the bottom of the problem.
My best guess is that setting the disk space limit has triggered some misuse of a pointer, which is resulting in the garbage-in, garbage-out syndrome. However, I could be way off.
I would be very happy to work with anyone on the TB team, and invoke whatever debugging tools are necessary (under direction) to find the root cause of this error.