** Package changed: compiz (Ubuntu) = unity (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/757043
Title:
Segfault reported by compiz
--
ubuntu-bugs mailing list
Some more details
GDM succesfully launches and prompts for login as expected, the bug
happens after login trying to bring up the desktop, which never
successfully happens. Virtually consoles can be switched too, and used
but the desktop never properly recovers (or even falls back to gdm)
without
Public bug reported:
Binary package hint: unity
This is an odd one that I have never experienced under the gnome desktop
+ compiz, so I am filing under unity even though it seems like its more
of a compiz bug.
This bug is sporadic and does not happen every time.
When right clicking on a window
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/757259
Title:
move to another workspace sparadically is wrong and doesn't work
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Public bug reported:
Binary package hint: unity
I don't have a method to reproduce this yet but it does happen to me
several times a day.
The keyboard input is lost from all windows in the workspace, and it
also seems to be lost from compiz. That is general hot keys to switch
workspaces,
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/757435
Title:
keyboard input lost, when window focus lost in unity
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Rob,
Correct there aren't, however it is now possible to easily replace
Ubuntu kernels with custom kernels now that we use pvgrub (it has even
been backported to previous releases). Once a custom kernel has been
made it can be installed into an ebs backed instance and reboot just
like you would
Donato,
can you please attach the output of the following command run from a terminal
apparmor_parser -p /etc/apparmor.d/usr.bin.chromium-browser
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Donato,
could you attach your log file or even just the portion of your log file
containing apparmor messages. Also please attach the output from the
following command that is run from a terminal
apparmor.parser -p /etc/apparmor.d/usr.bin.empathy
--
You received this bug notification
Donato,
the chromium profile has a lot of deny rules in it which by default
quiets known rejects (even in complain mode). Can you execute the
following command as root.
echo -n noquiet /sys/module/apparmor/parameters/audit
This will turn off audit quieting, then could attach the log messages
Yes it is unfortunate. You can however achieve the partially privileged user
using pam_cap.so. I think this may be sufficient for your needs
see http://www.linuxjournal.com/article/10249
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
While Eucalyptus fails on natty with a 2.6.35 kernel, a plain kvm
instance can boot on these machines.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/746751
Title:
kernel: [Firmware Bug]: the BIOS
** Changed in: linux (Ubuntu Maverick)
Assignee: (unassigned) = John Johansen (jjohansen)
** Changed in: linux (Ubuntu Lucid)
Assignee: (unassigned) = John Johansen (jjohansen)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu
This is being caused by the apparmor profile masking the capability set,
even in complain mode. ssd is requesting the capability set and then
modifying its behavior based off of the reduced capability set, and then
DAC does the actual reject.
AppArmor doesn't generate any messages hinting at
This is being caused by the apparmor profile masking the capability set,
even in complain mode. ssd is requesting the capability set and then
modifying its behavior based off of the reduced capability set, and then
DAC does the actual reject.
AppArmor doesn't generate any messages hinting at
Note: this bug does affect Lucid and Maverick code. It appears that
sshd has been updated in such a way that this bug is triggered in Natty
with natty sshd.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Description changed:
+ SRU Justification:
+
+ Impact: Can result in confined application failure with no information
logged on how to fix the problem.
+ Fix: Do not mask the capabilities returned by capget when in complain
mode, this allows the application
+ to progress as
It turns out, after further testing, the problem appears to be present
in 2.6.32-28-generic, but can need several hours (3-4) to surface.
Further testing of 2.6.32-27-generic has not shown the problem so, we
have started bisecting Ubuntu-2.6.32-28.56 Ubuntu-2.6.32-27.49
current bisect status
#
Updated bisect log to be followed by data dump from test system
# bad: [abed218c89023d7b804f4388f147ec3d2fe98952] UBUNTU: Ubuntu-2.6.32-28.56
# good: [ca74d536613567c9301308b54001b5861350b596] UBUNTU: Ubuntu-2.6.32-27.49
git bisect start 'Ubuntu-2.6.32-28.56' 'Ubuntu-2.6.32-27.49'
# good:
Yes, this ability should be coming in Oneiric, and we will hopefully
have some test kernels out soon.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/796588
Title:
Limit inet and inet6 access by
I have a bisect kernel for you to test, whether or not this succeeds
there will be several more kernels to test to narrow down the problem.
using
dpkg -i
please install the test kernel from
http://people.canonical.com/~jj/linux-image-2.6.39-2-generic_2.6.39-2.7~lp793437.1_amd64.deb
and
alright thanks, second test kernel
http://people.canonical.com/~jj/linux-
image-2.6.39-2-generic_2.6.39-2.7~lp793437.2_amd64.deb
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/793437
Title:
3rd test kernel
http://people.canonical.com/~jj/linux-image-2.6.39-2-generic_2.6.39-2.7~lp793437.3_amd64.deb
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/793437
Title:
Unusable Slowness In
4th test kernel
http://people.canonical.com/~jj/linux-image-2.6.39-2-generic_2.6.39-2.7~lp793437.4_amd64.deb
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/793437
Title:
Unusable Slowness In
I went back and retested this and it has already been fixed and released
(commit fcbc05a1be0a7600153e78207dcb8b62fe753a4a), it was just not
properly closed.
mapl,
If you are running an updated hardy guest running the 2.6.24-29 kernel this bug
should not be a problem. Can you please provide
Public bug reported:
AppArmor is doing a GFP_KERNEL allocation in apparmor_task_setrlimit,
which MAY sleep while a spin lock is being held.
BUG: sleeping function called from invalid context at mm/slub.c:847
in_atomic(): 1, irqs_disabled(): 0, pid: 1583, name: cupsd
2 locks held by cupsd/1583:
+0x19/0x3a
+ [811beaa5] security_task_setrlimit+0x11/0x13
+ [8104db6b] do_prlimit+0xd2/0x189
+ [8104dea9] sys_setrlimit+0x3b/0x48
+ [814062bb] system_call_fastpath+0x16/0x1b
** Changed in: linux (Ubuntu)
Assignee: (unassigned) = John Johansen (jjohansen
** Changed in: linux (Ubuntu)
Assignee: (unassigned) = John Johansen (jjohansen)
** Changed in: apparmor
Assignee: (unassigned) = John Johansen (jjohansen)
** Visibility changed to: Public
** This bug is no longer flagged as a security vulnerability
--
You received this bug
5th test kernel (sorry these are taking so long there are a lot of build
failures and git bisect skips)
http://people.canonical.com/~jj/linux-image-2.6.39-2-generic_2.6.39-2.7~lp793437.5_amd64.deb
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
No real consequences, it just takes longer as you have to kick off a
build let it fail, bisect skip and the startup a new build again. As
for your wireless not working, that really isn't a surprise as I haven't
been building the firmware package to match the kernel, its an extra
step I was hoping
7th test kernel
http://people.canonical.com/~jj/linux-image-2.6.39-2-generic_2.6.39-2.7~lp793437.7_amd64.deb
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/793437
Title:
Unusable Slowness In
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,
Note: I also tried to replicate this problem locally and have not been
able to do so.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/740549
Title:
Ubuntu 10.04LTS runs slow after kernel updates
--
Can you please attach the output of
apparmor_parser -p /etc/apparmor.d/sbin.dhclient
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/771544
Title:
natty apparmor + maverick kernel denies socket
No it doesn't need to be run against the specific kernel, it is merely
dumping out a flattened version of the profile (with all includes and
variables etc) before any other processing.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
shahar Or,
We will pick this patch up for older releases when tyler submits it
upstream to the stable kernel trees
** Changed in: linux (Ubuntu)
Assignee: Andy Whitcroft (apw) = John Johansen (jjohansen)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
Public bug reported:
Regression from 2.6.35 based Maverick kernels.
Single monitor attached to the machine via dvi (or hdmi via converter).
It will display grub, or console output, but at about the point gdm
starts the display goes black, and reports that no input is detected.
This behavior
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/757549
Title:
Monitor reports no input detected and goes into sleep mode
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Sesshomurai,
It would indeed be useful to know if the is seen in other distro
kernels, but at the moment I don't believe enough testing of the other
distro kernels have been to determine that.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Public bug reported:
Binary package hint: unity
I have the launcher dodging windows, and lately it is unhiding when
notifications are displayed (separate bug).
After receiving a notification that caused the launch to appear, the
launcher stopped hiding hide. Switching focus on windows, moving
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/759293
Title:
launcher stop auto hiding after notification
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Public bug reported:
Binary package hint: unity
I have the launcher set to dodge windows.
After the most recent updates the launcher unhides when a notification
is displayed
ProblemType: Bug
DistroRelease: Ubuntu 11.04
Package: unity 3.8.6-0ubuntu1
ProcVersionSignature: Ubuntu
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/759295
Title:
launch unhides when a notification is received
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Jakob,
it can be a lot of extra seeks, but it is only done for entries that are
long names, which are hopefully the exception. Unfortunately this is
the case for any method we use to store long name information that
doesn't fit in the underlying file system dentry (special dentry file,
file
Andrew M,
As to whether this breaks backups that will depend on how you do them.
If you backup to a file system that doesn't support extended attributes
and you don't stuff the files in an archive (tar etc) with xattr
preserving options set then, yes the backed up files will lose there
long
It was reproducible when I filed, it was popping out every time an
application in the launcher had a notification. So that instead of the
just the icon wiggling and showing the whole launcher was unhiding. I
didn't have to do anything special, get a notification in pidgin it
would show up, get
** Visibility changed to: Public
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/768720
Title:
ubiquity stalls when doing install waiting for udisks
--
ubuntu-bugs mailing list
Claiming
commit f17140b5f22a25e5731caa42c452bb026a17f0bc] Fix an error in abi
directory copy and bump it again
as bad was premature, and due to a misunderstanding. The above data is for the
system when it is behaving correctly.
Also note rythembox was running correctly, it was just minimized
The bisecting of the kernel between Ubuntu-2.6.32-28.56
Ubuntu-2.6.32-27.49 did not result in being able to track down the
problem.
DrDetrot reports the Ubuntu-2.6.32-30.59 is working for him with out the
regression for several hours now.
Marking this bug as closed, feel free to reopen if the
** Changed in: linux (Ubuntu)
Assignee: (unassigned) = John Johansen (jjohansen)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/748656
Title:
AppArmor complain doesn't always allow requested
Testing has reported that this issue occurs while booting a 2.6.35 in
natty.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/746751
Title:
kernel: [Firmware Bug]: the BIOS has corrupted hw-PMU
I don't have a reproducer for it yet, but it does seem to happen
sporadically. I think it may be tied to when I am switching workspaces,
so I have been watching for it but it hasn't surfaced for the last
couple of days (maybe already fixed by an update?)
As for this happening in the classic
I have tried to duplicate, with the latest updates and it isn't happen
for me in either classic gnome or unity. So we should probably just
close this unless I can duplicate again.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
A potential fix commit 1821df040ac3cd6a57518739f345da6d50ea9d3f in the
upstream kernel has been included in 2.6.38-9.43 which is currently in
-proposed.
Please test with this kernel and report if it fixes the issue reported
here
--
You received this bug notification because you are a member of
next test kernel
http://people.canonical.com/~jj/linux-image-2.6.39-2-generic_2.6.39-2.7~lp793437.35_amd64.deb
based on 969a6e521730153380ad7781095f503c040b684c
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
From a developer pov I actually don't like merge commits, the are a
pita. Where merges are nice is for the tree maintainers as they don't
have to deal with the individual commit series but track/deal with merge
entries. The deeper you go into tree maintainer hiearchy the more
important it
It is a possibility that bisecting won't be able to find the bad commit,
but we aren't there yet. There a still hundreds of commits to search
through. As for the kernel the rule is you don't break the build, there
are occasions when it happens, often because it build under one config
and then
next test kernel
http://people.canonical.com/~jj/linux-image-2.6.39-2-generic_2.6.39-2.7~lp793437.38_amd64.deb
based on cb655d0f3d57c23db51b981648e452988c0223f9
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
all right, hopefully this will be more stable its -rc6
next test kernel
http://people.canonical.com/~jj/linux-image-2.6.39-2-generic_2.6.39-2.7~lp793437.39_amd64.deb
based on 899611ee7d373e5eeda08e9a8632684e1ebbbf00
--
You received this bug notification because you are a member of Ubuntu
thanks, 2 more test kernels, one based on rc3 and the other is a rebuild
and upload of #35 (last good kernel) as a sanity check if rc3 is failing
rc3
http://people.canonical.com/~jj/linux-image-2.6.39-2-generic_2.6.39-2.7~lp793437.rc3_amd64.deb
#35
hrmm sorry about that, I am not sure what happened. Try again now.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/793437
Title:
Unusable Slowness In 2.6.38-8
To manage notifications about this
Alright lets hit the other rcs and see what they do
rc1 http://people.canonical.com/~jj/linux-
image-2.6.39-2-generic_2.6.39-2.7~lp793437.rc1_amd64.deb
rc2 http://people.canonical.com/~jj/linux-
image-2.6.39-2-generic_2.6.39-2.7~lp793437.rc2_amd64.deb
rc4 http://people.canonical.com/~jj/linux-
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/815238
Title:
middle mouse click does not launch application
To manage notifications about this bug go to:
Public bug reported:
With the latest update of unity, using the middle mouse click to launch
second and third copies of an application no longer works.
ProblemType: Bug
DistroRelease: Ubuntu 11.10
Package: unity 4.4.0-0ubuntu1
ProcVersionSignature: Ubuntu 3.0.0-6.7-generic 3.0.0-rc7
Uname: Linux
Public bug reported:
The restart option is missing from the system menu (possibly by design),
but after doing a system update I received a notification to restart the
system to complete the update but the Usually Restart to complete update
option was missing from the system menu.
ProblemType:
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/816016
Title:
system menu entry restart to complete update is missing
To manage notifications about this bug go to:
Public bug reported:
With the latest update when left clicking on an application icon in the
launcher it does not jump to the window of the already running
application.
ProblemType: Bug
DistroRelease: Ubuntu 11.10
Package: unity 4.4.0-0ubuntu1
ProcVersionSignature: Ubuntu 3.0.0-7.8-generic 3.0.0
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/816034
Title:
left mouse button click does not jump to open application
To manage notifications about this bug go to:
next test kernel
http://people.canonical.com/~jj/linux-image-2.6.39-2-generic_2.6.39-2.7~lp793437.26_amd64.deb
based on b83f920e179101a54721e5ab1d6c3edfb9d4bcbb
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
next test kernel
http://people.canonical.com/~jj/linux-image-2.6.39-2-generic_2.6.39-2.7~lp793437.27_amd64.deb
based on a0d069ea2c7b81a453d258c7f60e1f61a3fcbd9f
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
next test kernel
http://people.canonical.com/~jj/linux-image-2.6.39-2-generic_2.6.39-2.7~lp793437.28_amd64.deb
based on d9a73c00161f3eaa4c8c035c62f45afd1549e38a
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
They should be loaded at startup, have you made any modifications to
your startup?
Can you attach a copy of dmesg before you do
/etc/init.d/apparmor reload
What are the contents of your /etc/apparmor/ directory (its config files
for apparmor)
--
You received this bug notification because you
It looks like the stack is junk, the chain of fns listed just isn't
correct for what would happen within the apparmor hook. It is likely
that parts of that sequence happened at some point, but tracing down
what actually caused the oops from the attached screenshot isn't
possible.
Is this a
next test kernel
http://people.canonical.com/~jj/linux-image-2.6.39-2-generic_2.6.39-2.7~lp793437.29_amd64.deb
based on 216d7cdd3b060518a2d4faf584eb15ef5af862b6
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
next test kernel
http://people.canonical.com/~jj/linux-image-2.6.39-2-generic_2.6.39-2.7~lp793437.30_amd64.deb
based on 30c278192f9ab06125fb042f6e46763e0fd7140a
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Please note that there are multiple different crash bugs, not all of
them are going to be related to the wireless driver. I know of at least
one fix for crashes that has gone into the fglrx driver (if you are
running the proprietary ati driver) and some fixes to the fusion radeon
driver that went
Alright I think I have finally tracked this one down, and we should have
some packages for testing soon. This is a user space fix to make the
table actually work but will also get a kernel side test to ensure the
table is properly bounded at load time.
What is happening is the created dfa is not
There are maverick test kernels at
kernel.ubuntu.com/~jj/linux-image-2.6.35-23-virtual_2.6.35-23.36~ec2_amd64.deb
kernel.ubuntu.com/~jj/linux-image-2.6.35-23-virtual_2.6.35-23.36~ec2_i386.deb
--
ec2 kernel crash invalid opcode [#1]
https://bugs.launchpad.net/bugs/651370
You received this
** Changed in: linux (Ubuntu Maverick)
Status: New = In Progress
** Changed in: linux (Ubuntu)
Status: Confirmed = In Progress
--
ec2 kernel crash invalid opcode [#1]
https://bugs.launchpad.net/bugs/651370
You received this bug notification because you are a member of Ubuntu
** Description changed:
+ SRU Justification (apparmor)
+
+ 1. impact of the bug is medium for stable releases. There are two parts
+ to this bug: the kernel side OOPSing when a the parser generates invalid
+ tables, and the parser generating correct tables. The lucid kernel
+ should receive the
I went through and launch a multiple of each m1.small, m1.large, and
t1.micro instances in all zones. And none of them booted successfully.
I was however able to get logs from some of the failed instances. I
have attached one of the 6 logs I managed to collect. None of them are
significantly
I went through and launch a multiple of each m1.small, m1.large, and
t1.micro instances in all zones. And none of them booted successfully.
I was however able to get logs from some of the failed instances. I
have attached one of the 6 logs I managed to collect. None of them are
significantly
This is the patch from comment #17 backported to Lucid.
** Patch added: lp614853.patch
https://bugs.launchpad.net/ubuntu/+source/linux-ec2/+bug/614853/+attachment/1729278/+files/lp614853.patch
--
kernel panic divide error: [#1] SMP
https://bugs.launchpad.net/bugs/614853
You received
Mr. Morfoos,
can you please run your bit torrent client using strace from the command
line, and attach its output?
prompt strace program
--
hangs when saving files to encrypted hard drive
https://bugs.launchpad.net/bugs/674985
You received this bug notification because you are a member of
Update on the current status
* the on disk format is NOT stable. Changes will likely be made during the
upstreaming review cycle.
** If you have data stored using the test kernel, the migration process will be
to copy your data out of ecryptfs, update your kernel and then copy your data
back
Okay, I have been playing with this for a while and it seem stable (famous last
words), the patch in its current state is in the git tree.
git://kernel.ubuntu.com/jj/ubuntu-natty.git
And a current build against the natty kernel is available from
Alex,
Do you have a log log files, or console output that you can attach? If
not test could you take a picture of the your console?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/562044
Title:
antoirehew,
yes the mainline kernels will never have the above compatibility patch.
There are different patches in development that will replace the current
compatibility patches and that will go upstream when they are ready
--
You received this bug notification because you are a member of
The way the patch is currently setup you don't need a new ecryptfs-
utils, but I think that will likely change before the final iteration.
If you want to test this in a fedora kernel you will need to pull the
patch from the git repo and apply it to the fedora kernel and build.
pulling the patch
the security_path_mknod() call from
aufs.
** Affects: linux (Ubuntu)
Importance: Undecided
Assignee: John Johansen (jjohansen)
Status: New
** Changed in: linux (Ubuntu)
Assignee: (unassigned) = John Johansen (jjohansen)
--
You received this bug notification because you
** Changed in: linux (Ubuntu)
Assignee: (unassigned) = John Johansen (jjohansen)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/725089
Title:
QRT test-kernel-security causes kernel panic on EC2
So after several tests I have replicated this on a 2.6.35-25-virtual
kernel, not the crash is sporadic and does not show up every time.
So the bug is not a regression in the proposed linux-
image-2.6.35-27-virtual 2.6.35-27.48 kernel.
--
You received this bug notification because you are a
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
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
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
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
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
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
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.
--
701 - 800 of 8101 matches
Mail list logo