Valentin, do you have any DENIED messages from AppArmor in your dmesg
output, /var/log/syslog, or /var/log/audit/audit.log files?
Thanks
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/997269
Title:
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 fr
** Changed in: apparmor (Debian)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/997269
Title:
dovecot imap broken by apparmor policy
To manage notifications
** Changed in: apparmor (Ubuntu)
Status: Incomplete => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/997269
Title:
dovecot imap broken by apparmor policy
To manage notifications
Vin, this should be fixed since AppArmor bzr r2548 (but didn't make it
into 14.04 yet).
You can get the latest profile from to http://bazaar.launchpad.net
/~apparmor-dev/apparmor/master/files/head:/profiles/apparmor.d/ -
download usr.lib.dovecot.imap-login and abstractions/dovecot-common
(newly ad
In 14.04, the profile usr.lib.dovecot.imap-login does not allow the
process to read from /var/run/dovecot/config, causing the client to see
tls handshake timeouts if that profile is in enforce mode. Should I
open a new bug?
--
You received this bug notification because you are a member of Ubuntu
For me it has been fixed by 14.04 and can now run with the different
dovecot apparmor profiles swithed on
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/997269
Title:
dovecot imap broken by apparmor
** Changed in: apparmor (Ubuntu)
Status: Expired => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/997269
Title:
dovecot imap broken by apparmor policy
To manage notifications abou
** Changed in: apparmor (Debian)
Status: Unknown => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/997269
Title:
dovecot imap broken by apparmor policy
To manage notifications about
** Bug watch added: Debian Bug tracker #732184
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=732184
** Also affects: apparmor (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=732184
Importance: Unknown
Status: Unknown
--
You received this bug notification because
[Expired for apparmor (Ubuntu) because there has been no activity for 60
days.]
** Changed in: apparmor (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/9972
I am seeing this in 13.10 server.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/997269
Title:
dovecot imap broken by apparmor policy
To manage notifications about this bug go to:
https://bugs.launc
Is this still a problem with Ubuntu 14.04? The dovecot profiles received
a number of updates since this bug was reported.
** Changed in: apparmor (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
thanks for explanation and workaround. Helped me to solve it on 12.10
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/997269
Title:
dovecot imap broken by apparmor policy
To manage notifications abou
** Changed in: apparmor (Ubuntu)
Status: Expired => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/997269
Title:
dovecot imap broken by apparmor policy
To manage notifications about
[Expired for apparmor (Ubuntu) because there has been no activity for 60
days.]
** Changed in: apparmor (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/9972
On 07/08/2012 09:02 PM, Jamie Strandboge wrote:
> Thanks for the extra information. Can you also attach the output of:
> $ sudo aa-status
This is already there, in the attachment ApparmorStatusOutput.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subs
I am able to reproduce this on a fresh install some times but not
reliably. It would be great if someone who has some apparmor experience
could have a look at this.
Steps to re-produce:
1. Install Ubuntu 12.04 Server from amd64 ISO in a virtual machine and make
sure it is up to date:
# apt-get u
Thanks for the extra information. Can you also attach the output of:
$ sudo aa-status
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/997269
Title:
dovecot imap broken by apparmor policy
To manage no
apport information
** Tags added: apport-collected
** Description changed:
Syslog output:
Apr 29 10:59:06 host12 dovecot: imap(foobar): Error: fcntl(unlock) locking
failed for file /home/foobar/Maildir/dovecot.index.log: No such file or
directory
Apr 29 10:59:06 host12 dovecot: imap(f
Also, can you perform the following after seeing the error condition?
$ apport-collect 997269
This will provide logs and system information needed for diagnosing the
problem.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bug
Marking the dovecot task Invalid for now-- the apparmor profile is not
shipped by default or enabled by dovecot and if there is a problem, it
is with apparmor.
** Changed in: dovecot (Ubuntu)
Status: Confirmed => Invalid
** Changed in: apparmor (Ubuntu)
Status: Confirmed => Incomple
Thank you for using Ubuntu and reporting a bug. The 'null' lines are
used when the profile is in complain mode. The apparmor log message
states that the access was allowed, so I am not sure why it would be
getting in the way.
Can you provide exact steps on how to reproduce this?
--
You received
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: dovecot (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/997269
Title:
dov
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: apparmor (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/997269
Title:
do
** Changed in: dovecot (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/997269
Title:
dovecot imap broken by apparmor policy
To manage notifications about thi
This looks like it could be an apparmor bug instead of dovecot bug, it
just happens to manifest itself with dovecot. Adding "apparmor" in
"affects".
** Also affects: apparmor (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ub
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to 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/dovecot/+bu
28 matches
Mail list logo
