** Summary changed:
- [Intel Braswell/Apollo Lake] Cursor gets stuck on left side of the screen
+ [Intel Braswell] Cursor gets stuck on left side of the screen
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.
Actually, I'm not certain it is a duplicate of that one - this bug I
think is a regression in eoan due to some change in the kernel between
disco and eoan. Perhaps they are related though.
When I'm back from travelling I'll try to do a little bit of
investigation (but I don't know anything about t
** Changed in: hwe-next
Assignee: (unassigned) => AaronMa (mapengyu)
** Changed in: hwe-next
Importance: Undecided => Critical
** Changed in: hwe-next
Status: New => In Progress
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed
Each qemu (version) is slightly different in the road to this, but then
seems to behave.
This one is slightly better to get "in front" of the slow call to map all the
memory.
$ virsh nodedev-detach pci__21_00_1 --driver vfio
$ gdb /usr/bin/qemu-system-x86_64
(gdb) b vfio_dma_map
(gdb) command
This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:
apport-collect 1841722
and then change the status of the bug to 'Confirmed'.
If, due to the nature
--- Comment From mranw...@us.ibm.com 2019-08-28 02:19 EDT---
I did successfully check the HWE kernel on Xenial, but should have access to a
p8 tomorrow to check against the standard kernel.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscr
Public bug reported:
SRU justification:
[Impact]
The touchpads of some ThinkPad had a tap middle button.
But current 5.2- kernel doesn't support it.
[Fix]
Add device pnpid to support the middle button on these ThinkPads.
[Test]
Verified on 2 hardware. Tests result are good.
[Regression Potenti
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]
** Changed in: linux (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bu
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]
** Changed in: linux (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bu
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]
** Changed in: linux (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bu
This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:
apport-collect 1841704
and then change the status of the bug to 'Confirmed'.
If, due to the nature
This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:
apport-collect 1841707
and then change the status of the bug to 'Confirmed'.
If, due to the nature
** Also affects: ubuntu-kernel-tests
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/1841704
Title:
Test 391/u and 391/p from ubuntu_bpf failed
Public bug reported:
#491/u check deducing bounds from const, 5 FAIL
Unexpected success to load!
0: (b7) r0 = 0
1: (75) if r0 s>= 0x0 goto pc+1
3: (95) exit
processed 3 insns, stack depth 0
#491/p check deducing bounds from const, 5 FAIL
Unexpected success to load!
0: (b7) r0 =
Public bug reported:
#391/u bounds checks mixing signed and unsigned, variant 14 FAIL
Unexpected error message!
0: (61) r9 = *(u32 *)(r1 +8)
1: (7a) *(u64 *)(r10 -8) = 0
2: (bf) r2 = r10
3: (07) r2 += -8
4: (18) r1 = 0x0
6: (85) call bpf_map_lookup_elem#1
7: (15) if r0 == 0x0 goto
** Summary changed:
- [Intel Braswell] Cursor gets stuck on left side of the screen
+ [Intel Braswell/Apollo Lake] Cursor gets stuck on left side of the screen
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.
*** This bug is a duplicate of bug 1767654 ***
https://bugs.launchpad.net/bugs/1767654
Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1767654, so it is being marked as such. Please look
@mangoo-wpkg, that seems like valuable information upstream. Does anyone
know the procedure to get it upstream, please?
--
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/1730331
Titl
Pander, please open a new bug by running:
ubuntu-bug linux
--
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/1796573
Title:
Keyboard backlight not working on ubuntu 18.10, but works on 1
Thank you for reporting this bug to Ubuntu.
Ubuntu 18.10 (cosmic) reached end-of-life on July 18, 2019.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate that this bug may be old and you might not be interested
in discussing it any more. Bu
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 privile
Thank you for using Ubuntu and taking the time to report a bug. Your
report should contain, at a minimum, the following information so we can
better find the source of the bug and work to resolve it.
Submitting the bug about the proper source package is essential. For
help see https://wiki.ubuntu.
Fix up for review: https://review.opendev.org/#/c/678956/
** Changed in: charm-neutron-openvswitch
Assignee: (unassigned) => Tiago Pasqualini da Silva (tiago.pasqualini)
** Changed in: charm-neutron-openvswitch
Status: Confirmed => In Progress
--
You received this bug notification b
Sorry, agent looks missing on proposed for Xenial. Canonical, could you
please check it?
There is no libperf-jvmti.so afaics.
I'm marking it as 'verification-failed-xenial'.
gromero@gromero16:/tmp$ dpkg -L linux-tools-4.4.0-160
/.
/usr
/usr/lib
/usr/lib/linux-tools-4.4.0-160
/usr/lib/linux-tool
Public bug reported:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either directly from
Oh thank you, sir!
ср, 28 авг. 2019 г., 0:01 Iain Lane :
> On Tue, Aug 27, 2019 at 07:47:53PM -, Artyom Pozharov wrote:
> > Public bug reported:
> >
> > Sorry for low-quality video: https://photos.app.goo.gl/c6k8AHGJR6MifgHY8
>
> Yes, thanks for filing. I showed this to the upstream guys and
I have tried that on 19.04 with kernel 5.0.0-25-generic but it did not
work. What are ways to debug this?
/sys/class/leds/asus::kbd_backlight/brightness exists and can hold a
value of 0, 1, 2 or 3. Lower than 0 results in
bash: echo: write error: Invalid argument
Values over 3 result in 3.
Tree
On Tue, Aug 27, 2019 at 07:47:53PM -, Artyom Pozharov wrote:
> Public bug reported:
>
> Sorry for low-quality video: https://photos.app.goo.gl/c6k8AHGJR6MifgHY8
Yes, thanks for filing. I showed this to the upstream guys and they knew
about it. It's apparently a kernel problem as if you revert
You have been subscribed to a public bug:
Sorry for low-quality video: https://photos.app.goo.gl/c6k8AHGJR6MifgHY8
P.S. Any screen recorders don't work on Wayland.
ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: gnome-shell 3.33.91-1ubuntu1
ProcVersionSignature: Ubuntu 5.2.0-13.14-generic 5
As kernels 5.2.0-x will bring zfs 0.8.x to Bionic LTS, I'd like to draw
some attention to this request. People will get the 0.8.x zfs module via
HWE but won't be able to do much with the major new features without the
userland tools.
I tried to install the debs from Eoan, but they require a higher
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
packages:
** Changed in: linux (Ubuntu)
Status: Fix Committed => 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/787210
Title:
ath9k drivers freeze the system when changing stat
I update kernel 5.3-rc6 at this mail client environment.
kernel 5.3-rc6 may work fine at BIOS only PC.
I remained to use other PC, that are BIOS only, UEFI only.
step by step, I wish to test.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
** Changed in: kernel-sru-workflow/promote-to-security
Status: New => Invalid
** Changed in: kernel-sru-workflow/security-signoff
Status: New => Invalid
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the t
*** This bug is a duplicate of bug 1841658 ***
https://bugs.launchpad.net/bugs/1841658
** This bug is no longer a duplicate of bug 1840974
bionic/linux-ibm-gt: 4.15.0-1033.35 -proposed tracker
** This bug has been marked a duplicate of bug 1841658
linux-ibm-gt: -proposed tracker
--
Yo
** Summary changed:
- disco/linux-oracle: 5.0.0-1001.1 -proposed tracker
+ disco/linux-oracle: 5.0.0-1001.2 -proposed tracker
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oracle in Ubuntu.
https://bugs.launchpad.net/bugs/1840811
*** This bug is a duplicate of bug 1841658 ***
https://bugs.launchpad.net/bugs/1841658
** This bug is no longer a duplicate of bug 1840974
bionic/linux-ibm-gt: 4.15.0-1033.35 -proposed tracker
** This bug has been marked a duplicate of bug 1841658
linux-ibm-gt: -proposed tracker
--
Yo
** Changed in: kernel-sru-workflow/promote-to-proposed
Status: In Progress => Incomplete
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow s
** Summary changed:
- linux-ibm-gt: -proposed tracker
+ bionic/linux-ibm-gt: -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package
Status: New => Confirmed
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as s
** Summary changed:
- bionic/linux-ibm-gt: -proposed tracker
+ bionic/linux-ibm-gt: 4.15.0-1034.36 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package
Status: Confirmed => In Progress
** Changed in: kernel-sru-workflow/prepare-package
Assignee: Canonical Kernel Team
*** This bug is a duplicate of bug 1841658 ***
https://bugs.launchpad.net/bugs/1841658
** This bug is no longer a duplicate of bug 1840974
bionic/linux-ibm-gt: 4.15.0-1033.35 -proposed tracker
** This bug has been marked a duplicate of bug 1841658
linux-ibm-gt: -proposed tracker
--
Yo
*** This bug is a duplicate of bug 1841658 ***
https://bugs.launchpad.net/bugs/1841658
** Tags removed: kernel-sru-derivative-of-1841086
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanat
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
boot-testi
Public bug reported:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
kernel-stable-master-bug: 184
This bug was fixed in the package zfs-linux - 0.6.5.6-0ubuntu28
---
zfs-linux (0.6.5.6-0ubuntu28) xenial; urgency=medium
* Fix ZFS shrinker deadlock with xattrs (LP: #1839521)
- Upstream ZFS fix 31b6111fd92a ("Kill zp->z_xattr_parent to prevent
pinning")
and ddae16a9cf0b
The verification of the Stable Release Update for zfs-linux has
completed successfully and the package has now been released to
-updates. Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter
** Attachment added: "dmesg50028nvidia"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1840835/+attachment/5285033/+files/dmesg50028nvidia
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.ne
I installed the test kernel:
linux-headers-5.0.0-28_5.0.0-28.29~lp1840835_all.deb
linux-headers-5.0.0-28-generic_5.0.0-28.29~lp1840835_amd64.deb
linux-image-unsigned-5.0.0-28-generic_5.0.0-28.29~lp1840835_amd64.deb
linux-modules-5.0.0-28-generic_5.0.0-28.29~lp1840835_amd64.deb
linux-modules-extra-5
It broke again today :( Maybe the the solution earlier didn't work
--
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/1832144
Title:
Ubuntu 19.04 suspend freeze on Dell inspiron 7373
Status
Public bug reported:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either directly from
** Changed in: kernel-sru-workflow/automated-testing
Status: New => Confirmed
** Changed in: kernel-sru-workflow/promote-to-proposed
Status: Fix Committed => Fix Released
** Changed in: kernel-sru-workflow/regression-testing
Status: New => Confirmed
** Changed in: kernel-sru
Seems like you may be right. I could not reproduce it with
1bcf165ac6556d after about 10 attempts. This isn't conclusive
unfortunately. I will continue with a regular bisect.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
I can't reproduce this in a local VM on the disco/master-next branch
(tip of my branch is currently at: ebf9271500ba "UBUNTU: upstream stable
to v4.19.55, v5.1.14")
Here's what I'm doing:
sudo make -C tools/testing/selftests TARGETS=net run_tests
Here's the relevant test:
selftests: net: ip_def
My reproducer for Disco+ is a different bug. I get input/output errors
very quickly once specifying nfs vers=4.0. If you don't specify it, it
works fine.
** Changed in: linux (Ubuntu Disco)
Status: Confirmed => Fix Released
** Changed in: linux (Ubuntu)
Status: Confirmed => Fix Re
Thanks for reporting this bug and helping to make Ubuntu better.
Was an upstream bug ever filed? Was a clear reproducer ever identified?
** Changed in: linux (Ubuntu)
Status: Triaged => Incomplete
** Changed in: linux (Ubuntu Zesty)
Status: Triaged => Confirmed
** Changed in: lin
This problem happens for me, with newest firmware, newest kernel, as of
today - but turns out only in the following situation:
- wireless router supports both 2.4 and 5 GHz
- same SSID name is used for both ranges
I.e. after disabling 5 GHz support on the router, the wifi card no longer
crashes
** Also affects: linux-hwe (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux-hwe (Ubuntu Cosmic)
Status: New => Won't Fix
** Changed in: linux-hwe (Ubuntu Disco)
Status: New => Won't Fix
--
You received this bug notification because you are a member of Kern
I was also able to reproduce this on Eoan by specifying vers=4.0 - where
I thought it should be fixed.
I was able to confirm that the -proposed 4.15 kernel (I tested xenial
HWE version) does have the fix and it
works:https://lists.ubuntu.com/archives/xenial-
changes/2019-August/025318.html
--
Yo
Same here with kernel 5.0.0-25-generic, however the script from post
#120 seems to work around this.
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1752772/comments/120
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
backports: bug 1841158 (bionic/li
** Description changed:
+ === SRU Justification ===
+ [Impact]
+ r8169 network device unable to detect link after boot.
+
+ [Fix]
+ Don't use MSI for older r8169 chips.
+
+ [Test]
+ User confirmed the issue is fixed with the patch applied.
+
+ [Regression Potential]
+ Low. This reverts affected
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
kernel-sta
I think it's unlikely that these two caused the regression.
Please file an upstream bug at https://bugzilla.kernel.org/
Product: Drivers
Component: Network
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.laun
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
backports: bug 1841158 (bionic/li
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
kernel-sta
Hi Drew,
That's very good news! So it looks like that patch resolves the
problem.
Could you please test the kernel in bionic-proposed [1] (4.15.0-60-generic)
which has that patch to confirm it's also working correctly?
Thanks!
Mauricio
[1] https://wiki.ubuntu.com/Testing/EnableProposed
--
Yo
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
packages:
Some details about those debdiffs: they were prepared on top of a
version done by Connor Kuehl that could have landed in -proposed between
my uploading of the diff and the package upload/sponsorship.
That explains the extra changelog stanza and the versioning. It also
explains the change in the or
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
+ boot-testi
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
+ boot-testi
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
packages:
** Description changed:
+ [SRU Justification]
+
+ == Impact ==
+
+ 1bd4978a88ac2 ("tun: honor IFF_UP in tun_get_user()") which is part of
+ kernel v4.5 introduced an issue where userspace processes might not get
+ notified if a link comes up after initially being down. This was fixed
+ in the re
Works well!
--
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/1838477
Title:
[regression] r8169 network device unable to detect link on x86 arch
Status in linux package in Ubuntu:
Confir
A test kernel can be found here:
https://people.canonical.com/~khfeng/lp1840835/
--
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/1840835
Title:
High power consumption using 5.0.0-25-gener
I could next build a test kernel with some debug around the vfio iommu dma map
to check how time below that call is spent.
I'm sure that data already is hidden in some of my trace data, but to
eventually change/experiment I need to build one anyway.
I expect anyway to summarize and go into a dis
Excellent news! Thanks Eric :-)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to makedumpfile in Ubuntu.
https://bugs.launchpad.net/bugs/1681909
Title:
kdump is not captured in remote host when kdump over ssh is configured
Status in The
** Changed in: kernel-sru-workflow/automated-testing
Status: Incomplete => Fix Released
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow se
Hi Andrew Cloke,
Yes, I'm currently sponsoring D/B for cascardo/gpicolli.
Disco is already uploaded waiting for SRU team approval:
https://launchpad.net/ubuntu/disco/+queue?queue_state=1&queue_text=makedumpfile
Bionic debdiff needs some rework before I do the final upload.
- Eric
--
You recei
All tasks have been completed and the bug is being set to Fix Released
** Changed in: kernel-sru-workflow
Status: In Progress => Fix Released
** Tags removed: kernel-release-tracking-bug-live
--
You received this bug notification because you are a member of Kernel
Packages, which is sub
** Changed in: kernel-sru-workflow/automated-testing
Status: In Progress => Incomplete
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see
** Changed in: kernel-sru-workflow/automated-testing
Status: In Progress => Fix Released
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow s
** Changed in: kernel-sru-workflow/automated-testing
Status: In Progress => Fix Released
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow s
Reference:
this is the call from qemu that I think we see above (on x86) is at [1].
If this time the assumption is correct the kernel place would be at
vfio_iommu_type1_ioctl.
For debugging:
$ gdb qemu/x86_64-softmmu/qemu-system-x86_64
(gdb) catch syscall 16
(gdb) run -m 131072 -smp 1 -no-user-co
Next step is to consider backport feasibility for disco and bionic.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to makedumpfile in Ubuntu.
https://bugs.launchpad.net/bugs/1681909
Title:
kdump is not captured in remote host when kdump o
Awaiting confirmation from IBM (Anju), as per Michael's last comment.
--
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/1752002
Title:
[P9,POwer NV][WSP][DD2.1][Ubuntu 1804][Perf fuzzer] :
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
backports: bug 1840826 (bionic/li
My proposed patch to fix the issue:
https://lkml.org/lkml/2019/8/27/956
--
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/1840835
Title:
High power consumption using 5.0.0-25-generic
Statu
** Changed in: kernel-sru-workflow/promote-to-proposed
Status: Confirmed => Fix Committed
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
packages:
** Changed in: kernel-sru-workflow/promote-to-release
Status: Confirmed => Fix Released
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow se
** Changed in: kernel-sru-workflow/promote-to-proposed
Status: New => Confirmed
** Tags added: block-proposed-eoan
** Tags added: block-proposed
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For
@mvo I don't understand why we'd add the "assumes" to the kernel's
snapcraft.yaml now since we're reverting the problematic AppArmor
commit. A kernel with the AppArmor commit will never be released to
stable (or -updates/-security) so I don't think that the "assumes"
workaround is needed any longer
** Changed in: kernel-sru-workflow/prepare-package
Status: Fix Committed => Fix Released
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow s
This bug was fixed in the package linux - 5.2.0-13.14
---
linux (5.2.0-13.14) eoan; urgency=medium
* eoan/linux: 5.2.0-13.14 -proposed tracker (LP: #1840261)
* NULL pointer dereference when Inserting the VIMC module (LP: #1840028)
- media: vimc: fix component match compare
This bug was fixed in the package linux - 5.2.0-13.14
---
linux (5.2.0-13.14) eoan; urgency=medium
* eoan/linux: 5.2.0-13.14 -proposed tracker (LP: #1840261)
* NULL pointer dereference when Inserting the VIMC module (LP: #1840028)
- media: vimc: fix component match compare
*** This bug is a duplicate of bug 1784665 ***
https://bugs.launchpad.net/bugs/1784665
This bug was fixed in the package linux - 5.2.0-13.14
---
linux (5.2.0-13.14) eoan; urgency=medium
* eoan/linux: 5.2.0-13.14 -proposed tracker (LP: #1840261)
* NULL pointer dereference whe
This bug was fixed in the package linux - 5.2.0-13.14
---
linux (5.2.0-13.14) eoan; urgency=medium
* eoan/linux: 5.2.0-13.14 -proposed tracker (LP: #1840261)
* NULL pointer dereference when Inserting the VIMC module (LP: #1840028)
- media: vimc: fix component match compare
This bug was fixed in the package linux - 5.2.0-13.14
---
linux (5.2.0-13.14) eoan; urgency=medium
* eoan/linux: 5.2.0-13.14 -proposed tracker (LP: #1840261)
* NULL pointer dereference when Inserting the VIMC module (LP: #1840028)
- media: vimc: fix component match compare
Many ioctls (as expected) but they are all fast and match what we knew from
strace.
Thread 1 "qemu-system-x86" hit Catchpoint 1 (call to syscall ioctl),
0x772fae0b in ioctl () at ../sysdeps/unix/syscall-template.S:78
78 in ../sysdeps/unix/syscall-template.S
(gdb) bt
#0 0x772
This bug was fixed in the package linux - 5.2.0-13.14
---
linux (5.2.0-13.14) eoan; urgency=medium
* eoan/linux: 5.2.0-13.14 -proposed tracker (LP: #1840261)
* NULL pointer dereference when Inserting the VIMC module (LP: #1840028)
- media: vimc: fix component match compare
1 - 100 of 206 matches
Mail list logo
