Solved Delete

  • Thread starter Deleted member 69948
  • Start date
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:
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.
 
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.
 
Make sure there isn't anything running, then start it from the command line. I'm wondering if it spits out any of those warnings or errors when you try to close it.
 
… now I installed FreeBSD …

Did you somehow install FreeBSD over an installation of GhostBSD, reusing some files within the partition?

If so: which version of GhostBSD preceded the overwrite?

Incidentally, force (-f) by default is debatably not ideal. This example was harmless:

1637502290724.png

– other removals, without confirmation, might be troublesome. FreeBSD bug 259963 – ports-mgmt/octopkg consider not using -f -y (force) by default.

… VirtualBox.

(<https://forums.freebsd.org/posts/542594> Solved)
 
Did you setup doas for it? It needs setup.

This does ring a bell however:
<https://github.com/aarnt/octopkg/commit/88a4366a601bc3fd736ef1292c41ef95ef172b0a> (2020-04-01) was:

- Make octopkg-doas work with sudo when doas is not found.

Some escalation of privileges are needed.

Without doas, an authentication dialogue:
1637503250967.png
 
Back
Top