Bug 1924221 is private so I can't see it. But I'm confident we have the
right links now (unless you're experiencing multiple different crashes).
** Summary changed:
- bluetoothd segfaults when keyboard connects [SIGSEGV in get_report_cb() from
notify_handler() from notify_handler() from
** Changed in: bluez
Status: Unknown => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1924217
Title:
bluetoothd 5.56 segfaults when keyboard connects [SIGSEGV in
Judging by the newness of the problem, the crash address and the logs,
this looks like it's probably bug 1924220. But we will need you to
follow the instructions in comment #2 to confirm that.
** Bug watch added: github.com/bluez/bluez/issues #112
https://github.com/bluez/bluez/issues/112
--
I ran ubuntu-bug on the .crash file. The bug that created is here:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1924221
I also did a quick build of bluez 5.58 and can confirm it does not seem to
segfault when connecting my keyboard.
--
You received this bug notification because you are
Actually upstream bug report https://github.com/bluez/bluez/issues/112
confirms the symptoms.
** Summary changed:
- bluetoothd segfaults when Trackpoint II keyboard connects
+ bluetoothd segfaults when Trackpoint II keyboard connects [SIGSEGV in
get_report_cb() from notify_handler() from
*** This bug is a duplicate of bug 1924217 ***
https://bugs.launchpad.net/bugs/1924217
** Summary changed:
-
/usr/lib/bluetooth/bluetoothd:11:get_report_cb:notify_handler:notify_handler:queue_foreach:queue_foreach
+ bluetoothd crashed with SIGSEGV in get_report_cb() from notify_handler()
*** This bug is a duplicate of bug 1924217 ***
https://bugs.launchpad.net/bugs/1924217
Public bug reported:
The Ubuntu Error Tracker has been receiving reports about a problem regarding
bluez. This problem was most recently seen with package version 5.56-0ubuntu3,
the problem page at
Thank you for taking the time to report this bug and helping to make
Ubuntu better. It sounds like some part of the system has crashed. To
help us find the cause of the crash please follow these steps:
1. Look in /var/crash for crash files and if found run:
ubuntu-bug YOURFILE.crash
Then tell
Kernel 5.4.0-71 works for us with xen. Thank you very much!
** Changed in: linux (Ubuntu Focal)
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.
Public bug reported:
bluetoothd crashes when my Lenovo Trackpoint II keyboard connects. I see this
in dmesg:
[ 58.257605] input: TrackPoint Keyboard II Keyboard as
/devices/virtual/misc/uhid/0005:17EF:60E1.0005/input/input26
[ 58.258542] input: TrackPoint Keyboard II Mouse as
** Description changed:
SRU justification:
[Impact]
Realtek 8852A bluetooth can not work because of no support in 5.10- kernel.
[Fix]
Add realtek 8852 bluetooth ID in driver.
Chip firmware is in another SRU.
[Test]
Verified on hardware with bluetooth headset and file
** Changed in: linux (Ubuntu Hirsute)
Status: Incomplete => In Progress
** Changed in: linux (Ubuntu Groovy)
Status: New => In Progress
** Changed in: linux-oem-5.10 (Ubuntu Focal)
Status: New => In Progress
** Changed in: hwe-next
Assignee: (unassigned) => AaronMa
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 1924207
and then change the status of the bug to 'Confirmed'.
If, due to the
Public bug reported:
SRU justification:
[Impact]
Realtek 8852A bluetooth can not work because of no support in 5.10- kernel.
[Fix]
Add realtek 8852 bluetooth ID in driver.
Chip firmware is in another SRU.
[Test]
Verified on hardware with bluetooth headset and file transfer, all good.
[Where
https://kernel.ubuntu.com/git/ubuntu/autotest-client-
tests.git/commit/?id=7dea7776ce431e5a1c550dc73b1d9ac0ba49698d
** Changed in: ubuntu-kernel-tests
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is
Comment #1 is a different issue which either needs a new bug opened or
you might wish to use bug 1576559.
** Tags added: focal
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1923925
** Summary changed:
- l2tp.sh from net in ubuntu_kernel_selftests failed with test not executable
on F-OEM-5.6
+ l2tp.sh from net in ubuntu_kernel_selftests failed with test not executable
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
** Summary changed:
- [SRU][F/G] add realtek 8852 bluetooth fimware
+ [SRU][F/G][linux-firmware] add realtek 8852 bluetooth fimware
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
** Tags added: oem-priority originate-from-1923394 sutton
** Changed in: hwe-next
Assignee: (unassigned) => AaronMa (mapengyu)
** Description changed:
SRU justification:
[Impact]
Realtek 8852A bluetooth can not work without proper firmware.
[Fix]
Add realtek 8852 bluetooth
Public bug reported:
SRU justification:
[Impact]
Realtek 8852A bluetooth can not work without proper firmware.
[Fix]
Add realtek 8852 bluetooth fimware for driver.
Kernel driver will be in another SRU.
[Test]
Verified on hardware with bluetooth headset and file file transfer.
[Where problems
** Changed in: linux
Status: New => 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/1826125
Title:
Dell XPS 13 9380 flickering (Whiskey Lake)
Status in Linux:
Fix
Thanks Tim for building the test kernel, and Hmpf, thanks for testing it
and confirming it fixes the problem.
Okay, so the problem is:
commit a738c93fb1c17e386a09304b517b1c6b2a6a5a8b
Author: Shyam Prasad N
Date: Thu Feb 11 03:26:54 2021 -0800
Subject: cifs: Set CIFS_MOUNT_USE_PREFIX_PATH flag
** Package changed: ubuntu => linux (Ubuntu)
** Tags added: regression-update
--
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/1923844
Title:
i915 drm GPU hang - introduced with
Just recognized that only output is working, there is no mic device even
if I select HSP/HFP manually.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1923925
Title:
Bluetooth headset
You have been subscribed to a public bug:
This is a regression introduced with the latest kernel (linux-
image-5.8.0-49-generic).
Kubuntu 20.04, since upgrading kernel from version 5.8.0-48.54 to
version 5.8.0-49.55 the system boots properly but the GUI often hangs,
either immediately after user
Public bug reported:
A new bluetooth headset (Teufel Airy True Wireless) cannot be paired on
my dell precision 5530 having an intel ac 9260 bluetooth chipset using
ubuntu 20.04.
Using an ubuntu 18.04 (boot from usb) I was able to connect the headset
without any problem.
As a workaround I
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 1921355
and then change the status of the bug to 'Confirmed'.
If, due to the
** 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 in Ubuntu.
https://bugs.launchpad.net/bugs/1921355
Title:
cgroups related kernel panics
Status in linux
** Description changed:
+ SRU Justification
- 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
+
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-gcp (Ubuntu Bionic)
Status: New => Fix Committed
** Changed in: linux-gcp (Ubuntu Focal)
Status: New => Fix Committed
** Changed in: linux-gcp (Ubuntu Groovy)
Status: New => Fix Committed
** Changed in: linux-gke (Ubuntu Focal)
Status: New => Fix
I found a system running old firmware and I was able to reproduce this.
I updated the firmware, and the issue went away. Of course, it seems
like a regression that the kernel now *crashes* with the bad firmware
(see bug 1755304 for my reasoning for it being bad), when it used to
just emit errors.
To add more info on what I tried, I have put it here:
https://askubuntu.com/questions/1329928/legion-5-pro-brightness-control-
doesnt-work-on-ubuntu-20-04-with-nvidia-driver . Surprisingly the
brightness also works on Manjaro (as mentioned in my post) after adding
'Option "RegistryDwords"
Public bug reported:
A soft lockup is happening to Customers due to a bug in netvsc_poll.
Ubuntu 4.15.0-1103 has CONFIG_NET_POLL_CONTROLLER=y in kernel config
file, there is a bug in netvsc that may cause CPU lockup with
POLL_CONTROLLER. This bug has been fixed by the following patch:
commit
This bug was fixed in the package nvidia-graphics-drivers-450 -
450.102.04-0ubuntu0.18.04.2
---
nvidia-graphics-drivers-450 (450.102.04-0ubuntu0.18.04.2) bionic; urgency=medium
* debian/templates/control.in:
- Add missing conflict/replace/provide for libnvidia-common,
This bug was fixed in the package nvidia-graphics-drivers-460-server -
460.32.03-0ubuntu0.20.10.2
---
nvidia-graphics-drivers-460-server (460.32.03-0ubuntu0.20.10.2) groovy;
urgency=medium
* debian/templates/control.in:
- Add missing conflict/replace/provide for
This bug was fixed in the package nvidia-graphics-drivers-450-server -
450.102.04-0ubuntu0.20.10.2
---
nvidia-graphics-drivers-450-server (450.102.04-0ubuntu0.20.10.2) groovy;
urgency=medium
* debian/templates/control.in:
- Add missing conflict/replace/provide for
This bug was fixed in the package nvidia-graphics-drivers-450 -
450.102.04-0ubuntu0.20.10.2
---
nvidia-graphics-drivers-450 (450.102.04-0ubuntu0.20.10.2) groovy; urgency=medium
* debian/templates/control.in:
- Add missing conflict/replace/provide for libnvidia-common,
This bug was fixed in the package nvidia-graphics-drivers-418-server -
418.181.07-0ubuntu0.20.10.2
---
nvidia-graphics-drivers-418-server (418.181.07-0ubuntu0.20.10.2) groovy;
urgency=medium
* debian/templates/control.in:
- Add missing conflict/replace/provide for
This bug was fixed in the package nvidia-graphics-drivers-460-server -
460.32.03-0ubuntu0.20.04.2
---
nvidia-graphics-drivers-460-server (460.32.03-0ubuntu0.20.04.2) focal;
urgency=medium
* debian/templates/control.in:
- Add missing conflict/replace/provide for
This bug was fixed in the package nvidia-graphics-drivers-450-server -
450.102.04-0ubuntu0.20.04.2
---
nvidia-graphics-drivers-450-server (450.102.04-0ubuntu0.20.04.2) focal;
urgency=medium
* debian/templates/control.in:
- Add missing conflict/replace/provide for
This bug was fixed in the package nvidia-graphics-drivers-450 -
450.102.04-0ubuntu0.20.04.2
---
nvidia-graphics-drivers-450 (450.102.04-0ubuntu0.20.04.2) focal; urgency=medium
* debian/templates/control.in:
- Add missing conflict/replace/provide for libnvidia-common,
This bug was fixed in the package nvidia-graphics-drivers-418-server -
418.181.07-0ubuntu0.20.04.2
---
nvidia-graphics-drivers-418-server (418.181.07-0ubuntu0.20.04.2) focal;
urgency=medium
* debian/templates/control.in:
- Add missing conflict/replace/provide for
This bug was fixed in the package nvidia-graphics-drivers-460-server -
460.32.03-0ubuntu0.18.04.2
---
nvidia-graphics-drivers-460-server (460.32.03-0ubuntu0.18.04.2) bionic;
urgency=medium
* debian/templates/control.in:
- Add missing conflict/replace/provide for
This bug was fixed in the package nvidia-graphics-drivers-450-server -
450.102.04-0ubuntu0.18.04.2
---
nvidia-graphics-drivers-450-server (450.102.04-0ubuntu0.18.04.2) bionic;
urgency=medium
* debian/templates/control.in:
- Add missing conflict/replace/provide for
This bug was fixed in the package nvidia-graphics-drivers-418-server -
418.181.07-0ubuntu0.18.04.2
---
nvidia-graphics-drivers-418-server (418.181.07-0ubuntu0.18.04.2) bionic;
urgency=medium
* debian/templates/control.in:
- Add missing conflict/replace/provide for
This bug was fixed in the package nvidia-graphics-drivers-450 -
450.102.04-0ubuntu0.18.04.2
---
nvidia-graphics-drivers-450 (450.102.04-0ubuntu0.18.04.2) bionic; urgency=medium
* debian/templates/control.in:
- Add missing conflict/replace/provide for libnvidia-common,
This bug was fixed in the package nvidia-graphics-drivers-460-server -
460.32.03-0ubuntu0.20.10.2
---
nvidia-graphics-drivers-460-server (460.32.03-0ubuntu0.20.10.2) groovy;
urgency=medium
* debian/templates/control.in:
- Add missing conflict/replace/provide for
This bug was fixed in the package nvidia-graphics-drivers-450-server -
450.102.04-0ubuntu0.20.10.2
---
nvidia-graphics-drivers-450-server (450.102.04-0ubuntu0.20.10.2) groovy;
urgency=medium
* debian/templates/control.in:
- Add missing conflict/replace/provide for
This bug was fixed in the package nvidia-graphics-drivers-450 -
450.102.04-0ubuntu0.20.10.2
---
nvidia-graphics-drivers-450 (450.102.04-0ubuntu0.20.10.2) groovy; urgency=medium
* debian/templates/control.in:
- Add missing conflict/replace/provide for libnvidia-common,
This bug was fixed in the package nvidia-graphics-drivers-418-server -
418.181.07-0ubuntu0.20.10.2
---
nvidia-graphics-drivers-418-server (418.181.07-0ubuntu0.20.10.2) groovy;
urgency=medium
* debian/templates/control.in:
- Add missing conflict/replace/provide for
This bug was fixed in the package nvidia-graphics-drivers-390 -
390.141-0ubuntu0.20.10.2
---
nvidia-graphics-drivers-390 (390.141-0ubuntu0.20.10.2) groovy; urgency=medium
* debian/templates/control.in:
- Add conflicts/replace/provides for all the metapackages
(LP:
This bug was fixed in the package nvidia-graphics-drivers-460-server -
460.32.03-0ubuntu0.20.04.2
---
nvidia-graphics-drivers-460-server (460.32.03-0ubuntu0.20.04.2) focal;
urgency=medium
* debian/templates/control.in:
- Add missing conflict/replace/provide for
This bug was fixed in the package nvidia-graphics-drivers-450-server -
450.102.04-0ubuntu0.20.04.2
---
nvidia-graphics-drivers-450-server (450.102.04-0ubuntu0.20.04.2) focal;
urgency=medium
* debian/templates/control.in:
- Add missing conflict/replace/provide for
This bug was fixed in the package nvidia-graphics-drivers-450 -
450.102.04-0ubuntu0.20.04.2
---
nvidia-graphics-drivers-450 (450.102.04-0ubuntu0.20.04.2) focal; urgency=medium
* debian/templates/control.in:
- Add missing conflict/replace/provide for libnvidia-common,
This bug was fixed in the package nvidia-graphics-drivers-418-server -
418.181.07-0ubuntu0.20.04.2
---
nvidia-graphics-drivers-418-server (418.181.07-0ubuntu0.20.04.2) focal;
urgency=medium
* debian/templates/control.in:
- Add missing conflict/replace/provide for
This bug was fixed in the package nvidia-graphics-drivers-460-server -
460.32.03-0ubuntu0.18.04.2
---
nvidia-graphics-drivers-460-server (460.32.03-0ubuntu0.18.04.2) bionic;
urgency=medium
* debian/templates/control.in:
- Add missing conflict/replace/provide for
This bug was fixed in the package nvidia-graphics-drivers-450-server -
450.102.04-0ubuntu0.18.04.2
---
nvidia-graphics-drivers-450-server (450.102.04-0ubuntu0.18.04.2) bionic;
urgency=medium
* debian/templates/control.in:
- Add missing conflict/replace/provide for
This bug was fixed in the package nvidia-graphics-drivers-418-server -
418.181.07-0ubuntu0.18.04.2
---
nvidia-graphics-drivers-418-server (418.181.07-0ubuntu0.18.04.2) bionic;
urgency=medium
* debian/templates/control.in:
- Add missing conflict/replace/provide for
This bug was fixed in the package nvidia-graphics-drivers-390 -
390.141-0ubuntu0.18.04.2
---
nvidia-graphics-drivers-390 (390.141-0ubuntu0.18.04.2) bionic; urgency=medium
* debian/templates/control.in:
- Add conflicts/replace/provides for all the metapackages
(LP:
Yes, I can access the DFS entries with the provided test kernel. Please
let me know if you need more info from my side.
I do not think that it matters here, but I did not install the header
files as linux-headers-5.4.0-72-generic depends on linux-
headers-5.4.0-72 which is not in the linked web
Also worth mentioning. We are only seeing this on the A100. Neither
our automated testing or manual testing of ftrace saw any issues on
DGX2.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Here are the steps I used to reproduce:
#if using proposed pocket kernel
https://wiki.ubuntu.com/Testing/EnableProposed
#Need to enable deb-src for proposed/updates for this work
sudo apt update
$ sudo apt-get source linux
#After source is pulled, build and run ftrace selftests
$ sudo make -C
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 1923872
and then change the status of the bug to 'Confirmed'.
If, due to the
This is fixed in todays build, so closing this bug
** Changed in: zfs-linux (Ubuntu)
Status: Confirmed => Fix Released
** Changed in: snapd (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is
Testing on google cloud, this is still broken for:
bionic hwe (5.4.0-1041-gcp #44~18.04.1-Ubuntu)
focal ga (5.4.0-1041-gcp #44-Ubuntu)
focal hwe (5.8.0-49-generic #55~20.04.1-Ubuntu)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux
Hmpf - Here is a test kernel with just commit
ea42fd91d3041b81d704624b87f35b56f3a00841 from v5.4.112 applied.
https://kernel.ubuntu.com/~rtg/LP1923670/
--
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:
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
Public bug reported:
I use my Logitech Streamcam with Ubuntu 20.04.2 LTS and it does connect
properly. I can use it in some applications, like skype, zoom and
discord. But after some time (around 3 minutes, sometimes way longer)
the cam won't turn on anymore and the system completely freezes or
Second problem (freeze after suspend/resume) seems to be fixed with
5.4.0-71-generic.
--
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/1920674
Title:
AMD A8-7680 (amdgpu): broken Xorg
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: 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/1923670
Title:
CIFS DFS entries not accessible with
I did some manual ubuntu_kernel_selftests ftrace testing on the
5.4.0-71.79-generic kernel. I was able to replicate the panic, but not
on every run, but even on runs with no panic dmesg would report several
soft lockups.
After removing the MOFED dkms, I was unable to replicate a panic or any
of
** Also affects: linux (Ubuntu Focal)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Focal)
Status: New => In Progress
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** No longer affects: qemu (Ubuntu Hirsute)
** No longer affects: qemu (Ubuntu)
** No longer affects: glibc (Ubuntu Hirsute)
** No longer affects: glibc (Ubuntu)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
The commit "s390/vtime: fix increased steal time accounting" landed in hirsute
as c64e48d4ace3 in kernel Ubuntu-5.11.0-14 and this kernel is in hirsute's
release pocket:
linux-generic | 5.11.0.14.15 | hirsute | s390x
Hence closing the hirsute entry as Fix Released.
** Changed in:
** No longer affects: debianutils (Ubuntu)
** No longer affects: debianutils (Ubuntu Hirsute)
** No longer affects: debianutils (Ubuntu Focal)
** No longer affects: debianutils (Ubuntu Bionic)
--
You received this bug notification because you are a member of Kernel
Packages, which is
@Kamal, I am dropping "cifs: Set CIFS_MOUNT_USE_PREFIX_PATH flag on
setting cifs_sb->prepath." from the set due to bug #1923670
--
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/1920571
Daniel, just a heads-up: it fails for all Nvidia drivers, hence I marked
"nvidia-graphics-drivers" instead of the -460.
Cheers,
Guilherme
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-kvm in Ubuntu.
** Also affects: linux (Ubuntu Hirsute)
Importance: Undecided
Assignee: Kai-Heng Feng (kaihengfeng)
Status: In Progress
** Also affects: linux (Ubuntu Focal)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Hirsute)
Status: In Progress => Confirmed
** Description changed:
+ [Impact]
+
debian.aws-20.10/scripts/helpers/copy-files is unused and can be
- confusing.
+ confusing, especially for derivatives.
+
+ The eye of Sauron (in the form of apw) has cast its baleful glare on
+ this bit of cruft.
+
+ [Test Plan]
+
+ Perform a successful
Public bug reported:
[Impact]
debian.aws-20.10/scripts/helpers/copy-files is unused and can be
confusing, especially for derivatives.
The eye of Sauron (in the form of apw) has cast its baleful glare on
this bit of cruft.
[Test Plan]
Perform a successful build
[Where problems could occur]
After figuring out the correct upstream repo for the ubuntu kernel repo
(not https://git.launchpad.net/ubuntu/+source/linux but
https://git.launchpad.net/~ubuntu-
kernel/ubuntu/+source/linux/+git/focal) I replicated your command
$ git log --grep 'cifs' Ubuntu-5.4.0-70.78..Ubuntu-5.4.0-71.79
and
Public bug reported:
I use Hyper-V and created VM with "Generation 2", I cannot boot Ubuntu
Hirsute Hippo Live CD, it gives me kernel panic, I tried it when there
were included 5.11.0-13 and 5.11.0-14 kernels - same result, when there
was 5.11.0-11 and older it was fine.
** Affects: linux-signed
** Attachment added: "install.log"
https://bugs.launchpad.net/ubuntu/+source/evdi/+bug/1923638/+attachment/5487811/+files/install.log
** Description changed:
- evdi in hirsute cannot be used with the 5.11 kernel in hirsute. Upstream
- updates for 5.11 proved problematic, and a working set of
** Attachment added: "build.log"
https://bugs.launchpad.net/ubuntu/+source/evdi/+bug/1923638/+attachment/5487810/+files/build.log
--
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/1923638
The project does not maintain a changelog, so instead attaching the git
commit history between the v1.7.0 and v1.9.1 tags.
** Attachment added: "changelog.txt"
https://bugs.launchpad.net/ubuntu/+source/evdi/+bug/1923638/+attachment/5487808/+files/changelog.txt
--
You received this bug
This bug was fixed in the package linux-base - 4.5ubuntu5
---
linux-base (4.5ubuntu5) hirsute; urgency=medium
* Add kernel postinst hook to update initrd softlinks to match the kernel
version targets (LP: #1877088).
-- Stefan Bader Wed, 03 Feb 2021 16:05:08
+0100
**
** Changed in: linux (Ubuntu Groovy)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-restricted-modules in Ubuntu.
https://bugs.launchpad.net/bugs/1918134
Title:
LRMv4: switch to
** Changed in: linux (Ubuntu Bionic)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-restricted-modules in Ubuntu.
https://bugs.launchpad.net/bugs/1918134
Title:
LRMv4: switch to
** Summary changed:
- [FFE] evdi/1.7.0+dfsg-1ubuntu2 fails to build with linux 5.11
+ [FFe] evdi/1.7.0+dfsg-1ubuntu2 fails to build with linux 5.11
** Description changed:
- This is a scripted bug report about ADT failures while running evdi
- tests for linux/5.11.0-14.15 on hirsute. Whether
This bug was fixed in the package nvidia-graphics-drivers-460 -
460.56-0ubuntu0.20.10.1
---
nvidia-graphics-drivers-460 (460.56-0ubuntu0.20.10.1) groovy; urgency=medium
* New upstream release (LP: #1916908):
- Added support for the following GPUs:
GeForce RTX 3060
-
This bug was fixed in the package nvidia-graphics-drivers-460 -
460.56-0ubuntu0.20.04.1
---
nvidia-graphics-drivers-460 (460.56-0ubuntu0.20.04.1) focal; urgency=medium
* New upstream release (LP: #1916908):
- Added support for the following GPUs:
GeForce RTX 3060
-
This bug was fixed in the package nvidia-graphics-drivers-460 -
460.56-0ubuntu0.18.04.1
---
nvidia-graphics-drivers-460 (460.56-0ubuntu0.18.04.1) bionic; urgency=medium
* New upstream release (LP: #1916908):
- Added support for the following GPUs:
GeForce RTX 3060
-
This bug was fixed in the package nvidia-graphics-drivers-460 -
460.56-0ubuntu0.20.10.1
---
nvidia-graphics-drivers-460 (460.56-0ubuntu0.20.10.1) groovy; urgency=medium
* New upstream release (LP: #1916908):
- Added support for the following GPUs:
GeForce RTX 3060
-
This bug was fixed in the package nvidia-graphics-drivers-460 -
460.56-0ubuntu0.20.04.1
---
nvidia-graphics-drivers-460 (460.56-0ubuntu0.20.04.1) focal; urgency=medium
* New upstream release (LP: #1916908):
- Added support for the following GPUs:
GeForce RTX 3060
-
This bug was fixed in the package nvidia-graphics-drivers-460 -
460.56-0ubuntu0.18.04.1
---
nvidia-graphics-drivers-460 (460.56-0ubuntu0.18.04.1) bionic; urgency=medium
* New upstream release (LP: #1916908):
- Added support for the following GPUs:
GeForce RTX 3060
-
** Summary changed:
- evdi/1.7.0+dfsg-1ubuntu2 ADT test failure with linux/5.11.0-14.15
+ [FFE] evdi/1.7.0+dfsg-1ubuntu2 fails to build with linux 5.11
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
The verification of the Stable Release Update for nvidia-graphics-
drivers-390 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
** Changed in: linux (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-restricted-modules in Ubuntu.
https://bugs.launchpad.net/bugs/1918134
Title:
LRMv4: switch to signing
1 - 100 of 156 matches
Mail list logo
