** 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
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
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
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
Related: https://github.com/canonical/checkbox/issues/889
** Changed in: linux-signed-oem-6.5 (Ubuntu)
Status: New => Invalid
** Bug watch added: github.com/canonical/checkbox/issues #889
https://github.com/canonical/checkbox/issues/889
--
You received this bug notification because
Public bug reported:
Checkbox job "
com.canonical.certification::graphics/2_valid_opengl_renderer_PCI_ID_0x743f"
fails with error:
```
Setting up PRIME GPU offloading for AMD discrete GPU
OpenGL renderer string: Mesa Intel(R) Graphics (RPL-S)
ERROR: renderer is Intel when DRI_PRIME=1
```
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.
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:
Public bug reported:
External USB storage is not detected when running the beta Ubuntu Core
20 image [0] on CM4. Same happens with the armhf image.
The issue has been discovered using Checkbox - the failing test is
usb/storage-detect [1].
Step to reproduce:
- Provision the CM4 with [0]
- Plug a
** 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
** 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
** 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
** 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
** 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:
** 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
** 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
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
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
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
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
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
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
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
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
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
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 |
Ok the patch fixes the problem! I can see a stack trace still but it's
probably related to
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2036742/comments/13
?
Thanks!
** Attachment added: "dmesg-mantic-6.5.3-patched"
With `amdgpu.aspm=0` it works fine.
** Attachment added: "dmesg-focal-5.14-rc2-aspm0"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2036742/+attachment/5711750/+files/dmesg-focal-5.14-rc2-aspm0
--
You received this bug notification because you are a member of Kernel
Packages, which
I can't install Jammy because I can't see the installer, so I did the
test on Focal.
5.13.19 works, 5.14-rc2 fails (same for 5.14.0). Dmesg attached.
** Attachment added: "dmesg-focal-mainline.zip"
On Focal, it also works with 5.14.0-1059. dmesg attached.
** Attachment added: "dmesg-5.14oem"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2036742/+attachment/5709895/+files/dmesg-5.14oem
--
You received this bug notification because you are a member of Kernel
Packages, which is
> Thanks for checking. So good to know it hasn't regressed from stable
in 5.10. Can you redo your 5.15 test with the firmware in place so we
can see if we're OK there or not?
Unfortunately still no luck. I booted Focal with 5.10 OEM and then
rebooted to Mantic with 5.15.134. The screen freezes at
** 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:
** 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
** 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
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
** 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
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.
**
> Can you see if it keeps working with latest 5.10 OEM? 1057 it looks
like is newest.
Yes, it still works with that version.
** Attachment added: "dmesg-5.10.0-1057"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2036742/+attachment/570/+files/dmesg-5.10.0-1057
--
You received
The setup involves a custom KVM indeed, I'll attach the EDID file
involved in this setup.
I tested everything as requested, no luck unfortunately. The working
configuration, which I've now replicated, is involving the OEM image for
Ubuntu 20.04 with which the device has been certified.
Please
** Description changed:
[Impact]
- Booting from USB the latest Mantic Desktop canary image (2023-09-19),
+ Booting from USB the latest Mantic Desktop daily image (2023-09-20),
just after the initial logs, nothing is displayed on screen. The system
is still alive since _autoinstall_ works
Public bug reported:
[Impact]
Booting from USB the latest Mantic Desktop canary image (2023-09-19),
just after the initial logs, nothing is displayed on screen. The system
is still alive since _autoinstall_ works as intended. Once provisioned,
the problem is still present.
```
[4.189404]
Public bug reported:
I just upgrade Ubuntu fro 18.04 to 22.04
with Kernel new kernel 6.2.0.31 VIA USB 3.0 controller fails with
../..
[ 2812.150794] xhci_hcd :02:00.0: WARNING: Host System Error
[ 2812.150848] xhci_hcd :02:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT
domain=0x0011
** 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
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"
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"
** 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
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
** 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
** 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:
** 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
** 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:
** 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
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
** 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:
** 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
** 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:
** 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
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 |
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
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
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
** 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
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
** 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
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
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
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
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
** 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
** 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
** 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
+
** 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:
** 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.
** 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
** 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
** 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
** 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
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
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
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
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
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
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
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
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)
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
** 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
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
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
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
1 - 100 of 779 matches
Mail list logo
