After the installation of the 3isec-qubes-task-manager went very well on my Lenovo laptop, I now noticed, that it runs into errors on my Nitro-PC.
-rw-rw-r-- 1 TheGardner TheGardner 20845 Aug 30 19:40 3isec-qubes-task-manager-0.1-1.x86_64.rpm
[TheGardner@dom0 Downloads]$ sudo dnf install ./3isec-qubes-task-manager-0.1-1.x86_64.rpm
Qubes OS Repository for Dom0 0.0 B/s | 0 B 00:00
Errors during downloading metadata for repository 'qubes-dom0-cached':
- Curl error (37): Couldn't read a file:// file for file:///var/lib/qubes/updates/repodata/repomd.xml [Couldn't open file /var/lib/qubes/updates/repodata/repomd.xml]
Error: Failed to download metadata for repo 'qubes-dom0-cached': Cannot download repomd.xml: Cannot download repodata/repomd.xml: All mirrors were tried
[TheGardner@dom0 Downloads]$ ls -la /var/lib/qubes/updates/repodata/
total 8
drwxrwxr-x 2 root qubes 4096 Aug 30 20:09 .
drwxrwx--- 4 root qubes 4096 Aug 16 22:42 ..
[TheGardner@dom0 Downloads]$
can’t get the rpm.file installed and indeed the /var/lib/qubes/updates/repodata folder is empty. So what exactly is wrong here? When will the repomd.xml be updated/downloaded? Assume it always happens, when a installation is in progress.
desk is proper connected to the net…
other updates working like a charm…
did all previous steps as written by unman (on his 3isec webpage)
rpm.file has it’s full size and fingerprint was ok
For the most part these are based on minimal templates.
Minimal templates do not have passwordless-root installed.
If you want root access, then you have to do this from dom0. Like this: qvm-run -u root QUBE xterm
If you rename the cacher, or clone it, (so that you have one that
operates over Tor and one over clearnet, e.g.), then all you have to do
is change the entries in /etc/qubes/policy/30-user.policy
Templates using the update proxy have no idea what’s on the other end
of the qrexec call.
I never presume to speak for the Qubes team.
When I comment in the Forum or in the mailing lists I speak for myself.
This is a problem with your system unconnected with qubes-task.
I’ve seen reference to it before, but don’t recall a solution. (Perhaps
it was related to running out of disk space in dom0?)
You could try dnf clean all and then qubes-dom0-update?
I never presume to speak for the Qubes team.
When I comment in the Forum or in the mailing lists I speak for myself.
I tried and found a openvpn configuration file for manual setup from my vpn provider.
I downloaded everything and moved it to the sys-vpn template. I opened a root terminal like in the docs but I don’t understand to set up everything?
I only want to put my login data inside the template to at least use it
Edit: I mean how can I come from installing the templates with your salt terminal to connecting to my vpn?
If you look in the Description, or in the Readme in /srv/salt/openvpn,
you will see instructions on how to proceed.
Neither make any reference to opening a root terminal.
Dont do anything in the template.
Copy your openvpn file(s) to sys-vpn.
Run the install script, either from the Qubes Menu (you may need to
refresh the application list) , or by opening a terminal in sys-net and
running the setup script in /home/user
Ok. I moved the openvpn file in tar.gz format via
„Move to vm“ application in my sys-vpn template.
Then I refreshed my applications list and opened „ setup_vpn“ after I had restarted the template, but nothing changed. There is no connection, but I even never had to pick a town of the vpn. So I mean when I had the file in place in qubes and set it up, should I get any response? The connection is still not running …
Ok. I moved the openvpn file in tar.gz format via
???Move to vm??? application in my sys-vpn template.
Then I refreshed my applications list and opened ??? setup_vpn??? after I had restarted the template, but nothing changed. There is no connection, but I even never had to pick a town of the vpn. So I mean when I had the file in place in qubes and set it up, should I get any response? The connection is still not running ???
This is like pulling teeth.
Have you moved the file to sys-vpn? If so, it’s a qube, not a template.
What happened when you ran setup_vpn? Exactly what happened?
Seriously, tell me exactly what happened?
Look in /rw/config/vpn.
Are there openvpn files there?
did you perhaps mean: you relocated the file you downloaded (moving it again from VM to VM) which was in tar.gz format (if you are new to Linux - and this is not a Qubes issue by the way - a .gz or a .tar.gz file is similar to a zip which you may already know amounts to a compressed file) to someplace but have not yet extracted/decompressed the contents? I’m thinking that perhaps that will need to be done before either Network Manager or OpenVPN (depending upon how you are proceeding) will be prepared to cope with any datafiles contained within (if as I suspect it’s still compressed) for setting up the VPN connection.
I looked in the /rw/config/vpn direction and found only a file named qubes-vpn-handler.sh, my unzipped open vpn file ( I use perfect privacy btw. ) is in sys-net in the direction /home/user/qubesincoming/
At this point I started the Programm setup_vpn.
But after starting it, nothing changes. I waited several minutes to make sure nothing popped out after some time. So I get no response, I don’t get any error messages or something. I try to restart the qube but i get everytime the same result.
That was my fault, I meant in sys-vpn.
I used the a menu to run setup_vpn. I run the command in a normal sys-vpn terminal and came to the point that I have to insert a password for sudo. When I open up a sudo terminal, in the way you told me above. In sudo I get the message:
Root@sys-vpn:/home/user# ./install.sh
./install.sh: line 8: zenity: command not found
./install.sh: line 18: zenity: command not found
Zenity is included in the list of packages to be installed.
Clearly something went wrong with the installation.
I suggest you remove the package : sudo dnf remove 3isec-qubes-sys-vpn
Then reinstall.
You can check the log in /var/log/qubes/mgmt-template-openvpn.lof if
you want to check what went wrong.
Hmm, after deinstalling it, I jumped directly into another problem. I reinstalled the template multiple times but everytime in the q manager, I get the error message that the „setup_vpn” application is missing. I had copied my openvpn file to sys-vpn and refreshed the application list but the only thing what it’s do is that the “missed” application” (setup_vpn) disappears.
In the installing terminal I doesn’t see any failed packages or something.
