Comment 24 for bug 997269

Hm, a fix was released... Can we have more info on what was fixed in apparmor itself ? (which commit, and which ubuntu/debian package/version) ?
My server is in 12.04.1 LTS and I don't want to upgrade the whole system it only for this, so I need more info.

I just upgraded my apparmor package from 2.7.102-0ubuntu3.7 to 2.7.102-0ubuntu3.10 ... But the changelog does not seem to list this bug as fixed::

  * 0022-aa-logprof-PUx_rewrite_fix-lp982619.patch: fix aa-logprof
    rewrite of PUx modes (LP: #982619)
  * 0023-lp1091642-parser-reset_matchflags.patch: prevent reuse of
    matchflags in parser dfa backend and add testcase demonstrating
    the problem (LP: #1091642)
  * 0024-profiles-allow_exo-open-lp987578.patch: allow exo-open to work
    within ubuntu-integration (LP: #987578)

Also, the current bug thread is not clear about if this is related to apparmor-profile or to an apparmor bug.

But, I don't have any apparmor-profile package installed and I am experiencing this issue randomly.

Namely:

Feb 26 10:45:36 mail dovecot: imap(foobar): Error: fcntl(unlock) locking failed for file /home/foobar/.mail/dovecot.index.log: No such file or directory
Feb 26 10:45:36 mail dovecot: imap(foobar): Error: fstat() failed with file /home/foobar/.mail/dovecot.index.log: No such file or directory
Feb 26 10:47:00 dovecot: last message repeated 15 times

Many thanks if anybody as any info on this topic.