I have issues with installing qusals(qusal/docs/INSTALL.md at main · ben-grande/qusal · GitHub) salt in dom0. I have problems with Dom0 installation. I copied the qusal repo to vault and got it to /home/user. I used this command:
qvm-run --pass-io --localcmd=“UPDATES_MAX_FILES=10000 /usr/libexec/qubes/qfile-dom0-unpacker user ~/QubesIncoming/vault/qusal” \ “vault” /usr/lib/qubes/qfile-agent “/home/user/qusal”
and it gave me this error:
qvm-run: error: no such domain: ’ vault’
Where is the issue? What did i do wrong?
1 Like
Up
1 Like
What do you mean @QuberSecondComing54?
1 Like
qvm-run: error: no such domain: ’ vault’
Notice there is a space after the quotes before the v.
If the command line has no line breaks, remove the \ (backlash).
3 Likes
I changed command to this:
qvm-run --pass-io --localcmd=“UPDATES_MAX_FILES=10000 /usr/libexec/qubes/qfile-dom0-unpacker user ~QubesIncoming/vault/qusal” “vault” /usr/lib/qubes/qfile-agent “/home/user/qusal”
it now gives my this error:
Error chdir to ~QubesIncoming/vault/qusal
EOF
1 Like
You have yet another typo:
~QubesIncoming/vault/qusal is not a valid path.
~/QubesIncoming/vault/qusal is probably what you were aiming for.
Using ~/ is shorthand for /home/<username>/. In this case, that would expand to /home/user/QubesIncoming/vault/qusal.
Here is how it should look:
qvm-run --pass-io --localcmd=“UPDATES_MAX_FILES=10000 /usr/libexec/qubes/qfile-dom0-unpacker user ~/QubesIncoming/vault/qusal” “vault” /usr/lib/qubes/qfile-agent “/home/user/qusal”
2 Likes
I fully copied command and now it gives me another error:
Error chdir to /home/admin/QubesIncoming/vault/qusal
EOF
This time i compared it with online tools to make sure i didn’t make any typos
1 Like
This project looks like it’s above and beyond the competency of a new-to-Qubes user (or even moderately experienced). What are you trying to solve by installing this project?
Straight from the README.md:
Warning: Not ready for production, development only. Breaking changes can and will be introduced in the meantime. You’ve been warned.
Are you aiming for trial by fire? No judgement, everyone has their methods…
That being said, the output is very confusing. I assume you’ve replaced ${qube} with “vault” and ${file} with “/home/user/qusal”. However that doesn’t match with the error.
If you’re trying to copy the git repository over, the command looks correct, however, admin is not a default account on an AppVM. So what’s the path to your repository on the AppVM (aka, ${file})?
1 Like
I want to automatically install Audio qube with nice GUI, it seems like i can do it with one press of a button with salt(or one line of command after i install it).
qusal folder is located in my AppVM vault qube in “/home/user” directory. I tried doing “/home/user/” or “/home/user” instead of “/home/user/qusal” but it gives the same error
1 Like
So, the confusing bit here is the error
Where I’m confused is this: /home/admin is not /home/user unless there’s something in the background of qfile-dom0-unpacker…
Next thing you can try is to pack the folder in a tar, then copy it over and untar it in dom0…
2 Likes
Thank you! It worked, i managed to pass a file to dom0
1 Like
Glad to hear it.
Be careful.
2 Likes
@ben-grande Hello! Please, can you add what “state” and “top” means to the readme page somewhere on your github? It will be helpful to people like me who just want to have an automated way of creating audio qube/any other qube that your repo has and don’t know salt at all. If i understand correctly you need to use “top” commands to install the qube, and “state” commands to refresh the qube after changes into salt formulas, is this correct?
1 Like
@QuberSecondComing54 That is incorrect. You should choose just one of the options, either top or state. Top makes sense when you enable multiple formulas so you declare which minions to target based on their properties. Use both and see the difference. Easy answer would be to just use state as top might call other highstates if you don’t disable them after use.
Which docs have you read before trying to use the formula? This will help to give better visibility for important parts of the documentation.
Would be nice to know why “admin” user was mentioned before? Have you named you dom0 user or vault user as admin? Error chdir code
I understand the qfile-dom0-unpacker requires an immense, difficult to type, command-line and some people already have reported issues with it, always a typo. But it is a Qubes tool and does not require a compression tool available on the client. In the future, if I release signed archives, the installation will be easier. The script qvm-copy-to-dom0 can help alleviate the pain.
At last, I don’t want to make the Qubes forum a Qusal issue tracker / support forum, I’d be glad if issues were opened on Github. I mean, people seems eager to help here, such as @deeplow and @Cracker_Tesseract, that is great, I just don’t want to extrapolate using another project forum as mine. Hope you understand.
3 Likes
We generally honor the author’s request. For example for whonix we send people to the whonix forum. For Qusal, if you prefer, we can send them to github. It’s related enought that I feel it could stay here (may need to check with other mods).
2 Likes
I prefer if issues were opened on Github, there I can better assess the situation, close resolved issues, mark as fixed on commit messages etc.
I understand that some people don’t want to create an account on Github because of the company decisions, but I still need to use it as it gives far greater visibility and therefore more contributors and users compared to other forges. For those, that don’t want to create a Github account, sure, they can open a thread here on the Qubes forum, but I am far less responsive here and I don’t encourage users to open an issue on this forum as it can create a bad habit of users of 3rd party community projects (Qusal and othes) opening an issue upstream (Qubes) (Which I believe to be already the case).
If someone wants to help a user here, sure, but in addition, please inform that it is not the correct place to open Qusal issues.
2 Likes
@Quber865 consider yourself informed 
Closing the topic. Please follow up on github.
1 Like