Bug#979975: more info

dear maintainer, linux-image-5.10.0-2-amd64 (5.10.9.1) boots fine. Fulvio Ciriaco

Re: Bug#981442: apparmor: Please do not install by default or depend on python3

Hello, intrigeri, le lun. 01 févr. 2021 09:16:23 +0100, a ecrit: > Samuel Thibault (2021-01-31): > > As of Debian bullseye alpha3, apparmor is getting installed by default > > even in the base system, > > To be clear, in this context "base system" is d-i terminology, right? Yes. That's when one

Bug#979975: marked as done (linux-image-5.10.0-1-amd64: it does not boot)

Your message dated Mon, 01 Feb 2021 12:37:27 +0100 with message-id <2361360.OdQxPOZfLQ@bagend> and subject line Re: Bug#979975: more info has caused the Debian Bug report #979975, regarding linux-image-5.10.0-1-amd64: it does not boot to be marked as done. This means that you claim that the proble

linux_4.19.171-1_source.changes is NEW

Mapping stable-security to proposed-updates. binary:affs-modules-4.19.0-14-4kc-malta-di is NEW. binary:affs-modules-4.19.0-14-5kc-malta-di is NEW. binary:affs-modules-4.19.0-14-loongson-3-di is NEW. binary:affs-modules-4.19.0-14-octeon-di is NEW. binary:ata-modules-4.19.0-14-4kc-malta-di is NEW. bi

linux_4.19.171-2_source.changes is NEW

Mapping stable-security to proposed-updates. linux_4.19.171.orig.tar.xz is only available in NEW. Your package has been put into the NEW queue, which requires manual action from the ftpteam to process. The upload was otherwise valid (it had a good OpenPGP signature and file hashes are valid), so p

linux-latest_105+deb10u9_source.changes ACCEPTED into proposed-updates->stable-new

Mapping stable-security to proposed-updates. Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 30 Jan 2021 08:43:43 +0100 Source: linux-latest Architecture: source Version: 105+deb10u9 Distribution: buster-security Urgency: high Maintainer: Debian Kernel Team Chan

Which package is responsible for setting rlimits?

