Re: [Evolution] [Fwd: Re: local mail spool still unaccessible with evo 3.4.4.-1]

OK.  But the bottom line is that Evolution can't get a lock on your mail
spool file - if it can't get a lock, then it can't do anything with it.
If the permissions on the file are correct, then there must be some
other process holding a lock on it.  You need to find out which process
that is and why it is holding a lock.

Processes having locks are:
<user> 32629 2.8 10.6 536428 165880 ? Sl 09:12
2:36 /usr/lib/iceweasel/firefox-bin
<user> 1978  0.0  0.0   2128    12 ? Ss   Oct10   0:00 /usr/sbin/atd
daemon    1574  0.0  0.0  1960 304 ? Ss   Oct10   0:00 /sbin/portmap

and a non-existing process with PID 2105:
7: FLOCK  ADVISORY  WRITE 2105 00:0e:7109 0 EOF
What does this mean??

None of them are listing the inode number I have for /var/mail/<user>
ls -li /var/mail/<user>
15811 -rw-rw---- 1 <user> mail 95736997 Oct 31 10:02 /var/mail/<user>

OK.  I've done some more Googling on your behalf - there was a
Debian/Ubuntu packaging bug that might affect you - basically make sure
that /usr/lib/evolution/camel-lock-helper-1.2 is SGID mail.


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]