ar could you attach your profile set
--
BUG: unable to handle kernel NULL pointer dereference at 0010
https://bugs.launchpad.net/bugs/367499
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-
Your profile set is the text files of the profiles on your system. They
are found in /etc/apparmor.d/
--
BUG: unable to handle kernel NULL pointer dereference at 0010
https://bugs.launchpad.net/bugs/367499
You received this bug notification because you are a member of Ubuntu
Bugs, wh
** Changed in: linux (Ubuntu Jaunty)
Status: Triaged => Fix Committed
** Changed in: linux (Ubuntu)
Status: Triaged => Fix Committed
** Changed in: linux (Ubuntu)
Status: Fix Committed => Fix Released
--
AppArmor Debug: Hook being called from interrupt context
https://bugs.
Public bug reported:
Binary package hint: xorg
Xorg stopped responding to input from the keyboard and mouse. The
mouse cursor still moves, notifications are still being displayed,
but input from mouse and keyboard have no effect.
The vt can be switch to and is working, switching back and forth h
** Attachment added: "BootDmesg.txt"
http://launchpadlibrarian.net/30263441/BootDmesg.txt
** Attachment added: "CurrentDmesg.txt"
http://launchpadlibrarian.net/30263442/CurrentDmesg.txt
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/30263443/Dependencies.txt
** A
Public bug reported:
Binary package hint: xorg
After rotating the screen and then rotating back to Normal the mouse
cursor remains rotated.
ProblemType: Bug
Architecture: i386
Date: Fri Aug 7 04:59:00 2009
DistroRelease: Ubuntu 9.10
MachineType: LENOVO 7762WGS
Package: xorg 1:7.4+3ubuntu5
ProcC
** Attachment added: "BootDmesg.txt"
http://launchpadlibrarian.net/3330/BootDmesg.txt
** Attachment added: "CurrentDmesg.txt"
http://launchpadlibrarian.net/3331/CurrentDmesg.txt
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/3333/Dependencies.txt
** A
Public bug reported:
Binary package hint: xorg
Desktop effects can no longer be enabled. The desktop effects were
working but they have stopped functioning after a reboot and can not be
reenabled.
ProblemType: Bug
Architecture: i386
Date: Fri Aug 7 04:55:04 2009
DistroRelease: Ubuntu 9.10
Mach
** Attachment added: "BootDmesg.txt"
http://launchpadlibrarian.net/3463/BootDmesg.txt
** Attachment added: "CurrentDmesg.txt"
http://launchpadlibrarian.net/3464/CurrentDmesg.txt
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/3465/Dependencies.txt
** A
** Attachment added: "BootDmesg.txt"
http://launchpadlibrarian.net/30005993/BootDmesg.txt
** Attachment added: "CurrentDmesg.txt"
http://launchpadlibrarian.net/30005994/CurrentDmesg.txt
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/30005995/Dependencies.txt
** A
Public bug reported:
Binary package hint: xorg
After rotating the Desktop, and rotating back to Normal the screen goes
black. The screen is can be restored by switch to a VT and then back to
X or by closing the lid and opening it back up.
ProblemType: Bug
Architecture: i386
Date: Fri Aug 7 05:
** Changed in: linux (Ubuntu Karmic)
Status: Confirmed => In Progress
--
apparmor paths are broken when using ecryptfs on jaunty
https://bugs.launchpad.net/bugs/359338
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bug
This behavior still exists in Jaunty and Karmic and it is going to be handled
in the user space at the policy level. The user space tools are being extended
to be able to handle, this in a couple of ways.
1. There will be a global policy file where rules like the work around
specified above c
I took a look at this and it is behaving correctly, though I haven't
established whether it is due to a deviation in AppArmor's behavior, the
scripts or both. The executable /sbin/dhclient3 does a Px transition
(as specified in its profile) to /sbin/dhclient-script.
/sbin/dhclient-script
I have looked at this for Jaunty and have a patch that fixes this for all but 1
case in the kernel. That one case however requires a larger change and need
further investigation. That one case still requires
owner @{HOME}/.Private/** rw, be added to profiles.
Testing in Karmic has shown that
Dustin,
it shouldn't matter where the encrypted data is placed, so this change
should not have any effect.
--
apparmor paths are broken when using ecryptfs on jaunty
https://bugs.launchpad.net/bugs/359338
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscr
Dustin,
it shouldn't matter where the encrypted data is placed, so this change
should not have any effect.
--
apparmor paths are broken when using ecryptfs on jaunty
https://bugs.launchpad.net/bugs/359338
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscr
This turns out to be a regression in Jaunty, that is now fixed and
behaving properly in Karmic
** Changed in: linux (Ubuntu Karmic)
Status: Confirmed => Invalid
--
dhclient-script fails with apparmor
https://bugs.launchpad.net/bugs/400349
You received this bug notification because you are
practice.
** Changed in: linux (Ubuntu Jaunty)
Status: New => Confirmed
** Changed in: linux (Ubuntu Jaunty)
Assignee: (unassigned) => John Johansen (jjohansen)
--
dhclient-script fails with apparmor
https://bugs.launchpad.net/bugs/400349
You received this bug notification b
In the current fix apparmor is disabled by default, while further
testing is done.
To enable apparmor, on the grub command line add
security=apparmor
--
apparmor fails to load at startup
https://bugs.launchpad.net/bugs/375422
You received this bug notification because you are a member of Ubuntu
Sorry Bryce, I can't answer that one. The machine having this problem
had a failed update that resulted in a reinstall. With the reinstall
and latest updates desktop effects can now be enabled.
--
[i965GM] Desktop effects could not be enabled
https://bugs.launchpad.net/bugs/410258
You received
Bryce,
I haven't been able to reproduce since Friday when X completely locked
up on me and would kill all input once it started. This was consistent
behavior and would happen every time I started X, either through gdm at
startup or using startx. This is when I finally did a complete
reinstall.
Now that you mention it, I did have weird application input errors very
similar to what you describe a few hours before this complete lock up.
At the time I attributed it to the network as I doing a git clone and
several of the apps were X forwarded from another machine.
Also I was working in a fo
Sean,
would it be possible to attach your log files or a section of them so that I
can analyze why it is requiring
@{HOME}/Desktop/ w,
@{HOME}/Desktop/* w,
--
cups-pdf fails to generate file when user does not print to default ~/PDF
(apparmor vs.cups-pdf inconsistency)
https://bugs.launchp
well, I can confirm it, and even provide some insight.
MUGEN does some very uhm interesting things on startup. It creates a
new elf file in tmp, uses open to pin the file and then it deletes it.
This results in the file being removed from the namespace and completely
inaccessable except to proces
hrmm, well it seems I did fix this for unconfined processes before the
final version of hardy (I remember fixing it for AppArmor 2.3 but I
thought the fix missed Hardy), and my test machine wasn't properly
updating. So after a fresh install MUGEN now works.
So to clarify, in Hardy MUGEN will run
The log isn't displaying correctly in the browser because its type is
set as html, but it is a plain text file.
The log is corrupt but in a very odd way that I have never encountered
before. I have a few possible ideas:
Your kernel ring buffer is being filled and the messages are wrapping,
overw
Vincent can you attach your /var/log/messages & if present
/var/log/audit/audit.log
--
fails to start: cannot apply additional memory protection after relocation -
apparmor doesn't work on stacked file system (livecd)
https://bugs.launchpad.net/bugs/131976
You received this bug notification beca
Well I can say that this isn't related to
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/140508 as the
problem there was a message format change and not the message being
logged.
Since messages being sent to the kernel ring buffer (dmesg), we can
infer that auditd isn't running. What hap
could you take a look and verify the messages are showing up in
/var/log/syslog and /var/log/kern.log
and could you also attach your /etc/apparmor/logprofi.conf
--
Profile violations fail to log correctly
https://bugs.launchpad.net/bugs/157952
You received this bug notification because you are
err sorry for the typo the config file is /etc/apparmor/logprof.conf
--
Profile violations fail to log correctly
https://bugs.launchpad.net/bugs/157952
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ub
Can you check and see if the genprof marks and kernel messages are going
to /var/log/syslog and if they both are can you try editing your
/etc/apparmor/logprof.conf
from
logfiles = /var/log/audit/audit.log /var/log/messages /var/log/syslog
to
logfiles = /var/log/syslog
--
Profile violations
If the above doesn't work could you include the output from the
following command
ps aux | grep logd
--
Profile violations fail to log correctly
https://bugs.launchpad.net/bugs/157952
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
Your ps output shows that klogd isn't running. This means none of the
kernel messages will make it to syslog.
do "ps aux | grep logd" and kill the dd process and then run
"/etc/init.d/klogd start", then rerun "ps aux | grep logd" to make sure
klogd and syslogd are running. If they are try profi
Glad to hear it worked. My guess is that it happened because Ubuntu
runs klogd under the klogd user instead of root.
--
Profile violations fail to log correctly
https://bugs.launchpad.net/bugs/157952
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug con
Sadly the man pages didn't get updated to reflect locking, append,
network rules, or change_profile, this is a bug and you can add it to
launch pad or reference the bug filed in the forge bugzilla
https://bugzilla.novell.com/show_bug.cgi?id=326210.
genprof/logprof should be able to update the prof
hmm, strange it works for me. Is there away that I can get a login on
the machine, and take a look at what is going on?
If not I will see what else we can do.
--
Corrupted AppArmor audit log messages
https://bugs.launchpad.net/bugs/160238
You received this bug notification because you are a mem
Could you provide more detail about how your system is crashing? What
part of your system is crashing? Is this a default fiesty install or
have installed a custom kernel? I didn't see any oops in your dmesg
dump. The only "error" that I can see is the message below
audit(1196006403.262:3): type
You can either manually edit the klogd profile or use the profiling tool
logprof.
> logprof /sbin/klogd
logprof should scan your log file and find the reject and then ask to add "r"
permission for /proc/kallsyms, saying
yes will allow this and then you can save and place the profile in enforce m
Okay thankyou, looking at the kmesg dump it would appear I need to look
into the kernel auditing code more closely.
As for not being able to start klogd, sorry about that I seemed to have
edited my local profiles for testing long ago and had forgotten about
making the changes.
--
Corrupted AppAr
If auditd is working for you, I wouldn't worry about it.
If however you want to use syslog or just want to try debugging this I
can walk you through it step by step. It really wouldn't be much more
than copying and pasting some script lines and commenting others out.
--
Corrupted AppArmor audit
okay the first thing I want you to try is removing the use of dd from
the auditing chain
open /etc/init.d/klogd in an editor (you need to be root), find the line
that looks like this
# shovel /proc/kmsg to pipe readable by klogd user
start-stop-daemon --start --pidfile $kmsgpidfile --exec
your console log (near the end) shows that klogd is not running, which means
none of the kernel messages will get logged.
21:06:01~>ps aux | grep logd
syslog5093 0.1 0.0 1916 700 ?Ss 20:35 0:03 /sbin/syslogd
-u syslog
ubuntu8032 0.0 0.0 2976 768 pts/0R+ 21:
Both of those flags would be easy to implement, the question is it worth it?
As Kees pointed out an unconfined user can easily circumvent policy attachment
and thus the flags that AppArmor would be enforcing. There are four cases I
can see this working in:
- trusted start up of deamon, only wo
This is a side effect of linux personalities. When booting on an ia32
machine hardy has the READ_IMPLIES_EXEC flag set in its personality.
This causes an mmap for read permission to also ask for PROT_EXEC, which
causes the extra 'm' request seen above. Ubuntu by default is mounting
several things
sorry, I jumped the gun slightly and mis read a mount line and a piece
of code. The nosuid option does interact with this but is not whats
causing the clearing of the personality. Execution of any setuid binary
will cause the personality to get cleared, so using either su or sudo to
switch from u
Yes, it is part of the apparmor-utils package so it isn't a required part of
the default install, you will need to run it as root to be able to collect as
much information as possible. All the information collected by aa-status is
available manually (its just raw in a raw form) if you don't wan
there are a couple things going on here. The batch update recompiles the
policy which is cpu intensive, more so as multiple profiles are being done in
parallel. Once done, the compiled policy is cached in /etc/apparmor.d/cache/
We have discussed dropping the parallel compute part which would he
Nikolaus upstream does watch here and track bugs filed in launchpad.
This particular issue arise due to the LSM not providing AppArmor
sufficient information about access on stacked file systems. You can
mostly work around the issue using the alias command
can you try adding the following command
Nikolaus,
did you restart apparmor after making the change? The profiles will have to be
reloaded.
> sudo /etc/init.d/apparmor restart
if that doesn't work can you attach your profiles
--
apparmor doesn't work on stacked file system (livecd) -- DHCP/cups/others fail
to start
https://bugs.lau
Nikolaus,
thanks, it looks like you have hit a bug in the alias command, I'll look
into this and see if I can't get something for you to test in the next
couple of days.
--
apparmor doesn't work on stacked file system (livecd) -- DHCP/cups/others fail
to start
https://bugs.launchpad.net/bugs/13
Right I messed up the alias order but there is still a bug in alias processing,
that needs to be fixed before this will work. Basically setting
alias /etc -> /rofs/etc,
will result in rejections for accesses to /etc/ instead of /rofs/etc/
--
apparmor doesn't work on stacked file system (live
Matt,
sounds like virtual box crashing some where around when it does its
input grab, I have experienced virtual machines grabbing input and not
returning before too, can you try to replicate and then from a terminal
run
apport-collect -p linux-image-`uname -r` 367499
it might be an idea to have
Matt,
sounds like virtual box crashing some where around when it does its
input grab, I have experienced virtual machines grabbing input and not
returning before too, can you try to replicate and then from a terminal
run
apport-collect -p linux-image-`uname -r` 367499
it might be an idea to have
Same conflict here with a tablet pc. The failure message from synaptic
is:
Could not mark all packages for installation or upgrade
The following packages have unresolvable dependencies.
Make sure that all required repositories are added and enabled
in the preferences.
xserver-xorg-input-wacom:
Make that xserver-xorg-core
Which is installed.
--
xserver-xorg-input-wacom conflicts with xserver-xorg-core
https://bugs.launchpad.net/bugs/501206
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs
This bug has been isolated to the dfa and transition table generation in
the apparmor_parser, the HOMEDIRS tunable triggered this by causing many
extra states to be generated. The bug is not Atom specific but the
Atom doesn't deal well with the current code doing the generation.
There are a coup
The Lucid kernel add some flags to provide better control over this and
other path behaviors and it looks like the flag for deleted file lookup
isn't properly being applied. It will be fixed in the next update of
AppArmor.
--
apparmor disallows truncate of deleted file
https://bugs.launchpad.net
The Karmic proposed kernels have been tested on EC2. They boot and
everything appears to be working correctly.
--
ec2 kernel needs CONFIG_BLK_DEV_LOOP=y and other config changes
https://bugs.launchpad.net/bugs/428692
You received this bug notification because you are a member of Ubuntu
Bugs, whi
This is looking like a failure in AppArmor's path resolution
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => John Johansen (jjohansen)
--
apparmor not properly handling file deletion on NFS
https://bugs.launchpad.net/bugs/415632
You received this bug notification because y
Laszlo,
Have you seen a similar oops occur in Karmic? AppArmor no longer
touches ATTR_FILE so if you are seeing similar behavior I am going to
need an oops or something more tangible to examine.
--
aufs fchown() bug caused by apparmor
https://bugs.launchpad.net/bugs/487097
You received this bug
Yes I have now tested with the linux-backports-modules-wireless-karmic-
generic and a fully updated karmic but the problem persists. Network
manager now reports it as connect speed unknown and iwconfig as Bit
Rate=0 kb/s.
--
Wireless reports connection Bit Rate=0 kb/s
https://bugs.launchpad.net/
** Changed in: linux (Ubuntu Karmic)
Status: In Progress => Invalid
** Changed in: linux (Ubuntu Lucid)
Status: In Progress => Invalid
--
aufs fchown() bug caused by apparmor
https://bugs.launchpad.net/bugs/487097
You received this bug notification because you are a member of Ubunt
Just an update we have Karmic kernels now (see lp bug 418130), also the
alpha6 ami when release should a karmic kernel set as the default. This
should enable testing to proceed.
--
Provide Ubuntu EC2 kernels with 1000Hz timer (for VOIP/Asterisk)
https://bugs.launchpad.net/bugs/365233
You receive
No I haven't been able to confirm it is a kernel issue yet, though I am
planning on devoting some good time to this bug over the next couple
days.
--
Frequent random KVM host kernel OOPS
https://bugs.launchpad.net/bugs/361819
You received this bug notification because you are a member of Ubuntu
Importance lowered as there is a function karmic kernel with the Xen
patchset (lpn Bug #418130) that can be used. It is still desirable to
fix this bug as using a pv-ops kernel is desirable in the long run.
This bug is still blocked on obtaining further information from Amazon.
--
ami-bbf514d2:
** Changed in: apparmor (Ubuntu)
Status: In Progress => Fix Released
--
AppArmor generated includes files are not ignored by git
https://bugs.launchpad.net/bugs/419505
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bug
While it appears there is some kernel interaction it isn't just a kernel
issue. I did further testing and came up with some interesting
results.
ami | aki| ari
| full boot | init message go to console
fedora a
Jeremy,
Are you getting AppArmor rejects? They should show up in the output of
dmesg.
Can you run
apport-collect -p apparmor 445818
--
profile for usr.sbin.dnsmasq needs adjustment
https://bugs.launchpad.net/bugs/445818
You received this bug notification because you are a member of Ubuntu
Bug
lived learning session
where profile are frequently replaced.
** Affects: linux (Ubuntu)
Importance: Undecided
Assignee: John Johansen (jjohansen)
Status: In Progress
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => John Johansen (jjohansen)
** Changed in: linux
Public bug reported:
AppArmor will cause a hard lockup due to calling vfree in interrupt
context, backtrace attached below
** Affects: linux (Ubuntu)
Importance: Undecided
Assignee: John Johansen (jjohansen)
Status: In Progress
** Changed in: linux (Ubuntu)
Assignee
[ 80.250147] [ cut here ]
[ 80.251233] kernel BUG at
/home/jj/ubuntu/lucid/ubuntu-lucid/mm/vmalloc.c:1406!
[ 80.252769] invalid opcode: [#1] SMP
[ 80.253702] last sysfs file: /sys/devices/pci:00/:00:04.0/class
[ 80.255107] CPU 0
[ 80.29] Modul
** Changed in: apparmor (Ubuntu)
Assignee: (unassigned) => John Johansen (jjohansen)
** Changed in: apparmor (Ubuntu)
Status: Incomplete => In Progress
--
Triggers permanent high i/o load after upgrade
https://bugs.launchpad.net/bugs/549428
You received this bug notification b
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => John Johansen (jjohansen)
** Changed in: linux (Ubuntu)
Status: Incomplete => In Progress
--
"Kernel Oops" - unable to handle kernel paging request at 880323279bf2 RIP
is at aa_dfa_match_len
** Changed in: linux (Ubuntu)
Status: Incomplete => In Progress
--
BUG: unable to handle kernel NULL pointer dereference at 0010
https://bugs.launchpad.net/bugs/367499
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
: linux (Ubuntu)
Importance: Undecided
Assignee: John Johansen (jjohansen)
Status: In Progress
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => John Johansen (jjohansen)
** Changed in: linux (Ubuntu)
Status: New => In Progress
--
AppArmor leaks ch
Public bug reported:
The debug warning of scrubbing the environment variables is used by
userspace to detect when exec and permission failures may be caused
by environment variable scrubbing like when firefox execs java
as in bug http://bugs.launchpad.net/bugs/484148. Having it mispelled
makes it
be mediated by path instead of delegated.
** Affects: linux (Ubuntu)
Importance: Undecided
Assignee: John Johansen (jjohansen)
Status: In Progress
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => John Johansen (jjohansen)
** Changed in: linux (Ubuntu)
Sta
Public bug reported:
The error case for ptrace permission on exec missed putting the new_profile,
fix this ommission and consolidate the error cases to a single point.
** Affects: linux (Ubuntu)
Importance: Undecided
Assignee: John Johansen (jjohansen)
Status: In Progress
: cd5e6716a74226b5013f2467bf3ed6df394a6495
** Affects: linux (Ubuntu)
Importance: Undecided
Assignee: John Johansen (jjohansen)
Status: In Progress
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => John Johansen (jjohansen)
** Changed in: linux (Ubuntu)
Status: New => In Pr
Vadim,
have you seen this again with update Karmic kernels?
** Changed in: linux (Ubuntu)
Status: New => Incomplete
--
BUG: unable to handle kernel NULL pointer dereference at (null)
https://bugs.launchpad.net/bugs/453681
You received this bug notification because you are a member of Ub
Martin,
can you elaborate on how this helps, where you notice it, etc.
Also can you reboot with AppArmor enabled and rerun aa-status and attach
its output along with the the kern.log again.
Also can you try,
making symlinks in /etc/apparmor.d/disable/ to the /usr/sbin/mysqld and
/usr/bin/evince
crazybyte,
can you try this with the latest 2.6.32-21 Lucid kernel (yes I know the
report is against Karmic kernel). There have been several fixes there
and that will help narrow this down. You can install the Lucid kernel
package without upgrading to Lucid and be able to dual boot between the
K
crazybyte,
Hrmm okay thanks for the information, but we still need to try to
isolate this. First up have you checked to see if there is an updated
bios for your machine and have you tried running memtest for an extended
period on your machine?
I would very much like for you to try the latest ker
crazybyte,
Alright well I think you can start booting theLucid kernel with out the
extra boot parameters. Some bioses are just broken when it comes to
suspend/resume but there are sometimes workarounds for them. Have a
look at https://wiki.ubuntu.com/DebuggingKernelSuspendHibernateResume
Basica
Martin,
can you try booting with apparmor=0 as a kernel parameter at boot. This
will completely disable AppArmor so that it never initializes.
--
system bogs down when apparmor is running
https://bugs.launchpad.net/bugs/552225
You received this bug notification because you are a member of Ubunt
The cause of this wasn't found in time for beta1 deadline. It is being
worked on and will happen post beta1.
** Changed in: linux-ec2 (Ubuntu Lucid)
Milestone: ubuntu-10.04-beta-1 => ubuntu-10.04-beta-2
--
ec2 instance fails boot, no console output on c1.xlarge
https://bugs.launchpad.net/b
gt; In Progress
** Changed in: linux-ec2 (Ubuntu)
Assignee: (unassigned) => John Johansen (jjohansen)
--
High load averages on Lucid EC2 while idling
https://bugs.launchpad.net/bugs/574910
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
The proposed package was tested and works as expected.
--
apparmor fails to log change_hat transitions
https://bugs.launchpad.net/bugs/462824
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.
** Changed in: apparmor (Ubuntu Karmic)
Status: New => Fix Committed
** Changed in: apparmor (Ubuntu Lucid)
Status: Fix Committed => Fix Released
--
apparmor fails to log change_hat transitions
https://bugs.launchpad.net/bugs/462824
You received this bug notification because you ar
** Changed in: apparmor (Ubuntu)
Status: Confirmed => Fix Released
--
apparmor doesn't work on stacked file system (livecd) -- DHCP/cups/others fail
to start
https://bugs.launchpad.net/bugs/131976
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscri
Lamont, how long did you let it run for before trying to kill it, and
what are the machine specs (so I can make a guess at how long it should
have been computing for)? Did you check the apparmor_parser's reported
state and if so what was it?
--
unkillable apparmor_parser
https://bugs.launchpad.n
If you have been affected by this bug, please try the following test
kernel.
aki-5b658a32
ari-5d658a34
--
ec2 instance fails boot, no console output on c1.xlarge
https://bugs.launchpad.net/bugs/527208
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribe
Johan,
When package postinst replaces a profile there is a period where it goes
through recompiling the policy that takes a lot of cpu and memory. How
long the process takes depends on your processor and exact policy being
recompiled but on slower processors this can take a minute or so, and
can
Johan,
never mind I missed it below DarkNova's comment, thanks.
--
apparmor_parser: page allocation failure. order:5
https://bugs.launchpad.net/bugs/458299
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubu
DarkNova,
Can you attach your kernel message log (/var/log/kern.log), or out put
of dmesg?
--
apparmor_parser: page allocation failure. order:5
https://bugs.launchpad.net/bugs/458299
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
u
Loïc,
are you using auditd? If so can you attach output for /var/log/audit/audit.log
Also if you run into this again can you attach the output of aa_status.
--
Triggers permanent high i/o load after upgrade
https://bugs.launchpad.net/bugs/549428
You received this bug notification because you ar
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => John Johansen (jjohansen)
--
AppArmor oops when loading an empty profile
https://bugs.launchpad.net/bugs/496110
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-b
Dustin,
can you attach the dmesg from immediately after this happens
--
[Lucid] Error starting domain: could not remove profile
https://bugs.launchpad.net/bugs/517714
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailin
I haven't been able to reproduce this, and believe the commit mentioned
above was likely the fix so moving to incomplete.
** Changed in: linux (Ubuntu)
Status: Triaged => Incomplete
--
apparmor crashing apache when removing/changing hats
https://bugs.launchpad.net/bugs/502442
You receive
1 - 100 of 8093 matches
Mail list logo
