Processed: Re: Bug#1029584: Info received (Bug#1029584: Info received (Bug#1029584: Acknowledgement (linux-image-6.1.0-1-amd64: Mouswheel reports way too many events with Debian kernel config)))

Processing control commands: > tag -1 upstream Bug #1029584 [src:linux] linux-image-6.1.0-1-amd64: Mouswheel reports way too many events with Debian kernel config Added tag(s) upstream. > forwarded -1 https://gitlab.freedesktop.org/libinput/libinput/-/issues/852 Bug #1029584 [src:linux] linux-ima

Bug#1029584: Info received (Bug#1029584: Info received (Bug#1029584: Acknowledgement (linux-image-6.1.0-1-amd64: Mouswheel reports way too many events with Debian kernel config)))

Control: tag -1 upstream Control: forwarded -1 https://gitlab.freedesktop.org/libinput/libinput/-/issues/852 On 25 January 2023 17:52:10 CET, Tobias Klausmann wrote: >Also reported to libinput upstream: > >https://gitlab.freedesktop.org/libinput/libinput/-/issues/852 Thanks! Updated bug metada

Re: Shim and secure boot status, leading up to bookworm

Hi Jeremy, On Wed, Jan 25, 2023 at 12:40:07PM -0700, Jeremy Hall wrote: > >When things get built, will there be a path forward for people who >might need grub modules like serial console for accessibility reasons? The serial module has already been added to the signed grub binary a while back (2.

Re: Shim and secure boot status, leading up to bookworm

Hey Antonio, On Wed, Jan 25, 2023 at 04:17:50PM -0300, Antonio Terceiro wrote: >On Wed, Jan 25, 2023 at 06:11:45PM +, Steve McIntyre wrote: >> >> The MS and cert issues are now both resolved, and I'm now working on a >> shim *15.7* upload. There's a little more work and testing to do, but >>

linux-signed-i386_5.10.162+1_source.changes ACCEPTED into proposed-updates

Thank you for your contribution to Debian. Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 21 Jan 2023 15:35:48 +0100 Source: linux-signed-i386 Architecture: source Version: 5.10.162+1 Distribution: bullseye-security Urgency: high Maintainer: Debian Kernel Team

linux-signed-arm64_5.10.162+1_source.changes ACCEPTED into proposed-updates

Thank you for your contribution to Debian. Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 21 Jan 2023 15:35:48 +0100 Source: linux-signed-arm64 Architecture: source Version: 5.10.162+1 Distribution: bullseye-security Urgency: high Maintainer: Debian Kernel Tea

linux-signed-amd64_5.10.162+1_source.changes ACCEPTED into proposed-updates

Thank you for your contribution to Debian. Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 21 Jan 2023 15:35:48 +0100 Source: linux-signed-amd64 Architecture: source Version: 5.10.162+1 Distribution: bullseye-security Urgency: high Maintainer: Debian Kernel Tea

linux_5.10.162-1_source.changes ACCEPTED into proposed-updates

Thank you for your contribution to Debian. Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 21 Jan 2023 15:35:48 +0100 Source: linux Architecture: source Version: 5.10.162-1 Distribution: bullseye-security Urgency: high Maintainer: Debian Kernel Team Changed-By

Re: Shim and secure boot status, leading up to bookworm

Hi, When things get built, will there be a path forward for people who might need grub modules like serial console for accessibility reasons? Thanks _J On 1/25/23, Antonio Terceiro wrote: > On Wed, Jan 25, 2023 at 06:11:45PM +, Steve McIntyre wrote: >> Hey all! >> >> Here's a status update

Bug#1013249: marked as done (virtio_ring: module verification failed: signature and/or required key missing - tainting kernel)

Your message dated Wed, 25 Jan 2023 19:47:08 + with message-id and subject line Bug#825141: fixed in linux 5.10.162-1 has caused the Debian Bug report #825141, regarding virtio_ring: module verification failed: signature and/or required key missing - tainting kernel to be marked as done. Thi

Bug#825141: marked as done (dasd_mod: module verification failed: signature and/or required key missing - tainting kernel)

Your message dated Wed, 25 Jan 2023 19:47:08 + with message-id and subject line Bug#825141: fixed in linux 5.10.162-1 has caused the Debian Bug report #825141, regarding dasd_mod: module verification failed: signature and/or required key missing - tainting kernel to be marked as done. This m

Bug#1027430: marked as done (linux-image-5.10.0-20-amd64: No sound on Lenovo IdeaPad 3)

Your message dated Wed, 25 Jan 2023 19:47:08 + with message-id and subject line Bug#1027430: fixed in linux 5.10.162-1 has caused the Debian Bug report #1027430, regarding linux-image-5.10.0-20-amd64: No sound on Lenovo IdeaPad 3 to be marked as done. This means that you claim that the proble

Bug#1027483: marked as done (linux-image-5.10.0-20-amd64: sound with firmware-sof-intel on Intel Lake stops working with newer kernel)

Your message dated Wed, 25 Jan 2023 19:47:08 + with message-id and subject line Bug#1027483: fixed in linux 5.10.162-1 has caused the Debian Bug report #1027483, regarding linux-image-5.10.0-20-amd64: sound with firmware-sof-intel on Intel Lake stops working with newer kernel to be marked as

Bug#1027325: marked as done (/usr/src/linux-headers-5.10.0-20-common/scripts/pahole-flags.sh: inaccessible or not found)

Your message dated Wed, 25 Jan 2023 19:47:08 + with message-id and subject line Bug#1008501: fixed in linux 5.10.162-1 has caused the Debian Bug report #1008501, regarding /usr/src/linux-headers-5.10.0-20-common/scripts/pahole-flags.sh: inaccessible or not found to be marked as done. This me

Bug#1008501: marked as done (pahole-flags.sh: inaccessible or not found)

Your message dated Wed, 25 Jan 2023 19:47:08 + with message-id and subject line Bug#1008501: fixed in linux 5.10.162-1 has caused the Debian Bug report #1008501, regarding pahole-flags.sh: inaccessible or not found to be marked as done. This means that you claim that the problem has been deal

Re: Shim and secure boot status, leading up to bookworm

On Wed, Jan 25, 2023 at 06:11:45PM +, Steve McIntyre wrote: > Hey all! > > Here's a status update and plans for SB and shim. If any of this is > unclear or you have doubts, please say! > > We currently have *signed* shim *15.4* packages in the archive, for > all of buster, bullseye, bookworm

Bug#1029270: linux-image-6.1.0-2-686-pae fails to boot in qemu

Hi, I investigated this a bit more and can confirm that this worked: linux-image-6.1.0-1-686-pae 6.1.4-1 while this one does not: linux-image-6.1.0-2-686-pae 6.1.7-1 To figure out where the regression comes from, I built 6.1.7 from git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git

Shim and secure boot status, leading up to bookworm

Hey all! Here's a status update and plans for SB and shim. If any of this is unclear or you have doubts, please say! We currently have *signed* shim *15.4* packages in the archive, for all of buster, bullseye, bookworm and sid. That works OK at the moment, but is getting old (July 2021) and needs

Bug#1029584: Info received (Bug#1029584: Info received (Bug#1029584: Acknowledgement (linux-image-6.1.0-1-amd64: Mouswheel reports way too many events with Debian kernel config)))

Hi! Also reported to libinput upstream: https://gitlab.freedesktop.org/libinput/libinput/-/issues/852

Bug#1029584: Info received (Bug#1029584: Acknowledgement (linux-image-6.1.0-1-amd64: Mouswheel reports way too many events with Debian kernel config))

Hi! After some digging, I have found the kernel option/mmodule that causes this: HID_LOGITECH_HIDPP. I presume my mouse (Logitech 903) is handled by this module (hid_logitech_hidpp.ko), though it's not strictly needed. Things that work to make the original problem go away: - Build a kernel with

Bug#1029602: vmwgfx: kernel oops when using fbterm in vmware

Did some simple debugging on fbterm just now, and I found out that kernel oops when fbterm running `Screen::move()` () The most suspicious function inside is setupOffset(), which calls an ioctl(), setting yoffset: ``` void FbDe

Bug#1029602: vmwgfx: kernel oops when using fbterm in vmware

Control: found -1 5.10.162-1 On Wednesday, 25 January 2023 11:18:35 CET Keyu Tao wrote: > [ 214.783069] CPU: 0 PID: 372 Comm: kworker/0:4 Kdump: loaded Not tainted > 5.10.0-21-amd64 #1 Debian 5.10.162-1 signature.asc Description: This is a digitally signed message part.

Processed: Re: Bug#1029602: vmwgfx: kernel oops when using fbterm in vmware

Processing control commands: > found -1 5.10.162-1 Bug #1029602 [src:linux] vmwgfx: kernel oops when using fbterm in vmware Marked as found in versions linux/5.10.162-1. -- 1029602: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1029602 Debian Bug Tracking System Contact ow...@bugs.debian.org

Bug#1027483: thank you!

Hi Tomas, On Wed, Jan 25, 2023 at 10:42:50AM +0100, Tomas Pospisek wrote: > and I guess #1027483 can be closed as it is still open along with #1027430 ? Thanks for confirming. It does not need to be manually closed, as I added bug closer in the debian/changelog accordingly. I twill happens as soo

Bug#1029602: vmwgfx: kernel oops when using fbterm in vmware

Source: linux Severity: normal X-Debbugs-Cc: taok...@outlook.com Dear Maintainer, It seems that fbterm triggers an out-of-bound memory write (memcpy) when vmwgfx loads. Dmesg oops message: [ 214.780971] BUG: unable to handle page fault for address: ae3dc1171000 [ 214.781348] #PF: supervi

Bug#1027483: thank you!

Woah guys, a new Debian stable kernel came my way and finally sound works again consistently. Many, many, many thanks to you for bisecting, patching and shipping the fix. Muito, muito obrigado! *t

Bug#1027483: thank you!

and I guess #1027483 can be closed as it is still open along with #1027430 ? On Wed, 25 Jan 2023, Tomas Pospisek wrote: Woah guys, a new Debian stable kernel came my way and finally sound works again consistently. Many, many, many thanks to you for bisecting, patching and shipping the fix. Mu