Bug#944839: linux-image-5.2.0-0.bpo.3-rt-amd64-unsigned: issues for application crash with this kernel

2019-11-15 Thread Jose R R
Niltze [Hello]- On Fri, Nov 15, 2019 at 8:27 PM westlake wrote: > > Package: linux-image-5.2.0-0.bpo.3-rt-amd64-unsigned > Version: 5.2.17-1~bpo10+1 > Severity: important > > When this kernel is used, the latest version of chrome crashes saying it > can't launch because it is not able to create i

Bug#944839: linux-image-5.2.0-0.bpo.3-rt-amd64-unsigned: issues for application crash with this kernel

2019-11-15 Thread westlake
Package: linux-image-5.2.0-0.bpo.3-rt-amd64-unsigned Version: 5.2.17-1~bpo10+1 Severity: important When this kernel is used, the latest version of chrome crashes saying it can't launch because it is not able to create its own sandbox. (chrome "Version 78.0.3904.97 (Official Build) (64-bit)")

Bug#944822: linux-image-4.19.0-6-amd64: radeon hdmi digital audio (ac3/dts/multi-channel) not working on certain display refresh rates

2019-11-15 Thread Markus Schulz
Package: src:linux Version: 4.19.67-2+deb10u2 Severity: important playing digital audio (ac3/dts/multi-channel) produces no audio if the screen is currently at some specific refresh rate. test-setup: change screen refresh rate (xrandr) to 1920x1080 with 60.00, 59.94, 50.00, 30.00, 29.97,

Processed: Re: Bug#944777: initramfs-tools-core: Resume fails when UUID= syntax used in conf.d/resume.

2019-11-15 Thread Debian Bug Tracking System
Processing control commands: > tag -1 moreinfo Bug #944777 [initramfs-tools-core] initramfs-tools-core: Resume fails when UUID= syntax used in conf.d/resume. Added tag(s) moreinfo. -- 944777: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=944777 Debian Bug Tracking System Contact ow...@bugs.

Bug#944777: initramfs-tools-core: Resume fails when UUID= syntax used in conf.d/resume.

2019-11-15 Thread Ben Hutchings
Control: tag -1 moreinfo On Fri, 2019-11-15 at 01:30 -0600, Glenn Washburn wrote: > Package: initramfs-tools-core > Version: 0.130ubuntu3.9 This is an Ubuntu version, so maybe you should report this on Launchpad. > Severity: normal > Tags: newcomer > > Dear Maintainer, > > Resume from hibernat

Processed: severity of 944779 is wishlist, tagging 944779

2019-11-15 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > severity 944779 wishlist Bug #944779 [initramfs-tools-core] initramfs-tools-core: debug setting does not turn on tracing for scripts called by init Severity set to 'wishlist' from 'normal' > tags 944779 - newcomer Bug #944779 [initramfs-tools-cor

Bug#914967: marked as done (linux-image-4.18.0-3-amd64: errors "Failed to get unique processor _UID")

2019-11-15 Thread Debian Bug Tracking System
Your message dated Fri, 15 Nov 2019 13:53:43 +0100 with message-id <20191115125343.ga3...@cventin.lip.ens-lyon.fr> and subject line Re: linux-image-4.18.0-3-amd64: errors "Failed to get unique processor _UID" has caused the Debian Bug report #914967, regarding linux-image-4.18.0-3-amd64: errors "F

Processed: Re: linux-image-4.18.0-3-amd64: errors "Failed to get unique processor _UID"

2019-11-15 Thread Debian Bug Tracking System
Processing control commands: > found -1 4.19.67-2+deb10u2 Bug #914967 [src:linux] linux-image-4.18.0-3-amd64: errors "Failed to get unique processor _UID" Marked as found in versions linux/4.19.67-2+deb10u2. -- 914967: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=914967 Debian Bug Tracking

Bug#914967: linux-image-4.18.0-3-amd64: errors "Failed to get unique processor _UID"

2019-11-15 Thread Vincent Lefevre
Control: found -1 4.19.67-2+deb10u2 On 2018-11-29 09:21:31 +0100, Vincent Lefevre wrote: > I get the following errors at boot time: > > Nov 29 09:04:20 cventin kernel: acpi LNXCPU:06: Failed to get unique > processor _UID (0xff) > Nov 29 09:04:20 cventin kernel: acpi LNXCPU:07: Failed to get uni

Bug#944779: initramfs-tools-core: debug setting does not turn on tracing for scripts called by init

2019-11-15 Thread Glenn Washburn
Package: initramfs-tools-core Version: 0.130ubuntu3.9 Severity: normal Tags: newcomer Dear Maintainer, When adding "debug" to the kernel commandline debug output is turned on and is very useful for debugging. However, none of the scripts (eg. local-premount/resume) recognize the debug variable