Bug#1053860: /usr/share/bash-completion/completions/ethtool: completes with ^[[36m at the start

2023-10-12 Thread наб
Package: ethtool Version: 1:6.4-1 Severity: normal File: /usr/share/bash-completion/completions/ethtool Dear Maintainer, $ ethtool -g yields $ ethtool -g ^[[36m $ ethtool -g ^[[36m yields $ ethtool -g ^[[36m ^[[36mbond1 ^[[36mcard1 ^[[36mcard2 ^[[36mlo

Bug#1053856: (no subject)

2023-10-12 Thread Mario Limonciello
The specific issue here is that there is a firmware binary in upstream linux-firwmare.git, also documented in WHENCE upstream but not installed in Debian's package.

Bug#1053122: Fwd: Bug#1053122: linux-image-6.5.0-1-amd64: using smp_processor_id() in preemptible

2023-10-12 Thread Gabriel Francisco
-- Forwarded message - From: Gabriel Francisco Date: Thu, Oct 12, 2023 at 8:23 PM Subject: Re: Bug#1053122: linux-image-6.5.0-1-amd64: using smp_processor_id() in preemptible To: Ben Hutchings Hi, > The CPU registers contain several addresses starting 89, except for > rbx

Bug#1053856: firmware-amd-graphics: Inconsistent firmware snapshot for Zen4/Phoenix1 GPUs

2023-10-12 Thread Diederik de Haas
Control: notfound -1 20230210-5 Control: found -1 20230515-3 On Thursday, 12 October 2023 18:52:26 CEST Wiktor Janas wrote: > Package: firmware-amd-graphics > Version: 20230210-5 > > firmware-amd-graphics version 20230515-3 (currently in unstable and testing) > ships an inconsistent snapshot of

Processed: Re: Bug#1053856: firmware-amd-graphics: Inconsistent firmware snapshot for Zen4/Phoenix1 GPUs

2023-10-12 Thread Debian Bug Tracking System
Processing control commands: > notfound -1 20230210-5 Bug #1053856 [firmware-amd-graphics] firmware-amd-graphics: Inconsistent firmware snapshot for Zen4/Phoenix1 GPUs No longer marked as found in versions firmware-nonfree/20230210-5. > found -1 20230515-3 Bug #1053856 [firmware-amd-graphics]

Bug#1053856: firmware-amd-graphics: Inconsistent firmware snapshot for Zen4/Phoenix1 GPUs

2023-10-12 Thread Wiktor Janas
Package: firmware-amd-graphics Version: 20230210-5 Severity: grave Justification: renders package unusable X-Debbugs-Cc: mario.limoncie...@amd.com, wixorp...@gmail.com firmware-amd-graphics version 20230515-3 (currently in unstable and testing) ships an inconsistent snapshot of the firmware

Bug#1052006: marked as done (linux-image-6.5.0-1-amd64 breaks X on amd GPU)

2023-10-12 Thread Debian Bug Tracking System
Your message dated Thu, 12 Oct 2023 09:54:47 +0200 with message-id <2785354.ud88dkUTql@bagend> and subject line Re: Bug#1052006: Info received (Bug#1052006: linux-image-6.5.0-1-amd64 breaks X on amd GPU) has caused the Debian Bug report #1052006, regarding linux-image-6.5.0-1-amd64 breaks X on

Bug#1053825: Acknowledgement (Screensaver with only blank does not work after suspend)

2023-10-12 Thread Klaus Ethgen
Hi, The bug definitively only happens in that combination. When using fvwm2 instead of fvwm3, everything is fine. fvwm3 was bringing support for xrandr. So I believe that the screen do get reconfigured after waking up from suspend. That was not the case with earlier kernel. Regards Klaus --

Bug#1053825: Screensaver with only blank does not work after suspend

2023-10-12 Thread Klaus Ethgen
Package: src:linux Version: 6.5.6-1 Severity: critical Tags: security X-Debbugs-Cc: Debian Security Team It is not fully clear for me, where exactly this bug happens. First I was thinking about xscreensaver but that package got not updated for ages. The bug happens with updates from kernel 6.4.0