linutil
linutil copied to clipboard
ChrisTitusTech
Error on line 198 (running on /linuxdev)
Describe the bug
I was installing archtitus on my mini pc and came up with the error after the essential utilities (network manager etc) Exact error says "/bin/bash: line 198 cd /tmp/linutil_scrips.llPufCmADD9g/system-setup/arch no such file or directory"
To Reproduce
Steps to reproduce the behavior:
- Run the dev branch of linutil (christitus.com/linuxdev)
- Arch setup
- Try and install archtitus
- See error
Expected behavior
Not to error/continue with install
Screenshots
If applicable, add screenshots to help explain your problem.
Additional context
Add any other context about the problem here.
I got the same error but I rebooted into arch server ok ( didn't time all this was in the 2 minute region though) and installed plasma back around to linutil for install other bits after I now have fingers crossed but yes that error was there at install...
I was able to replicate this issue as well. However, if you exit out of linutil and reboot your system you'll see that it did install the server. But the error is dumb and will confuse users.
Playing around with the script code locally, if adding a mkdir -p /tmp/ and comment out the cd line inside "Cleaning", seem to resolve this issue.
I'm not sure if its ommit any of the logic around reverting the sudors though.
I was able to replicate this issue as well. However, if you exit out of linutil and reboot your system you'll see that it did install the server. But the error is dumb and will confuse users.
And I think that is why it confused me a lot. As the error popped up and didn't even think to test it out if it installed or not
@ChrisTitusTech is there any chance that this could be looked into? I know you mainly look at PRs but. Not sure if this is worth a PR. Plus. Not sure what to mainly fix. As I had a look at the code and line 198 doesn't say anything about it
@ChrisTitusTech is there any chance that this could be looked into? I know you mainly look at PRs but. Not sure if this is worth a PR. Plus. Not sure what to mainly fix. As I had a look at the code and line 198 doesn't say anything about it
I think I fixed this and in the next latest release it will work properly.
