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

2019-11-09 Thread Debian FTP Masters
Mapping sid to unstable. binary:linux-image-5.3.0-2-amd64 is NEW. binary:linux-image-5.3.0-2-cloud-amd64 is 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

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

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

Bug#944428: Additional information

2019-11-09 Thread Marc Bonnor
-- Package-specific info: ** Version: Linux version 5.3.0-1-amd64 (debian-kernel@lists.debian.org) (gcc version 9.2.1 20191008 (Debian 9.2.1-9)) #1 SMP Debian 5.3.7-1 (2019- 10-19) ** Command line: BOOT_IMAGE=/boot/vmlinuz-5.3.0-1-amd64 root=UUID=7761194e-0340-44b9- b0bd-2b0643ef86ca ro quiet

Re: Dropping haveged from the installer

2019-11-09 Thread Ben Hutchings
On Thu, 2019-11-07 at 22:36 +0100, Cyril Brulebois wrote: > Hi Ben, > > Ben Hutchings (2019-11-07): > > Linux 5.4 introduces an in-kernel jitter-entropy implementation for > > systems without a usable hardware RNG, which should remove the need for > > haveged. > > > > We could possibly

linux_5.3.9-1_source.changes ACCEPTED into unstable, unstable

2019-11-09 Thread Debian FTP Masters
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 09 Nov 2019 15:42:49 + Source: linux Architecture: source Version: 5.3.9-1 Distribution: unstable Urgency: medium Maintainer: Debian Kernel Team Changed-By: Ben Hutchings Closes: 924705 931341 935945 942861

Bug#943422: marked as done (linux: 5.3.7 breaks soundcard)

2019-11-09 Thread Debian Bug Tracking System
Your message dated Sat, 09 Nov 2019 21:10:12 + with message-id and subject line Bug#942881: fixed in linux 5.3.9-1 has caused the Debian Bug report #942881, regarding linux: 5.3.7 breaks soundcard to be marked as done. This means that you claim that the problem has been dealt with. If this

Bug#943953: marked as done (linux: DKMS module builds are failing on arm64 due to lack of armhf cross-compiler)

2019-11-09 Thread Debian Bug Tracking System
Your message dated Sat, 09 Nov 2019 21:10:12 + with message-id and subject line Bug#943953: fixed in linux 5.3.9-1 has caused the Debian Bug report #943953, regarding linux: DKMS module builds are failing on arm64 due to lack of armhf cross-compiler to be marked as done. This means that you

Bug#943545: marked as done (pulseaudio: audio completely broken)

2019-11-09 Thread Debian Bug Tracking System
Your message dated Sat, 09 Nov 2019 21:10:12 + with message-id and subject line Bug#942881: fixed in linux 5.3.9-1 has caused the Debian Bug report #942881, regarding pulseaudio: audio completely broken to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#943355: marked as done (audio broken)

2019-11-09 Thread Debian Bug Tracking System
Your message dated Sat, 09 Nov 2019 21:10:12 + with message-id and subject line Bug#942881: fixed in linux 5.3.9-1 has caused the Debian Bug report #942881, regarding audio broken to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it

Bug#942886: marked as done (linux-image-5.3.0-1-amd64: Can not modprobe "snd_hda_codec_hdmi")

2019-11-09 Thread Debian Bug Tracking System
Your message dated Sat, 09 Nov 2019 21:10:12 + with message-id and subject line Bug#942881: fixed in linux 5.3.9-1 has caused the Debian Bug report #942881, regarding linux-image-5.3.0-1-amd64: Can not modprobe "snd_hda_codec_hdmi" to be marked as done. This means that you claim that the

Bug#942836: marked as done (snd_hda_intel: No response from codec, resetting bus)

2019-11-09 Thread Debian Bug Tracking System
Your message dated Sat, 09 Nov 2019 21:10:12 + with message-id and subject line Bug#942881: fixed in linux 5.3.9-1 has caused the Debian Bug report #942881, regarding snd_hda_intel: No response from codec, resetting bus to be marked as done. This means that you claim that the problem has

