FIX (Maybe?)
I put the keyboard aside for (about) a week. During this time the laptop when
through a usual
'apt update/apt upgrade' process and reboot.
When I tried to subsequently re-pair the keyboard, the 'passcode dialog' stayed
visible,
and the keyboard paired.
Considerations:
- This
I am seeing this bug in Ubuntu 23.10.
bluez 5.68-0ubuntu1.1
Hardware: Logi POP Keys
https://www.logitech.com/en-au/products/keyboards/pop-keys-wireless-mechanical.920-011226.html
I have managed to have it working in the past, but the 6-digit code pop-
up disappears very quickly (as described,
Related to https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/241000
--
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/2052492
Title:
Pairing: passcode dialogue disappears in <1 second
Some things that I have tried which didn't immediately fix the problem.
Resetting the bluez package did NOT fix the problem.
Removing the bluez package(s), removing /var/lib/bluetooth and re-installing.
sudo apt remove --purge bluez
rm -rf /var/lib/bluetooth
sudo apt install bluez
Public bug reported:
UPDATE: I am creating this bug in case it comes back again. My Fix was to put
the bluetooth keyboard
aside for a week (not use it), then reconnect after the laptop had been
rebooted after an update
and daily use.
I will post the things that I tried, just in case:
1)
- This occurs on my daily use laptop which has been upgraded from 23.04
-> 23.10
- I have just tried to pair on another laptop with freshly installed 23.10
- The dialog displaying the pairing code persists
and I can pair correctly with same keyboard (it can pair with 3 separate
devices)
Tested on jammy on an older version 5.15.67:
installed linux-tools-gcp
And then linux-tools-kvm
Unpacking linux-kvm-tools-5.15.0-1049 (5.15.0-1049.54) ...
dpkg: error processing archive
/var/cache/apt/archives/linux-kvm-tools-5.15.0-1049_5.15.0-1049
.54_amd64.deb (--unpack):
trying to overwrite
** Tags removed: verification-needed-lunar-linux-azure
verification-needed-lunar-linux-gcp verification-needed-lunar-linux-kvm
verification-needed-lunar-linux-riscv verification-needed-lunar-linux-starfive
** Tags added: verification-done-lunar-linux-azure
verification-done-lunar-linux-gcp
** Tags removed: verification-needed-jammy-linux
verification-needed-jammy-linux-intel-iotg verification-needed-mantic-linux
** Tags added: verification-done-jammy-linux
verification-done-jammy-linux-intel-iotg verification-done-mantic-linux
--
You received this bug notification because you
** Tags removed: verification-needed-jammy-linux-oracle
verification-needed-mantic-linux-oracle
** Tags added: verification-done-jammy-linux-oracle
verification-done-mantic-linux-oracle
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
** Tags removed: verification-needed-lunar-linux
verification-needed-mantic-linux
** Tags added: verification-done-lunar-linux verification-done-mantic-linux
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** Tags removed: verification-needed-jammy-linux
verification-needed-jammy-linux-ibm-gt-fips
verification-needed-jammy-linux-intel-iotg verification-needed-mantic-linux
** Tags added: verification-done-jammy-linux
verification-done-jammy-linux-ibm-gt-fips
** Tags removed: verification-needed-mantic-linux
** Tags added: verification-done-mantic-linux
--
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/2039151
Title:
Support speaker
** Tags removed: verification-needed-mantic-linux
** Tags added: verification-done-mantic-linux
--
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/2038263
Title:
Add SoF topology
** Tags removed: verification-needed-mantic-linux
** Tags added: verification-done-mantic-linux
--
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/2042912
Title:
System hang after
** Tags removed: verification-needed-lunar-linux
verification-needed-mantic-linux
** Tags added: verification-done-lunar-linux verification-done-mantic-linux
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.5 in Ubuntu.
** Tags removed: verification-needed-mantic-linux
** Tags added: verification-done-mantic-linux
--
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/2041613
Title:
correct cephfs pull request
** Tags removed: verification-needed-mantic-linux
** Tags added: verification-done-mantic-linux
--
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/2043730
Title:
Update io_uring to 6.6
linux-image-6.5.0-14-generic does not display this behaviour so this is
clearly a regression.
--
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/2052411
Title:
thunderbolt: interrupt
A just finished test install of the (same) Ubuntu 22.04.1 Desktop ISO
now resulted in the gcc-12 being automatically installed, and the Nvidia
545 driver modules successfully compiling. After a fresh install, set up
wireless, installed build-essential, and then used software &
Updates/Additional
Noble got updated: https://launchpad.net/ubuntu/+source/linux-
firmware/20240202.git36777504-0ubuntu1
Still waiting for others.
** Changed in: linux-firmware (Ubuntu Noble)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages,
Public bug reported:
Apply patches to linux-nvidia-tegra and linux-nvida-tegra-igx.
** Affects: linux-nvidia-tegra (Ubuntu)
Importance: Undecided
Status: New
** Affects: linux-nvidia-tegra-igx (Ubuntu)
Importance: Undecided
Status: New
** Also affects:
** Description changed:
[Feature Description]
Use the powercap/idle-inject framework for intel Power clamp driver.
Allow CPU mask and max idle percent as module parameter. This way way driver
can be used for LPM mode in MTL.
-
- Target Kernel: 6.3
- Target Release: 23.10
-
[HW/SW
** Changed in: linux-gcp (Ubuntu Jammy)
Status: New => In Progress
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-gcp in Ubuntu.
https://bugs.launchpad.net/bugs/2052451
Title:
Incorrect argument to
Public bug reported:
[Impact]
* Oracle requested 64k page size flavour.
[Fix]
* Add flavour and configs for 64k flavour
[Test Case]
* Compile tested
* Boot tested
[Where things could go wrong]
* Low chance of regression. Isolated logic fix.
[Other Info]
* SF #00377602
** Affects:
Public bug reported:
Unplugging an exteranal usb-c monitor caused the GPU to crash - the
screen went white and unresponsive, reboot was required for the machine
to become usable.
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: linux-image-6.6.0-14-generic 6.6.0-14.14
ProcVersionSignature:
** Attachment added: "dmesg from the time of the crash"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2052467/+attachment/5744733/+files/journalctl-last-boot.log
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** Changed in: linux-gcp (Ubuntu Jammy)
Assignee: (unassigned) => John Cabaj (john-cabaj)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-gcp in Ubuntu.
https://bugs.launchpad.net/bugs/2052451
Title:
Incorrect argument to
Prior to version 5.15.0-1008.8, the Tegra out-of-tree modules were built
as part of the main kernel build. This caused the module ABI check to
fail when the out-of-tree modules were not built in the case where the
DKMS package containing these modules is missing.
As of version 5.15.0-1008.8, the
Mike and I have posted Disclaimers to the users on Jammy **Warning of
potential breakage with the added PPA
Mike has also included some very straight forward work-around's with The
*Warning* to users on 22.04 until the fix is pushed to the users.
--
You received this bug notification because
Ran ./io_uring_open_close_audit_hang --directory /tmp/deleteme --count 1 on
6.5.0-17-generic
and it finished
** Tags removed: verification-needed-lunar-linux
verification-needed-mantic-linux
** Tags added: verification-done-lunar-linux verification-done-mantic-linux
--
You received this
Dan Clash, apologize for the late reply. Next time feel free to test it since
you know the details better than anyone. Just use the latest version in
proposed.
But providing the test info was really useful as I managed to test it without
spending time on it, so thanks for that :)
--
You
** Changed in: linux-oem-6.1 (Ubuntu Jammy)
Status: In Progress => Fix Committed
--
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/2051050
Title:
Audio balancing setting
I finally managed to fix this using the answer linked here:
https://askubuntu.com/questions/1500474/cant-suspend-sleep-after-
upgrade-to-23-10/1502550#1502550. It was due to some broken nvidia-
related symlinks.
--
You received this bug notification because you are a member of Kernel
Packages,
** Changed in: linux-oem-6.1 (Ubuntu Jammy)
Status: In Progress => Fix Committed
--
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/2051334
Title:
There is sound from the
** Also affects: linux-azure (Ubuntu Mantic)
Importance: Undecided
Status: New
** Also affects: linux-azure (Ubuntu Jammy)
Importance: Undecided
Status: New
** Changed in: linux-azure (Ubuntu Jammy)
Importance: Undecided => High
** Changed in: linux-azure (Ubuntu Jammy)
** Tags removed: verification-needed-mantic-linux
** Tags added: verification-done-mantic-linux
--
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/2044096
Title:
Support Cirrus
While the above MP is now merged, I still see additional potential races
in the code. For example, anything calling mount_partition() for the
first partition, and also maybe bug 2030771. I don't see a good way to
solve that w/o `udevadm lock` because these functions don't currently
know what the
Looks alright to me
...
# Compress kernel modules, on mantic+
find debian/linux-buildinfo-6.5.0-20-generic -name '*.ko' -print0 | xargs -0
-n1 -P 4 -r zstd -19 --quiet --rm
dh_fixperms -plinux-buildinfo-6.5.0-20-generic -X/boot/
...
@mkukri ---
>>>
The question is, are we going to backport the fix to 2.06 and push that to the
updates channel, or can this wait for the 2.12 SRU sometimes after April?
>>>
What does that mean?
Option #1 -- The cherry picked Grub2 2.12 ZFS related commit code gets
applied to Grub2 2.06 as a
Public bug reported:
SRU Justification
[Impact]
Microsoft requested the addition of 3 patches in LP: #2045069. A
regression was discovered in Focal.
[Fix]
hv_netvsc: Register VF in netvsc_probe if NET_DEVICE_REGISTER missed
hv_netvsc: Fix race condition between netvsc_probe and netvsc_remove
** Description changed:
[Impact]
* Google requested fix to notify_page_enc_status_changed() passing
incorrect argument.
[Fix]
- * Include change from upstream 064ce6c550a06
+ * 27ba8c7 modified notify_page_enc_status_changed(), when it should not
+ have
[Test Case]
*
** 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:
Public bug reported:
[Impact]
* Google requested fix to notify_page_enc_status_changed() passing
incorrect argument.
[Fix]
* Include change from upstream 064ce6c550a06
[Test Case]
* Compile tested
* Boot tested
* Tested by Google
[Where things could go wrong]
* Low chance of regression.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: systemd (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** Tags removed: verification-needed-jammy-linux-azure
** Tags added: verification-done-jammy-linux-azure
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https://bugs.launchpad.net/bugs/2039208
Title:
Azure:
** Tags removed: verification-needed-jammy-linux-azure
verification-needed-mantic-linux-azure
** Tags added: verification-done-jammy-linux-azure
verification-done-mantic-linux-azure
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
** Tags removed: verification-needed-mantic-linux-aws
** Tags added: verification-done-mantic-linux-aws
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-aws in Ubuntu.
https://bugs.launchpad.net/bugs/2045428
Title:
AWS: Set
** Tags added: patch
--
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/2052420
Title:
nvidia-dkms-* FTBS with linux 6.8
Status in nvidia-graphics-drivers-470
Public bug reported:
Would it be possible to update the wireless-regdb on all active ubuntu releases
to the latest upstream (2024-01.23) release? New regulations have been
published. One of those is the 6GHz Wifi in Switzerland.
The current package, 2022.06.06 is quite outdated.
With an update
*** This bug is a duplicate of bug 2048183 ***
https://bugs.launchpad.net/bugs/2048183
** This bug is no longer a duplicate of bug 2044003
Don't produce linux-*-cloud-tools-common, linux-*-tools-common and
linux-*-tools-host binary packages
** This bug has been marked a duplicate of bug
*** This bug is a duplicate of bug 2048183 ***
https://bugs.launchpad.net/bugs/2048183
** No longer affects: linux-bluefield (Ubuntu)
** No longer affects: linux-hwe-5.15 (Ubuntu)
** No longer affects: linux-bluefield (Ubuntu Jammy)
** No longer affects: linux-hwe-5.15 (Ubuntu Focal)
**
** Description changed:
- This is a duplicate bug report for bug 2044003. All duplicates are
- linked to this bug because they cannot be linked to 2044003 (LP times
- out due to too many bug tasks, sigh). See bug 2008514 for that problem.
+ [Impact]
- Problem: Some kernels incorrectly provide
Public bug reported:
[Impact]
Some kernels produce a linux-*-source- binary deb package. That
is all wrong and confusing, only the primary/main linux source package
should produce that package.
[Test Case]
Check list of built binary packages in LP and verify the package is not
built.
[Where
Also tested on hwe-6.5 and lowlatency-hwe-6.5.
Installing linux-tools-common will install hwdata
--
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/2039439
Title:
usbip: error: failed to
Marking all these derivatives as verified since the main ones are verified.
I need to check why these were triggered in the first place.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** 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
All autopkgtests for the newly accepted linux-meta-oem-6.1 (6.1.0.1032.33) for
jammy have finished running.
The following regressions have been reported in tests triggered by the package:
snapd/2.58+22.04.1 (amd64)
Please visit the excuses page listed below and investigate the failures,
All autopkgtests for the newly accepted linux-meta-oem-6.1 (6.1.0.1032.33) for
jammy have finished running.
The following regressions have been reported in tests triggered by the package:
snapd/2.58+22.04.1 (amd64)
Please visit the excuses page listed below and investigate the failures,
** Tags removed: verification-needed-lunar-linux-starfive
verification-needed-mantic-linux-azure verification-needed-mantic-linux-gcp
verification-needed-mantic-linux-lowlatency
** Tags added: verification-done-lunar-linux-starfive
verification-done-mantic-linux-azure
Public bug reported:
no touchpad
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: linux-image-6.6.0-14-generic 6.6.0-14.14
ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3
Uname: Linux 6.6.0-14-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.27.0-0ubuntu6
** Tags removed: verification-needed-jammy-linux
verification-needed-jammy-linux-ibm-gt-fips
verification-needed-jammy-linux-intel-iotg verification-needed-mantic-linux
** Tags added: verification-done-jammy-linux
verification-done-jammy-linux-ibm-gt-fips
jammy:lowlatency-hwe-6.5
modprobe: FATAL: Module shiftfs not found in directory
/lib/modules/6.5.0-14-lowlatency
jammy:hwe-6.5
modprobe: FATAL: Module shiftfs not found in directory
/lib/modules/6.5.0-17-generic
** Tags removed: verification-needed-mantic-linux-azure
Same for lowlatency-hwe-6.5
** Tags removed: verification-needed-jammy-linux-hwe-6.5
verification-needed-jammy-linux-lowlatency-hwe-6.5
** Tags added: verification-done-jammy-linux-hwe-6.5
verification-done-jammy-linux-lowlatency-hwe-6.5
** Tags removed:
Same for nvidia-6.5
--
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/2036587
Title:
[Mediatek] mt8195-demo: enable CONFIG_MTK_IOMMU as module for
multimedia and PCIE peripherals
Status
jammy:hwe-6.5
CONFIGS/arm64-config.flavour.generic-64k:11066:CONFIG_IOMMU_IO_PGTABLE_ARMV7S=y
CONFIGS/arm64-config.flavour.generic:11071:CONFIG_IOMMU_IO_PGTABLE_ARMV7S=y
CONFIGS/arm64-config.flavour.generic:11096:CONFIG_MTK_IOMMU=m
CONFIGS/arm64-config.flavour.generic-64k:11091:CONFIG_MTK_IOMMU=m
mantic:linux
CONFIGS/arm64-config.flavour.generic:11096:CONFIG_MTK_IOMMU=m
CONFIGS/arm64-config.flavour.generic-64k:11091:CONFIG_MTK_IOMMU=m
** Tags removed: verification-needed-mantic-linux
** Tags added: verification-done-mantic-linux
** Tags removed: verification-needed-mantic-linux-azure
focal:linux-intel-iotg-5.15
CONFIGS/amd64-config.flavour.intel-iotg-5.15:4039:CONFIG_WWAN=m
** Tags removed: verification-needed-focal-linux-intel-iotg-5.15
** Tags added: verification-done-focal-linux-intel-iotg-5.15
** Tags removed: verification-needed-focal-linux-gcp-tcpx
** Tags added:
jammy:linux-gkeop
CONFIGS/amd64-config.flavour.gkeop:4042:CONFIG_WWAN=m
** Tags removed: verification-needed-jammy-linux-azure-fips
** Tags added: verification-done-jammy-linux-azure-fips
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
jammy:linux-azure-fips
CONFIGS/arm64-config.flavour.azure-fips:3372:CONFIG_WWAN=m
CONFIGS/amd64-config.flavour.azure-fips:3226:CONFIG_WWAN=m
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
jammy:linux-intel-iotg
CONFIGS/amd64-config.flavour.intel-iotg:4043:CONFIG_WWAN=m
** Tags removed: verification-needed-jammy-linux-intel-iotg
** Tags added: verification-done-jammy-linux-intel-iotg
** Tags removed: verification-needed-focal-linux-gcp-5.15
** Tags added:
jammy:hwe-6.5
ONFIGS/riscv64-config.flavour.generic:3819:CONFIG_WWAN=m
CONFIGS/armhf-config.flavour.generic:4222:CONFIG_WWAN=y
CONFIGS/arm64-config.flavour.generic:4366:CONFIG_WWAN=m
CONFIGS/arm64-config.flavour.generic-64k:4363:CONFIG_WWAN=m
jammy:lowlatency-hwe-6.5
CONFIGS/amd64-config.flavour.lowlatency:4216:CONFIG_WWAN=m
CONFIGS/arm64-config.flavour.lowlatency:4371:CONFIG_WWAN=m
CONFIGS/arm64-config.flavour.lowlatency-64k:4368:CONFIG_WWAN=m
** Tags removed: verification-needed-jammy-linux-lowlatency-hwe-6.2
** Tags added:
jammy:linux-nvidia-6.5
CONFIGS/arm64-config.flavour.nvidia:4362:CONFIG_WWAN=m
CONFIGS/arm64-config.flavour.nvidia-64k:4359:CONFIG_WWAN=m
CONFIGS/amd64-config.flavour.nvidia:4211:CONFIG_WWAN=m
** Tags removed: verification-needed-jammy-linux-nvidia-tegra
mantic:linux-gcp
CONFIGS/amd64-config.flavour.gcp:4213:CONFIG_WWAN=m
CONFIGS/arm64-config.flavour.gcp:4434:CONFIG_WWAN=m
--
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/2033406
Title:
mantic:linux
CONFIGS/riscv64-config.flavour.generic:3822:CONFIG_WWAN=m
CONFIGS/armhf-config.flavour.generic:4222:CONFIG_WWAN=y
CONFIGS/arm64-config.flavour.generic:4366:CONFIG_WWAN=m
CONFIGS/arm64-config.flavour.generic-64k:4363:CONFIG_WWAN=m
mantic:linux-azure
CONFIGS/arm64-config.flavour.azure:4438:CONFIG_WWAN=m
CONFIGS/amd64-config.flavour.azure:3383:CONFIG_WWAN=m
** Tags removed: verification-needed-lunar-linux-riscv
verification-needed-lunar-linux-starfive verification-needed-mantic-linux
verification-needed-mantic-linux-azure
mantic:linux-laptop
CONFIGS/arm64-config.flavour.laptop:4367:CONFIG_WWAN=m
--
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/2033406
Title:
[SRU][J/L/M] UBUNTU: [Packaging] Make WWAN
Considering the lack of time and the no of VT needed, I won't boot the kernels
and then check if the module is there.
I'll generate the configs options and then if WWAN is m.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
mantic:linux-laptop
CONFIGS/arm64-config.flavour.laptop:3151:CONFIG_DM_VERITY_VERIFY_ROOTHASH_SIG=y
CONFIGS/arm64-config.flavour.laptop:3152:CONFIG_DM_VERITY_VERIFY_ROOTHASH_SIG_SECONDARY_KEYRING=y
--
You received this bug notification because you are a member of Kernel
Packages, which is
mantic:linux-gcp
CONFIGS/amd64-config.flavour.gcp:3080:CONFIG_DM_VERITY_VERIFY_ROOTHASH_SIG=y
CONFIGS/amd64-config.flavour.gcp:3081:CONFIG_DM_VERITY_VERIFY_ROOTHASH_SIG_SECONDARY_KEYRING=y
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
mantic:linux-azure
CONFIGS/amd64-config.flavour.azure:2785:CONFIG_DM_VERITY_VERIFY_ROOTHASH_SIG=y
CONFIGS/amd64-config.flavour.azure:2786:CONFIG_DM_VERITY_VERIFY_ROOTHASH_SIG_SECONDARY_KEYRING=y
** Tags removed: verification-needed-mantic-linux-azure
** Tags added:
jammy:nvidia-6.5
CONFIGS/amd64-config.flavour.nvidia:3079:CONFIG_DM_VERITY_VERIFY_ROOTHASH_SIG=y
CONFIGS/amd64-config.flavour.nvidia:3080:CONFIG_DM_VERITY_VERIFY_ROOTHASH_SIG_SECONDARY_KEYRING=y
** Tags removed: verification-needed-jammy-linux-nvidia-6.5
** Tags added:
Jammy:hwe-6.5
CONFIGS/amd64-config.flavour.generic:3079:CONFIG_DM_VERITY_VERIFY_ROOTHASH_SIG=y
CONFIGS/amd64-config.flavour.generic:3080:CONFIG_DM_VERITY_VERIFY_ROOTHASH_SIG_SECONDARY_KEYRING=y
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed
This bug VT is a mess.. Nevertheless.
Jammy:lowlatency-hwe-6.5
./amd64-config.flavour.lowlatency:3084:CONFIG_DM_VERITY_VERIFY_ROOTHASH_SIG=y
./amd64-config.flavour.lowlatency:3085:CONFIG_DM_VERITY_VERIFY_ROOTHASH_SIG_SECONDARY_KEYRING=y
** Tags removed:
** Changed in: linux-meta-azure (Ubuntu Lunar)
Status: New => Invalid
** Changed in: linux-meta-kvm (Ubuntu Jammy)
Status: New => Invalid
** Changed in: linux-meta-kvm (Ubuntu Kinetic)
Status: New => Invalid
** Changed in: linux-meta-kvm (Ubuntu Lunar)
Status: New =>
not really verified, but can't remove at this point anymore
** Tags removed: verification-needed-jammy-linux-oem-6.5
** Tags added: verification-done-jammy-linux-oem-6.5
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.5 in
Tested on multiple main kernels but also derivatives
** Tags removed: verification-needed-focal-linux
verification-needed-jammy-linux-ibm-gt-fips
verification-needed-jammy-linux-intel-iotg verification-needed-lunar-linux
** Tags added: verification-done-focal-linux
Public bug reported:
>From /var/log/kern.log :
Feb 5 11:01:59 nb-mpiccinini kernel: [ 8841.672031] i915 :00:02.0: [drm]
*ERROR* [CRTC:131:pipe B] flip_done timed out
2832 Feb 5 11:02:44 nb-mpiccinini kernel: [ 8886.728515] i915 :00:02.0:
[drm] *ERROR* flip_done timed out
2833 Feb 5
About the comment "users with a custom wsize", note that I didn't set a
custom wsize.
This is the script I am using to mount the SMB 1.0 shares:
https://github.com/rdiez/Tools/blob/master/MountWindowsShares/mount-
windows-shares-sudo.sh
There is no wsize parameter there. I did write above that
** 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
GRUB 2.12 isn't going into the updates channel anywhere at this point.
(It's going in proposed then release on Noble soon however)
The question is, are we going to backport the fix to 2.06 and push that
to the updates channel, or can this wait for the 2.12 SRU sometimes
after April?
It's good to
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
** Changed in: plymouth (Ubuntu)
Importance: Undecided => Medium
--
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/1970069
Many thanks for confirming this problem. I was worried that there might
be something wrong with the server, instead of with the Linux client.
In the meantime, I have posted about this to the linux-
c...@vger.kernel.org mailing list, so at least some people there are
already aware:
SMB 1.0 broken
95 matches
Mail list logo