Ubuntu Support Template
Ubuntu Version:
Example: 25.10 (ubuntu-server + ubuntustudio)
Desktop Environment (if applicable):
Example: ubuntustudio (KDE)
Problem Description:
Can not run sudo apt update, it just hangs there…
What should I do?
All components appear to be operating normally:
https://status.canonical.com/
I usually wait and try again in an hour.
If still no luck, then report back here.
1 Like
apt doesnt skip urls that does not respond ?
liviu@bobdenaut:~$ sudo apt -o Debug::Acquire::http=true update
0% [Working]GET /ubuntu/dists/questing/InRelease HTTP/1.1
Host: archive.ubuntu.com
Cache-Control: max-age=0
Accept: text/*
If-Modified-Since: Thu, 09 Oct 2025 09:26:50 GMT
User-Agent: Debian APT-HTTP/1.3 (3.1.6ubuntu2)
Answer for: http://archive.ubuntu.com/ubuntu/dists/questing/InRelease
HTTP/1.1 304 Not Modified
Date: Fri, 31 Oct 2025 06:47:52 GMT
Server: Apache/2.4.52 (Ubuntu)
Last-Modified: Thu, 09 Oct 2025 09:26:50 GMT
ETag: "4308c-640b666a5cc2d"
Accept-Ranges: bytes
Cache-Control: max-age=0, proxy-revalidate, s-maxage=3300
Expires: Fri, 31 Oct 2025 06:47:52 GMT
GET /ubuntu/dists/questing-updates/InRelease HTTP/1.1
Host: archive.ubuntu.com
Cache-Control: max-age=0
Accept: text/*
If-Modified-Since: Fri, 31 Oct 2025 02:31:49 GMT
User-Agent: Debian APT-HTTP/1.3 (3.1.6ubuntu2)
Hit:1 http://archive.ubuntu.com/ubuntu questing InRelease
Hit:2 https://brave-browser-apt-release.s3.brave.com stable InRelease
0% [Connecting to repo.librewolf.net (2603:c020:801b:4300:c17b:cc5a:cba7:3d8d)] [Waiting for headers] [Waiting foAnswer for: http://archive.ubuntu.com/ubuntu/dists/questing-updates/InRelease
HTTP/1.1 304 Not Modified
Date: Fri, 31 Oct 2025 06:47:52 GMT
Server: Apache/2.4.52 (Ubuntu)
Last-Modified: Fri, 31 Oct 2025 02:31:49 GMT
ETag: "21187-6426b2af4301a"
Accept-Ranges: bytes
Cache-Control: max-age=0, proxy-revalidate, s-maxage=3300
Expires: Fri, 31 Oct 2025 06:47:52 GMT
GET /ubuntu/dists/questing-backports/InRelease HTTP/1.1
Host: archive.ubuntu.com
Cache-Control: max-age=0
Accept: text/*
If-Modified-Since: Fri, 31 Oct 2025 02:32:30 GMT
User-Agent: Debian APT-HTTP/1.3 (3.1.6ubuntu2)
Hit:3 http://archive.ubuntu.com/ubuntu questing-updates InRelease
0% [Connecting to repo.librewolf.net (2603:c020:801b:4300:c17b:cc5a:cba7:3d8d)] [Waiting for headers] [Waiting foAnswer for: http://archive.ubuntu.com/ubuntu/dists/questing-backports/InRelease
HTTP/1.1 304 Not Modified
Date: Fri, 31 Oct 2025 06:47:52 GMT
Server: Apache/2.4.52 (Ubuntu)
Last-Modified: Fri, 31 Oct 2025 02:32:30 GMT
ETag: "2072a-6426b2d6511d2"
Accept-Ranges: bytes
Cache-Control: max-age=0, proxy-revalidate, s-maxage=3300
Expires: Fri, 31 Oct 2025 06:47:52 GMT
Hit:4 http://archive.ubuntu.com/ubuntu questing-backports InRelease
Hit:5 https://ppa.launchpadcontent.net/kubuntu-ppa/backports/ubuntu questing InRelease
0% [Connecting to repo.librewolf.net (2603:c020:801b:4300:c17b:cc5a:cba7:3d8d)] [Waiting for headers] [ConnectingGET /ubuntu/dists/questing-security/InRelease HTTP/1.1
Host: security.ubuntu.com
Cache-Control: max-age=0
Accept: text/*
If-Modified-Since: Fri, 31 Oct 2025 02:31:39 GMT
User-Agent: Debian APT-HTTP/1.3 (3.1.6ubuntu2)
Answer for: http://security.ubuntu.com/ubuntu/dists/questing-security/InRelease
HTTP/1.1 304 Not Modified
Date: Fri, 31 Oct 2025 06:47:52 GMT
Server: Apache/2.4.52 (Ubuntu)
Last-Modified: Fri, 31 Oct 2025 02:31:39 GMT
ETag: "21189-6426b2a59a55d"
Accept-Ranges: bytes
Cache-Control: max-age=0, proxy-revalidate, s-maxage=3300
Expires: Fri, 31 Oct 2025 06:47:52 GMT
Hit:6 http://security.ubuntu.com/ubuntu questing-security InRelease
Hit:7 https://packages.mozilla.org/apt mozilla InRelease
0% [Connecting to repo.librewolf.net (130.61.181.106)]
0% [Connecting to repo.librewolf.net (130.61.181.106)]
0% [Connecting to repo.librewolf.net (130.61.181.106)]
0% [Connecting to repo.librewolf.net (130.61.181.106)]
0% [Connecting to repo.librewolf.net (130.61.181.106)]
Ign:8 https://repo.librewolf.net librewolf InRelease
Ign:8 https://repo.librewolf.net librewolf InRelease
Ign:8 https://repo.librewolf.net librewolf InRelease
Err:8 https://repo.librewolf.net librewolf InRelease
Could not connect to repo.librewolf.net:443 (2603:c020:801b:4300:c17b:cc5a:cba7:3d8d), connection timed out Could not connect to repo.librewolf.net:443 (130.61.181.106), connection timed out
Unable to connect to repo.librewolf.net:https:
Looks like the librewolf repo might have issues.
ping repo.librewolf.net
curl -I https://repo.librewolf.net
If both time out then the issue is not with your system.
If the repo is down the temporary workaround is to disable it by commenting out the line in your sources list and then re-enable later once it comes back online.
Can this situation happen because of " Introducing architecture variants: amd64v3 now available in Ubuntu 25.10" as described here?
Very strange, I had to execute this to get it working:
sudo mv /etc/apt/apt.conf.d/50command-not-found /etc/apt/apt.conf.d/50command-not-found.disabled
Out of curiosity, how did you manage to figure out this was causing the block?
Is apt update now running normally including for librewolf?
By running this:
sudo strace -f -o /tmp/apt.strace.log apt update
and ofcourse chatgpt read my hundreds of lines from that trace.log and told me to deactivate the file /etc/apt/apt.conf.d/50command-not-found
liviu@bobdenaut:/etc/apt/sources.list.d$ cat /etc/apt/apt.conf.d/50command-not-found
## This file is provided by command-not-found(1) to download
## Commands metadata files.
Acquire::IndexTargets {
# The deb822 metadata files
deb::CNF {
MetaKey "$(COMPONENT)/cnf/Commands-$(NATIVE_ARCHITECTURE)";
ShortDescription "Commands-$(NATIVE_ARCHITECTURE)";
Description "$(RELEASE)/$(COMPONENT) $(NATIVE_ARCHITECTURE) c-n-f Metadata";
};
};
# Refresh AppStream cache when APT's cache is updated (i.e. apt update)
APT::Update::Post-Invoke-Success {
"if /usr/bin/test -w /var/lib/command-not-found/ -a -e /usr/lib/cnf-update-db; then /usr/lib/cnf-update-db > /dev/null; fi";
};
1 Like
so, Introducing architecture variants: amd64v3 breaks the system of something else
yes, the mirror was OK, the real issue was /etc/apt/apt.conf.d/50command-not-found
too bad I had to deactivate it…
2 Likes
Can anyone who understands the full implications speak to the possible impact of doing what Liviu has done with the following command:
Please confirm that this issue appeared when you were testing the new architecture variants.
It is possible, thanks @ogra for pointing me in the right direction, that there are integration bugs with command-not-found and possibly other scripts.
You might want to consider filing a bug report to help with this because this seems to be a special case related to that new architecture.
In other words, we would not normally recommend deactivating the command-not-found configuration.
1 Like
Confirm! I just did rollback from amd64v3 because this also blocks updating the system!
even after rollback from amd64v3 to amd64 the update apt is broken if you do rollback from no-found-command.disabled:
liviu@bobdenaut:~$ sudo mv /etc/apt/apt.conf.d/50command-not-found.disabled /etc/apt/apt.conf.d/50command-not-found
after the rollback the “sudo apt update” is not working so /etc/apt/apt.conf.d/50command-not-found must remain disabled.
You should file a bug report.
This is potentially very important information for the developers.
agreed, please tell me where should I go to post the bug?
thanks
I would ask in the main thread where the best place to file it would be.
I assume on Launchpad, but would ask which package you should file it against.
You should also note that apt has no rolling back option, it can only go forward, so if you installed any of the amd64v3 packages on your system just turning off the arch will not remove the amd64v3 binaries on your machine, they will only be replaced once the packages get an update with a higher version from the archive, until then you will use the binaries you installed during your amd64v3 testing
That really sucks!
We were asked to test that amd64v3 without all this information otherwise I would not make the move.
That was my last attempt to help.