Change-detection.io update script, 'Possible debconf database corruption'

[mgrimace]

Hello,
I'm attempting to update change-detection.io using update from within the LXC. Non-verbose hangs, and verbose shows the following screens (likely causing the hang, as user input is required). The screens identify a potential database corruption error:

You can proceed by hitting 'enter' to manually move through, and it appears to work. However,

1. Non-verbose will not proceed
2. LXC size jumps from about 4gb to about 7gb (likely the updated playwright browsers, potentially not cleaning up old ones.

Overal, looks like there's some breaking errors/changes in some dependencies, at least on my end and sharing because I have a default installation of it.

[MickLesk]

@community-scripts/contributor can anyone investigate or convert to issue?

[tremor021]

Can you do cat /etc/apt/sources.list for me and paste the result here? @mgrimace

[mgrimace]

post-update (after running the update script, and hitting 'enter, enter' on both error screens above):

deb http://deb.debian.org/debian bookworm main contrib

deb http://deb.debian.org/debian bookworm-updates main contrib

deb http://security.debian.org bookworm-security main contrib

[tremor021]

yea, that seems correct.

try running /usr/share/debconf/fix_db.pl
and reboot

[mgrimace]

yea, that seems correct.

try running /usr/share/debconf/fix_db.pl and reboot

Completed, it appears to be working as expected. I'll keep watch and see if it does indeed work as expected or if there's anything unusual.

The two outstanding issues IMHO are the indefinite hanging when updating using non-verbose (likely due to those screens requiring user interaction), and the storage jumps from about 60% to about 90% of default values after update (e.g., maybe older playwright browsers aren't being tidied up or something during the process).

The workaround so far is using verbose, manually hitting 'enter' on both screens, then likely running fix_db.pland rebooting.

[tremor021]

the thing is, i think there shouldnt be any user interaction there and there shouldn't be any need to run fix_db.pl.

This is a bug which we need to investigate.

Your issue is solved?

[mgrimace]

the thing is, i think there shouldnt be any user interaction there and there shouldn't be any need to run fix_db.pl.

This is a bug which we need to investigate.

Your issue is solved?

Ah yes, sorry I was conflating two separate things here. Yes, my issue is solved (thank you!), and yes, there still appears to be a bug(s).