** Changed in: linux-oem-5.13 (Ubuntu Focal)
Status: New => Fix Committed
** Changed in: linux-oem-5.14 (Ubuntu Focal)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.14 in Ubuntu.
ht
** Changed in: linux-oem-5.13 (Ubuntu Focal)
Status: Confirmed => Fix Committed
** Changed in: linux-oem-5.14 (Ubuntu Focal)
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** Changed in: linux-oem-5.13 (Ubuntu Focal)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.13 in Ubuntu.
https://bugs.launchpad.net/bugs/1942043
Title:
Noise will pop up during W
** Changed in: linux-oem-5.13 (Ubuntu Focal)
Status: In Progress => Fix Committed
** Changed in: linux-oem-5.13 (Ubuntu)
Status: In Progress => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.10 in Ubuntu
** Changed in: linux-oem-5.13 (Ubuntu Focal)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.13 in Ubuntu.
https://bugs.launchpad.net/bugs/1941829
Title:
ubunut_kernel_selftests: m
The verification of the Stable Release Update for wireless-regdb has
completed successfully and the package is now being 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 enco
This bug was fixed in the package wireless-regdb -
2021.08.28-0ubuntu1~21.04.1
---
wireless-regdb (2021.08.28-0ubuntu1~21.04.1) hirsute; urgency=medium
* Backport to hirsute (LP: #1941955)
-- Seth Forshee Sun, 29 Aug 2021 14:00:29 -0500
** Changed in: wireless-regdb (Ubuntu Hir
This bug was fixed in the package wireless-regdb -
2021.08.28-0ubuntu1~18.04.1
---
wireless-regdb (2021.08.28-0ubuntu1~18.04.1) bionic; urgency=medium
* Backport to bionic (LP: #1941955)
-- Seth Forshee Sun, 29 Aug 2021 14:56:08 -0500
--
You received this bug notification beca
This bug was fixed in the package wireless-regdb -
2021.08.28-0ubuntu1~20.04.1
---
wireless-regdb (2021.08.28-0ubuntu1~20.04.1) focal; urgency=medium
* Backport to focal (LP: #1941955)
-- Seth Forshee Sun, 29 Aug 2021 14:49:57 -0500
** Changed in: wireless-regdb (Ubuntu Bionic)
Public bug reported:
I'm trying to install Ubuntu 20.04.3 on a brand new Dell 7520, which is
equipped with:
* 11th Gen Intel® Core™ i7-1185G7 @ 3.00GHz × 8
* Intel Iris XE GPU (reported as Mesa Intel® Xe Graphics (TGL GT2))
Since on my first try I was getting a lot of SEGFAULTS, I repeated th
This bug was fixed in the package linux-oem-5.13 - 5.13.0-1012.16
---
linux-oem-5.13 (5.13.0-1012.16) focal; urgency=medium
* focal/linux-oem-5.13: 5.13.0-1012.16 -proposed tracker (LP:
#1942861)
* Fix sluggish r8169 by disaling ASPM L1.2 (LP: #1942830)
- SAUCE: r8169: Disabl
This bug was fixed in the package linux-oem-5.13 - 5.13.0-1012.16
---
linux-oem-5.13 (5.13.0-1012.16) focal; urgency=medium
* focal/linux-oem-5.13: 5.13.0-1012.16 -proposed tracker (LP:
#1942861)
* Fix sluggish r8169 by disaling ASPM L1.2 (LP: #1942830)
- SAUCE: r8169: Disabl
This bug was fixed in the package linux-oem-5.13 - 5.13.0-1012.16
---
linux-oem-5.13 (5.13.0-1012.16) focal; urgency=medium
* focal/linux-oem-5.13: 5.13.0-1012.16 -proposed tracker (LP:
#1942861)
* Fix sluggish r8169 by disaling ASPM L1.2 (LP: #1942830)
- SAUCE: r8169: Disabl
This bug was fixed in the package linux-oem-5.13 - 5.13.0-1012.16
---
linux-oem-5.13 (5.13.0-1012.16) focal; urgency=medium
* focal/linux-oem-5.13: 5.13.0-1012.16 -proposed tracker (LP:
#1942861)
* Fix sluggish r8169 by disaling ASPM L1.2 (LP: #1942830)
- SAUCE: r8169: Disabl
This bug was fixed in the package linux-oem-5.13 - 5.13.0-1012.16
---
linux-oem-5.13 (5.13.0-1012.16) focal; urgency=medium
* focal/linux-oem-5.13: 5.13.0-1012.16 -proposed tracker (LP:
#1942861)
* Fix sluggish r8169 by disaling ASPM L1.2 (LP: #1942830)
- SAUCE: r8169: Disabl
This bug was fixed in the package linux-oem-5.13 - 5.13.0-1012.16
---
linux-oem-5.13 (5.13.0-1012.16) focal; urgency=medium
* focal/linux-oem-5.13: 5.13.0-1012.16 -proposed tracker (LP:
#1942861)
* Fix sluggish r8169 by disaling ASPM L1.2 (LP: #1942830)
- SAUCE: r8169: Disabl
This bug was fixed in the package linux-oem-5.13 - 5.13.0-1012.16
---
linux-oem-5.13 (5.13.0-1012.16) focal; urgency=medium
* focal/linux-oem-5.13: 5.13.0-1012.16 -proposed tracker (LP:
#1942861)
* Fix sluggish r8169 by disaling ASPM L1.2 (LP: #1942830)
- SAUCE: r8169: Disabl
This bug was fixed in the package linux-oem-5.13 - 5.13.0-1012.16
---
linux-oem-5.13 (5.13.0-1012.16) focal; urgency=medium
* focal/linux-oem-5.13: 5.13.0-1012.16 -proposed tracker (LP:
#1942861)
* Fix sluggish r8169 by disaling ASPM L1.2 (LP: #1942830)
- SAUCE: r8169: Disabl
@kaihengfeng
Sorry for delay reply. Yes mine laptop is based on AMD Ryzen 5 3500U with
integrated Vega 8. (HP Laptop 15s-eq0035nw)
--
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/1912935
T
This bug was fixed in the package linux-oem-5.13 - 5.13.0-1012.16
---
linux-oem-5.13 (5.13.0-1012.16) focal; urgency=medium
* focal/linux-oem-5.13: 5.13.0-1012.16 -proposed tracker (LP:
#1942861)
* Fix sluggish r8169 by disaling ASPM L1.2 (LP: #1942830)
- SAUCE: r8169: Disabl
This bug was fixed in the package linux-oem-5.13 - 5.13.0-1012.16
---
linux-oem-5.13 (5.13.0-1012.16) focal; urgency=medium
* focal/linux-oem-5.13: 5.13.0-1012.16 -proposed tracker (LP:
#1942861)
* Fix sluggish r8169 by disaling ASPM L1.2 (LP: #1942830)
- SAUCE: r8169: Disabl
This bug was fixed in the package linux-oem-5.13 - 5.13.0-1012.16
---
linux-oem-5.13 (5.13.0-1012.16) focal; urgency=medium
* focal/linux-oem-5.13: 5.13.0-1012.16 -proposed tracker (LP:
#1942861)
* Fix sluggish r8169 by disaling ASPM L1.2 (LP: #1942830)
- SAUCE: r8169: Disabl
This bug was fixed in the package linux-oem-5.13 - 5.13.0-1012.16
---
linux-oem-5.13 (5.13.0-1012.16) focal; urgency=medium
* focal/linux-oem-5.13: 5.13.0-1012.16 -proposed tracker (LP:
#1942861)
* Fix sluggish r8169 by disaling ASPM L1.2 (LP: #1942830)
- SAUCE: r8169: Disabl
This bug was fixed in the package linux-oem-5.13 - 5.13.0-1012.16
---
linux-oem-5.13 (5.13.0-1012.16) focal; urgency=medium
* focal/linux-oem-5.13: 5.13.0-1012.16 -proposed tracker (LP:
#1942861)
* Fix sluggish r8169 by disaling ASPM L1.2 (LP: #1942830)
- SAUCE: r8169: Disabl
This bug was fixed in the package linux-oem-5.13 - 5.13.0-1012.16
---
linux-oem-5.13 (5.13.0-1012.16) focal; urgency=medium
* focal/linux-oem-5.13: 5.13.0-1012.16 -proposed tracker (LP:
#1942861)
* Fix sluggish r8169 by disaling ASPM L1.2 (LP: #1942830)
- SAUCE: r8169: Disabl
This bug was fixed in the package linux-oem-5.13 - 5.13.0-1012.16
---
linux-oem-5.13 (5.13.0-1012.16) focal; urgency=medium
* focal/linux-oem-5.13: 5.13.0-1012.16 -proposed tracker (LP:
#1942861)
* Fix sluggish r8169 by disaling ASPM L1.2 (LP: #1942830)
- SAUCE: r8169: Disabl
Public bug reported:
Ubuntu 5.4.0-84.94-generic 5.4.133
Description:Ubuntu 20.04.3 LTS
Release:20.04
xinput -list
⎡ Virtual core pointer id=2[master pointer (3)]
⎜ ↳ Virtual core XTEST pointerid=4[slave pointer (2)]
⎜ ↳ Logitech
This change was made by a bot.
** Changed in: linux (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1943425
Title:
Touchpad is not working and de
Hi Chris,
Apologises emailed my update rather than posting it via the webui. Yes
it that version worked.
Regards,
James
--
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/1938697
Title:
Public bug reported:
Was using the computer quickly to join a zoom call like normal. Didn't
install anything or modify any files. Shut off the computer only to
start it up again and have the touchpad not working. Using Thinkpad
T470S. Worth mentioning that the trackpoint (red button on keyboard) h
** Changed in: linux-oem-5.13 (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.13 in Ubuntu.
https://bugs.launchpad.net/bugs/1943421
Title:
Error while enabling somerville driver: packag
** Changed in: linux-oem-5.14 (Ubuntu Focal)
Status: New => Fix Committed
** Changed in: linux-oem-5.13 (Ubuntu Focal)
Status: New => Fix Committed
** Changed in: linux-oem-5.13 (Ubuntu)
Status: New => Invalid
** Changed in: linux-oem-5.14 (Ubuntu)
Status: New => Inva
Feel free to bisect, i'm checking our SAUCE patches/configs.
BTW:
Firmware Version: 2017-10-12 12:34:31
it's the last FW version available, isn't it? I'm wondering about the
device tree.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to l
** Also affects: nvidia-settings (Ubuntu Focal)
Importance: Undecided
Status: New
** Changed in: nvidia-settings (Ubuntu Focal)
Status: New => In Progress
** Changed in: nvidia-settings (Ubuntu Focal)
Importance: Undecided => Medium
** Changed in: nvidia-settings (Ubuntu)
Validated by Microsoft on test kernels. Tagging as verification done.
** Tags removed: verification-needed-hirsute
** Tags added: verification-done-hirsute
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https://bug
@tuxinvader
While trying to install Kernel 5.14.3 (Sep 12, 2021) on Ubuntu MATE
21.04, I ran into similar issue but for libc6 2.34.
Error:
dpkg: dependency problems prevent configuration of linux-
headers-5.14.3-051403-generic: linux-headers-5.14.3-051403-generic
depends on libc6 (>= 2.34); howe
I think I've seen this issue once per two different systems so I think
this is software issue. Does anybody know if patch in comment #6 is
going to be included in Ubuntu 20.04 LTS?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-sign
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: linux-signed-hwe-5.11 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed-hwe-5.11 in Ubuntu.
https://b
One of the systems was using package linux-generic and in practice
Linux pedabackup 5.4.0-80-generic #90-Ubuntu SMP Fri Jul 9 22:49:44 UTC
2021 x86_64 x86_64 x86_64 GNU/Linux
$ cat /proc/version_signature
Ubuntu 5.4.0-80.90-generic 5.4.124
--
You received this bug notification because you are
Hi @jagsdesai
I think you're using the package from mainline. I publish a PPA for
20.04 LTS, and version 5.14.3 has just finished building on launchpad
this morning, so any package you installed yesterday was nothing to do
with me ;-)
Here's my dependencies
$ dpkg -I
linux-headers-5.14.3-05
You have been subscribed to a public bug:
After installing kernel package linux-image-
unsigned-5.14.2-051402-lowlatency from
https://kernel.ubuntu.com/~kernel-ppa/mainline/ starting libvirtd, and
thus qemu, results in 2 stack traces. Then libvirtd stops.
Rolling back to 5.11.0-34-lowlatency fixe
*** This bug is a duplicate of bug 1872159 ***
https://bugs.launchpad.net/bugs/1872159
Lenovo Legion 5 15IMH05
$ uname -rv
5.11.0-34-generic #36~20.04.1-Ubuntu SMP Fri Aug 27 08:06:32 UTC 2021
NVIDIA Driver Version: 470.63.01
Had the same issue for some time, until I've "fixed it" recently.
** Package changed: ubuntu => linux (Ubuntu)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1943287
Title:
Can't start qemu on linux-5.14.2-051402-lowlatency
Status in linux package in
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 1943287
and then change the status of the bug to 'Confirmed'.
If, due to the nature
You have been subscribed to a public bug:
After reassign RoCE CX5 Mojawe Card Pchid to another LPAR dmesg show
under Ubuntu the following Error message
Ubuntu 20.04.01 with updates
oot@t35lp02:~# uname -a
Linux t35lp02.lnxne.boe 5.4.0-80-generic #90-Ubuntu SMP Fri Jul 9 17:41:33 UTC
2021 s390x
Public bug reported:
After reassign RoCE CX5 Mojawe Card Pchid to another LPAR dmesg show
under Ubuntu the following Error message
Ubuntu 20.04.01 with updates
oot@t35lp02:~# uname -a
Linux t35lp02.lnxne.boe 5.4.0-80-generic #90-Ubuntu SMP Fri Jul 9 17:41:33 UTC
2021 s390x s390x s390x GNU/Linux
@jagsdesai
both #81 #57 still work with 5.14.3, installed yesterday on Xubuntu 20.04 ;-)
--
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/1926938
Title:
Recent mainline packages are built
Closing, as I discovered that the root cause was interference from my
antivirus (Sophos).
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.13 in Ubuntu.
https://bugs.launchpad.net/bugs/1943421
Title:
Error while enabling some
** Also affects: ubuntu-z-systems
Importance: Undecided
Status: New
** Changed in: ubuntu-z-systems
Assignee: (unassigned) => Skipper Bug Screeners (skipper-screen-team)
** Changed in: linux (Ubuntu)
Importance: Undecided => Low
** Changed in: ubuntu-z-systems
Importance: Un
For the CRB1S systems, the following is the firmware string that
matters, and it shows that phanpy is running the latest (and very likely
final) version:
BIOS Date: 06/14/2018 14:42:48 Ver: 0ACGA022
Note that this is also reproducible on our Gigabyte R120 systems which
use acpi=force by default,
The solution to this issue was documented in my #3 comment. The
misleading error messages coming from Linux were indicating that it was
time to fresh reformat the MP3 player and start over. Once done, no
issues.
This defect report may be close. Thank you.
--
You received this bug notification be
This bug was fixed in the package nvidia-settings - 470.57.01-0ubuntu2
---
nvidia-settings (470.57.01-0ubuntu2) impish; urgency=medium
* debian/patches/17_do_not_read_config_on_power_saving_mode.patch:
- Do not read config on Power Saving mode. (LP: #1943160).
-- Shengyao Xue
The patch hasn't made it into mainline from what I have seen, it looks
like it died back in March waiting for feedback from additional kernel
developers. From what I have gathered this is a deadlock scenario
directly caused by pausing the resync while the system is under heavy
write activity.
Don
I downgraded to 20.04 LTS and 5.8 kernel. So far, it seems more
reliable than the 5.11 kernel. The watchdog_thresh is default 10.
--
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/1942952
T
Sorry for the wait, I took a few days off.
This kernel worked well.
** Attachment added: "journalctl.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1940113/+attachment/5525012/+files/journalctl.log
--
You received this bug notification because you are a member of Kernel
Packages,
@tuxinvader @k3dar7 many thanks for the replies.
Yes, I installed packages from mainline. Sorry, I thought this bug
report is for mainline packages.
Now I did see your PPA through AskUbuntu thread but is it just for
"Focal" or from your PPA, I can install kernels in Hirsute too?
--
You received
** Summary changed:
- Reassign I/O Path of Mojave Port 1 before Port 2 causes NULL dereference
+ Reassign I/O Path of ConnectX-5 Port 1 before Port 2 causes NULL dereference
** Description changed:
- After reassign RoCE CX5 Mojawe Card Pchid to another LPAR dmesg show
+ After reassign RoCE Conne
** Summary changed:
- package shim-signed 1.47+15.4-0ubuntu2 failed to install/upgrade: installed
shim-signed package post-installation script subprocess returned error exit
status 1
+ package shim-signed 1.47+15.4-0ubuntu2 failed to install/upgrade: installed
shim-signed package post-installat
All autopkgtests for the newly accepted linux-meta-snapdragon (4.15.0.1113.116)
for bionic have finished running.
The following regressions have been reported in tests triggered by the package:
lxd/3.0.3-0ubuntu1~18.04.1 (arm64)
Please visit the excuses page listed below and investigate the fai
This is happening because the mainline kernels started getting built
with CONFIG_UBSAN=y.
Apparently, turning this on at build time inserts code at various points
that helps identify undefined behaviour, and even though the runtime
reporter is not on, the inserted code breaks the nvidia driver.
I
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
** Changed in: linux (Ubuntu Focal)
Status: New => In Progress
** Changed in: linux (Ubuntu Focal)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu Focal)
Assignee: (unassigned) => Kamal Mostafa (kamalmostafa)
** Description changed:
+ SRU Justification
- SRU J
Thanks for the feedback.
Closing as requested.
** Changed in: linux (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/1938645
Title:
Ubuntu 20
All autopkgtests for the newly accepted linux-meta-gkeop-5.4
(5.4.0.1024.25~18.04.25) for bionic have finished running.
The following regressions have been reported in tests triggered by the package:
lxc/3.0.3-0ubuntu1~18.04.1 (amd64)
kpatch/0.5.0-0ubuntu1.1 (amd64)
Please visit the excuses pag
Hi, Tim. I'm dropping the 5.4 backport from focal/linux-azure in the
current cycle because this commit is causing the boot to hang:
http://10.246.72.46:8080/view/all/job/focal-linux-azure-azure-
amd64-5.4.0-Standard_A2_v2-ubuntu_boot/4/console
I managed to reproduce the problem manually and rever
All autopkgtests for the newly accepted linux-meta-gke-5.4
(5.4.0.1053.56~18.04.18) for bionic have finished running.
The following regressions have been reported in tests triggered by the package:
kpatch/0.5.0-0ubuntu1.1 (amd64)
systemd/unknown (amd64)
lxc/3.0.3-0ubuntu1~18.04.1 (amd64)
Please
I recorded a video (using my phone) of what the computer looks like once the
crash has happened:
https://www.youtube.com/watch?v=36kg68mfrds
--
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/
It's gotten to the point where this happens at least once a day. I'm
lost for answers.
--
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/1939966
Title:
Random system stops
Status in linux
All autopkgtests for the newly accepted linux-meta-gke (5.4.0.1053.63) for
focal have finished running.
The following regressions have been reported in tests triggered by the package:
backport-iwlwifi-dkms/8324-0ubuntu3~20.04.4 (amd64)
Please visit the excuses page listed below and investigate
All autopkgtests for the newly accepted linux-meta-gcp-5.4 (5.4.0.1053.39) for
bionic have finished running.
The following regressions have been reported in tests triggered by the package:
systemd/237-3ubuntu10.51 (amd64)
Please visit the excuses page listed below and investigate the failures,
Here is Donald Buczek's reproducer script. I setup an Ubuntu 20.04 VM
with latest linux-image-generic and was able to reproduce it within
maybe 10 or 15 minutes. Exactly the same issue.
Filesystem layout built as follows:
# assemble raid devices
mdadm --create /dev/md0 --level=1 --raid-devices=
The system has now been running stably for 6 days, which is an order of
magnitude better than what I was experiencing since filing this bug
report.
I will at some point flip the firmware setting back to see how it
behaves. Are there any other tests I should try?
--
You received this bug notific
All autopkgtests for the newly accepted linux-meta-gkeop (5.4.0.1024.27) for
focal have finished running.
The following regressions have been reported in tests triggered by the package:
backport-iwlwifi-dkms/8324-0ubuntu3~20.04.4 (amd64)
Please visit the excuses page listed below and investigat
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed-hwe-5.11 in Ubuntu.
https://bugs.launchpad.net/bugs/1942935
Title:
kernel io hangs during mdcheck/r
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 1942935
and then change the status of the bug to 'Confirmed'.
If, due to the nature
I've run that debugging script. Unfortunately, Launchpad currently
OOPSes when I try to attach the output to the bug. I'll keep trying
every now and then.
The throttling did not occur during that test, and doesn't seem to have
occurred while running the build of thermald from git, but this does no
** Tags removed: hirsute
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed-hwe-5.11 in Ubuntu.
https://bugs.launchpad.net/bugs/1942935
Title:
kernel io hangs during mdcheck/resync
Status in linux package in Ubuntu:
Incompl
We should get some hints from the system log usually... Each time the
crash happens please:
1. Wait 10 seconds.
2. Reboot.
3. Run:
journalctl -b-1 > prevboot.txt
4. Attach the resulting text file here.
--
You received this bug notification because you are a member of Kernel
Packages, whic
You have been subscribed to a public bug:
computer "wakes up" from sleep mode after 1 second no matter if i wait
the given time for it to sleep, or if i put it to sleep with terminal.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.11.0-3
Thanks for the bug report. The first thing to try is to unplug your
peripherals (before sleeping) to see if it is any of them waking the
machine up.
** Package changed: xorg (Ubuntu) => linux-hwe-5.11 (Ubuntu)
** Changed in: linux-hwe-5.11 (Ubuntu)
Status: New => Incomplete
--
You receiv
** Changed in: pulseaudio (Ubuntu)
Status: New => In Progress
** Also affects: alsa-ucm-conf (Ubuntu)
Importance: Undecided
Status: New
** No longer affects: alsa-ucm-conf (Ubuntu)
** No longer affects: alsa-ucm-conf (Ubuntu Focal)
** No longer affects: alsa-ucm-conf (Ubuntu Hi
** No longer affects: alsa-ucm-conf (Ubuntu)
** Also affects: alsa-ucm-conf (Ubuntu)
Importance: Undecided
Status: New
** No longer affects: linux (Ubuntu)
** Package changed: alsa-ucm-conf (Ubuntu) => linux (Ubuntu)
--
You received this bug notification because you are a member of K
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 1930188
and then change the status of the bug to 'Confirmed'.
If, due to the nature
This is the debdiff of alsa-ucm-conf for impish.
thx.
** Changed in: linux (Ubuntu Impish)
Status: Incomplete => Fix Released
** Patch added: "alsa-ucm-conf_1.2.4-2ubuntu5.debdiff"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1930188/+attachment/5525076/+files/alsa-ucm-conf_1
This is the debdiff of alsa-ucm-conf for hirsute.
thx.
** Patch added: "alsa-ucm-conf_1.2.4-2ubuntu1.4.debdiff"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1930188/+attachment/5525077/+files/alsa-ucm-conf_1.2.4-2ubuntu1.4.debdiff
--
You received this bug notification because you a
This is the debdiff of alsa-ucm-conf for focal.
thx.
** Patch added: "alsa-ucm-conf_1.2.2-1ubuntu0.11.debdiff"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1930188/+attachment/5525078/+files/alsa-ucm-conf_1.2.2-1ubuntu0.11.debdiff
--
You received this bug notification because you a
** Description changed:
+ SRU Justification for alsa-ucm-conf:
+
+ [Impact]
+ On the machines with the sof audio driver, users could adjust the input
+ volume from UI, but this only adjusts the "Capture Volume", the "Mic
+ Boost" can't be changed, if "Mic Boost" is 0, even we adjust the "Capture
Hello, regarding the latest SRU Justification for alsa-ucm-conf
Isn't it normal to have separate microphone volume and mic boost.
Currently I have mic volume on 100% and mic boost on 20db gain. It's
just like windows where microphone volume and mic boost is separate. We
just don't have UI for it n
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: bcmwl (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bcmwl in Ubuntu.
https://bugs.launchpad.net/bugs/1940730
Patch request submitted:
https://lists.ubuntu.com/archives/kernel-team/2021-September/thread.html#124043
Updating status to 'In Progress'.
** Changed in: ubuntu-z-systems
Status: Triaged => In Progress
** Changed in: linux (Ubuntu)
Status: Triaged => In Progress
** Information type
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
focal' to 'verification-done-focal'. If the problem still exists, change
the tag 'verificati
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
focal' to 'verification-done-focal'. If the problem still exists, change
the tag 'verificati
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
focal' to 'verification-done-focal'. If the problem still exists, change
the tag 'verificati
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
focal' to 'verification-done-focal'. If the problem still exists, change
the tag 'verificati
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
focal' to 'verification-done-focal'. If the problem still exists, change
the tag 'verificati
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
focal' to 'verification-done-focal'. If the problem still exists, change
the tag 'verificati
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
focal' to 'verification-done-focal'. If the problem still exists, change
the tag 'verificati
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
focal' to 'verification-done-focal'. If the problem still exists, change
the tag 'verificati
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
focal' to 'verification-done-focal'. If the problem still exists, change
the tag 'verificati
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
focal' to 'verification-done-focal'. If the problem still exists, change
the tag 'verificati
1 - 100 of 112 matches
Mail list logo
