Ok, I finally found the root cause of this problem
On the NFS server, dmesg output included the line:
"lockd: cannot monitor host1"
repeated many times. It would appear several times each time I tried to
start icedove.
Looking in other logs, I found that /var had filled up on the NFS serve
On Fri, Aug 07, 2015 at 10:33:17AM +0200, Daniel Pocock wrote:
> > You are not working on a NFS/CIFS or BTRFS filesystem?
>
> It is a BtrFs filesystem accessed over NFS
>
> It has been working this way for a long time
>
> I checked the BtrFs filesystem and it definitely has free space and free
>
On 07/08/15 09:20, Carsten Schoenert wrote:
> Hello Daniel,
>
> On Thu, Aug 06, 2015 at 06:24:22PM +0200, Daniel Pocock wrote:
>> I did some more tests
>>
>> I moved the following to a backup location:
>>~/.icedove
>>~/.thunderbird
>>~/.cache/icedove
>>
>> so it should create a complete
Hello Daniel,
On Thu, Aug 06, 2015 at 06:24:22PM +0200, Daniel Pocock wrote:
> I did some more tests
>
> I moved the following to a backup location:
>~/.icedove
>~/.thunderbird
>~/.cache/icedove
>
> so it should create a completely new profile.
~/.thunderbird is completely unrelated
I did some more tests
I moved the following to a backup location:
~/.icedove
~/.thunderbird
~/.cache/icedove
so it should create a completely new profile.
Then I run it in safe mode to avoid any plugins:
$ icedove -safe-mode
The main window appears but it is unresponsive to any mous
5 matches
Mail list logo
