-
Notifications
You must be signed in to change notification settings - Fork 46
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Templates updates sometimes fail, requiring manual dpkg --configure -a
run
#428
Comments
All I did in the |
I am not sure what was modifying And the this added: https://github.com/Whonix/whonix-legacy/blob/master/debian/whonix-legacy.preinst
There is...
https://github.com/Whonix/usability-misc/blob/master/usr/bin/apt-get-noninteractive Would probably be easy to invent that for dpkg too. Let me know if you need that - then I could add that to Whonix/usability-misc. |
Can report that I have experienced this as well and solved as above. If I encounter it again I will share more detailed information. |
just fyi, ran into this updater issue twice today:
Running the following in
|
Do you still have any output from the |
No I don't but here are the full logs for
I also looked for 'error' or 'fail' in |
@eaon saw this issue recently during a Whonix update, so it's still a thing - leaving open for now |
Needs reproducing on Qubes 4.2. |
On both Nina's and my laptop, I've experienced template update failures (not reported by the cron job, but reported by the Qubes updater, or the script if run in a terminal), most recently in
sd-proxy-buster-template
. The failures were usually "easily" resolvable by runningdpkg --configure -a
in the impacted template, which the error message itself recommended.In the most recent cases, it was due to the file
/etc/machine-id
being in a modified state (I've never edited or touched the file). These may have been leftover issues from the Whonix/Buster transition, but I'm filing it anyway in case we encounter it again or there's more that we can do to mitigate such issues.The text was updated successfully, but these errors were encountered: