[Bug 997269] Re: dovecot imap broken by apparmor policy
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. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to dovecot in Ubuntu. https://bugs.launchpad.net/bugs/997269 Title: dovecot imap broken by apparmor policy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/997269/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1402657] Re: etckeeper doesn't commit. Missing executable permissions on /etc/etckeeper/commit.d/50vcs-commit
If someone wanted to silently and efficiently deactivate etckeeper history tracking with the least action, this would be the best thing to do. Was hit by this also. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to etckeeper in Ubuntu. https://bugs.launchpad.net/bugs/1402657 Title: etckeeper doesn't commit. Missing executable permissions on /etc/etckeeper/commit.d/50vcs-commit To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/etckeeper/+bug/1402657/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1204069] Re: lxc dhcp fails
I had a 12.04, upgraded to the kernel of 12.10 (kernel v3.5.0-21-generic), and used it flawlessly for several month with LXC containers. Very recently, I had a btrfs issue that made my update my kernel to v3.15.1-031501-generic. That's when my existing containers didn't catch anymore their IP on boot via DHCP. A tcpdump shows bad udp cksum: 16:32:32.032975 IP (tos 0x0, ttl 64, id 25006, offset 0, flags [DF], proto UDP (17), length 71) ns3262489.ovh.net.61855 172.128.0.75.domain: [bad udp cksum 0xdbeb - 0x0796!] 43449+ PTR? 75.0.128.172.in-addr.arpa. (43) For a good blog post around this issue and how to deal with it (not mine): http://colinnewell.wordpress.com/2013/12/18/lxc-networking/ -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1204069 Title: lxc dhcp fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1204069/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
