Bug#988688: workaround for bug 988688 - disable security chip

[Salvatore Bonaccorso <carnil@debian.org>]

Hi Jonathan,

On Sat, Sep 13, 2025 at 10:43:26PM +0200, Salvatore Bonaccorso wrote:
> Hi Jonathan,
> 
> On Wed, Apr 30, 2025 at 04:38:49PM +0200, Salvatore Bonaccorso wrote:
> > Hi Jonathan,
> > 
> > On Tue, Apr 29, 2025 at 10:40:28AM +0100, Jonathan Dowland wrote:
> > > 
> > > Hi Salvatore,
> > > 
> > > Sorry I have not responded yet, I've been too busy and had to prioritise
> > > other things.
> > > 
> > > On Thu Apr 24, 2025 at 1:57 PM BST, Salvatore Bonaccorso wrote:
> > > > Accordingly going to close now the bug. If you feel though strongly
> > > > taht it is not okay please *do* reopen, but in that case we really
> > > > would need your help for the above.
> > > 
> > > I intend to work on this post-Trixie. I personally would find it useful if
> > > the bug was open: Between first discovering it, and finding the bug and
> > > useful information in it; and when I hit the bug a second time, a year or
> > > more later, it took me longer to find the useful information because the bug
> > > was closed and archived. However, I won't re-open it myself without your
> > > consent.
> > 
> > Given you have a clear intent to work on it post-trixie, let's reopen
> > it. I do not want to hide things, just make things more easy for us
> > for issues which are not anymore relevant. 
> > 
> > With your above statement, lets keep it open for now.
> 
> Did you had a chance to look into this? otherwise as stated earlier it
> it would be helpful to not keep bugs open for years and close it.

Any news here? Or should/can we go ahead and close the bug?

Regards,
Salvatore