Minimal standalone not able to reach network (Debian 12)

User Support
21

Just the debian-12-minimal template I downloaded a few days ago. No modifications on my part. Same results for my attempt at Printer qube based on same template.

Will try this later.

22

What’s the output of:

systemctl status qubes-updates-proxy-forwarder.socket

In your debian-12-minimal template?
Are you able to update your debian-12-minimal?

23

Here’s what I’ve done:

  1. clone this problematic(?) debian-12-minimal template to debian-12-minimal-faulty; deleted the original template.
  2. downloaded a fresh copy of the template
  3. run Updater on fresh debian-12-minimal and debian-12-minimal-faulty. Green checks on both. The updates on the fresh template were very large (understandably). The update on faulty template was limited to qubes-core-agent 4.2.29-1+deb12u1 -> 4.2.30+deb12u1 - maybe that’s what was missing?
  4. on the template test

I can’t copy and paste from xterm, but it reports inactive (dead) and start condition failed…13 hours ago. Also, Forward connection to updates proxy over Qubes RPC was skipped because of an unmet condition check (ConditionPathExists=/var/run/qubes-service/updates-proxy-setup).

24

Looking at core-agent-linux v4.2.30 (r4.2) · Issue #4597 · QubesOS/updates-status · GitHub, the only thing vaguely connected to my problems is Qubes Updater considers in-place upgraded qubes to be "no longer supported" · Issue #8725 · QubesOS/qubes-issues · GitHub. Maybe.

25

Did you upgrade your debian-12-minimal-faulty from debian-11-minimal in-place?

Is this the output in the fresh debian-12-minimal or in test standalone qube created from fresh debian-12-minimal?

You can press Ctrl + middle mouse click on the xterm window and choose “Select to clipboard” and then all selected text will be copied to clipboard automatically.