These URLs don’t seem right. I don’t know how they got there, but as a workaround I would be curious to see if you can find them in /etc/apt/sources.list/ (or in one of the files in the /etc/apt/sources.list.d/ directory).
If you find them, replacing http://HTTPS/// by https:// would likely resolve the errors.
Thank you sir, I’ll give it a go this weekend when I’m off work and let you know…
I’m still learning the Qubes OS, so I wouldn’t know how they got in there or changed
This isn’t the problem - those are the canonical way of using TLS
repositories via a caching proxy like apt-cacher-ng.
They are build artefacts.
But they aren’t the problem in this case - the problem is (obviously)
command not found and the qubes-core-agent dependency which
I had fixed in the parrot, but not in this old kali template.
I’ll rebuild a kali for 4.0 overnight and post it in the morning.
It’s not advisable to mix Ubuntu and Debian packages, and
Terminator is available in the Debian repository - so the appropriate
thing is not to add a Ubuntu ppa, but to apt install terminator
@B_ryr Please see @unman’s answer and disregard mine.
I had never seen the URLs of repositories used through a proxy and missed the command not found error 
Thank you unman…
Yes I ever tried…
(apt install terminator/apt-get install terminator) it would not install either way.
So unmann, I was able to upgrade the Arch Linux template but big problems now. Nothing works, (terminal, leafpad, package updated… etc) the only thing that will run is the qubes settings for the Arch Linux template.I know it should work as even if the “archlinux” template is shut down. If I click any app I have selected to display under the template I see that the template is starting but no app shows up after it has started. will just delete and reinstall, just not update/upgrade… -Syu
It’s been pointed out to me that the Mint template (ulyssa) ships with a
limited icon set, so file manager is hard to use.
Installing gnome-icon-theme will fix this.
sudo apt install gnome-icon-theme
thank you and will do
worked like a “charm” for ulyssa… file explorers habe icons back!
Thanks a ton!
The same happens if you try to update the Parrot Template VM; the update aborts with a lot of messages 500 Unable to connect [IP: 127.0.0.1 8082].
If the offending lines in /etc/apt/sources.list.d/qubes-r4.list and .../parrot.list are changed from
deb ... http://HTTPS///deb... to
deb ... https://deb..., the update runs without problems.
Since all right thinking people use apt-cacher-ng as a caching proxy, I
would not describe these as “offending lines”.
@unman, there’s absolutely need to take ofense over this or offend others with “No True Scotsman” fallacies. As I’m sure you’re aware “offending lines” is the term used to describe the lines that caused the error.
If it was a joke, please add a winky face or something, as otherwise it gets lost in translation.
I don’t take offence, but I’m not a winky face person.
I thought that “all right thinking people” would indicate a note of
levity. Apparently I was wrong.
It’s not a matter of right thinking - as a non-linux-speakting guy, I simply don’t know and never heard of apt-cacher-ng. 
And now you have.
One of the issues with Qubes is that if you start to expand templates
beyond the standard, by cloning and configuring for particular purposes,
there is a good deal of redundancy keeping them up to date.
A caching proxy helps, since a package is downloaded once and then cached
for use by other templates. This is more efficient, and allows for very
fast updates.
If you use Qubes builder, using the same proxy allows for very fast
rebuilds, etc.
There is no loss of security because the client performs the same
security checks as normal.
apt-cacher-ng is a Debian based caching proxy, which works out of the
box for Debian based clients, Arch, Suse, and Cygwin. With minimal
configuration it will cache Fedora too.
If it is configured to listen on port 8082 it can be dropped in to place
in a standard Qubes configuration.
I have a note on this at GitHub - unman/notes
There is also a salt packaged solution at GitHub - unman/shaker
What’s the reason for the http://HTTPS/// ?
Any proxy has to deal with https requests - either it passes them without
caching, or it provides some MITM solution.
apt-cacher-ng has various solutions - the canonical way is to change the
request at the client - so the client requests http://HTTPS///, the
proxy gets a standard http, requests using TLS, caches and
passes back via http.
Anyone who has cloned templates will benefit from using a caching proxy,
and apt-cacher-ng is drop in usable in Qubes. Well worth a try.
I’ll be happy to help if anyone has any questions, or hits problems.
Thanks a lot for this explanation, which makes it a lot clearer to me!
With the Parrot template, the problem then seems to be that it somehow does not use this caching, which is a bit awkward, since it is debian-based. Or how else could it get that confused on update?
Well parrot will not even update from “qubes update”. I see the qubes update pop-up by the icons. I go to the “qubes update” widget, click it and it states parrot. I click next the uodate states. It finshes with a green cherxhmark BUT when reading what updated it states…
FAILED and a list of why it failed. something along the lines that “no OS” or to that matter. and qubes uodate keeps poping up now stating parrot update. and it wont update, same problem.
Kali is doing the same thing parrot is with the http//HTTPS// errors when trying to update
I updated my Parrot template manually, using sudo apt-get update and sudo apt-get upgrade from a terminal. After that, the updater just showed that it had nothing more to update.