A recent regression in gnome-keyring (perhaps only on systems that use dbus-x11, it isn't completely clear to me yet) has prompted me to look at how rlimits work in Debian. It isn't clear to me which package is or should be responsible for choosing what arbitrary limits we use in practice. The ker

Re: Which package is responsible for setting rlimits?

On Mon, 01 Feb 2021 at 13:58:57 +, Simon McVittie wrote: > Rationale: on sysvinit or runit systems, pid 1 is very simple and is > unlikely to need to elevate any limits, but sysadmins are expected > to restart system services in an unpredictable execution environment > (certainly true for syste

linux-signed-arm64_4.19.171+2_source.changes is NEW

Mapping stable-security to proposed-updates. binary:ata-modules-4.19.0-14-arm64-di is NEW. binary:btrfs-modules-4.19.0-14-arm64-di is NEW. binary:cdrom-core-modules-4.19.0-14-arm64-di is NEW. binary:compress-modules-4.19.0-14-arm64-di is NEW. binary:crc-modules-4.19.0-14-arm64-di is NEW. binary:cry

linux-signed-i386_4.19.171+2_source.changes is NEW

Mapping stable-security to proposed-updates. binary:acpi-modules-4.19.0-14-686-di is NEW. binary:acpi-modules-4.19.0-14-686-pae-di is NEW. binary:ata-modules-4.19.0-14-686-di is NEW. binary:ata-modules-4.19.0-14-686-pae-di is NEW. binary:btrfs-modules-4.19.0-14-686-di is NEW. binary:btrfs-modules-4

linux-signed-i386_4.19.171+1_source.changes is NEW

Mapping stable-security to proposed-updates. binary:acpi-modules-4.19.0-14-686-di is NEW. binary:acpi-modules-4.19.0-14-686-pae-di is NEW. binary:ata-modules-4.19.0-14-686-di is NEW. binary:ata-modules-4.19.0-14-686-pae-di is NEW. binary:btrfs-modules-4.19.0-14-686-di is NEW. binary:btrfs-modules-4

linux-signed-amd64_4.19.171+2_source.changes is NEW

Mapping stable-security to proposed-updates. binary:acpi-modules-4.19.0-14-amd64-di is NEW. binary:ata-modules-4.19.0-14-amd64-di is NEW. binary:btrfs-modules-4.19.0-14-amd64-di is NEW. binary:cdrom-core-modules-4.19.0-14-amd64-di is NEW. binary:compress-modules-4.19.0-14-amd64-di is NEW. binary:cr

Re: Which package is responsible for setting rlimits?

> "Simon" == Simon McVittie writes: I'm assuming that the proposal is to change this for bookworm. It seems like it's too late in the process to change something like this for bullseye without more explicit and significant harm documented than you have given so far. Simon> Rationale: on

Re: Which package is responsible for setting rlimits?

On Mon, 01 Feb 2021 at 11:49:25 -0500, Sam Hartman wrote: > > "Simon" == Simon McVittie writes: > I'm assuming that the proposal is to change this for bookworm. I'm sorry, I don't have a concrete proposal, and I don't understand which package is meant to be responsible for this well enough to

Re: Which package is responsible for setting rlimits?

> "Simon" == Simon McVittie writes: Simon> On Mon, 01 Feb 2021 at 11:49:25 -0500, Sam Hartman wrote: >> > "Simon" == Simon McVittie writes: I'm >> assuming that the proposal is to change this for bookworm. Simon> I'm sorry, I don't have a concrete proposal, and I don't

Bug#981586: Bullseye armhf kernel for Raspberry Pi 4b does not boot

Package: linux-image-5.10.0-2-armmp Version: 5.10.9-1: armhf Package: linux-image-5.10.0-2-armmp-lpae Version: 5.10.9-1: armhf Analysis showed that it does reach init-top. But when usbcore and usbhid are loaded, peripherals like mouse and keyboard are not at all detected. When later usbhid, us

Bug#981588: linux-image-5.10.0-2-amd64: Using pen crashes system

Package: linux-image-5.10.0-2-amd64 Severity: important X-Debbugs-Cc: e...@wolke7.net Dear Maintainer, after installation of linux-image-5.10.0-2-amd64 (5.10.9-1) on a Lenovo X1 Yoga Gen5 touching the screen with the pen immediately crashes the system immediately and completely. It seems that

Re: please consider disabling obsolete crypto in 5.10 and later

Hi Ard, On Sat, Jan 30, 2021 at 04:41:16PM +0100, Ard Biesheuvel wrote: > L.S., > > This is a request to consider disabling obsolete crypto in 5.10 and > later Debian builds of the Linux kernel on any architecture. > > We are all familiar with the rigid rules when it comes to not breaking > user

Processed: reassign 981588 to 5.10.9-1

Processing commands for cont...@bugs.debian.org: > reassign 981588 5.10.9-1 Bug #981588 [linux-image-5.10.0-2-amd64] linux-image-5.10.0-2-amd64: Using pen crashes system Bug reassigned from package 'linux-image-5.10.0-2-amd64' to '5.10.9-1'. Warning: Unknown package '5.10.9-1' Warning: Unknown pa

Processed: reassign 981588 to src:linux

Processing commands for cont...@bugs.debian.org: > reassign 981588 src:linux 5.10.9-1 Bug #981588 {Done: Salvatore Bonaccorso } [5.10.9-1] linux-image-5.10.0-2-amd64: Using pen crashes system Warning: Unknown package '5.10.9-1' Bug reassigned from package '5.10.9-1' to 'src:linux'. Ignoring reque

Processed: closing 981588

Processing commands for cont...@bugs.debian.org: > close 981588 5.10.12-1 Bug #981588 {Done: Salvatore Bonaccorso } [src:linux] linux-image-5.10.0-2-amd64: Using pen crashes system Marked as fixed in versions linux/5.10.12-1. Bug #981588 {Done: Salvatore Bonaccorso } [src:linux] linux-image-5.10

Bug#980785: linux-image-5.10.0-1-arm64: vc4.ko garbles screen ouput on raspi 4B

Patches are incorporated into the 5.10-stable branch as https://git.kernel.org/pub/scm/linux/kernel/git/stable/stable-queue.git/diff/queue-5.10/drm-vc4-correct-lbm-size-and-calculation.patch?id=138ad5c64ba368c5e077b8c178c47f12b29b8701 https://git.kernel.org/pub/scm/linux/kernel/git/stable/stable-

Processing of linux-signed-amd64_5.10.12+1_source.changes

linux-signed-amd64_5.10.12+1_source.changes uploaded successfully to localhost along with the files: linux-signed-amd64_5.10.12+1.dsc linux-signed-amd64_5.10.12+1.tar.xz Greetings, Your Debian queue daemon (running on host usper.debian.org)

linux-signed-amd64_5.10.12+1_source.changes is NEW

Mapping sid to unstable. binary:acpi-modules-5.10.0-3-amd64-di is NEW. binary:ata-modules-5.10.0-3-amd64-di is NEW. binary:btrfs-modules-5.10.0-3-amd64-di is NEW. binary:cdrom-core-modules-5.10.0-3-amd64-di is NEW. binary:crc-modules-5.10.0-3-amd64-di is NEW. binary:crypto-dm-modules-5.10.0-3-amd64

Processing of linux-signed-arm64_5.10.12+1_source.changes

linux-signed-arm64_5.10.12+1_source.changes uploaded successfully to localhost along with the files: linux-signed-arm64_5.10.12+1.dsc linux-signed-arm64_5.10.12+1.tar.xz Greetings, Your Debian queue daemon (running on host usper.debian.org)

linux-signed-arm64_5.10.12+1_source.changes is NEW

Mapping sid to unstable. binary:ata-modules-5.10.0-3-arm64-di is NEW. binary:btrfs-modules-5.10.0-3-arm64-di is NEW. binary:cdrom-core-modules-5.10.0-3-arm64-di is NEW. binary:crc-modules-5.10.0-3-arm64-di is NEW. binary:crypto-dm-modules-5.10.0-3-arm64-di is NEW. binary:crypto-modules-5.10.0-3-arm

Processing of linux-signed-i386_5.10.12+1_source.changes

linux-signed-i386_5.10.12+1_source.changes uploaded successfully to localhost along with the files: linux-signed-i386_5.10.12+1.dsc linux-signed-i386_5.10.12+1.tar.xz Greetings, Your Debian queue daemon (running on host usper.debian.org)

linux-signed-i386_5.10.12+1_source.changes is NEW

Mapping sid to unstable. binary:acpi-modules-5.10.0-3-686-di is NEW. binary:acpi-modules-5.10.0-3-686-pae-di is NEW. binary:ata-modules-5.10.0-3-686-di is NEW. binary:ata-modules-5.10.0-3-686-pae-di is NEW. binary:btrfs-modules-5.10.0-3-686-di is NEW. binary:btrfs-modules-5.10.0-3-686-pae-di is NEW

Bug#970736: marked as done (cdc_ncm_fill_tx_frame calls memset with huge length when called from cdc_mbim_tx_fixup)

Your message dated Tue, 02 Feb 2021 06:47:08 + with message-id and subject line Bug#970736: fixed in linux 4.19.171-1 has caused the Debian Bug report #970736, regarding cdc_ncm_fill_tx_frame calls memset with huge length when called from cdc_mbim_tx_fixup to be marked as done. This means th

Bug#977615: marked as done (arm64: memory corruption bug)

Your message dated Tue, 02 Feb 2021 06:47:08 + with message-id and subject line Bug#977615: fixed in linux 4.19.171-1 has caused the Debian Bug report #977615, regarding arm64: memory corruption bug to be marked as done. This means that you claim that the problem has been dealt with. If this

linux_4.19.171-1_source.changes ACCEPTED into proposed-updates->stable-new, proposed-updates

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 29 Jan 2021 23:03:16 +0100 Source: linux Architecture: source Version: 4.19.171-1 Distribution: buster-security Urgency: high Maintainer: Debian Kernel Team Changed-By: Salvatore Bonaccorso Closes: 970736 972345

linux_4.19.171-2_source.changes ACCEPTED into proposed-updates->stable-new, proposed-updates

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 30 Jan 2021 10:35:46 +0100 Source: linux Architecture: source Version: 4.19.171-2 Distribution: buster-security Urgency: high Maintainer: Debian Kernel Team Changed-By: Salvatore Bonaccorso Changes: linux (4.19

linux-latest_105+deb10u9_source.changes ACCEPTED into proposed-updates->stable-new, proposed-updates

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 30 Jan 2021 08:43:43 +0100 Source: linux-latest Architecture: source Version: 105+deb10u9 Distribution: buster-security Urgency: high Maintainer: Debian Kernel Team Changed-By: Salvatore Bonaccorso Changes: lin

linux-signed-amd64_4.19.171+2_source.changes ACCEPTED into proposed-updates->stable-new, proposed-updates

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 30 Jan 2021 10:35:46 +0100 Source: linux-signed-amd64 Architecture: source Version: 4.19.171+2 Distribution: buster-security Urgency: high Maintainer: Debian Kernel Team Changed-By: Salvatore Bonaccorso Changes:

linux-signed-arm64_4.19.171+2_source.changes ACCEPTED into proposed-updates->stable-new, proposed-updates

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 30 Jan 2021 10:35:46 +0100 Source: linux-signed-arm64 Architecture: source Version: 4.19.171+2 Distribution: buster-security Urgency: high Maintainer: Debian Kernel Team Changed-By: Salvatore Bonaccorso Changes:

linux-signed-i386_4.19.171+2_source.changes ACCEPTED into proposed-updates->stable-new, proposed-updates

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 30 Jan 2021 10:35:46 +0100 Source: linux-signed-i386 Architecture: source Version: 4.19.171+2 Distribution: buster-security Urgency: high Maintainer: Debian Kernel Team Changed-By: Salvatore Bonaccorso Changes:

linux-signed-i386_4.19.171+1_source.changes ACCEPTED into proposed-updates->stable-new, proposed-updates

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 29 Jan 2021 23:03:16 +0100 Source: linux-signed-i386 Architecture: source Version: 4.19.171+1 Distribution: buster-security Urgency: high Maintainer: Debian Kernel Team Changed-By: Salvatore Bonaccorso Changes:

Bug#981616: linux-image-5.10.0-3-arm64-unsigned: WiFi does not work with vc4.ko on RPi4, module_blacklist=vc4 enables WiFi

Package: src:linux Version: 5.10.12-1 Severity: important Dear Maintainer, With Debian kernel 5.10.12-1, WiFi does not work on my RPi 4B 8GB model. Disabling vc4.ko by module_blacklist=vc4 in kernel command line restores WiFi connection... I have not yet verified if this is an upstream issue. T