Public bug reported:
During Oracular archive opening, noble/linux-ibm and noble/linux-gke
were forward copied but these kernels are EOL and not supported in OO,
thus asking for archive removal of these two packages.
** Affects: linux-gke (Ubuntu)
Importance: Undecided
Status: New
*
** Patch added: "nvidia-dkms-470-server fix."
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-470-server/+bug/2076176/+attachment/5803499/+files/0001-nvidia-graphics-drivers-470-470.256.02-0ubuntu2.patch
--
You received this bug notification because you are a member of Kerne
** Patch added: "nvidia-dkms-470-server fix."
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-470-server/+bug/2076176/+attachment/5803500/+files/0001-nvidia-graphics-drivers-470-server-470.256.02-0ubuntu2.patch
--
You received this bug notification because you are a member o
** Patch added: "nvidia-dkms-470 fix."
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-470-server/+bug/2076176/+attachment/5803498/+files/0001-nvidia-graphics-drivers-470-470.256.02-0ubuntu2.patch
--
You received this bug notification because you are a member of Kernel
Packa
** Description changed:
[Impact]
Full build log:
https://launchpadlibrarian.net/741978316/buildlog_ubuntu-oracular-
amd64.linux-restricted-modules_6.10.0-18.18+1_BUILDING.txt.gz
- As soon as you fix one, another one shows up, and so on - it turned out,
- the conftest.sh & Kbuild fram
Public bug reported:
[Impact]
Full build log:
https://launchpadlibrarian.net/741978316/buildlog_ubuntu-oracular-
amd64.linux-restricted-modules_6.10.0-18.18+1_BUILDING.txt.gz
As soon as you fix one, another one shows up, and so on - it turned out,
the conftest.sh & Kbuild framework NVIDIA DKMS u
** Patch added:
"0001-UBUNTU-Packaging-Recommends-linux-tools-kernel-abi-v.patch"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2064266/+attachment/5773019/+files/0001-UBUNTU-Packaging-Recommends-linux-tools-kernel-abi-v.patch
** Description changed:
[Impact]
- The linux-virtual
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:
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:
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:
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
Can you update a working image to the latest bootstrap kernel and try
again?
https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/bootstrap -
6.8.0-15.15
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bug
Proceed with the removal of linux-modules-ipu6-oem-22.04, linux-modules-
ivsc-oem-22.04, linux-modules-nvidia-440-oem-20.04, linux-modules-
nvidia-450-oem-20.04 from noble and noble-proposed, please.
** Changed in: linux (Ubuntu Noble)
Status: Incomplete => Confirmed
--
You received this
Ok, so every commit was upstream by v6.3-rc1.
** Changed in: linux (Ubuntu)
Status: Incomplete => 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/2008522
Title:
Intel
** Patch added: "nvidia-graphics-drivers-535-server_535.154.05-0ubuntu2.debdiff"
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-470/+bug/2052420/+attachment/5744907/+files/nvidia-graphics-drivers-535-server_535.154.05-0ubuntu2.debdiff
--
You received this bug notification b
** Patch added: "nvidia-graphics-drivers-545_545.29.06-0ubuntu5.debdiff"
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-470/+bug/2052420/+attachment/5744864/+files/nvidia-graphics-drivers-545_545.29.06-0ubuntu5.debdiff
--
You received this bug notification because you are a
** Patch added: "nvidia-graphics-drivers-535_535.154.05-0ubuntu2.debdiff"
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-470/+bug/2052420/+attachment/5744863/+files/nvidia-graphics-drivers-535_535.154.05-0ubuntu2.debdiff
--
You received this bug notification because you are
** Patch added: "nvidia-graphics-drivers-545_545.29.06-0ubuntu5.debdiff"
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-470/+bug/2052420/+attachment/5744855/+files/nvidia-graphics-drivers-545_545.29.06-0ubuntu5.debdiff
--
You received this bug notification because you are a
** Patch added: "nvidia-graphics-drivers-470-server_470.223.02-0ubuntu2.debdiff"
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-470-server/+bug/2052420/+attachment/5744699/+files/nvidia-graphics-drivers-470-server_470.223.02-0ubuntu2.debdiff
** Also affects: nvidia-graphics-
** Patch added: "nvidia-graphics-drivers-470_470.223.02-0ubuntu2.debdiff"
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-470/+bug/2052420/+attachment/5744687/+files/nvidia-graphics-drivers-470_470.223.02-0ubuntu2.debdiff
** Also affects: nvidia-graphics-drivers-470-server (U
** Description changed:
[Impact]
...
+ In file included from
/var/lib/dkms/nvidia/470.223.02/build/nvidia-drm/nvidia-drm-drv.c:60:
+ /var/lib/dkms/nvidia/470.223.02/build/nvidia-drm/nvidia-drm-drv.c:748:40:
error: ‘DRM_UNLOCKED’ undeclared here (not in a function); did you mean
‘VM_LOCKE
Public bug reported:
[Impact]
...
...
[Fix]
Apply the attached debdiff.
[How to test]
Install (and rebuild) the patched package.
[Regression potential]
Two patches, none originating from NVidia and both touching locking:
there's definitely regression potential here, hence i'm proposing this
Commit
acbc661032b8,bbfc3349c4e7,c7cd6f04c0df,98e596fc85fe,ebf519710218,966d0ab67350,621084965459,8526eb7fc75a,8e4736358837
were all part of v6.3-rc1, thus shipped with 23.10 GA kernel.
While the last mentioned commit (c4e927da893b68b99e94a4a2) is nowhere to
be found, can you double check the SHA?
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:
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:
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:
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:
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:
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:
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:
[Impact]
...
/var/lib/dkms/zfs/2.2.0/build/module/os/linux/zfs/zfs_ctldir.c: In function
‘zfsctl_inode_alloc’:
/var/lib/dkms/zfs/2.2.0/build/module/os/linux/zfs/zfs_ctldir.c:525:13: error:
‘struct inode’ has no member named ‘i_ctime’; did you mean ‘i_atime’?
525 |
** Also affects: iproute2 (Ubuntu Mantic)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to iproute2 in Ubuntu.
Matching subscriptions: iproute2
https://bugs.launchpad.net/bugs/2039280
Title:
Su
** Patch added: "iproute2_6.1.0-1ubuntu3.debdiff"
https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/2039280/+attachment/5709212/+files/iproute2_6.1.0-1ubuntu3.debdiff
** Description changed:
[Impact]
IPv4 and IPv6 addresses can be assigned a protocol value that indicates the
pr
** Description changed:
[Impact]
IPv4 and IPv6 addresses can be assigned a protocol value that indicates the
provenance of the IP address. The attribute is modeled after ip route
protocols, and essentially allows the administrator or userspace stack to
tag addresses in some way that m
Public bug reported:
[Impact]
IPv4 and IPv6 addresses can be assigned a protocol value that indicates the
provenance of the IP address. The attribute is modeled after ip route
protocols, and essentially allows the administrator or userspace stack to
tag addresses in some way that makes sense to t
** No longer affects: linux (Ubuntu Mantic)
** No longer affects: linux (Ubuntu)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.5 in Ubuntu.
https://bugs.launchpad.net/bugs/2031302
Title:
test_290_config_hardened_usercopy
** Summary changed:
- test_290_config_hardened_usercopy in ubuntu_qrt_kernel_security failed with
J-oem-6.5 (HAVE_HARDENED_USERCOPY_ALLOCATOR does not exist anymore)
+ test_290_config_hardened_usercopy in ubuntu_qrt_kernel_security failed with
J-oem-6.5 / M-linux (HAVE_HARDENED_USERCOPY_ALLOCATO
I've sent a pull req to fix the test:
https://code.launchpad.net/~p-pisati/qa-regression-testing/+git/qa-
regression-testing/+merge/453326
basically, the HAVE_HARDENED_USERCOPY_ALLOCATOR has been retired in
v6.5-rc1 so the test thinks the option is off and thus the test should
always fail.
** Al
** Patch added: "nvidia-graphics-drivers-525_525.125.06-0ubuntu4.debdiff"
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/2028165/+attachment/5696045/+files/nvidia-graphics-drivers-525_525.125.06-0ubuntu4.debdiff
--
You received this bug notification because you are
450-server Linux 6.5 fix.
** Also affects: nvidia-graphics-drivers-450-server (Ubuntu)
Importance: Undecided
Status: New
** Patch added: "nvidia-graphics-drivers-450-server_450.248.02-0ubuntu2.debdiff"
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-450-server/+bug
525-server fix for Linux 6.5
** Also affects: nvidia-graphics-drivers-525-server (Ubuntu)
Importance: Undecided
Status: New
** Patch added: "nvidia-graphics-drivers-525-server_525.125.06-0ubuntu2.debdiff"
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-525-server/+
** Patch added: "nvidia-graphics-drivers-470-server_470.199.02-0ubuntu2.debdiff"
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/2028165/+attachment/5688347/+files/nvidia-graphics-drivers-470-server_470.199.02-0ubuntu2.debdiff
--
You received this bug notification b
New patch for the 470 driver
** Patch added: "nvidia-graphics-drivers-470_470.199.02-0ubuntu2.debdiff"
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/2028165/+attachment/5688321/+files/nvidia-graphics-drivers-470_470.199.02-0ubuntu2.debdiff
--
You received this bu
** Also affects: nvidia-graphics-drivers-470-server (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-470-server in
Ubuntu.
https://bugs.launchpad.net/bugs/2028165
** Patch added: "nvidia-graphics-drivers-470_470.199.02-0ubuntu2.debdiff"
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-525/+bug/2028165/+attachment/5688058/+files/nvidia-graphics-drivers-470_470.199.02-0ubuntu2.debdiff
--
You received this bug notification because you are
** Also affects: nvidia-graphics-drivers-470 (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-470 in Ubuntu.
https://bugs.launchpad.net/bugs/2028165
Title:
nvid
** Patch added: "nvidia-graphics-drivers-525_525.125.06-0ubuntu2.debdiff"
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-525/+bug/2028165/+attachment/5687461/+files/nvidia-graphics-drivers-525_525.125.06-0ubuntu2.debdiff
--
You received this bug notification because you are
** Also affects: nvidia-graphics-drivers-525 (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu.
https://bugs.launchpad.net/bugs/2028165
Title:
nvid
** Patch added: "nvidia-graphics-drivers-390_390.157-0ubuntu8.debdiff"
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/2028165/+attachment/5687148/+files/nvidia-graphics-drivers-390_390.157-0ubuntu8.debdiff
--
You received this bug notification because you are a mem
Public bug reported:
[Impact]
...
In file included from
/var/lib/dkms/nvidia/390.157/build/common/inc/nv-linux.h:21,
from
/var/lib/dkms/nvidia/390.157/build/nvidia/nv-instance.c:13:
/var/lib/dkms/nvidia/390.157/build/common/inc/nv-mm.h: In function
‘NV_GET_USER_PAGES_REMOTE’:
** Also affects: nvidia-graphics-drivers-515 (Ubuntu)
Importance: Undecided
Status: New
** Changed in: nvidia-graphics-drivers-510 (Ubuntu Mantic)
Status: New => Won't Fix
** Changed in: nvidia-graphics-drivers-515 (Ubuntu Mantic)
Status: New => Won't Fix
--
You received
** Also affects: nvidia-graphics-drivers-510 (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-470 in Ubuntu.
https://bugs.launchpad.net/bugs/2025266
Title:
nvid
** Patch added: "nvidia-graphics-drivers-470_470.182.03-0ubuntu3.debdiff"
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-470/+bug/2025266/+attachment/5682856/+files/nvidia-graphics-drivers-470_470.182.03-0ubuntu3.debdiff
--
You received this bug notification because you are
** Also affects: nvidia-graphics-drivers-470 (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu.
https://bugs.launchpad.net/bugs/2025266
Title:
nvid
** Patch added: "nvidia-graphics-drivers-390_390.157-0ubuntu7.debdiff"
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/2025266/+attachment/5682792/+files/nvidia-graphics-drivers-390_390.157-0ubuntu7.debdiff
--
You received this bug notification because you are a mem
Public bug reported:
[Impact]
/var/lib/dkms/nvidia/390.157/build/nvidia-drm/nvidia-drm-drv.c: In function
‘nv_drm_update_drm_driver_features’:
/var/lib/dkms/nvidia/390.157/build/nvidia-drm/nvidia-drm-drv.c:769:18: error:
‘struct drm_driver’ has no member named ‘dumb_destroy’
769 | nv_drm_
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:
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:
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
** Patch added: "nvidia-graphics-drivers-515_515.105.01-0ubuntu3.debdiff"
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/2019979/+attachment/5678457/+files/nvidia-graphics-drivers-515_515.105.01-0ubuntu3.debdiff
--
You received this bug notification because you are
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
** Patch added: "nvidia-graphics-drivers-450-server_450.236.01-0ubuntu3.debdiff"
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/2019979/+attachment/5677154/+files/nvidia-graphics-drivers-450-server_450.236.01-0ubuntu3.debdiff
--
You received this bug notification b
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:
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:
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:
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
** Patch added: "nvidia-graphics-drivers-470-server_470.182.03-0ubuntu2.debdiff"
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-470-server/+bug/2019979/+attachment/5674711/+files/nvidia-graphics-drivers-470-server_470.182.03-0ubuntu2.debdiff
--
You received this bug notific
** Patch added: "nvidia-graphics-drivers-450-server_450.236.01-0ubuntu2.debdiff"
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-470-server/+bug/2019979/+attachment/5674704/+files/nvidia-graphics-drivers-450-server_450.236.01-0ubuntu2.debdiff
--
You received this bug notific
** Also affects: nvidia-graphics-drivers-450-server (Ubuntu)
Importance: Undecided
Status: New
** Also affects: nvidia-graphics-drivers-470-server (Ubuntu)
Importance: Undecided
Status: New
** Summary changed:
- nvidia-dkms-390|470|510|515|515-server FTBS with linux 6.3
+ nvi
** Summary changed:
- nvidia-dkms-390|470|510|515 FTBS with linux 6.3
+ nvidia-dkms-390|470|510|515|515-server FTBS with linux 6.3
** Also affects: nvidia-graphics-drivers-515-server (Ubuntu)
Importance: Undecided
Status: New
** Patch added: "nvidia-graphics-drivers-515-server_515.105.
** Patch added: "nvidia-graphics-drivers-515_515.105.01-0ubuntu2.debdiff"
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-510/+bug/2019979/+attachment/5673905/+files/nvidia-graphics-drivers-515_515.105.01-0ubuntu2.debdiff
** Also affects: nvidia-graphics-drivers-515 (Ubuntu)
** Summary changed:
- nvidia-dkms-390|470|510 FTBS with linux 6.3
+ nvidia-dkms-390|470|510|515 FTBS with linux 6.3
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu.
https://bugs.launchpad.net/bugs/201
** Patch added: "nvidia-graphics-drivers-510_510.108.03-0ubuntu3.debdiff"
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-510/+bug/2019979/+attachment/5673845/+files/nvidia-graphics-drivers-510_510.108.03-0ubuntu3.debdiff
--
You received this bug notification because you are
** Also affects: nvidia-graphics-drivers-510 (Ubuntu)
Importance: Undecided
Status: New
** Summary changed:
- nvidia-dkms-390|470 FTBS with linux 6.3
+ nvidia-dkms-390|470|510 FTBS with linux 6.3
--
You received this bug notification because you are a member of Kernel
Packages, which
** Patch added: "nvidia-graphics-drivers-470_470.182.03-0ubuntu2.debdiff"
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-470/+bug/2019979/+attachment/5673813/+files/nvidia-graphics-drivers-470_470.182.03-0ubuntu2.debdiff
--
You received this bug notification because you are
** Summary changed:
- nvidia-dkms-390 FTBS with linux 6.3
+ nvidia-dkms-390|470 FTBS with linux 6.3
** Also affects: nvidia-graphics-drivers-470 (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subsc
** Patch added: "nvidia-graphics-drivers-390_390.157-0ubuntu6.debdiff"
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/2019979/+attachment/5673790/+files/nvidia-graphics-drivers-390_390.157-0ubuntu6.debdiff
--
You received this bug notification because you are a mem
Public bug reported:
[Impact]
/var/lib/dkms/nvidia/390.157/build/nvidia/nv-mmap.c: In function
‘nvidia_mmap_helper’:
/var/lib/dkms/nvidia/390.157/build/nvidia/nv-mmap.c:474:23: error: assignment
of read-only member ‘vm_flags’
474 | vma->vm_flags |= VM_IO;
|
Temporary workaround:
$ sudo apt-get autoremove
will fix your installation issue.
--
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/2017685
Title:
package linux-generic 6.2.0.20.20 failed
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:
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:
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:
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:
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:
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
With the broadcom-sta-dkms package installed, can you blacklist bcma,
reboot, and see if wireless shows up?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/2013236
Title:
Failed
These are the size of linux-kvm debs at the time of this writing[1]:
linux-buildinfo-6.2.0-1003-kvm_6.2.0-1003.3_amd64.deb (397.9 KiB)
linux-headers-6.2.0-1003-kvm_6.2.0-1003.3_amd64.deb (15.9 MiB)
linux-image-unsigned-6.2.0-1003-kvm-dbgsym_6.2.0-1003.3_amd64.ddeb (203.2
MiB)
linu
New drivers are available in proposed (e.g. 515.105.01-0ubuntu1), can
you test them and and report your results?
Thanks!
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed in Ubuntu.
https://bugs.launchpad.net/bugs/2012908
Titl
** Also affects: nvidia-graphics-drivers-515 (Ubuntu)
Importance: Undecided
Status: New
** Changed in: nvidia-graphics-drivers-515 (Ubuntu)
Status: New => In Progress
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux
** Changed in: nvidia-graphics-drivers-515 (Ubuntu)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed in Ubuntu.
https://bugs.launchpad.net/bugs/2012908
Title:
nvidia driver 515 fails t
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:
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:
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:
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:
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:
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
** Also affects: linux-oem-5.14 (Ubuntu)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: linux-oem-5.14 (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: linux-oem-5.17 (Ubunt
Public bug reported:
[Impact]
During AMD Genoa development, the datacenter team identified performance
regressions that were root caused in the amd-pstate driver. A first
round of fixes already landed upstream (v6.1-rc7) in the amd-pstate
driver, and should be backported to all the affected kerne
** Description changed:
[Issue]
- The linux-kvm wasn't using annotations from debian.master, and that
- induced a skew in important options between master and kvm.
+ linux-kvm wasn't using annotations from debian.master, and that induced a
+ skew in fundamental config options between main and
Public bug reported:
[Issue]
The linux-kvm wasn't using annotations from debian.master, and that
induced a skew in important options between master and kvm.
[Fix]
Apply the attached series.
[How to test]
Crank updateconfigs shouldn't report any check-config error.
** Affects: linux-kvm (Ubun
1 - 100 of 668 matches
Mail list logo
