As I already wrote, using ~/.config/openbox/autostart.sh is deprecated. Remove it or comment out the call to it in ~/.xinitrc or ~/.xprofile (whichever applies).
EDIT: Sorry for the confusion, I meant ~/.config/DSB/autostart.sh. Use either the XDG autostart mechanism or Openbox’ autostart.sh, but not both.
If I had read this thread here in the forum first before updating, it would have saved a lot of time and I would have been spared a lot of frustration as well.
I do not with Oktopkg, but with commands in the terminal performed the update.
Same trouble as everyone else.
One piece of information is absent in almost all of the posts in this thread:
Which version of NomadBSD is used!?
Is every post in this thread related to the newest version R130?
-or could it be, that the different experiences and solutions are explained by the fact that different versions are used???
Please state your version of NomadBSD (130R, 1.4, 1.3 or older) and let us shed some light on this possibility…
On NomadBSD 130R-20210508 and NomadBSD-1.4 I succeeded with this big package upgrade
Here are my steps:
% su
# bectl create 2021-07-21_bf-pkg-upgrade (gives you a fallback boot environment if anything goes wrong)
# sh
# for i in $(pkg query -g %n ‘py37-*’); do echo ${i}:py38-${i#py37-}; done
NB.
please notice the change in quotes (') compared to posts above mentioning this command!
With the wrong quotes the command fails silently without doing anything…
Now executing pkg query -g %n 'py37-*' should return nothing and
executing pkg query -g %n 'py38-*' should return a whole list of packages.
Continuing with:
# exit (return from sh - not strictly necessary)
# pkg upgrade (read the upgrade message and press [y] - probably necessary 2 times)
# sed -i ‘’ ‘s/python3.7/python3.8/’ /usr/local/bin/dsbxinput
# sed -i ‘’ ‘s/python3.7/python3.8/’ /usr/local/bin/lbi-gui
# sed -i ‘’ ‘s/python3.7/python3.8/’ /usr/bin/nomadbsd-chusr
# pkg remove python37
# pkg autoremove
reboot with crossed fingers (reboot meant to test if everything starts up normally, in general not needed after upgrade)
This way py38-qt5-* is updated/installed during the pkg upgrade, so no need to do it separately,
and the only python-3.7 package left is python37 itself - it can safely be removed.
If you ignore the for i in $(pkg query...-command, you will end up with a mess of duplicate packages for py37 and py38,
and a few py37 not upgraded to py38 (probably somewhat cleaned up by autoremove).
After a reboot everything is coming up successfully (plank, tint2, BSD)
PS.
If you later need to boot into the boot environment created before the upgrade please read my other thread:
If you recieve the following error (maybe multiple times):
pkg: sqlite error while executing UPDATE packages SET name=?1 WHERE id=?2 in file pkgdb.c:2643: UNIQUE constraint failed: packages.name
It could indicate, you already have installed some of the py38-* packages and your system is in a "messy’ state (unless you’re a developer) where some packages are installed for both versions of python. Everything could still function normally and without a problem, though
Can you please specify if in case one hasn’t performed such updade yet, are the errata steps due to be applied in any case before, or else the latest update already includes such fix?
Thank you
(Edit:) OK, I don’t know why, but even as root I was denied changing ipfwGUI without changing permissions. But I now see, the other files changed with sed have exactly the same permissions. So I may have overlooked something when changing this file…
Not relevant:
Before running sed on ipfwGUI it is necessary to manipulate the permissions and add write permission (and withdraw it afterwards).