D
Deleted member 69948
Guest
Whenever I close Octopkg I cannot open it again without going to the system monitor and ending the octopkg processes first. Any way to fix this?
Last edited by a moderator:
There aren't any warnings or errors in the terminal when I type bsd@bsd-ghostbsd-pc /u/l/bin> octopkg. It doesn't do anything when the octopkg processes are still running.Try starting it from a terminal window, it may spit out a bunch of warnings and/or errors that might be useful to figure out what is going wrong.
?There aren't any warnings or errors in the terminal when I type bsd@bsd-ghostbsd-pc /u/l/bin> octopkg. It doesn't do anything when the octopkg processes are still running.
Yes, it seems really buggy, so now I installed FreeBSD, but I'm having issues getting it working in VirtualBox.OP: is this a GhostBSD instance?
… now I installed FreeBSD …
-f
) by default is debatably not ideal. This example was harmless:… VirtualBox.
Did you setup doas for it? It needs setup.
- Make octopkg-doas work with sudo when doas is not found.
Some escalation of privileges are needed.