Qubes Update Tool fails

Hi,

i received a notification, that for 3 of my qubes updates are available.
I started the Update tool, however all 3 qubes fail to be updated.

I received for each qubes the following message:

Updating debian-12-clone-office
Refreshing package info
Refreshing packages.
Fail to refresh InRelease: Index of /r4.2/vm/ bookworm InRelease from https://deb.qubes-os.org/r4.2/vm/dists/bookworm/InRelease
Fail to refresh InRelease: Index of /debian bookworm InRelease from https://deb.debian.org/debian/dists/bookworm/InRelease
Fail to refresh InRelease: https://deb.debian.org/debian-security bookworm-security InRelease from https://deb.debian.org/debian-security/dists/bookworm-security/InRelease
Fail to refresh InRelease: Index of /r4.2/vm/ bookworm InRelease from https://deb.qubes-os.org/r4.2/vm/dists/bookworm/InRelease
Fail to refresh InRelease: Index of /debian bookworm InRelease from https://deb.debian.org/debian/dists/bookworm/InRelease
Fail to refresh InRelease: Index of /r4.2/vm/ bookworm InRelease from https://deb.qubes-os.org/r4.2/vm/dists/bookworm/InRelease
Fail to refresh InRelease: https://deb.debian.org/debian-security bookworm-security InRelease from https://deb.debian.org/debian-security/dists/bookworm-security/InRelease
Fail to refresh InRelease: Index of /r4.2/vm/ bookworm InRelease from https://deb.qubes-os.org/r4.2/vm/dists/bookworm/InRelease
Fail to refresh InRelease: Index of /debian bookworm InRelease from https://deb.debian.org/debian/dists/bookworm/InRelease
Fail to refresh InRelease: https://deb.debian.org/debian-security bookworm-security InRelease from https://deb.debian.org/debian-security/dists/bookworm-security/InRelease
Fail to refresh InRelease: Index of /debian bookworm InRelease from https://deb.debian.org/debian/dists/bookworm/InRelease
Refreshed.
Fail to refresh InRelease: https://deb.debian.org/debian-security bookworm-security InRelease from https://deb.debian.org/debian-security/dists/bookworm-security/InRelease
E:Failed to fetch https://deb.debian.org/debian/dists/bookworm/InRelease Reading from proxy failed - select (115: Die Operation ist jetzt in Bearbeitung) [IP: 127.0.0.1 8082], E:Failed to fetch https://deb.debian.org/debian-security/dists/bookworm-security/InRelease Reading from proxy failed - select (115: Die Operation ist jetzt in Bearbeitung) [IP: 127.0.0.1 8082], E:Failed to fetch https://deb.qubes-os.org/r4.2/vm/dists/bookworm/InRelease Reading from proxy failed - select (115: Die Operation ist jetzt in Bearbeitung) [IP: 127.0.0.1 8082], E:Some index files failed to download. They have been ignored, or old ones used instead.

Why ? What happened and how to resolve the situation ??

Regards, hitam

Are you using a Fedora based updatevm? Would you please check within your updatevm inside /etc/qubes-rpc directory and see if you have a file named qubes.UpdateProxy.rpmnew

I use Debian based updatevm. No fedora at all.

1 Like

What’s your update proxy qube?
Do you have VPN in it?
Maybe your update proxy qube is using IPv6?
There was something similar:

Hi, no i do not have VPN in it a the moment.

IPV6
IP Address 2001 dbb8:1::2/128
more addresses:
fe80::f925:cfbe:b0e6:8ec2/64
Default route fe80::1
Primary DNS fe80::1
in the network manager the IPV6 Method was set to automatic.
Regards, hitam

Is sys-net your update proxy qube?
Try to change the IPv6 configuration in network manager from automatic to disabled.
And then disable/enable networking using network manager to apply to changes.

Ok, i will do.

dom0…is the update qube ??

Open Qubes Global Settings → Updates tab. What’s the qube for “Default update proxy”?

where do i find qubes global settings ???

Open Qubes OS menu in the top left corner Q → gear icon → Qubes Tools → Qubes Global Config.

1 Like

Thanks…
The update of dom0 works…the others are still pending…

Update proxy is sys-firewall

Is it “Dom0 update proxy” or “Default update proxy”?

default update proxy sys-net

Ok, then it could be an issue with IPv6 in sys-net. Disabling IPv6 in sys-net should solve this.

Dom0 update proxy

dom0 was updated successfully…the three other qubes still have the same problem to connect like before…

done

Did you disable/enable networking using network manager to apply to changes in sys-net?