I'm getting several errors and warnings on apt update, making it look like the zorin ppa is down or it's certificate is expired or something. Anyone else seeing this?
Also curious why apt shows several updates available but there's nothing in the Zorin software updater - but I'm thinking that may be related to all the ppa errors.
This is a harmless warning, informing you that is trying to fetch the Brave package for the i386 architecture while your computer isn't of said architecture. It's perfectly safe to ignore but also easy to fix:
This kind of error can happen when the server is too busy and preemptively starts rejecting some connections to avoid getting overwhelmed. It's also possible that it's rejecting too many requests from the same IP address, if you are using a VPN or something similar.
Another cause of this error is poor network conditions that cause it to drop packages in the certificate verification process (since it's using HTTPS). This is not within your control and can happen even if you have a good connection.
Although now that I'm checking on my system, I don't have that same repository:
It was a fresh install in December. Running 17.3. Strange that the repos would be different. Is there a list somewhere of what they should be? I don't want to just go changing them to what you have without knowing why.
The ZorinOS Packages Inrelease repository supplies the Zorin Specific packages that are layered on top of the base Ubuntu.
I just visited it as a url and received the "forbidden" notice.
I, too, lack this source, though I know I have seen it listed in the past. I am on the Main Server. And all the Zorin OS specific packages appear installed and up to date.
It may be that the ZorinGroup is refactoring how the repositories are managed.
That would be a normal thing and generally harmless.
That is a question best answered by the ZorinGroup directly; @AZorin or @zorink;
The "odd" looking one of course is the "zorin-os-ubuntu-packages-jammy", which you do not have. That is also the one that contains deb https://ppa.launchpadcontent.net/zorinos/packages/ubuntu jammy main, which is the one showing the 403 error.
I would just remove it, but that would leave me with no "packages" repo - don't know if that's OK or not. I guess it must be OK since it can't get to it now and it doesn't seem to be hurting anything other than my OCD. Also you don't have a packages repo.
zorin@Box:~$ cat /etc/apt/sources.list.d/zorin-os-ubuntu-packages-jammy.list
deb https://ppa.launchpadcontent.net/zorinos/packages/ubuntu jammy main
# deb-src https://ppa.launchpadcontent.net/zorinos/packages/ubuntu jammy main
zorin@Box:~$ cat /etc/apt/sources.list.d/zorin-os-ubuntu-packages-jammy.list.save
deb https://ppa.launchpadcontent.net/zorinos/packages/ubuntu jammy main
# deb-src https://ppa.launchpadcontent.net/zorinos/packages/ubuntu jammy main
It was a new install in December. Downloaded from Zorin. I've never checked hashes on Zorin downloads as I don't see them on the download page. This repo points to legitimate launchpadcontent.net - just a directory that appears to be unsigned or not exist. Maybe it's an old repo that Zorin has abandoned? I don't see it in https://launchpad.net/~zorinos.
Been using it since install with no issue. I do have a couple of other repos added that aren't related to this issue so kept them out of the list (docker & netbird).
I really wonder if the zorin-os-ubuntu-packages-jammy repos are old, discontinued ones. If you look at the full list in the GUI in my install there looks to be a replacement in packages.zorinos.com/
They are/were preventing Zorin updates from showing up in the GUI software updater, although the updates showed up in apt in terminal. It appears that the GUI software updater does not show updates if there are errors in apt update.
I tried unselecting the offending repo in software updater GUI and then it refreshed and showed the updates - apt update also runs clean now.
It must be an old repo. Probably worth someone looking at though, as you've suggested, since who knows how many other installs out there are having zorin updates held back because of these errors. There's NO indication to the casual user of any issues. They would have to do an apt update to notice it.
Current state after unchecking the offending repo:
