4.10.0-8.10-generic has the fix for this bug so marking the zesty task
as released.
** Changed in: linux (Ubuntu)
Status: Incomplete => Fix Released
** Changed in: apparmor
Status: Triaged => In Progress
** Changed in: apparmor
Assignee: (unassigned) => John Johansen
4.4.0-65.86-generic fixes this issue on xenial.
** Tags removed: verification-needed-xenial verification-needed-yakkety
** Tags added: verification-done-xenial verification-done-yakkety
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
4.8.0-40.43-generic fixes this issue on yakkety.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1658219
Title:
flock not mediated by 'k'
Status in AppArmor:
In Progress
Status in
FYI, this issue was hitting snapcrafters on Raspberry Pi3
(https://lists.ubuntu.com/archives/snapcraft/2017-February/003366.html).
Please also update the other reference kernels and snaps. Thanks!
--
You received this bug notification because you are a member of Kernel
Packages, which is
Confirmed this bug is fixed with 4.4.0-65.86-generic on xenial.
** Tags removed: verification-needed-xenial
** Tags added: verification-done-xenial
** Changed in: apparmor
Status: New => In Progress
** Changed in: apparmor
Assignee: (unassigned) => John Johansen (jjohansen)
--
You
Confirmed this bug is fixed with 4.8.0-40.43-generic on yakkety.
** Tags removed: verification-needed-yakkety
** Tags added: verification-done-yakkety
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
This is fixed with 4.10.0-8.10-generic. Marking zesty task as fixed.
** Changed in: linux (Ubuntu)
Status: Incomplete => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1621899/+attachment/4737712/+files/WifiSyslog.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1621899/+attachment/4737711/+files/UdevDb.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "RfKill.txt"
https://bugs.launchpad.net/bugs/1621899/+attachment/4737710/+files/RfKill.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "PulseList.txt"
https://bugs.launchpad.net/bugs/1621899/+attachment/4737709/+files/PulseList.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Tags added: apport-collected
** Description changed:
I noticed this system failed to suspend properly and failed to resume.
Closed the lid, the fans kept going. Opened the lid and lights were
flashing indicating an error and had to hard reset. It had the following
I found that the system sometimes suspends and resumes, seemingly ok,
but then there is a kernel trace when I try to reboot that halts the
reboot and need to hard reset on reboot. The trace is not logged.
With the kernel from xenial-updates (4.4.0.36) I found a reliable
reproducer:
1. boot
2.
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1621899/+attachment/4737708/+files/ProcModules.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1621899/+attachment/4737707/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "JournalErrors.txt"
https://bugs.launchpad.net/bugs/1621899/+attachment/4737702/+files/JournalErrors.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1621899/+attachment/4737706/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1621899/+attachment/4737700/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "CRDA.txt"
https://bugs.launchpad.net/bugs/1621899/+attachment/4737699/+files/CRDA.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1621899
apport information
** Attachment added: "IwConfig.txt"
https://bugs.launchpad.net/bugs/1621899/+attachment/4737701/+files/IwConfig.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1621899/+attachment/4737703/+files/Lspci.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1621899
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1621899/+attachment/4737704/+files/Lsusb.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1621899
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1621899/+attachment/4737705/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Public bug reported:
I noticed this system failed to suspend properly and failed to resume.
Closed the lid, the fans kept going. Opened the lid and lights were
flashing indicating an error and had to hard reset. It had the following
in the logs:
Sep 9 07:43:19 ginny gnome-session[6351]:
FYI, this will likely cause tests in (at least) snap-confine to fail.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1626194
Title:
Seccomp actions are not audited in the 4.8 kernel
Marking as 'confirmed' so the bot doesn't auto-close it.
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1636847
Public bug reported:
This came up in snapd spread tests but can be reproduced with:
In an i386 up to date 16.04 VM:
1. in one terminal, run this:
$ cat changehat_reproducer.sh
#!/bin/sh
set -e
sudo sysctl -w kernel.printk_ratelimit=0
sudo snap install hello-world || true
count=0
while
** Description changed:
This came up in snapd spread tests but can be reproduced with:
In an i386 up to date 16.04 VM:
1. in one terminal, run this:
- $ cat changehat_reproducer.sh
+ $ cat reproducer.sh
#!/bin/sh
set -e
sudo sysctl -w kernel.printk_ratelimit=0
sudo snap
@Frode, I can yes, when I file them. I need to do a bit of work for
simple reproducers/etc/etc to file them. I've added an item to add a
comment to this bug when I do.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Actually, I marked the MAAS task as incomplete in case people want to
give feedback.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1408106
Title:
attach_disconnected not sufficient for
Ok, I spent quite a bit of time evaluating this and believe this bug can
be closed, but other bugs open.
In looking at this I created https://code.launchpad.net/~jdstrand/+git
/test-overlay (to build simply git clone, run 'snapcraft', install the
snap and then run 'test-overlay' for instructions
Closing the MAAS task as it the referenced bug is marked Fix Release. If
there are issues there still, please see my previous comment and look at
the code in that snap-- there are viable ways to use overlayfs with
chroot and an apparmor alias rule, or overlayfs with private mount,
chroot and
Marking as "Won't Fix" for the bluez deb -- the postinst is doing the
right thing, there just happens to be something installed outside of
dpkg/apt that is getting in the way.
** Changed in: bluez (Ubuntu)
Status: Confirmed => Won't Fix
--
You received this bug notification because you
Looking at the logs I see:
Sep 13 07:51:08 agda-HP-Pavilion-dv6500-Notebook-PC audit[1221]: AVC
apparmor="STATUS" operation="profile_replace" profile="unconfined"
name="snap.bluez.bluetoothctl" pid=1221 comm="apparmor_parser"
This indicates you have the bluez snap installed. This bug is about
@mvo - this is probably obvious, but if you used '#include' instead of
'include', it would side-step the issue.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1734038
Title:
utils don't
Since snapd is using this bug for its SRU blocker and we have bug
#1733700 that is the same issue, I'm going to use this bug as the snapd
one and for the apparmor one.
** Summary changed:
- utils don't understand «include "/where/ever"» (was: Potential regression
found with apparmor test on
I too am seeing this after the most recent upgrade:
$ grep -cF 'sit: non-ECT' /var/log/syslog
2917
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1772775
Title:
4.4.0-127.153 generates
** Changed in: qtbase-opensource-src (Ubuntu)
Status: New => Won't Fix
** Changed in: qtmultimedia-opensource-src (Ubuntu)
Status: New => Won't Fix
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** Changed in: kernel-sru-workflow/security-signoff
Assignee: Canonical Security Team (canonical-security) => Ubuntu Security
Team (ubuntu-security)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
** Changed in: kernel-sru-workflow/security-signoff
Assignee: Canonical Security Team (canonical-security) => Ubuntu Security
Team (ubuntu-security)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Add a snapd task so that when the https://launchpad.net/ubuntu/+source
/linux-gcp is Fix Released, snapd can re-enable the tests/main/lxd test
on GCE.
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Artful)
Status: New => Fix
Since this is going to be fixed in 'linux' and 'linux-gcp', adding tasks
for those.
** Changed in: apparmor (Ubuntu Artful)
Status: Won't Fix => Fix Committed
** Changed in: linux (Ubuntu Artful)
Status: Fix Committed => Confirmed
** Also affects: linux-gcp (Ubuntu)
Importance:
FYI, the following kernels are also affected (all 4.13 based):
* linux-azure
* linux-hwe
* linux-hwe-edge
* linux-oem
* linux-raspi2
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1746463
This is fixed in xenial 2.3.1-2.1ubuntu2~16.04.1
** Changed in: libseccomp (Ubuntu Xenial)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Thanks John! :)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1898280
Title:
Please unrevert the apparmor audit rule filtering feature
Status in linux package in Ubuntu:
Fix
** Changed in: telepathy-mission-control-5 (Ubuntu)
Status: In Progress = Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-maguro in Ubuntu.
https://bugs.launchpad.net/bugs/1217618
Title:
apparmor DENIED in
Public bug reported:
Currently one cannot use access() to see if the call would be blocked by
the LSM. It would be nice if this was in place so application developers
could use a standard method to determine access instead of resorting to
looking up sandbox variables or trying to open files in
Public bug reported:
I was trying to diagnose network problems on this machine and found that Ubuntu
12.04 LTS, -56 and -57 will show the following with ifconfig:
$ ifconfig eth0
eth0 Link encap:Ethernet HWaddr 1c:75:08:5a:9f:b1
UP BROADCAST MULTICAST MTU:1500 Metric:1
** Description changed:
- I was trying to diagnose network problems on this machine and found that
Ubuntu 12.04 LTS, -56 and -57 will show the following with ifconfig:
+ I was trying to diagnose network problems on this machine and found that
Ubuntu 12.04 will show the following with ifconfig
** Description changed:
I was trying to diagnose network problems on this machine and found that
Ubuntu 12.04 will show the following with ifconfig after a little while:
$ ifconfig eth0
eth0 Link encap:Ethernet HWaddr 1c:75:08:5a:9f:b1
UP BROADCAST MULTICAST MTU:1500
This was fixed in at least 25.0.1+build1-0ubuntu0.13.10.1
** Changed in: firefox (Ubuntu Saucy)
Status: Fix Committed = Fix Released
** Changed in: apparmor
Status: Triaged = Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is
Trusty firefox has the fix as well.
** Changed in: firefox (Ubuntu)
Status: Fix Committed = Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-maguro in Ubuntu.
https://bugs.launchpad.net/bugs/1208988
Title:
Preliminary testing shows that this is no longer a problem with
3.11.0-1.4
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1204005
Title:
[saucy] kvm host hangs of guest boot with
Ok, I had her run the release kernel (-23) and the issue is there too:
$ ifconfig eth0
eth0 Link encap:Ethernet HWaddr 1c:75:08:5a:9f:b1
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:4294744618 errors:4293631228 dropped:4294521940
overruns:4294744618
** Also affects: qa-regression-testing
Importance: Undecided
Status: New
** Changed in: qa-regression-testing
Assignee: (unassigned) = Steve Beattie (sbeattie)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-ti-omap4
** Changed in: linux-lts-backport-maverick (Ubuntu Lucid)
Status: New = Won't Fix
** Changed in: linux-lts-backport-natty (Ubuntu Lucid)
Status: New = Won't Fix
** Changed in: linux-lts-backport-maverick (Ubuntu Precise)
Status: New = Won't Fix
** Changed in:
** Changed in: linux-lts-backport-maverick (Ubuntu Lucid)
Status: New = Won't Fix
** Changed in: linux-lts-backport-natty (Ubuntu Lucid)
Status: New = Won't Fix
** Changed in: linux-lts-backport-maverick (Ubuntu Precise)
Status: New = Won't Fix
** Changed in:
** Changed in: linux-lts-backport-maverick (Ubuntu Lucid)
Status: New = Won't Fix
** Changed in: linux-lts-backport-natty (Ubuntu Lucid)
Status: New = Won't Fix
** Changed in: linux-lts-backport-maverick (Ubuntu Precise)
Status: New = Won't Fix
** Changed in:
** Changed in: linux-lts-backport-maverick (Ubuntu Lucid)
Status: New = Won't Fix
** Changed in: linux-lts-backport-natty (Ubuntu Lucid)
Status: New = Won't Fix
** Changed in: linux-lts-backport-maverick (Ubuntu Precise)
Status: New = Won't Fix
** Changed in:
** Changed in: linux-lts-backport-maverick (Ubuntu Lucid)
Status: New = Won't Fix
** Changed in: linux-lts-backport-natty (Ubuntu Lucid)
Status: New = Won't Fix
** Changed in: linux-lts-backport-maverick (Ubuntu Precise)
Status: New = Won't Fix
** Changed in:
** Changed in: linux-lts-backport-maverick (Ubuntu Lucid)
Status: New = Won't Fix
** Changed in: linux-lts-backport-natty (Ubuntu Lucid)
Status: New = Won't Fix
** Changed in: linux-lts-backport-maverick (Ubuntu Precise)
Status: New = Won't Fix
** Changed in:
** Changed in: linux-lts-backport-maverick (Ubuntu Lucid)
Status: New = Won't Fix
** Changed in: linux-lts-backport-natty (Ubuntu Lucid)
Status: New = Won't Fix
** Changed in: linux-lts-backport-maverick (Ubuntu Precise)
Status: New = Won't Fix
** Changed in:
** Changed in: linux-lts-backport-maverick (Ubuntu Lucid)
Status: New = Won't Fix
** Changed in: linux-lts-backport-natty (Ubuntu Lucid)
Status: New = Won't Fix
** Changed in: linux-lts-backport-maverick (Ubuntu Precise)
Status: New = Won't Fix
** Changed in:
** Changed in: linux-lts-backport-maverick (Ubuntu Lucid)
Status: New = Won't Fix
** Changed in: linux-lts-backport-natty (Ubuntu Lucid)
Status: New = Won't Fix
** Changed in: linux-lts-backport-maverick (Ubuntu Precise)
Status: New = Won't Fix
** Changed in:
** Changed in: linux-lts-backport-maverick (Ubuntu Lucid)
Status: New = Won't Fix
** Changed in: linux-lts-backport-natty (Ubuntu Lucid)
Status: New = Won't Fix
** Changed in: linux-lts-backport-maverick (Ubuntu Precise)
Status: New = Won't Fix
** Changed in:
** Changed in: linux-lts-backport-maverick (Ubuntu Lucid)
Status: New = Won't Fix
** Changed in: linux-lts-backport-natty (Ubuntu Lucid)
Status: New = Won't Fix
** Changed in: linux-lts-backport-maverick (Ubuntu Precise)
Status: New = Won't Fix
** Changed in:
** Changed in: linux-lts-backport-maverick (Ubuntu Lucid)
Status: New = Won't Fix
** Changed in: linux-lts-backport-natty (Ubuntu Lucid)
Status: New = Won't Fix
** Changed in: linux-lts-backport-maverick (Ubuntu Precise)
Status: New = Won't Fix
** Changed in:
** Changed in: linux-lts-backport-maverick (Ubuntu Lucid)
Status: New = Won't Fix
** Changed in: linux-lts-backport-natty (Ubuntu Lucid)
Status: New = Won't Fix
** Changed in: linux-lts-backport-maverick (Ubuntu Precise)
Status: New = Won't Fix
** Changed in:
** Changed in: linux-lts-backport-maverick (Ubuntu Lucid)
Status: New = Won't Fix
** Changed in: linux-lts-backport-natty (Ubuntu Lucid)
Status: New = Won't Fix
** Changed in: linux-lts-backport-maverick (Ubuntu Precise)
Status: New = Won't Fix
** Changed in:
** Changed in: linux-lts-backport-maverick (Ubuntu Lucid)
Status: New = Won't Fix
** Changed in: linux-lts-backport-natty (Ubuntu Lucid)
Status: New = Won't Fix
** Changed in: linux-lts-backport-maverick (Ubuntu Precise)
Status: New = Won't Fix
** Changed in:
** Changed in: linux-lts-backport-maverick (Ubuntu Lucid)
Status: New = Won't Fix
** Changed in: linux-lts-backport-natty (Ubuntu Lucid)
Status: New = Won't Fix
** Changed in: linux-lts-backport-maverick (Ubuntu Precise)
Status: New = Won't Fix
** Changed in:
** Changed in: linux-lts-backport-maverick (Ubuntu Lucid)
Status: New = Won't Fix
** Changed in: linux-lts-backport-natty (Ubuntu Lucid)
Status: New = Won't Fix
** Changed in: linux-lts-backport-maverick (Ubuntu Precise)
Status: New = Won't Fix
** Changed in:
** Changed in: linux-lts-backport-maverick (Ubuntu Lucid)
Status: New = Won't Fix
** Changed in: linux-lts-backport-natty (Ubuntu Lucid)
Status: New = Won't Fix
** Changed in: linux-lts-backport-maverick (Ubuntu Precise)
Status: New = Won't Fix
** Changed in:
** Changed in: linux-lts-backport-maverick (Ubuntu Lucid)
Status: New = Won't Fix
** Changed in: linux-lts-backport-natty (Ubuntu Lucid)
Status: New = Won't Fix
** Changed in: linux-lts-backport-maverick (Ubuntu Precise)
Status: New = Won't Fix
** Changed in:
** Changed in: linux-lts-backport-maverick (Ubuntu Lucid)
Status: New = Won't Fix
** Changed in: linux-lts-backport-natty (Ubuntu Lucid)
Status: New = Won't Fix
** Changed in: linux-lts-backport-maverick (Ubuntu Precise)
Status: New = Won't Fix
** Changed in:
** Changed in: linux-lts-backport-maverick (Ubuntu Lucid)
Status: New = Won't Fix
** Changed in: linux-lts-backport-natty (Ubuntu Lucid)
Status: New = Won't Fix
** Changed in: linux-lts-backport-maverick (Ubuntu Precise)
Status: New = Won't Fix
** Changed in:
** Changed in: linux-lts-backport-maverick (Ubuntu Lucid)
Status: New = Won't Fix
** Changed in: linux-lts-backport-natty (Ubuntu Lucid)
Status: New = Won't Fix
** Changed in: linux-lts-backport-maverick (Ubuntu Precise)
Status: New = Won't Fix
** Changed in:
** Changed in: linux-lts-backport-maverick (Ubuntu Lucid)
Status: New = Won't Fix
** Changed in: linux-lts-backport-natty (Ubuntu Lucid)
Status: New = Won't Fix
** Changed in: linux-lts-backport-maverick (Ubuntu Precise)
Status: New = Won't Fix
** Changed in:
** Changed in: linux-lts-backport-maverick (Ubuntu Lucid)
Status: New = Won't Fix
** Changed in: linux-lts-backport-natty (Ubuntu Lucid)
Status: New = Won't Fix
** Changed in: linux-lts-backport-maverick (Ubuntu Precise)
Status: New = Won't Fix
** Changed in:
** Changed in: linux-lts-backport-maverick (Ubuntu Lucid)
Status: New = Won't Fix
** Changed in: linux-lts-backport-natty (Ubuntu Lucid)
Status: New = Won't Fix
** Changed in: linux-lts-backport-maverick (Ubuntu Precise)
Status: New = Won't Fix
** Changed in:
** Changed in: linux-lts-backport-maverick (Ubuntu Lucid)
Status: New = Won't Fix
** Changed in: linux-lts-backport-natty (Ubuntu Lucid)
Status: New = Won't Fix
** Changed in: linux-lts-backport-maverick (Ubuntu Precise)
Status: New = Won't Fix
** Changed in:
*** This bug is a duplicate of bug 1228380 ***
https://bugs.launchpad.net/bugs/1228380
** Information type changed from Private Security to Public
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bcmwl in Ubuntu.
*** This bug is a duplicate of bug 1228472 ***
https://bugs.launchpad.net/bugs/1228472
** Information type changed from Private Security to Public
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bcmwl in Ubuntu.
** Information type changed from Private Security to Public
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bcmwl in Ubuntu.
https://bugs.launchpad.net/bugs/1228988
Title:
bcmwl-kernel-source 6.20.155.1+bdcom-0ubuntu0.0.1: bcmwl kernel
** Information type changed from Private Security to Public
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1228473
Title:
[Dell Inc. Dell System XPS L502X] suspend/resume failure
Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a regular (non-security) bug. I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross
** Also affects: linux (Ubuntu Saucy)
Importance: Critical
Assignee: Andy Whitcroft (apw)
Status: Triaged
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1204005
Title:
For adding the attach_disconnected flag, unfortunately there isn't a
convenient way to apply attach_disconnected without modifying the
profile directly.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apparmor-easyprof-ubuntu needs to allow /dev/socket/property_service and
use attach_disconnected on touch images.
** Changed in: apparmor-easyprof-ubuntu (Ubuntu Saucy)
Status: Fix Released = In Progress
--
You received this bug notification because you are a member of Kernel
Packages,
** Changed in: apparmor (Ubuntu Saucy)
Status: In Progress = Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-maguro in Ubuntu.
https://bugs.launchpad.net/bugs/1208988
Title:
AppArmor no longer mediates access
** Changed in: firefox (Ubuntu Saucy)
Status: Triaged = Fix Committed
** Changed in: firefox (Ubuntu Saucy)
Milestone: None = saucy-updates
** Changed in: firefox (Ubuntu Saucy)
Assignee: (unassigned) = Jamie Strandboge (jdstrand)
--
You received this bug notification because
I have not seen this on 13.10 since 3.11.0-1.4. This bug can probably be
closed.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1204005
Title:
[saucy] kvm host hangs of guest boot with
** Tags removed: rls-t-incoming
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1244157
Title:
[3.11.0-12.18 regression] Failed name lookup - disconnected path in
dhclient D-BUS access
Public bug reported:
I have a lenovo USB 2.0 port replicator with Digtial Video (MODEL
#VDK8736). I discovered that whenever I unplugged my port replicator,
there would be a kernel traceback. My laptop has a VGA port which I plug
an external monitor into, and I use the port replicator for
** Description changed:
I have a lenovo USB 2.0 port replicator with Digtial Video (MODEL
#VDK8736). I discovered that whenever I unplugged my port replicator,
there would be a kernel traceback. My laptop has a VGA port which I plug
an external monitor into, and I use the port replicator
This was all prompted by me thinking there was a bug in
lightdm/screenlocking since I was sometimes unable to
suspend/resume/unlock. I'm going to attach my test matrix procedure for
how I discovered the traceback and proved to myself that the traceback
is the most likely cause of my failure to
Using the amd64 kernel in http://kernel.ubuntu.com/~kernel-
ppa/mainline/v3.14-rc7-trusty/, I can reproduce the problem. Attached is
the dmesg after booting with the port replicator plugged in and
unplugging.
** Attachment added: lp1295646_v3.14-rc7-trusty.dmesg
** Package changed: apparmor (Ubuntu) = linux (Ubuntu)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1015440
Title:
package apparmor 2.7.102-0ubuntu3.1 failed to install/upgrade:
** No longer affects: linux-lts-backport-maverick (Ubuntu)
** No longer affects: linux-lts-backport-natty (Ubuntu)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-armadaxp in Ubuntu.
https://bugs.launchpad.net/bugs/1271441
Title:
** Changed in: linux-ti-omap4 (Ubuntu Raring)
Status: Fix Committed = Won't Fix
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-armadaxp in Ubuntu.
https://bugs.launchpad.net/bugs/1079859
Title:
CVE-2012-
Status in
1 - 100 of 684 matches
Mail list logo
