ng 1.20.4 connected started full enabled enabled
enabled enabled enabled
---
ProblemType: Bug
ApportVersion: 2.20.9-0ubuntu7.9
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: christian 1686 F pulseaudio
/dev/snd
Ping, what is up with this nowadays?
I'm still not seeing this in Focals kernels (but as mentioned before in
Debian).
This blocks XDP support in DPDK for 20.04.
And most likely will make us need a Delta to Debian :-/
Therefore I wanted to ask if there is any update on this, a clear
blocker so I
-HW WWAN
running 1.20.4 connected started full enabled enabled
enabled enabled enabled
---
ProblemType: Bug
ApportVersion: 2.20.9-0ubuntu7.9
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: christian 1686 F pu
1.20.4 connected started full enabled enabled
enabled enabled enabled
---
ProblemType: Bug
ApportVersion: 2.20.9-0ubuntu7.9
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: christian 1686 F pulseaudio
/dev/snd/c
N
running 1.20.4 connected started full enabled enabled
enabled enabled enabled
---
ProblemType: Bug
ApportVersion: 2.20.9-0ubuntu7.9
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: christian 1686 F pulseaudio
connected started full enabled enabled
enabled enabled enabled
---
ProblemType: Bug
ApportVersion: 2.20.9-0ubuntu7.9
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: christian 1686 F pulseaudio
/dev/snd/controlC0:
N
running 1.20.4 connected started full enabled enabled
enabled enabled enabled
---
ProblemType: Bug
ApportVersion: 2.20.9-0ubuntu7.9
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: christian 1686 F pulseaudio
1.20.4 connected started full enabled enabled
enabled enabled enabled
---
ProblemType: Bug
ApportVersion: 2.20.9-0ubuntu7.9
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: christian 1686 F pulseaudio
/dev/snd/c
ESS COMMAND
/dev/snd/controlC1: christian 1686 F pulseaudio
/dev/snd/controlC0: christian 1686 F pulseaudio
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 18.04
InstallationDate: Installed on 2019-11-25 (1 days ago)
InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver
connected started full enabled enabled
enabled enabled enabled
---
ProblemType: Bug
ApportVersion: 2.20.9-0ubuntu7.9
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: christian 1686 F pulseaudio
/dev/snd/controlC
connected started full enabled enabled
enabled enabled enabled
---
ProblemType: Bug
ApportVersion: 2.20.9-0ubuntu7.9
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: christian 1686 F pulseaudio
/dev/snd/controlC
connected started full enabled enabled
enabled enabled enabled
---
ProblemType: Bug
ApportVersion: 2.20.9-0ubuntu7.9
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: christian 1686 F pulseaudio
/dev/snd/controlC0:
1.20.4 connected started full enabled enabled
enabled enabled enabled
---
ProblemType: Bug
ApportVersion: 2.20.9-0ubuntu7.9
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: christian 1686 F pulseaudio
/dev/snd/c
N
running 1.20.4 connected started full enabled enabled
enabled enabled enabled
---
ProblemType: Bug
ApportVersion: 2.20.9-0ubuntu7.9
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: christian 1686 F pulseaudio
N
running 1.20.4 connected started full enabled enabled
enabled enabled enabled
---
ProblemType: Bug
ApportVersion: 2.20.9-0ubuntu7.9
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: christian 1686 F pulseaudio
-HW
WIFI WWAN-HW WWAN
running 1.20.4 connected started full enabled enabled
enabled enabled enabled
+ ---
+ ProblemType: Bug
+ ApportVersion: 2.20.9-0ubuntu7.9
+ Architecture: amd64
+ AudioDevicesInUse:
+ USERPID ACCESS COMMAND
+ /dev/snd/controlC1: christia
I found no obvious regressions with this build in a run of our usual set
of tests.
@IBM - for SRu verification - can you give the actual testcase it was
intended for a shot in your environment as you had that set up int he
past?
--
You received this bug notification because you are a member of
** Tags removed: verification-needed-disco verification-needed-eoan
** Tags added: verification-done-disco verification-done-eoan
--
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/1849482
** Tags removed: verification-needed-disco verification-needed-eoan
** Tags added: verification-done-disco verification-done-eoan
--
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/1849483
** Tags removed: verification-needed-disco verification-needed-eoan
** Tags added: verification-done-disco verification-done-eoan
--
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/1849281
5.4 is around and will be in Focal soon.
If you could test there then that it is good the kernel team can consider
backports.
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
** Changed in: strongswan (Ubuntu)
Status: Triaged => Invalid
--
You received this bug
** Changed in: strongswan (Ubuntu)
Status: Incomplete => 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/1828035
Title:
StrongSwan with GCM and large packet sizes produces
This got surpassed by a security upload while waiting for SRU Team.
I have uploaded rebased versions to -unapproved.
--
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/1842774
Title:
This got surpassed by a security upload while waiting for SRU Team.
I have uploaded rebased versions to -unapproved.
--
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/1847948
Title:
** Changed in: qemu (Ubuntu)
Assignee: Rafael David Tinoco (rafaeldtinoco) => (unassigned)
--
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/1849720
Title:
KVM with e1000e and
On Tue, Nov 12, 2019 at 5:35 AM Zach Graceffa
<1849...@bugs.launchpad.net> wrote:
>
> @Christian - 5.4-rc7 worked for both e1000e and virtio NICs. No crash as
> of about 15 minutes.
Great, thanks Zach for the check!
@kernel-team, that means there likely is something in 5.3 ->
I did a retry on my own as well (kernel 5.3, virtual e1000e card, win
server guest), but it just won't fail for me. That confirmed Rafaels
much more various tests :-/
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
@Rafael - IIRC you said all combinations you tried didn't trigger anything for
you - is that correct?
If so please state it here and mark the bug on the qemu task invalid and
unassign yourself as it seems much more a kernel issue right now.
Or did you have combinations left to try?
--
You
@Kernel Team - this has enough affected people that I'd rate this at least high
severity.
Unfortunately none of "us" could reproduce it on our side yet to bisect on our
own.
As you see above affected users were so kind to test mainline kernels and
identified 5.2.21-050221 - 5.3.0-050300
I'm afraid I won't be able to test the Bionic version before the end of the
year. I don't have a Bionic installation on my machine, and the next free
weekend for installing a new system and doing tests like that would be in
2020...
Anybody else, who could give it a try?
--
You received this
This doesn't need kernel logs at this state of the bug, bot pleas stop
spamming :-)
** 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.
Zach, thanks for the feedback.
Since we still struggle to recreate this on our side is there a chance that you
could test kernels from [1] to help spotting which version bump exactly it was?
Going further we might even need to bisect things, but one step at a time.
I'd not want to put this on
Most likely we will have qemu 4.2 in Ubuntu 20.04.
But we already closed this bug for qemu with the patches you identified in the
past.
If you need - for tracking purposes - a bug that closes once these further
changes are in I'd ask you to open a new one.
--
You received this bug notification
Uploaded for SRU Team review and acceptance into proposed.
--
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/1847948
Title:
Improve NVMe guest performance on Bionic QEMU
Status in The
Uploaded the Disco version along the upload to Bionic for SRU Team
review and acceptance into proposed.
--
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/1842774
Title:
Enhanced Hardware
** Tags removed: verification-needed-eoan
** Tags added: verification-done-eoan
--
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/1846265
Title:
shiftfs: rework how shiftfs opens files
** Tags removed: verification-needed-disco verification-needed-eoan
** Tags added: verification-done-disco verification-done-eoan
--
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/1847744
** Tags removed: verification-needed-eoan
** Tags added: verification-done-eoan
--
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/1846272
Title:
overlayfs: allow with shiftfs as underlay
As outlined in the past conceptually there is nothing that qemu can do.
The kernel can in theory get memory zeroing to become concurrent and thereby
scale with CPUs but that is an effort that was already started twice and didn't
get into the kernel yet.
Workarounds are known to shrink that size
.
** Affects: linux (Ubuntu)
Importance: Undecided
Assignee: Christian Brauner (cbrauner)
Status: In Progress
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Christian Brauner (cbrauner)
** Changed in: linux (Ubuntu)
Status: New => In Progress
--
You re
on a fixed kernel and see that the call succeeds and the file is of the
expected size.
Target Kernels:
All LTS kernels with shiftfs support.
** Affects: linux (Ubuntu)
Importance: Undecided
Assignee: Christian Brauner (cbrauner)
Status: In Progress
** Changed in: linux (Ubuntu
** Tags removed: verification-needed-disco
** Tags added: verification-done-disco
--
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/1846272
Title:
overlayfs: allow with shiftfs as underlay
** Tags removed: verification-needed-eoan
** Tags added: verification-done-eoan
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/1848848
Title:
Firmware for Radeon RX5700
I can confirm that the new linux-firmware package in eoan-proposed
solves this issue. I'm getting some warnings, but the system boots and
graphics is fine:
$ sudo update-initramfs -u -k all
update-initramfs: Generating /boot/initrd.img-5.3.0-19-generic
W: Possible missing firmware
=2aa8d8d04ca29c3269154e1d48855e498be8882f
** Affects: linux (Ubuntu)
Importance: Undecided
Assignee: Christian Brauner (cbrauner)
Status: In Progress
** Changed in: linux (Ubuntu)
Status: New => In Progress
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Christian B
as you suggested might be useful, will you come up with a draft for it?
@Rafael/Christian - lets also talk with the Team about it to get everyone on
the same page.
[1]: https://wiki.ubuntu.com/OpenStack/CloudArchive
** Changed in: libvirt (Ubuntu Disco)
Status: Opinion => Won't Fix
--
Actually the bug here has nothing to so with the kernel bug which was
just a build issue, lets remove the kernel task to not distract.
** No longer affects: linux (Ubuntu)
** No longer affects: linux (Ubuntu Bionic)
** No longer affects: linux (Ubuntu Disco)
** No longer affects: linux (Ubuntu
Next issue is around skb_frag_size_sub skb_frag_dma_map skb_frag_address
/usr/src/dpdk-rte-kni-18.11.2/ethtool/igb/igb_main.c:5352:12: error: assignment
to ‘struct skb_frag_struct *’ from incompatible pointer type ‘skb_frag_t *’
{aka ‘struct bio_vec *’} [-Werror=incompatible-pointer-types]
Fix the next issue around num_online_cpus
** Patch added: "num-online-cpus"
https://bugs.launchpad.net/ubuntu/eoan/+source/dpdk/+bug/1848585/+attachment/5298831/+files/dpdk-kni-fix-num_online_cpus.patch
--
You received this bug notification because you are a member of Kernel
Packages, which
Probably related to kernel change:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=0c09ab96fc820109d63097a2adcbbd20836b655f
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Here is the fix for the first issue that was hit (attached), but there
is more after that, now I hit:
/usr/src/dpdk-rte-kni-18.11.2/ethtool/ixgbe/kcompat.h:239:27: error:
‘smp_num_cpus’ undeclared (first use in this function)
239 | #define num_online_cpus() smp_num_cpus
** Patch added: "fix
## DPDK in Ubuntu ##
18.11.x:
$ grep -Hrn pci-aspm *
kernel/linux/kni/ethtool/ixgbe/kcompat.h:2225:#include
kernel/linux/kni/ethtool/igb/kcompat.h:2417:#include
The same is true for DPDK 17.11.x in Bionic.
That is in the file of dpdk-rte-kni-dkms:
After that detour now back to DKMS on DPDK.
The issue is this:
make: Entering directory '/usr/src/linux-headers-5.4.0-050400rc3-generic'
CC [M] /var/lib/dkms/dpdk-rte-kni/18.11.2/build/kni_net.o
CC [M] /var/lib/dkms/dpdk-rte-kni/18.11.2/build/kni_misc.o
CC [M]
Confirmed the new rebuild of the mainline kernels resolved the issue
** 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.
[23:45] I'm trying to perform a test build against a 5.4 mainline
kernel, it appears that the Makefile is missing from the linux headers (it's a
broken symlink)
[23:45] I'm pulling the linux stuff from:
https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.4-rc3/
[23:46] (the test build is for a
I marked it to affect kernel as well, but it seems from above discussion that
it might already be solved by a rebuild now.
Checking ...
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Public bug reported:
As an owner of a Radeon RX5700 GPU, I was really looking forward to the
Eoan release which includes the Linux Kernel 5.3 and Mesa 19.2 - both
with finally Radeon RX5700 (navi10) support. However, upgrading my
system from Kubuntu 18.10 (working) via 19.04 (does not boot) to
I opened up the MP for review again after pushing the extra patches that you
tested.
Once that is done I can push it to the SRU teams queue ...
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Thanks Murilo, I need no test with the basic kernel yet.
But later when we really SRU this it will be good to do both a old and a HWE
kernel check.
Let me add that to the verification steps ...
** Description changed:
[Impact]
- * In the past qemu has generally not allowd MSI-X BAR
Thanks for your feedback and tests Murilo*2 (There seems to be a team of
Murilo's on this :-) - thanks for your efforts and fast responses
bringing this case forward.)
With the main changes requested I really think we need the patch in #8
to avoid issues on other HW setups that due to the new
@Murilo: I was wondering - I think we might want/need also [1] to not
run into fatal false positives. What is your opinion on this?
[1]:
https://git.qemu.org/?p=qemu.git;a=commit;h=567b5b309abe744b1098018a2eb157e7109c9f30
** Description changed:
+ [Impact]
+
+ * In the past qemu has generally
And on top of the former question most likely then also [1].
[1]:
https://git.qemu.org/?p=qemu.git;a=commit;h=5c08600547c059e3fd072995f9f367cdaf3c7d9d
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** Description changed:
+ @SRU Team: For SRU template of Qemu please scroll down ...
+
SRU Justification Kernel:
=
[Impact]
* Add / activate support for IBM z15 and LinuxONE III systems
[Fix]
* a0e2251132995b962281aa80ab54a9288f9e0b6b a0e2251
All systems I could easily get a hold of already had their NVME drives
in use so I couldn't pass them through easily. Therefore I'd like to
come back to your offer to check the test build.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
FYI: Test builds are in [1]. It isn't required, but would be great if
you could give it a check as well ahead of the actual SRU.
[1]:
https://launchpad.net/~paelzer/+archive/ubuntu/bug-1847948-nvmeperf-1842774
-z15name-bionic
--
You received this bug notification because you are a member of
@SRU Team:
As outlined above this is important for IBM to get product names right
everywhere. But at the same time this is "only" a change in a description which
doesn't qualify an SRU on its own. So we agreed to only upload it once there is
another SRU.
I now have an Qemu SRU for Bionic that
I must have been blind, of course your testcase in the description is
fine. Sorry for even asking.
I'll give it a try if it also works to reflect the improvement on some
HW I can access, but if not thanks for offer to test it on your side.
--
You received this bug notification because you are a
The kernel part of this is in since 4.16 so it either needs a HWE kernel
or to add a kernel Task to backport the related change for the kernel as
well. I'll add a task but it depends the Kernelteam (doability) and the
reporters request (for which kernel it is needed).
** Also affects: linux
FYI kernel commit is [1] I haven't checked if any context is needed.
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1847948
--
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/1847948
For Qemu the code is in 2.12, therefore as requested we only need to
consider Bionic.
@Murilo: do you have a good testcase for this to verify the bug when it became
an accepted SRU?
Could you outline what has to be done and if it requires special HW or a rather
complex setup maybe even commit
ap to userspace")
** Affects: linux (Ubuntu)
Importance: Undecided
Assignee: Christian Brauner (cbrauner)
Status: In Progress
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Christian Brauner (cbrauner)
** Changed in: linux (Ubuntu)
Status: New => In
Thanks Andreas for already commenting on the upstream ZFS issue!
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1847105
Title:
very slow disk creation, snapshotting
Status in
FYI - it seems upstream of libvirt/virt-manager settles on the new
behavior actually being preferable. I tend to agree, and the pain only
happens if you also run things on ZFS which would be resolved if [1] is
ever fully resolved.
Adding a ZFS task for that.
[1]:
** Tags removed: verification-needed-disco
** Tags added: verification-done-disco
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Christian Brauner (cbrauner)
** Changed in: linux (Ubuntu Disco)
Assignee: (unassigned) => Christian Brauner (cbrauner)
--
You received th
** Tags removed: verification-needed-disco
** Tags added: verification-done-disco
** Changed in: linux (Ubuntu Disco)
Assignee: (unassigned) => Christian Brauner (cbrauner)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to li
** Changed in: linux (Ubuntu Disco)
Assignee: (unassigned) => Christian Brauner (cbrauner)
** Tags removed: verification-needed-disco
** Tags added: verification-done-disco
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to li
uced with the new patch.
Target kernels: All LTS kernels that do support shiftfs, if possible.
** Affects: linux (Ubuntu)
Importance: Undecided
Assignee: Christian Brauner (cbrauner)
Status: In Progress
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => C
** Changed in: linux (Ubuntu)
Status: Incomplete => In Progress
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Christian Brauner (cbrauner)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Public bug reported:
SRU Justification
Impact: Currently, shiftfs maintains a kmem cache for struct
shiftfs_file_info which stashes away a struct path and the struct file
for the underlay. The path however is never used anywhere so the struct
shiftfs_file_info and therefore the whole kmem cache
We are working on a fix. Can you give this testpatch a spin?
** Patch added: "testpatch"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1845323/+attachment/5291775/+files/0001-s390-dasd-Fix-error-handling-during-online-processin.patch
--
You received this bug notification because you
** Also affects: qemu (Ubuntu Eoan)
Importance: Undecided
Status: Invalid
** Also affects: linux (Ubuntu Eoan)
Importance: Medium
Status: In Progress
** Changed in: linux (Ubuntu Bionic)
Status: In Progress => Won't Fix
--
You received this bug notification because
> $ apt-cache policy linux-image-4.15.0-65-generic
> linux-image-4.15.0-65-generic:
> Installed: 4.15.0-65.74
> Candidate: 4.15.0-65.74
> Version table:
> *** 4.15.0-65.74 500
> 500 http://at.archive.ubuntu.com/ubuntu bionic-proposed/main amd64
> Packages
> 100
@vladisslav: Your version is too old, that's not from bionic-proposed!
;-)
> $ apt-cache policy linux-image-generic
linux-image-generic:
> Installed: 4.15.0.65.67
> Candidate: 4.15.0.65.67
> Version table:
> *** 4.15.0.65.67 500
> 500 http://at.archive.ubuntu.com/ubuntu
In fact while I was waiting to submit this the MP got reviewed.
Uploaded to Eoan ...
But since beta freeze is in place acceptance there might have to wait a
few days.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Test build [1] seems ok and MP opened [2].
But the change is trivial so that should be quick ...
[1]:
https://launchpad.net/~paelzer/+archive/ubuntu/fix-1842774-z15-model-name-eoan
[2]:
https://code.launchpad.net/~paelzer/ubuntu/+source/qemu/+git/qemu/+merge/373118
--
You received this bug
Hi,
since [1] doesn't change the identifier (it stays gen15a), so the only thing
that is changing is the description of e.g. seen here:
$ qemu-system-s390x -cpu ? | grep gen15
s390 gen15a-base IBM 8561 GA1(static,
migration-safe)
s390 gen15a IBM 8561 GA1
** Also affects: qemu (Ubuntu)
Importance: Undecided
Status: New
--
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/1842774
Title:
Enhanced Hardware Support - Finalize Naming
*** This bug is a duplicate of bug 1843323 ***
https://bugs.launchpad.net/bugs/1843323
** This bug has been marked a duplicate of bug 1843323
Kernel 4.15.0-59 (and onwards) breaks scroll wheel of USB mouse (A4Tech
X5-50D)
--
You received this bug notification because you are a member of
> […] but I've not tested it yet.
Confirmed, fixed in bionic-proposed! :-)
** Changed in: linux (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
This should be fixed at 4.15.0-63.72 (and 4.15.0-65.74) -- available at
bionic-proposed.
It's mentioned in the changelog, but I've not tested it yet.
https://wiki.ubuntu.com/Testing/EnableProposed
--
You received this bug notification because you are a member of Kernel
Packages, which is
It was already clear on the bug that for qemu I can't do much more as-is.
So I had a discussion with the Maas Team today.
To core issue for me stays that it seems it is unreproducible outside of Maas.
We agree that:
- they try to recreate it in a MAAS
- Once they can we sync and find day(s) to
** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic
--
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/1836910
Title:
br_netfilter: namespace sysctl
@vladisslav: Thanks! :-)
@Maintainer: I've build a test package with
1c703b53e5bfb5c2205c30f0fb157ce271fd42fb.patch and it fixes the bug for
me. So it's a clear +1 from me for backporting this patch ASAP.
--
You received this bug notification because you are a member of Kernel
Packages, which
** Attachment removed: "CurrentDmesg.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1843323/+attachment/5287557/+files/CurrentDmesg.txt
** Attachment removed: "UdevDb.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1843323/+attachment/5287567/+files/UdevDb.txt
**
** Description changed:
The latest kernel upgrade makes it impossible to use the scroll wheel of
one specific mouse.
- Affected Ubuntu release: 18.04.3
- Last working kernel version: 4.15.0-58
- Affected kernel versions: 4.15.0-59, 4.15.0-60, 4.15.0-62, …
+ Affected
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1843323/+attachment/5287567/+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: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1843323/+attachment/5287568/+files/WifiSyslog.txt
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
** Attachment removed: "WifiSyslog.txt"
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1843323/+attachment/5287563/+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: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1843323/+attachment/5287561/+files/ProcCpuinfo.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/1843323/+attachment/5287556/+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/1843323
501 - 600 of 1329 matches
Mail list logo
