** Also affects: thermald (Ubuntu Bionic)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to thermald in Ubuntu.
https://bugs.launchpad.net/bugs/1811730
Title:
Thermald does not set max CPU after
"Good" in PowerTop usually means it is set to sleep. It sounds like the
setting you want is actually the one labelled "Bad".
--
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/1801642
Title:
Can confirm, just upgraded to latest linux hwe package and mouse wheel
is not working.
--
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/1838601
Title:
kernel update 5.0.0-23 breaks scroll
Exactly. But I can't figure our where this setting, for a permanent
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/1801642
Title:
Bluetooth mouse sleeps after 5 seconds of inac
** Description changed:
Hi,
I was using Ubuntu 18.10 thermald package, but I noted that, after few
seconds at max CPU usage (max temp), thermald send the signal to RALP to
reduce the voltage of the CPU. It set the freq to minimum (800MHz in my
case). But when the CPU is idle and temp
Such settings are in the /sys filesystem as text files you can read and
write to. Writing to them is not remembered across boots though --
that's what software like powertop or tlp does.
So you can script writing to /sys/SOMETHING to control power management.
Otherwise to change the defaults in th
Alberto,
I think the change can be applied universally. The PCI core will call
pci_save_state() if driver doesn't do it.
--
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/1836630
Title:
Sy
** Changed in: kernel-sru-workflow/promote-signing-to-proposed
Status: New => Confirmed
** Changed in: kernel-sru-workflow/promote-to-proposed
Status: Fix Committed => Fix Released
** Description changed:
This bug will contain status and test results related to a kernel source
/sys is huge, with many directories and files.
Can't find here bluetooth related config.
--
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/1801642
Title:
Bluetooth mouse sleeps after 5 seco
Does kernel parameter `btusb.enable_autosuspend=0` help?
--
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/1801642
Title:
Bluetooth mouse sleeps after 5 seconds of inactivity
Status in lin
Additional info:
sudo service bluetooth status:
.
.
.
Aug 09 11:05:47 boaz-desktop systemd[1]: Started Bluetooth service.
Aug 09 11:05:47 boaz-desktop bluetoothd[944]: Starting SDP server
Aug 09 11:05:47 boaz-desktop bluetoothd[944]: Bluetooth management interface
1.14 initia
Aug 09 11:05:51 boaz-
** Changed in: kernel-sru-workflow/promote-to-proposed
Status: Confirmed => In Progress
** Changed in: kernel-sru-workflow/promote-to-proposed
Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Łukasz
Zemczak (sil2100)
--
You received this bug notification because you are
** 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 1839286 (trusty/li
** Changed in: kernel-sru-workflow/promote-to-proposed
Status: In Progress => Confirmed
** Changed in: kernel-sru-workflow/promote-to-proposed
Assignee: Łukasz Zemczak (sil2100) => Ubuntu Stable Release Updates Team
(ubuntu-sru)
--
You received this bug notification because you are
** Changed in: kernel-sru-workflow/promote-signing-to-proposed
Assignee: (unassigned) => Andy Whitcroft (apw)
** Changed in: kernel-sru-workflow/promote-signing-to-proposed
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Kernel
Packa
** 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 1839286 (trusty/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 --
boot-testi
** Changed in: kernel-sru-workflow/promote-to-proposed
Status: Confirmed => In Progress
** Changed in: kernel-sru-workflow/promote-to-proposed
Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Andy
Whitcroft (apw)
--
You received this bug notification because you are a me
btusb.enable_autosuspend=0 is a magic! Yay!!!
Later I will try to permanent set it.
P.S. Still wondering why Kernel (or linux-firmware?) upgrade bring this
issue?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://b
** 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
I was incorrect, it's actually a racy read on /proc/bus/pci/:00/00.0
that's causing a hang:
sudo cat /proc/bus/pci/\:00/00.0
..takes a few seconds.. with stress-ng we have a multi-threaded
open/read/close on this file with random read sizes, this seems to cause
the machine to hang and reb
** Also affects: linux-aws (Ubuntu Disco)
Importance: Undecided
Status: New
** Also affects: ubuntu-kernel-tests
Importance: Undecided
Status: New
** Tags added: sru-20190722 ubuntu-stress-smoke-test
--
You received this bug notification because you are a member of Kernel
Pa
Thanks Mauricio, I've sponsored this package, and sent the kernel
related changes to the kernel-team mailing list:
https://lists.ubuntu.com/archives/kernel-team/2019-August/102938.html
I also sanity checked the code with the ubuntu kernel team ZFS
regression tests and they all pass successfully.
** Changed in: linux-aws (Ubuntu)
Assignee: (unassigned) => Colin Ian King (colin-king)
** Changed in: linux-aws (Ubuntu)
Importance: Undecided => Medium
** Changed in: linux-aws (Ubuntu)
Status: New => In Progress
--
You received this bug notification because you are a member of
dptfxtract 1.4.2-0ubuntu1 uploaded to my PPA for review.
Colin, could you help sponsor this upload?
** Changed in: dptfxtract (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to thermald in Ubuntu.
htt
dptfxtract 1.4.2-0ubuntu1 uploaded to
https://launchpad.net/~anthonywong/+archive/ubuntu/for-review/+packages for
review.
Colin, could you help sponsor this upload?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to thermald in Ubuntu.
http
Sorry, I don't have per-package upload rights to dptfxtract, you need to
ask a MOTU.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to thermald in Ubuntu.
https://bugs.launchpad.net/bugs/1838590
Title:
Update thermald to 1.9 release
Stat
This bug was fixed in the package linux - 5.2.0-10.11
---
linux (5.2.0-10.11) eoan; urgency=medium
* eoan/linux: 5.2.0-10.11 -proposed tracker (LP: #1838113)
* Packaging resync (LP: #1786013)
- [Packaging] resync git-ubuntu-log
* Eoan update: v5.2.4 upstream stable release
This bug was fixed in the package linux - 5.2.0-10.11
---
linux (5.2.0-10.11) eoan; urgency=medium
* eoan/linux: 5.2.0-10.11 -proposed tracker (LP: #1838113)
* Packaging resync (LP: #1786013)
- [Packaging] resync git-ubuntu-log
* Eoan update: v5.2.4 upstream stable release
This bug was fixed in the package linux - 5.2.0-10.11
---
linux (5.2.0-10.11) eoan; urgency=medium
* eoan/linux: 5.2.0-10.11 -proposed tracker (LP: #1838113)
* Packaging resync (LP: #1786013)
- [Packaging] resync git-ubuntu-log
* Eoan update: v5.2.4 upstream stable release
This bug was fixed in the package linux - 5.2.0-10.11
---
linux (5.2.0-10.11) eoan; urgency=medium
* eoan/linux: 5.2.0-10.11 -proposed tracker (LP: #1838113)
* Packaging resync (LP: #1786013)
- [Packaging] resync git-ubuntu-log
* Eoan update: v5.2.4 upstream stable release
This bug was fixed in the package linux - 5.2.0-10.11
---
linux (5.2.0-10.11) eoan; urgency=medium
* eoan/linux: 5.2.0-10.11 -proposed tracker (LP: #1838113)
* Packaging resync (LP: #1786013)
- [Packaging] resync git-ubuntu-log
* Eoan update: v5.2.4 upstream stable release
This bug was fixed in the package linux - 5.2.0-10.11
---
linux (5.2.0-10.11) eoan; urgency=medium
* eoan/linux: 5.2.0-10.11 -proposed tracker (LP: #1838113)
* Packaging resync (LP: #1786013)
- [Packaging] resync git-ubuntu-log
* Eoan update: v5.2.4 upstream stable release
This bug was fixed in the package linux - 5.2.0-10.11
---
linux (5.2.0-10.11) eoan; urgency=medium
* eoan/linux: 5.2.0-10.11 -proposed tracker (LP: #1838113)
* Packaging resync (LP: #1786013)
- [Packaging] resync git-ubuntu-log
* Eoan update: v5.2.4 upstream stable release
This bug was fixed in the package linux - 5.2.0-10.11
---
linux (5.2.0-10.11) eoan; urgency=medium
* eoan/linux: 5.2.0-10.11 -proposed tracker (LP: #1838113)
* Packaging resync (LP: #1786013)
- [Packaging] resync git-ubuntu-log
* Eoan update: v5.2.4 upstream stable release
This bug was fixed in the package linux - 5.2.0-10.11
---
linux (5.2.0-10.11) eoan; urgency=medium
* eoan/linux: 5.2.0-10.11 -proposed tracker (LP: #1838113)
* Packaging resync (LP: #1786013)
- [Packaging] resync git-ubuntu-log
* Eoan update: v5.2.4 upstream stable release
This bug was fixed in the package linux - 5.2.0-10.11
---
linux (5.2.0-10.11) eoan; urgency=medium
* eoan/linux: 5.2.0-10.11 -proposed tracker (LP: #1838113)
* Packaging resync (LP: #1786013)
- [Packaging] resync git-ubuntu-log
* Eoan update: v5.2.4 upstream stable release
This bug was fixed in the package linux - 5.2.0-10.11
---
linux (5.2.0-10.11) eoan; urgency=medium
* eoan/linux: 5.2.0-10.11 -proposed tracker (LP: #1838113)
* Packaging resync (LP: #1786013)
- [Packaging] resync git-ubuntu-log
* Eoan update: v5.2.4 upstream stable release
This bug was fixed in the package linux - 5.2.0-10.11
---
linux (5.2.0-10.11) eoan; urgency=medium
* eoan/linux: 5.2.0-10.11 -proposed tracker (LP: #1838113)
* Packaging resync (LP: #1786013)
- [Packaging] resync git-ubuntu-log
* Eoan update: v5.2.4 upstream stable release
This bug was fixed in the package linux - 5.2.0-10.11
---
linux (5.2.0-10.11) eoan; urgency=medium
* eoan/linux: 5.2.0-10.11 -proposed tracker (LP: #1838113)
* Packaging resync (LP: #1786013)
- [Packaging] resync git-ubuntu-log
* Eoan update: v5.2.4 upstream stable release
This bug was fixed in the package linux - 5.2.0-10.11
---
linux (5.2.0-10.11) eoan; urgency=medium
* eoan/linux: 5.2.0-10.11 -proposed tracker (LP: #1838113)
* Packaging resync (LP: #1786013)
- [Packaging] resync git-ubuntu-log
* Eoan update: v5.2.4 upstream stable release
This bug was fixed in the package linux - 5.2.0-10.11
---
linux (5.2.0-10.11) eoan; urgency=medium
* eoan/linux: 5.2.0-10.11 -proposed tracker (LP: #1838113)
* Packaging resync (LP: #1786013)
- [Packaging] resync git-ubuntu-log
* Eoan update: v5.2.4 upstream stable release
This bug was fixed in the package linux - 5.2.0-10.11
---
linux (5.2.0-10.11) eoan; urgency=medium
* eoan/linux: 5.2.0-10.11 -proposed tracker (LP: #1838113)
* Packaging resync (LP: #1786013)
- [Packaging] resync git-ubuntu-log
* Eoan update: v5.2.4 upstream stable release
This bug was fixed in the package linux - 5.2.0-10.11
---
linux (5.2.0-10.11) eoan; urgency=medium
* eoan/linux: 5.2.0-10.11 -proposed tracker (LP: #1838113)
* Packaging resync (LP: #1786013)
- [Packaging] resync git-ubuntu-log
* Eoan update: v5.2.4 upstream stable release
This bug was fixed in the package linux - 5.2.0-10.11
---
linux (5.2.0-10.11) eoan; urgency=medium
* eoan/linux: 5.2.0-10.11 -proposed tracker (LP: #1838113)
* Packaging resync (LP: #1786013)
- [Packaging] resync git-ubuntu-log
* Eoan update: v5.2.4 upstream stable release
This bug was fixed in the package linux - 5.2.0-10.11
---
linux (5.2.0-10.11) eoan; urgency=medium
* eoan/linux: 5.2.0-10.11 -proposed tracker (LP: #1838113)
* Packaging resync (LP: #1786013)
- [Packaging] resync git-ubuntu-log
* Eoan update: v5.2.4 upstream stable release
This bug was fixed in the package linux - 5.2.0-10.11
---
linux (5.2.0-10.11) eoan; urgency=medium
* eoan/linux: 5.2.0-10.11 -proposed tracker (LP: #1838113)
* Packaging resync (LP: #1786013)
- [Packaging] resync git-ubuntu-log
* Eoan update: v5.2.4 upstream stable release
This bug was fixed in the package linux - 5.2.0-10.11
---
linux (5.2.0-10.11) eoan; urgency=medium
* eoan/linux: 5.2.0-10.11 -proposed tracker (LP: #1838113)
* Packaging resync (LP: #1786013)
- [Packaging] resync git-ubuntu-log
* Eoan update: v5.2.4 upstream stable release
This bug was fixed in the package linux - 5.2.0-10.11
---
linux (5.2.0-10.11) eoan; urgency=medium
* eoan/linux: 5.2.0-10.11 -proposed tracker (LP: #1838113)
* Packaging resync (LP: #1786013)
- [Packaging] resync git-ubuntu-log
* Eoan update: v5.2.4 upstream stable release
This bug was fixed in the package linux - 5.2.0-10.11
---
linux (5.2.0-10.11) eoan; urgency=medium
* eoan/linux: 5.2.0-10.11 -proposed tracker (LP: #1838113)
* Packaging resync (LP: #1786013)
- [Packaging] resync git-ubuntu-log
* Eoan update: v5.2.4 upstream stable release
This bug was fixed in the package linux - 5.2.0-10.11
---
linux (5.2.0-10.11) eoan; urgency=medium
* eoan/linux: 5.2.0-10.11 -proposed tracker (LP: #1838113)
* Packaging resync (LP: #1786013)
- [Packaging] resync git-ubuntu-log
* Eoan update: v5.2.4 upstream stable release
This bug was fixed in the package linux - 5.2.0-10.11
---
linux (5.2.0-10.11) eoan; urgency=medium
* eoan/linux: 5.2.0-10.11 -proposed tracker (LP: #1838113)
* Packaging resync (LP: #1786013)
- [Packaging] resync git-ubuntu-log
* Eoan update: v5.2.4 upstream stable release
This bug was fixed in the package linux - 5.2.0-10.11
---
linux (5.2.0-10.11) eoan; urgency=medium
* eoan/linux: 5.2.0-10.11 -proposed tracker (LP: #1838113)
* Packaging resync (LP: #1786013)
- [Packaging] resync git-ubuntu-log
* Eoan update: v5.2.4 upstream stable release
** 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
Reviewing the package in your PPA I do have a few comments that should
be addressed.
1) It looks like the standards version has been downgraded. If being modified
at all it should be bumped up to match standards version in Eoan. This should
also be mentioned in debian/changelog
2) VCS-Git and
** Changed in: ubuntu-z-systems
Status: In Progress => Fix Committed
--
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/1836860
Title:
[18.04 FEAT] Enhanced CPU-MF hardware counters -
** Changed in: linux (Ubuntu Eoan)
Status: Confirmed => Fix Committed
--
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/1784665
Title:
bcache: bch_allocator_thread(): hung task timeo
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
Kernel deb testing completes, no regressions found. Ready for Updates.
Results here: https://trello.com/c/46BHK5zc/128-disco-linux-
image-500-25-generic-500-2526
** Changed in: kernel-sru-workflow/certification-testing
Status: Confirmed => Fix Released
--
You received this bug notificatio
Colin, thanks for sponsoring and additional testing!
Is this ZFS regression test suite available to other people?
It sounds great for future work with ZFS.
--
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 1839099 (bionic/li
Affects me too on a T480 running Manjaro
** Also affects: thermald (Arch Linux)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to thermald in Ubuntu.
https://bugs.launchpad.net/bugs/1815214
Title
Public bug reported:
s390x support secureboot via secure IPL mechanism.
When booted with Secure IPL, lock-down should be enabled.
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which
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
backports: bug 1839623 (bionic/linux-hwe-edge)
--
** 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 1839623 (bionic/li
** 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
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 1839622
and then change the status of the bug to 'Confirmed'.
If, due to the nature
** Tags added: bot-stop-nagging
** Changed in: linux (Ubuntu)
Status: Incomplete => 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/1839622
Title:
enable lockdown on s390x
Sorry, I didn't notice that this bug had expired, or that it was waiting
on log files. I don't have the system that I originally reproduced the
issue on set up any more, but it should be easily reproducible.
I'll set up another system to reproduce and generate the requested log
files, but in the m
** 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
** 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
** Changed in: kernel-sru-workflow/promote-to-proposed
Status: Confirmed => In Progress
** Changed in: kernel-sru-workflow/promote-to-proposed
Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Andy
Whitcroft (apw)
--
You received this bug notification because you are a me
** 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 1839286 (trusty/li
Hi Guilherme,
Apologies if I missed it, but could you elaborate on the issues you're
experiencing with the Disco kernel that are preventing you from
verifying this fix? I saw in an earlier comment you were waiting for
5.0.0-24 but that kernel should be available in -updates now.
Thanks,
Connor
** Changed in: kernel-sru-workflow
Status: In Progress => Invalid
** Changed in: kernel-sru-workflow/automated-testing
Status: New => Invalid
** Changed in: kernel-sru-workflow/prepare-package
Status: In Progress => Invalid
** Changed in: kernel-sru-workflow/prepare-package-
Setting automated-testing manually to 'Fix Released'.
Tests completed successfully:
https://people.canonical.com/~kernel/status/adt-matrix/bionic-linux-meta.html
Due to an issue with the network-manager package, the status won't be
set automatically by the bot.
** Changed in: kernel-sru-workflow
** 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 => 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
** 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 1839287 (xenial/li
** 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
** 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
Oops, I think I took the bionic source package and updated from there...
You're right we have a git tree and it should be used, I will post the
correct version later.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to thermald in Ubuntu.
http
Hi Paweł,
I saw you were able to confirm the test kernel from comment #3 worked.
The kernel that's in the -proposed repository should also contain this
fix. If possible, could I trouble you to enable the -proposed repository
[1] and install the new kernel to confirm that the fix is working as
expe
** 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
** Changed in: kernel-sru-workflow/promote-to-proposed
Status: In Progress => 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 workflo
Hi Wojciech,
I know it's been some time since this bug has been active, but I'm a bit
concerned about your comment #42. It sounds like the fix that was made
to allow you to adjust the volume away from 100% did not end up working,
in fact, it sounds like it disabled the sound altogether (at least o
** Also affects: linux (Ubuntu Eoan)
Importance: Medium
Status: 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/1215411
Title:
libcpupower.so is not installed from l
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
backports: bug 1839645 (bionic/linux-hwe-edge)
--
*** This bug is a duplicate of bug 1839646 ***
https://bugs.launchpad.net/bugs/1839646
** 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:
Hi Giovanni,
Regarding your question in comment #36: yes, please change the tag to
'verification-done-disco' if you've confirmed the issue is resolved on
your 5.0 Disco kernel. If it doesn't resolve the issue, go ahead and
change it to 'verification-failed-disco'
Thanks,
Connor
--
You received
** 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 1839645 (bionic/li
** Changed in: kernel-sru-workflow/promote-signing-to-proposed
Status: In Progress => 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
** Changed in: kernel-sru-workflow/promote-to-proposed
Status: In Progress => 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 workflo
Hi Hui,
If you still have access to a Dell computer that's affected by this,
could you please verify that the kernel(s) in -proposed fix this issue?
Thanks,
Connor
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem in Ubuntu.
htt
Hi Damir (or anyone else affected by this that may be reading the bug),
If you get a chance, could you please test the kernel that is in
-proposed to verify that it resolves the issue for you? There are
instructions in comment #12 for verifying this for Bionic or if you're
using Xenial, the instru
** Changed in: kernel-sru-workflow/automated-testing
Status: New => Confirmed
** Changed in: kernel-sru-workflow/promote-signing-to-proposed
Status: Fix Committed => Fix Released
** Changed in: kernel-sru-workflow/regression-testing
Status: New => Confirmed
** Changed in: ke
** Changed in: kernel-sru-workflow/security-signoff
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-raspi2 in Ubuntu.
https://bugs.launchpad.net/bugs/1839258
Title:
bionic/linux-raspi2: 4
1 - 100 of 141 matches
Mail list logo
