Bug#606713: unarchiving 606713, reopening 606713, found 606713 in 5.10.28-1

[Paul Wise]

On Fri, 2022-06-10 at 00:36 +0200, Diederik de Haas wrote:

> A year has passed and it has been quiet on the upstream bug for almost a year.
> Has there been progress which isn't visible in upstream or Debian's BTS?

There hasn't. I haven't had time to try this bug again but I will try
to make time to reproduce it towards the end of June.

-- 
bye,
pabs

https://wiki.debian.org/PaulWise


signature.asc
Description: This is a digitally signed message part

Bug#606713: unarchiving 606713, reopening 606713, found 606713 in 5.10.28-1

[Diederik de Haas]

Control: tag -1 moreinfo

On Sat, 05 Jun 2021 19:59:40 +0800 Paul Wise  wrote:
> # still present in bullseye, talking with upstream about debugging etc
> unarchive 606713
> reopen 606713 
> found 606713 5.10.28-1

A year has passed and it has been quiet on the upstream bug for almost a year.
Has there been progress which isn't visible in upstream or Debian's BTS?

It looks like a 5.10.120-1 release is 'around the corner' and in Unstable we 
now have a 5.18.x release. Can you test whether it's still reproducible?

> The issue doesn't happen with Windows XP running on the same machine, so I
> do think this is a Linux specific bug.

This sounds like a BIOS/ACPI bug and AFAIK it's not uncommon that WinXP has 
'workarounds' for things like that. Given the age of the laptop, I doubt a 
BIOS fix is in the works. Maybe WinXP source code has been leaked somewhere?

signature.asc
Description: This is a digitally signed message part.