Bug#940181: marked as done (linux-image-5.2.0-2-amd64: Kernel does not accept self-signed modules using UEFI db key)

2019-11-09 Thread Debian Bug Tracking System
Your message dated Sat, 09 Nov 2019 21:10:12 + with message-id and subject line Bug#935945: fixed in linux 5.3.9-1 has caused the Debian Bug report #935945, regarding linux-image-5.2.0-2-amd64: Kernel does not accept self-signed modules using UEFI db key to be marked as done. This means

Bug#942881: marked as done (snd-hda-codec-hdmi signature corruption)

2019-11-09 Thread Debian Bug Tracking System
Your message dated Sat, 09 Nov 2019 21:10:12 + with message-id and subject line Bug#942881: fixed in linux 5.3.9-1 has caused the Debian Bug report #942881, regarding snd-hda-codec-hdmi signature corruption to be marked as done. This means that you claim that the problem has been dealt with.

Bug#942823: marked as done (linux-image-5.3.0-1-amd64: Dell XPS 13 gets stuck on sddm login screen at boot)

2019-11-09 Thread Debian Bug Tracking System
Your message dated Sat, 09 Nov 2019 21:10:12 + with message-id and subject line Bug#942881: fixed in linux 5.3.9-1 has caused the Debian Bug report #942881, regarding linux-image-5.3.0-1-amd64: Dell XPS 13 gets stuck on sddm login screen at boot to be marked as done. This means that you

Bug#939773: marked as done (linux-image-5.2.0-2-amd64: MOK key not used for verification of modules signatures.)

2019-11-09 Thread Debian Bug Tracking System
Your message dated Sat, 09 Nov 2019 21:10:12 + with message-id and subject line Bug#935945: fixed in linux 5.3.9-1 has caused the Debian Bug report #935945, regarding linux-image-5.2.0-2-amd64: MOK key not used for verification of modules signatures. to be marked as done. This means that

Bug#941827: marked as done (module loading fails with error: "Lockdown: modprobe: Loading of unsigned module is restricted; see https://wiki.debian.org/SecureBoot")

2019-11-09 Thread Debian Bug Tracking System
Your message dated Sat, 09 Nov 2019 21:10:12 + with message-id and subject line Bug#935945: fixed in linux 5.3.9-1 has caused the Debian Bug report #935945, regarding module loading fails with error: "Lockdown: modprobe: Loading of unsigned module is restricted; see

Bug#942861: marked as done (linux-image-amd64: missing-copyright-file /usr/share/doc/linux-image-amd64/copyright)

2019-11-09 Thread Debian Bug Tracking System
Your message dated Sat, 09 Nov 2019 21:10:12 + with message-id and subject line Bug#942861: fixed in linux 5.3.9-1 has caused the Debian Bug report #942861, regarding linux-image-amd64: missing-copyright-file /usr/share/doc/linux-image-amd64/copyright to be marked as done. This means that

Bug#931341: marked as done (linux-image-4.19.0-5-cloud-amd64 does not have /dev/rtc, used by GCE images)

2019-11-09 Thread Debian Bug Tracking System
Your message dated Sat, 09 Nov 2019 21:10:12 + with message-id and subject line Bug#931341: fixed in linux 5.3.9-1 has caused the Debian Bug report #931341, regarding linux-image-4.19.0-5-cloud-amd64 does not have /dev/rtc, used by GCE images to be marked as done. This means that you claim

Bug#935945: marked as done (linux-image-5.2.0-2-amd64: does not load signed kernel modules when UEFI Secure Boot is enabled)

