On the system PORT-DVT2-D1, BIOS 0.2.31 with proposed kernel
5.14.0-1037-oem and linux-modules-iwlwifi-oem-20.04d.
I can still reproduce the RT ucode start timeout log, but it will be loaded
after retry.
May 18 13:37:48 PORT-DVT2-D1 kernel: iwlwifi :00:14.3: Failed to start RT
ucode: -110
Ma
apport information
** Attachment added: "Lspci-vt.txt"
https://bugs.launchpad.net/bugs/1973394/+attachment/5590610/+files/Lspci-vt.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/19
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1973394/+attachment/5590609/+files/Lspci.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1973394
apport information
** Attachment added: "IwConfig.txt"
https://bugs.launchpad.net/bugs/1973394/+attachment/5590607/+files/IwConfig.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/19
I have uploaded the apport info as requested.
Extra Info.
*I have just opened "SIGNAL" & tried the video link to make a call.**
**It opens with a normal, if somewhat grainy, video.*
**
*This tells me Signal can find & use the camera.**
**So far this is the only programme that can find the camera
apport information
** Attachment added: "Lsusb-t.txt"
https://bugs.launchpad.net/bugs/1973394/+attachment/5590611/+files/Lsusb-t.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1973
apport information
** Attachment added: "AlsaInfo.txt"
https://bugs.launchpad.net/bugs/1973394/+attachment/5590605/+files/AlsaInfo.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/19
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1973394/+attachment/5590606/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net
I have uploaded the apport information as requested.
Extra Info.
I have just opened "SIGNAL" & tried the video link call.
It opens with a normal, if somewhat grainy, video.
This tells me Signal can find & use the camera.
So far this is the only programme that can find the camera.
** Descriptio
apport information
** Attachment added: "PulseList.txt"
https://bugs.launchpad.net/bugs/1973394/+attachment/5590600/+files/PulseList.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/
apport information
** Attachment added: "acpidump.txt"
https://bugs.launchpad.net/bugs/1973394/+attachment/5590604/+files/acpidump.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/19
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1973394/+attachment/5590603/+files/WifiSyslog.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bug
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1973394/+attachment/5590602/+files/UdevDb.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1973394
apport information
** Attachment added: "RfKill.txt"
https://bugs.launchpad.net/bugs/1973394/+attachment/5590601/+files/RfKill.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1973394
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1973394/+attachment/5590598/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1973394/+attachment/5590599/+files/ProcModules.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/b
apport information
** Attachment added: "Lsusb-v.txt"
https://bugs.launchpad.net/bugs/1973394/+attachment/5590593/+files/Lsusb-v.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1973
apport information
** Attachment added: "Lsusb-t.txt"
https://bugs.launchpad.net/bugs/1973394/+attachment/5590592/+files/Lsusb-t.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1973
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1973394/+attachment/5590597/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/b
apport information
** Attachment added: "Lspci-vt.txt"
https://bugs.launchpad.net/bugs/1973394/+attachment/5590591/+files/Lspci-vt.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/19
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1973394/+attachment/5590596/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.l
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1973394/+attachment/5590595/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/b
apport information
** Attachment added: "PaInfo.txt"
https://bugs.launchpad.net/bugs/1973394/+attachment/5590594/+files/PaInfo.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1973394
apport information
** Tags added: apport-collected
** Description changed:
Dual boot, Win 10 & Ubuntu 22.04.
Camera works on Win but not discoverable on Ubuntu 22.04
Never any image or video in cheese
F6 does not turn it on in Cheese.
Used synaptic, nothing broken.
Checked for driver
apport information
** Attachment added: "IwConfig.txt"
https://bugs.launchpad.net/bugs/1973394/+attachment/5590589/+files/IwConfig.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/19
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1973394/+attachment/5590590/+files/Lspci.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1973394
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1973394/+attachment/5590588/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net
No need to build a kernel, at least for a quick test you can pick up one from
the mainline PPA and try it.
https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.18-rc7/
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://
** Tags added: patch
--
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/1972140
Title:
UBSAN: array-index-out-of-bounds in /build/linux-
HMZHpV/linux-5.15.0/drivers/net/wireless/ath/ath5k/
Please give this patch a try, thanks!
** Patch added: "0001-ath5k-Fix-out-of-bound-access.patch"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1972140/+attachment/5590578/+files/0001-ath5k-Fix-out-of-bound-access.patch
--
You received this bug notification because you are a member of
[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
I've made this confirmed, because the log collection (apport-collect
1973839) is hundreds of megabytes, as dmesg is full of the tracebacks
discussed
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Kernel
Packa
Hello Kahled, For Mario's comments#33, will you or can you build a main
kernel (v5.16) for testing? //thanks.
--
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/1971576
Title:
SATA device ho
Please give this patch a try, thanks!
** Patch added: "0001-ath5k-Fix-out-of-bound-access.patch"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1933839/+attachment/5590562/+files/0001-ath5k-Fix-out-of-bound-access.patch
--
You received this bug notification because you are a member of
Hello Kahled,
First, thanks for your effort to find this root cause in a short time.
For your comment #31, parnter has confirmed it is same for other type of disk.
I also asked them to raise this issue to AMD and AMD technical guy
reply below.
"Yes, 1022:7901h is AMD SATA AHCI controlle
All autopkgtests for the newly accepted linux-meta-oem-5.17 (5.17.0.1005.5) for
jammy have finished running.
The following regressions have been reported in tests triggered by the package:
dahdi-linux/1:2.11.1~dfsg-1ubuntu11 (amd64)
r8168/8.049.02-1ubuntu1 (amd64)
Please visit the excuses page
This bug was fixed in the package zfs-linux - 0.8.3-1ubuntu12.14
---
zfs-linux (0.8.3-1ubuntu12.14) focal; urgency=medium
* Fix zfs_get_data access to files causing panics (LP: #1946686)
-
debian/patches/4920-Fix-zfs_get_data-access-to-files-with-wrong-generati.patch
backpo
All autopkgtests for the newly accepted linux-meta-oem-5.17 (5.17.0.1005.5) for
jammy have finished running.
The following regressions have been reported in tests triggered by the package:
dahdi-linux/1:2.11.1~dfsg-1ubuntu11 (amd64)
r8168/8.049.02-1ubuntu1 (amd64)
Please visit the excuses page
This bug is awaiting verification that the linux/5.15.0-32.33 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-jammy' to 'verification-done-jammy'. If the problem
still exists, change t
This bug is awaiting verification that the linux/5.15.0-32.33 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-jammy' to 'verification-done-jammy'. If the problem
still exists, change t
This bug is awaiting verification that the linux/5.15.0-32.33 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-jammy' to 'verification-done-jammy'. If the problem
still exists, change t
This bug is awaiting verification that the linux/5.15.0-32.33 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-jammy' to 'verification-done-jammy'. If the problem
still exists, change t
This bug is awaiting verification that the linux/5.15.0-32.33 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-jammy' to 'verification-done-jammy'. If the problem
still exists, change t
> but I believe you are using an AMD EPYC server, so I don't understand
why you would be affected at all.
It may be that this server silicon has the same HW IP as the client
chip. The change was tested on client chips before submitting. What it
is supposed to do is set the policy for the drives
Can you please give mainline kernel a try?
If mainline kernel still doesn't work, please run the following:
$ sudo trace-cmd record -p function -l "*ata*" -l "*ahci*"
... then plug the disk, Ctrl + C on trace-cmd, attach trace.dat here.
--
You received this bug notification because you are a mem
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 1973839
and then change the status of the bug to 'Confirmed'.
If, due to the nature
Public bug reported:
When booting this in one of our clouds, we see an error early in the
kernel output
kernel: unchecked MSR access error: WRMSR to 0x48 (tried to write
0x0004) at rIP: 0xabc90af4
(native_write_msr+0x4/0x20)
and then an un-ending stream of "bare" tracebacks
Thanks Zhanglei. Great. We have identified the problem patch, which is
this one:
380cd49e207ba4 ata: ahci: Add Green Sardine vendor ID as
board_ahci_mobile
But I am not really sure why this patch is causing a problem.
The patch only adds one new line as you can see here:
https://pastebin.ubunt
This bug is awaiting verification that the linux-
raspi-5.4/5.4.0-1061.69~18.04.1 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-bionic' to
'verification-done-bionic'. If the problem
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
https://github.com/juju/juju/pull/14028
** Changed in: juju
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to ubuntu-fan in Ubuntu.
https://bugs.launchpad.net/bugs/1944080
Title:
[fan-network]
This bug was fixed in the package fabric-manager-510 -
510.73.05-0ubuntu0.18.04.1
---
fabric-manager-510 (510.73.05-0ubuntu0.18.04.1) bionic; urgency=medium
* New upstream release (LP: #1973300).
-- Alberto Milone Mon, 16 May 2022
15:12:57 +
** Changed in: libnvidia-nscq-45
This bug was fixed in the package libnvidia-nscq-510 -
510.73.05-0ubuntu0.18.04.1
---
libnvidia-nscq-510 (510.73.05-0ubuntu0.18.04.1) bionic; urgency=medium
* New upstream release (LP: #1973300).
-- Alberto Milone Mon, 16 May 2022
15:53:09 +
--
You received this bug notifi
This bug was fixed in the package libnvidia-nscq-470 -
470.129.06-0ubuntu0.22.04.1
---
libnvidia-nscq-470 (470.129.06-0ubuntu0.22.04.1) jammy; urgency=medium
* New upstream release (LP: #1973300).
-- Alberto Milone Mon, 16 May 2022
11:02:17 +
** Changed in: libnvidia-nscq-4
This bug was fixed in the package libnvidia-nscq-510 -
510.73.05-0ubuntu0.21.10.1
---
libnvidia-nscq-510 (510.73.05-0ubuntu0.21.10.1) impish; urgency=medium
* New upstream release (LP: #1973300).
-- Alberto Milone Mon, 16 May 2022
15:51:17 +
** Changed in: libnvidia-nscq-51
This bug was fixed in the package libnvidia-nscq-450 -
450.191.01-0ubuntu0.22.04.1
---
libnvidia-nscq-450 (450.191.01-0ubuntu0.22.04.1) jammy; urgency=medium
* New upstream release (LP: #1973300).
-- Alberto Milone Mon, 16 May 2022
09:39:08 +
** Changed in: libnvidia-nscq-4
This bug was fixed in the package libnvidia-nscq-510 -
510.73.05-0ubuntu0.20.04.1
---
libnvidia-nscq-510 (510.73.05-0ubuntu0.20.04.1) focal; urgency=medium
* New upstream release (LP: #1973300).
-- Alberto Milone Mon, 16 May 2022
15:52:07 +
** Changed in: libnvidia-nscq-510
This bug was fixed in the package libnvidia-nscq-450 -
450.191.01-0ubuntu0.20.04.1
---
libnvidia-nscq-450 (450.191.01-0ubuntu0.20.04.1) focal; urgency=medium
* New upstream release (LP: #1973300).
-- Alberto Milone Mon, 16 May 2022
10:11:57 +
** Changed in: libnvidia-nscq-4
This bug was fixed in the package libnvidia-nscq-450 -
450.191.01-0ubuntu0.18.04.1
---
libnvidia-nscq-450 (450.191.01-0ubuntu0.18.04.1) bionic; urgency=medium
* New upstream release (LP: #1973300).
-- Alberto Milone Mon, 16 May 2022
10:12:48 +
** Changed in: libnvidia-nscq-
This bug was fixed in the package libnvidia-nscq-470 -
470.129.06-0ubuntu0.21.10.1
---
libnvidia-nscq-470 (470.129.06-0ubuntu0.21.10.1) impish; urgency=medium
* New upstream release (LP: #1973300).
-- Alberto Milone Mon, 16 May 2022
11:05:08 +
** Changed in: libnvidia-nscq-
This bug was fixed in the package libnvidia-nscq-510 -
510.73.05-0ubuntu0.22.04.1
---
libnvidia-nscq-510 (510.73.05-0ubuntu0.22.04.1) jammy; urgency=medium
* New upstream release (LP: #1973300).
-- Alberto Milone Mon, 16 May 2022
15:48:47 +
** Changed in: libnvidia-nscq-510
This bug was fixed in the package libnvidia-nscq-450 -
450.191.01-0ubuntu0.21.10.1
---
libnvidia-nscq-450 (450.191.01-0ubuntu0.21.10.1) impish; urgency=medium
* New upstream release (LP: #1973300).
-- Alberto Milone Mon, 16 May 2022
10:11:05 +
** Changed in: libnvidia-nscq-
This bug was fixed in the package libnvidia-nscq-470 -
470.129.06-0ubuntu0.20.04.1
---
libnvidia-nscq-470 (470.129.06-0ubuntu0.20.04.1) focal; urgency=medium
* New upstream release (LP: #1973300).
-- Alberto Milone Mon, 16 May 2022
11:05:51 +
** Changed in: libnvidia-nscq-4
This bug was fixed in the package libnvidia-nscq-470 -
470.129.06-0ubuntu0.18.04.1
---
libnvidia-nscq-470 (470.129.06-0ubuntu0.18.04.1) bionic; urgency=medium
* New upstream release (LP: #1973300).
-- Alberto Milone Mon, 16 May 2022
11:06:36 +
** Changed in: libnvidia-nscq-
This bug was fixed in the package fabric-manager-510 -
510.73.05-0ubuntu0.21.10.1
---
fabric-manager-510 (510.73.05-0ubuntu0.21.10.1) impish; urgency=medium
* New upstream release (LP: #1973300).
-- Alberto Milone Mon, 16 May 2022
15:11:24 +
** Changed in: fabric-manager-51
This bug was fixed in the package fabric-manager-510 -
510.73.05-0ubuntu0.20.04.1
---
fabric-manager-510 (510.73.05-0ubuntu0.20.04.1) focal; urgency=medium
* New upstream release (LP: #1973300).
-- Alberto Milone Mon, 16 May 2022
15:12:16 +
** Changed in: fabric-manager-510
This bug was fixed in the package fabric-manager-510 -
510.73.05-0ubuntu0.22.04.1
---
fabric-manager-510 (510.73.05-0ubuntu0.22.04.1) jammy; urgency=medium
* New upstream release (LP: #1973300).
-- Alberto Milone Mon, 16 May 2022
15:03:51 +
** Changed in: fabric-manager-510
This bug was fixed in the package fabric-manager-470 -
470.129.06-0ubuntu0.20.04.1
---
fabric-manager-470 (470.129.06-0ubuntu0.20.04.1) focal; urgency=medium
* New upstream release (LP: #1973300).
-- Alberto Milone Mon, 16 May 2022
11:19:12 +
** Changed in: fabric-manager-4
This bug was fixed in the package fabric-manager-470 -
470.129.06-0ubuntu0.18.04.1
---
fabric-manager-470 (470.129.06-0ubuntu0.18.04.1) bionic; urgency=medium
* New upstream release (LP: #1973300).
-- Alberto Milone Mon, 16 May 2022
11:19:50 +
** Changed in: fabric-manager-
This bug was fixed in the package fabric-manager-470 -
470.129.06-0ubuntu0.21.10.1
---
fabric-manager-470 (470.129.06-0ubuntu0.21.10.1) impish; urgency=medium
* New upstream release (LP: #1973300).
-- Alberto Milone Mon, 16 May 2022
11:18:18 +
** Changed in: fabric-manager-
This bug was fixed in the package fabric-manager-450 -
450.191.01-0ubuntu0.21.10.1
---
fabric-manager-450 (450.191.01-0ubuntu0.21.10.1) impish; urgency=medium
* New upstream release (LP: #1973300).
-- Alberto Milone Fri, 13 May 2022
15:45:42 +
** Changed in: fabric-manager-
This bug was fixed in the package fabric-manager-450 -
450.191.01-0ubuntu0.18.04.1
---
fabric-manager-450 (450.191.01-0ubuntu0.18.04.1) bionic; urgency=medium
* New upstream release (LP: #1973300).
-- Alberto Milone Fri, 13 May 2022
15:48:25 +
** Changed in: fabric-manager-
This bug was fixed in the package fabric-manager-470 -
470.129.06-0ubuntu0.22.04.1
---
fabric-manager-470 (470.129.06-0ubuntu0.22.04.1) jammy; urgency=medium
* New upstream release (LP: #1973300).
-- Alberto Milone Mon, 16 May 2022
11:14:40 +
** Changed in: fabric-manager-4
This bug was fixed in the package nvidia-graphics-drivers-510-server -
510.73.05-0ubuntu0.20.04.1
---
nvidia-graphics-drivers-510-server (510.73.05-0ubuntu0.20.04.1) focal;
urgency=medium
* New upstream release (LP: #1973300).
-- Alberto Milone Mon, 16 May 2022
11:42:03 +
This bug was fixed in the package nvidia-graphics-drivers-510-server -
510.73.05-0ubuntu0.18.04.1
---
nvidia-graphics-drivers-510-server (510.73.05-0ubuntu0.18.04.1) bionic;
urgency=medium
* New upstream release (LP: #1973300).
-- Alberto Milone Mon, 16 May 2022
11:42:40 +
This bug was fixed in the package nvidia-graphics-drivers-510-server -
510.73.05-0ubuntu0.21.10.1
---
nvidia-graphics-drivers-510-server (510.73.05-0ubuntu0.21.10.1) impish;
urgency=medium
* New upstream release (LP: #1973300).
-- Alberto Milone Mon, 16 May 2022
11:41:05 +
This bug was fixed in the package nvidia-graphics-drivers-510 -
510.73.05-0ubuntu0.18.04.1
---
nvidia-graphics-drivers-510 (510.73.05-0ubuntu0.18.04.1) bionic; urgency=medium
[ Alberto Milone ]
* New upstream release (LP: #1973300).
[ Ian May ]
* debian/{additional_card_ids|a
This bug was fixed in the package fabric-manager-450 -
450.191.01-0ubuntu0.22.04.1
---
fabric-manager-450 (450.191.01-0ubuntu0.22.04.1) jammy; urgency=medium
* New upstream release (LP: #1973300).
-- Alberto Milone Fri, 13 May 2022
15:43:09 +
** Changed in: fabric-manager-4
This bug was fixed in the package nvidia-graphics-drivers-510 -
510.73.05-0ubuntu0.20.04.1
---
nvidia-graphics-drivers-510 (510.73.05-0ubuntu0.20.04.1) focal; urgency=medium
[ Alberto Milone ]
* New upstream release (LP: #1973300).
[ Ian May ]
* debian/{additional_card_ids|ad
This bug was fixed in the package nvidia-graphics-drivers-510-server -
510.73.05-0ubuntu0.22.04.1
---
nvidia-graphics-drivers-510-server (510.73.05-0ubuntu0.22.04.1) jammy;
urgency=medium
* New upstream release (LP: #1973300).
-- Alberto Milone Mon, 16 May 2022
11:34:20 +
This bug was fixed in the package fabric-manager-450 -
450.191.01-0ubuntu0.20.04.1
---
fabric-manager-450 (450.191.01-0ubuntu0.20.04.1) focal; urgency=medium
* New upstream release (LP: #1973300).
-- Alberto Milone Fri, 13 May 2022
15:47:02 +
** Changed in: fabric-manager-4
This bug was fixed in the package nvidia-graphics-drivers-510 -
510.73.05-0ubuntu0.21.10.1
---
nvidia-graphics-drivers-510 (510.73.05-0ubuntu0.21.10.1) impish; urgency=medium
[ Alberto Milone ]
* New upstream release (LP: #1973300).
[ Ian May ]
* debian/{additional_card_ids|a
This bug was fixed in the package nvidia-graphics-drivers-470 -
470.129.06-0ubuntu0.20.04.1
---
nvidia-graphics-drivers-470 (470.129.06-0ubuntu0.20.04.1) focal; urgency=medium
* New upstream release (LP: #1973300).
-- Alberto Milone Mon, 16 May 2022
10:26:46 +
** Changed in
This bug was fixed in the package nvidia-graphics-drivers-450-server -
450.191.01-0ubuntu0.18.04.1
---
nvidia-graphics-drivers-450-server (450.191.01-0ubuntu0.18.04.1) bionic;
urgency=medium
* New upstream release (LP: #1973300).
-- Alberto Milone Fri, 13 May 2022
15:19:12 +000
This bug was fixed in the package nvidia-graphics-drivers-470-server -
470.129.06-0ubuntu0.22.04.1
---
nvidia-graphics-drivers-470-server (470.129.06-0ubuntu0.22.04.1) jammy;
urgency=medium
* New upstream release (LP: #1973300).
-- Alberto Milone Mon, 16 May 2022
10:41:55 +
This bug was fixed in the package nvidia-graphics-drivers-470 -
470.129.06-0ubuntu0.21.10.1
---
nvidia-graphics-drivers-470 (470.129.06-0ubuntu0.21.10.1) impish; urgency=medium
* New upstream release (LP: #1973300).
-- Alberto Milone Mon, 16 May 2022
10:25:10 +
** Changed i
This bug was fixed in the package nvidia-graphics-drivers-470 -
470.129.06-0ubuntu0.18.04.1
---
nvidia-graphics-drivers-470 (470.129.06-0ubuntu0.18.04.1) bionic; urgency=medium
* New upstream release (LP: #1973300).
-- Alberto Milone Mon, 16 May 2022
10:27:52 +
** Changed i
This bug was fixed in the package nvidia-graphics-drivers-470 -
470.129.06-0ubuntu0.22.04.1
---
nvidia-graphics-drivers-470 (470.129.06-0ubuntu0.22.04.1) jammy; urgency=medium
* New upstream release (LP: #1973300).
-- Alberto Milone Mon, 16 May 2022
10:23:38 +
** Changed in
This bug was fixed in the package nvidia-graphics-drivers-450-server -
450.191.01-0ubuntu0.20.04.1
---
nvidia-graphics-drivers-450-server (450.191.01-0ubuntu0.20.04.1) focal;
urgency=medium
* New upstream release (LP: #1973300).
-- Alberto Milone Fri, 13 May 2022
15:17:35 +
This bug was fixed in the package nvidia-graphics-drivers-510 -
510.73.05-0ubuntu0.22.04.1
---
nvidia-graphics-drivers-510 (510.73.05-0ubuntu0.22.04.1) jammy; urgency=medium
[ Alberto Milone ]
* New upstream release (LP: #1973300).
[ Ian May ]
* debian/{additional_card_ids|ad
This bug was fixed in the package nvidia-graphics-drivers-470-server -
470.129.06-0ubuntu0.18.04.1
---
nvidia-graphics-drivers-470-server (470.129.06-0ubuntu0.18.04.1) bionic;
urgency=medium
* New upstream release (LP: #1973300).
-- Alberto Milone Mon, 16 May 2022
10:49:13 +000
This bug was fixed in the package nvidia-graphics-drivers-470-server -
470.129.06-0ubuntu0.20.04.1
---
nvidia-graphics-drivers-470-server (470.129.06-0ubuntu0.20.04.1) focal;
urgency=medium
* New upstream release (LP: #1973300).
-- Alberto Milone Mon, 16 May 2022
10:48:01 +
This bug was fixed in the package nvidia-graphics-drivers-470-server -
470.129.06-0ubuntu0.21.10.1
---
nvidia-graphics-drivers-470-server (470.129.06-0ubuntu0.21.10.1) impish;
urgency=medium
* New upstream release (LP: #1973300).
-- Alberto Milone Mon, 16 May 2022
10:46:17 +000
This bug was fixed in the package nvidia-graphics-drivers-450-server -
450.191.01-0ubuntu0.21.10.1
---
nvidia-graphics-drivers-450-server (450.191.01-0ubuntu0.21.10.1) impish;
urgency=medium
* New upstream release (LP: #1973300).
-- Alberto Milone Fri, 13 May 2022
15:15:55 +000
This bug was fixed in the package nvidia-graphics-drivers-450-server -
450.191.01-0ubuntu0.22.04.1
---
nvidia-graphics-drivers-450-server (450.191.01-0ubuntu0.22.04.1) jammy;
urgency=medium
* New upstream release (LP: #1973300).
* debian/templates/dkms_nvidia.conf.in:
- Drop
This bug was fixed in the package nvidia-graphics-drivers-390 -
390.151-0ubuntu0.18.04.1
---
nvidia-graphics-drivers-390 (390.151-0ubuntu0.18.04.1) bionic; urgency=medium
* New upstream release (LP: #1973300).
* debian/templates/dkms_nvidia.conf.in:
- Drop buildfix_kernel_5.17
This bug was fixed in the package nvidia-graphics-drivers-390 -
390.151-0ubuntu0.21.10.1
---
nvidia-graphics-drivers-390 (390.151-0ubuntu0.21.10.1) impish; urgency=medium
* New upstream release (LP: #1973300).
* debian/templates/dkms_nvidia.conf.in:
- Drop buildfix_kernel_5.17
This bug was fixed in the package nvidia-graphics-drivers-390 -
390.151-0ubuntu0.20.04.1
---
nvidia-graphics-drivers-390 (390.151-0ubuntu0.20.04.1) focal; urgency=medium
* New upstream release (LP: #1973300).
* debian/templates/dkms_nvidia.conf.in:
- Drop buildfix_kernel_5.17.
This bug was fixed in the package nvidia-graphics-drivers-390 -
390.151-0ubuntu0.22.04.1
---
nvidia-graphics-drivers-390 (390.151-0ubuntu0.22.04.1) jammy; urgency=medium
* New upstream release (LP: #1973300).
* debian/templates/dkms_nvidia.conf.in:
- Drop buildfix_kernel_5.17.
This bug was fixed in the package nvidia-graphics-drivers-510 -
510.73.05-0ubuntu0.22.04.1
---
nvidia-graphics-drivers-510 (510.73.05-0ubuntu0.22.04.1) jammy; urgency=medium
[ Alberto Milone ]
* New upstream release (LP: #1973300).
[ Ian May ]
* debian/{additional_card_ids|ad
1 - 100 of 150 matches
Mail list logo
