Marking the ufw task as Invalid. The kernel doesn't have what is needed
to run iptables.
** Changed in: ufw (Ubuntu)
Status: New => Invalid
** Changed in: ufw (Ubuntu)
Assignee: Jamie Strandboge (jdstrand) => (unassigned)
--
You received this bug notification becaus
I can confirm that without linux-modules-extra-*, iptables is broken.
Reduced test case:
$ sudo iptables -L -n
iptables: No chain/target/match by that name.
Full test case:
$ sudo /usr/share/ufw/check-requirements -f
...
ERROR: could not create 'ufw-check-requirements'. Aborting
FAIL: check your
FYI, I saw this when looking at
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1823862. In the
other bug, the reporter say a different error message, but I saw
'iptables v1.6.1: can't initialize iptables table `filter': Memory
allocation problem'. If those in this bug do not have linux-module
To be clear, when I installed linux-modules-extra-5.0.0-8-generic, I no
longer saw this error message. Of course, it might not strictly be a
duplicate, but I'll let the kernel team figure that out.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscri
The following will reproduce the issue in a disco VM with disco LXD
container:
Initial setup:
1. have an up to date disco vm
$ cat /proc/version_signature
Ubuntu 5.0.0-11.12-generic 5.0.6
2. sudo snap install lxd
3. sudo adduser `id -un` lxd
4. newgrp lxd
5. sudo lxd init # use defaults
6. . /et
Since the apparmor SFS_MOUNTPOINT change is small, I'll prepare an
upload for that immediately. We may need another parser update for the
other issue.
** Changed in: apparmor (Ubuntu)
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Kernel
P
Uploaded 2.13.2-9ubuntu6 with the SFS_MOUNTPOINT change.
--
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/1824812
Title:
apparmor does not start in Disco LXD containers
Status in AppArmor
** Changed in: ufw (Ubuntu)
Status: New => Triaged
** Changed in: ufw (Ubuntu)
Importance: Undecided => Medium
** Changed in: ufw (Ubuntu)
Assignee: (unassigned) => Jamie Strandboge (jdstrand)
--
You received this bug notification because you are a member of Kernel
After discussing with Field, snapd, kernel and the security team, this
will break existing Ubuntu Core devices that use the 4.4 kernel and the
network-manager snap in the default channel (per reporter, the 1.10
channel is unaffected). Therefore, the 4.4 kernels snaps that include
this change (ie, 4
FYI, I cannot reproduce this with even less memory:
$ iptables --version
iptables v1.6.1
$ free
totalusedfree shared buff/cache available
Mem: 265712 114824 667441024 84144 36024
Swap: 0 0
Are there additional steps that need to occur?
** Changed in: iptables (Ubuntu)
Status: New => Incomplete
--
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/1820114
Title:
iptables v
FYI, please note that seccomp 2.4.1 was pushed to bionic in
https://usn.ubuntu.com/4001-1/ on 2019/05/30. It shouldn't affect this
bug report AFAICT because while the 2.4.1 Ubuntu packaging drops these
patches, the upstream commits for lp-1815415-arch-update-syscalls-for-
Linux-4.9.patch and lp-181
This entry:
* swap storms kills interactive use (LP: #1861359)
- SAUCE: mm/page_alloc.c: disable memory reclaim watermark boosting by
default
closed this bug, but per latest comments, that isn't sufficient to
address the issue. Putting back to Confirmed.
** Changed in: linux (Ubuntu Focal
P_REVISION}/{,**}
rwl,
since the snap already has read/write access to these directories when
/system-data is not prepended. I've taken a todo to send up a PR for
this.
** Also affects: snapd
Importance: Undecided
Status: New
** Changed in: snapd
Status: New => Triaged
** C
The linux task can be marked as Fix Released since
net/netfilter/nf_conntrack_helper has defaulted to 0 since 4.7.
** Changed in: ufw (Ubuntu)
Status: Triaged => In Progress
** Changed in: linux (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification becau
Users seeing this issue should modify IPT_MODULES in /etc/defaults/ufw
to be empty. Ubuntu 20.04 will do this be default and future releases of
ufw will introduce rule syntax for working with helper rules.
--
You received this bug notification because you are a member of Kernel
Packages, which is
*** This bug is a duplicate of bug 1879690 ***
https://bugs.launchpad.net/bugs/1879690
Actually, this is 1879690 which is a bug in the Ubuntu kernel.
** Project changed: snapd => linux (Ubuntu)
** Changed in: linux (Ubuntu)
Status: New => Confirmed
** This bug has been marked a dupli
*** This bug is a duplicate of bug 1848567 ***
https://bugs.launchpad.net/bugs/1848567
I'm going to mark the linux task as Invalid and then mark as a dupe of
bug 1848567
** Changed in: linux (Ubuntu)
Status: Confirmed => Won't Fix
** Changed in: apparmor (Ubuntu)
Status: New =>
This was fixed upstream in 61c27d8808f0589beb6a319cc04073e8bb32d860
** Changed in: apparmor
Status: Triaged => Fix Released
--
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/1824812
T
Seth and I talked about this and I marked this as affects me. If it
helps, I saw this on eoan and focal doesn't make a difference (which
might suggest the change is between disco and eoan).
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to l
FYI, I decided to do this:
$ sudo swapoff -a && sudo swapon -a
$ free -h
totalusedfree shared buff/cache available
Mem: 15Gi 5.9Gi 4.8Gi 2.0Gi 4.8Gi 7.2Gi
Swap: 15Gi 348Mi15Gi
Even though I am no
I forgot to mention, I also have nvme.
--
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/1861359
Title:
swap storms kills interactive use
Status in linux package in Ubuntu:
Confirmed
Bu
** Changed in: apparmor (Ubuntu)
Status: Confirmed => Invalid
--
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/1701297
Title:
NTP reload failure (unable to read library) on overlayf
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: 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.
https://bugs.
** 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.
https://bugs.launch
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 o
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
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 pivot_
Public bug reported:
Ubuntu carried a patch to apparmor for audit rule filtering, but it was
reverted due to conflicts related to secids with earlier LSM stacking
patchsets. The upstream LSM stacking patchset is believed to resolve
these issues and groovy now carries the updated LSM stacking patch
After more discussion with John, while groovy does have a newer stacking
patchset, it doesn't have the latest patchset that resolves the audit
subsystem. Unfortunately, as of today, all of those patches haven't been
signed-off on yet so there might be future changes.
** Description changed:
Ubu
FYI, John refreshed the patchset to v20 and reenabled audit rule
filtering and submitted to https://lists.ubuntu.com/archives/kernel-
team/2020-October/113932.html. Since this is a significant change, it
will be considered for a stable release update (SRU) after groovy
release (to allow for peer re
Public bug reported:
Per 'man namespaces':
"Permission to dereference or read (readlink(2)) these symbolic links is
governed by a ptrace access mode PTRACE_MODE_READ_FSCREDS check; see
ptrace(2)."
This suggests that a 'ptrace read' rule should be sufficient to
readlink() /proc/*/ns/*, which is t
** Summary changed:
- 'ptrace trace' needed to readlink() /proc/*/ns/* files
+ 'ptrace trace' needed to readlink() /proc/*/ns/* files on older kernels
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad
Thanks John! Is this something that we can get into the next SRU cycle?
--
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/1890848
Title:
'ptrace trace' needed to readlink() /proc/*/ns/* fil
** 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/1891020
Title:
No IPv4 iptable kernel module can be loaded
Status in linux pac
I spoke with John and he plans to SRU this. Marking as triaged and
assigning to him. Thanks John!
** Changed in: linux (Ubuntu Xenial)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu Xenial)
Status: Confirmed => Triaged
** Changed in: linux (Ubuntu Bionic)
Status: C
** Summary changed:
- No IPv4 iptable kernel module can be loaded
+ iptable_filter and ip6table_filter cannot be loaded with 5.8 kernel
--
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/18910
I cannot confirm this with the 5.8.0-12 kernel. Eg, with the 5.4 kernel
in groovy, things work fine:
$ cat /proc/version_signature
Ubuntu 5.4.0-42.46-generic 5.4.44
$ sudo modprobe iptable_filter
$ sudo modprobe ip6table_filter
$ lsmod|grep table_filter
ip6table_filter16384 0
ip6_tables
FYI, John provided me a test kernel for 18.04 and it resolved the issue.
This will be the basis of the SRU.
--
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/1890848
Title:
'ptrace trace' n
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 Released
@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 Xeni
Marking the incomplete tasks as confirmed so the bot doesn't auto-close
the bug.
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
** Changed in: linux (Ubuntu Artful)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ker
** 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.
https://bug
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 Committ
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.
https://bugs.launchpad.net/bugs/1567597
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 ar
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 the
@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.
https:
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.
https://bugs.launchpad.net/bugs/
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.
https://bugs.launchpad
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 subscrib
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 (jjohanse
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 linu
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 linu
The kernels from http://kernel.ubuntu.com/~jsalisbury/lp1547619 are
4.4.0-040400rc1.201602231809 and have the same checksums as the kernels
I tested in
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1547619/comments/15.
--
You received this bug notification because you are a member of Kerne
I saw a new kernel in xenial with intel fixes so I decided to try it.
This kernel has the bug:
$ cat /proc/version_signature
Ubuntu 4.4.0-9.24-generic 4.4.3
I'll try the bisected kernel now.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed
I have booted into this kernel:
$ cat /proc/version
Linux version 4.3.0-040300-generic (jsalisbury@gomeisa) (gcc version 5.3.1
20160225 (Ubuntu 5.3.1-10ubuntu2) ) #201603030935 SMP Thu Mar 3 14:39:41 UTC
2016
Since the bug doesn't always show itself right away, I will want to use
the kernel fo
While I can't be 100% sure cause the issue is intermittent, it seems
that this kernel does not have the bug:
$ cat /proc/version
Linux version 4.3.0-040300-generic (jsalisbury@gomeisa) (gcc version 5.3.1
20160225 (Ubuntu 5.3.1-10ubuntu2) ) #201603030935 SMP Thu Mar 3 14:39:41 UTC
2016
$ uptime
I have booted into this kernel:
$ cat /proc/version
Linux version 4.3.0-040300-generic (jsalisbury@gomeisa) (gcc version 5.3.1
20160225 (Ubuntu 5.3.1-10ubuntu2) ) #201603101009 SMP Thu Mar 10 15:13:56 UTC
2016
Since the bug doesn't always show itself right away, I will want to use
the kernel fo
FYI, I needed overlayfs and so had to interrupt my 4.3.0-040300-generic
(#201603101009) testing and booted into 4.4.0-12.28. 4.4.0-12.28 has the
bug.
I am back in 4.3.0-040300-generic (#201603101009) now.
--
You received this bug notification because you are a member of Kernel
Packages, which is
FYI, this is not a new 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/1556419
Title:
nf_conntrack: automatic helper assignment is deprecated
Status in iptables package in Ubuntu
While I can't be 100% sure cause the issue is intermittent, it seems
that this kernel does not have the bug:
$ cat /proc/version
Linux version 4.3.0-040300-generic (jsalisbury@gomeisa) (gcc version 5.3.1
20160225 (Ubuntu 5.3.1-10ubuntu2) ) #201603101009 SMP Thu Mar 10 15:13:56 UTC
2016
$ uptime
Your snapcraft.yaml is wrong for the new world. Ie, you have:
apps:
bluetoothctl:
command: usr/bin/bluetoothctl
uses: [bluez-client]
obexctl:
command: usr/bin/obexctl
uses: [bluez-client]
bluez:
command: "usr/lib/bluetooth/bluetoothd -E"
daemon: simple
uses: [
Also, you should be using the new snappy interface for dbus instead of
adding rules to copy dbus bus policy files into place. I haven't used
this before-- you might ping zyga for details.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to blu
Public bug reported:
$ cat ./t
#include
profile t {
#include
/bin/cat ixr,
/sys/kernel/security/apparmor/profiles r,
}
$ sudo apparmor_parser -r ./t
$ sudo aa-exec -p t -- cat /sys/kernel/security/apparmor/profiles
cat: /sys/kernel/security/apparmor/profiles: Permission denied
[1]
k
** Changed in: linux (Ubuntu)
Status: Confirmed => In Progress
--
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/1560583
Title:
reading /sys/kernel/security/apparmor/profiles require
** Description changed:
$ sudo snappy install ubuntu-clock-app.ubuntucore-dev
$ ubuntu-clock-app.clock
aa_change_onexec failed with -1. errmsg: Permission denied
[1]
Downgrading to ubuntu-core-launcher doesn't help the clock app get past
this failure.
The hello-world app works
I took the hello-world application, then adjusted its yaml to be the
same as the ubuntu-clock-app (using ubuntu-cl0ck-app as the name) and
was unable to reproduce.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bu
** Tags added: apparmor
--
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/1562989
Title:
'aa_change_onexec failed with -1. errmsg: Permission denied'
Status in linux package in Ubuntu:
C
Here is a reproducer. See main.c for instructions.
** Attachment added: "1562989.tar.gz"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1562989/+attachment/4615205/+files/1562989.tar.gz
--
You received this bug notification because you are a member of Kernel
Packages, which is subscrib
It appears that the profile name can't start with 'u'. If I change the
app-profile to prepend anything other than 'u', then it works.
Eg, if I update app-profile accordingly before each call to change the profile
name:
$ sudo apparmor_parser -r ./app-profile ./launcher-profile && aa-exec -p
laun
** Changed in: linux (Ubuntu)
Status: Confirmed => 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/1562989
Title:
'aa_change_onexec failed with -1. errmsg: Permission denie
anged in: ubuntu-core-launcher (Ubuntu)
Status: Triaged => In Progress
** Changed in: ubuntu-core-launcher (Ubuntu)
Assignee: Tyler Hicks (tyhicks) => Jamie Strandboge (jdstrand)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscrib
I have booted into this kernel:
$ cat /proc/version_signature
Ubuntu 4.4.0-0.10Commit3b7e590bf-generic 4.4.0
Since the bug doesn't always show itself right away, I will want to use
the kernel for at least several hours. I'll report back as soon as I see
the bug or after using the computer throug
** Description changed:
- When using an external 4K monitor plugging into the mini display port on my
Dell XPS 13 9343 using both the laptop screen and the external monitor
(external monitor is left and laptop screen right), when using all of the
following kernels:
+ When using an external 4K m
This kernel has the bug:
$ cat /proc/version_signature
Ubuntu 4.4.0-0.10Commit3b7e590bf-generic 4.4.0
--
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/1547619
Title:
Intermittent screen
Public bug reported:
When using an external 4K monitor plugged into the mini display port on my Dell
XPS 13 9343 using both the laptop screen and the external monitor (external
monitor is left and laptop screen right), when using all of the following
kernels:
4.4.0-2.16-generic
4.4.0-4.19-gener
This kernel has the bug:
$ cat /proc/version_signature
Ubuntu 4.4.0-1.15-generic 4.4.0
--
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/1547619
Title:
Intermittent screen blinking with 4
I have booted into this kernel:
$ cat /proc/version_signature
Ubuntu 4.4.0-0.3~lp1547619Commit324ae35-generic 4.4.0
Since the bug doesn't always show itself right away, I will want to use
the kernel for at least several hours. I'll report back as soon as I see
the bug or after using the computer
This kernel has the bug:
$ cat /proc/version_signature
Ubuntu 4.4.0-0.3~lp1547619Commit324ae35-generic 4.4.0
--
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/1547619
Title:
Intermittent s
It is difficult for me to use a non-Ubuntu kernel since I do a lot of
work with apparmor for the distro. I suppose I could try for a little
while at a time, but my ability to test will be impeded (ie, I'll need
to run mainline only when not doing the other work).
--
You received this bug notifica
I have booted into this kernel:
$ cat /proc/version
Linux version 4.4.0-040400rc1-generic (jsalisbury@gomeisa) (gcc version 5.3.1
20160222 (Ubuntu 5.3.1-9ubuntu3) ) #201602231809 SMP Tue Feb 23 23:12:04 UTC
2016
Since the bug doesn't always show itself right away, I will want to use
the kernel
This kernel has the bug:
$ cat /proc/version
Linux version 4.4.0-040400rc1-generic (jsalisbury@gomeisa) (gcc version 5.3.1
20160222 (Ubuntu 5.3.1-9ubuntu3) ) #201602231809 SMP Tue Feb 23 23:12:04 UTC
2016
--
You received this bug notification because you are a member of Kernel
Packages, which
** Description changed:
- I'm on arale, OTA9. With OTA8.5 I could pair, listen to music and make
- calls with no problem. After upgrading (and without unpairing/re-pairing
- after upgrading), I can connect to the car, and I can listen to music
- but if I try to make a call while connected to bluet
Public bug reported:
I'm on arale, OTA9. With OTA8.5 I could pair, listen to music and make
calls with no problem. After upgrading (and without unpairing/re-pairing
after upgrading), I can connect to the car, and I can listen to music
but if I try to make a call while connected to bluetooth, the c
** Description changed:
I'm on arale, OTA9. With OTA8.5 I could pair, listen to music and make
calls with no problem. After upgrading (and without unpairing/re-pairing
after upgrading), I can connect to the car, and I can listen to music
but if I try to make a call while connected to bluet
Apologies for the delay-- I needed our Ubuntu kernel for a number of
weeks and had to pause this bisection.
I have booted into this kernel:
$ cat /proc/version
Linux version 4.3.0-040300-generic (jsalisbury@gomeisa) (gcc version 5.3.1
20160311 (Ubuntu 5.3.1-11ubuntu1) ) #201603151533 SMP Tue Ma
Ah, that was fast. This kernel has the bug:
$ cat /proc/version
Linux version 4.3.0-040300-generic (jsalisbury@gomeisa) (gcc version 5.3.1
20160311 (Ubuntu 5.3.1-11ubuntu1) ) #201603151533 SMP Tue Mar 15 19:37:15 UTC
2016
--
You received this bug notification because you are a member of Kernel
I have booted into this kernel:
$ cat /proc/version
Linux version 4.4.9-040409-generic (kernel@gomeisa) (gcc version 5.3.1 20160413
(Ubuntu 5.3.1-14ubuntu2) ) #201605041832 SMP Wed May 4 22:34:16 UTC 2016
Since the bug doesn't always show itself right away, I will want to use
the kernel for at
This kernel has the bug:
$ cat /proc/version
Linux version 4.4.9-040409-generic (kernel@gomeisa) (gcc version 5.3.1 20160413
(Ubuntu 5.3.1-14ubuntu2) ) #201605041832 SMP Wed May 4 22:34:16 UTC 2016
--
You received this bug notification because you are a member of Kernel
Packages, which is subsc
I have booted into this kernel:
$ cat /proc/version
Linux version 4.3.0-040300rc5-generic (jsalisbury@gomeisa) (gcc version 5.2.1
20151010 (Ubuntu 5.2.1-22ubuntu2) ) #201605111621 SMP Wed May 11 20:26:24 UTC
2016
Since the bug doesn't always show itself right away, I will want to use
the kernel
This kernel does not seem to have the bug after using the system all
day:
$ cat /proc/version
Linux version 4.3.0-040300rc5-generic (jsalisbury@gomeisa) (gcc version 5.2.1
20151010 (Ubuntu 5.2.1-22ubuntu2) ) #201605111621 SMP Wed May 11 20:26:24 UTC
2016
--
You received this bug notification
** Changed in: linux-lts-backport-maverick (Ubuntu Saucy)
Status: New => Won't Fix
** Changed in: linux-lts-backport-natty (Ubuntu Saucy)
Status: New => Won't Fix
** Changed in: linux-lts-backport-oneiric (Ubuntu Saucy)
Status: New => Won't Fix
** Changed in: linux-lts-backp
** Changed in: linux (Ubuntu Quantal)
Status: New => Won't Fix
** Changed in: linux-armadaxp (Ubuntu Quantal)
Status: New => Won't Fix
** Changed in: linux-ti-omap4 (Ubuntu Quantal)
Status: New => Won't Fix
--
You received this bug notification because you are a member of K
** Changed in: linux (Ubuntu Quantal)
Status: Fix Committed => Won't Fix
** Changed in: linux-ti-omap4 (Ubuntu Quantal)
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 Ubu
1 - 100 of 711 matches
Mail list logo