2019-11-09 Thread Debian Bug Tracking System
Your message dated Sat, 09 Nov 2019 21:10:12 + with message-id and subject line Bug#935945: fixed in linux 5.3.9-1 has caused the Debian Bug report #935945, regarding linux-image-5.2.0-2-amd64: does not load signed kernel modules when UEFI Secure Boot is enabled to be marked as done. This

Bug#924705: marked as done (Please enable PKCS8_PRIVATE_KEY_PARSER)

2019-11-09 Thread Debian Bug Tracking System
Your message dated Sat, 09 Nov 2019 21:10:12 + with message-id and subject line Bug#924705: fixed in linux 5.3.9-1 has caused the Debian Bug report #924705, regarding Please enable PKCS8_PRIVATE_KEY_PARSER to be marked as done. This means that you claim that the problem has been dealt with.

linux_5.3.9-1_source.changes is NEW

2019-11-09 Thread Debian FTP Masters
binary:acpi-modules-5.3.0-2-686-di is NEW. binary:acpi-modules-5.3.0-2-686-pae-di is NEW. binary:acpi-modules-5.3.0-2-amd64-di is NEW. binary:affs-modules-5.3.0-2-4kc-malta-di is NEW. binary:affs-modules-5.3.0-2-5kc-malta-di is NEW. binary:affs-modules-5.3.0-2-loongson-3-di is NEW.

Processing of linux_5.3.9-1_source.changes

2019-11-09 Thread Debian FTP Masters
linux_5.3.9-1_source.changes uploaded successfully to localhost along with the files: linux_5.3.9-1.dsc linux_5.3.9.orig.tar.xz linux_5.3.9-1.debian.tar.xz linux_5.3.9-1_source.buildinfo Greetings, Your Debian queue daemon (running on host usper.debian.org)

Bug#944420: Also tried 5.2.0

2019-11-09 Thread Philipp Klaus Krause
I also tried an older 5.2.0 kernel: linux-image-5.2.0-3-amd64 5.2.17-1 The problem there is the same, but it seems I have a somewhat higher chance to make it to XFCE (in which I still see graphical corruption) than just getting a green screen (which I there see bit less than half of the time).

Bug#944420: Wrong info

2019-11-09 Thread Philipp Klaus Krause
I see reportbug added a lot of information from the system on which I submitted the bug report. Please disregard that; sorry for the noise. Do you need any further information from the system on which I see the bug that I should provide?

Bug#944420: linux-image-5.3.0-1-amd64: green screen in X

2019-11-09 Thread Philipp Klaus Krause
Package: src:linux Version: 5.3.7-1 Severity: important A few days ago, I installed Debian on a new Ryzen 3400G system (not the system on which I write this report, hope reportbug doesn't add any invalid information from the system on which I type this). I see graphical problems in X. I am not

Bug#880549: nfs-kernel-server: NFSv4 sec=krb5p option broken on stretch

2019-11-09 Thread Dietrich Clauss
Package: nfs-kernel-server Followup-For: Bug #880549 This bug is still present in Buster. It can be workarounded by using the mount option "vers=4.0". NFS versions 4.2 (default in Buster), and 4.1 are affected by this bug. Version 4.0 works fine. Can anyone confirm this? -- System

Bug#884284: nfs4_reclaim_open_state: Lock reclaim failed

2019-11-09 Thread Dietrich Clauss
Package: nfs-kernel-server Followup-For: Bug #884284 Duplicate of #880549? -- System Information: Debian Release: 10.1 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-6-amd64 (SMP w/4 CPU cores) Locale:

Bug#884284: nfs4_reclaim_open_state: Lock reclaim failed

2019-11-09 Thread Dietrich Clauss
Duplicate of #880549?

Bug#880549: nfs-kernel-server: NFSv4 sec=krb5p option broken on stretch

2019-11-09 Thread Dietrich Clauss
This bug is still present in Buster. It can be workarounded by using the mount option "vers=4.0". NFS versions 4.2 (default in Buster), and 4.1 are affected by this bug. Version 4.0 works fine. Can anyone confirm this?