O-Wiki: Clean Install - Performance - Crashes

[rgleason]

I have started a new FAQ Item under Performance - Crashes
following Corsair's directions for a Clean Install for Windows.


https://opencpn.org/wiki/dokuwiki/do...asic:faq:crash


We need the similar instructions for


LINUX
Debian
Flatpak

MACOS


Will you help by posting the OS and the directions here?

[Corsair63]

Not so long ago I had a major crash in my Rpi4 with Debian Bookworm ARM64, the only I could recover was connecting the SSD to my computer and back-up the following files in /home/USER/.opencpn for later use:

• navobj.xml
• opencpn.conf

I had to install from the scratch opencpn, I don't like to use any fork and I use to install as plain o.s.

I do not have to uninstall either clean the installation, because all the SSD was corrupted so I have to start from the beginning.

the uninstall procedure could be that another would find it not properly, so never mind, I want to be corrected if needed.

what I had to do is the installation and setup and was as the second example:

sudo su
sudo apt autoremove opencpn -y
sudo apt autoclean opencpn -y
sudo apt autoremove -y
sudo apt autoclean -y
cd /
sudo chmod 777 /usr/share/opencpn 
sudo chmod 777 /usr/share/opencpn/* 
sudo chmod 777 /usr/share/opencpn/*.*
rm -rf /usr/share/opencpn
sudo chmod 777 /home/USER/.opencpn 
sudo chmod 777 /home/USER/.opencpn/* 
sudo chmod 777 /home/USER/.opencpn/*.*
rm -rf /home/USER/.opencpn
exit
sudo reboot now

USER is the user displayed in the command windows in the Raspberry pi.

after restarted RasPi:

sudo apt update
apt list --upgradable -a
sudo apt full-upgrade -y
sudo apt install opencpn -y
sudo apt install glew-utils -y
sudo apt install opencpn-sglock-arm64 -y
sudo apt autoremove -y
sudo apt autoclean -y
sudo reboot now

• great care with the saved opencpn.conf, you can copy in /home/USER/.opencpn after the installation, but if the program crashes just delete it and restart the program setting up from zero.
• after restarted start with setup of opencpn and check that everything is working.
• connect all devices
• copy the saved navobj.xml to /home/USER/.opencpn
• save the configuration
• install charts
• start installing plugins needed one by one and check for proper operation of plugin and program.

and if everything is fine, had fair winds and nice sailing.

[rgleason]

Originally Posted by Corsair63

Not so long ago I had a major crash in my Rpi4 with Debian Bookworm ARM64, the only I could recover was connecting the SSD to my computer and back-up the following files in /home/USER/.opencpn for later use:

• navobj.xml
• opencpn.conf

I had to install from the scratch opencpn, I don't like to use any fork and I use to install as plain o.s.

I do not have to uninstall either clean the installation, because all the SSD was corrupted so I have to start from the beginning.

the uninstall procedure could be that another would find it not properly, so never mind, I want to be corrected if needed.

what I had to do is the installation and setup and was as the second example:

sudo su
sudo apt autoremove opencpn -y
sudo apt autoclean opencpn -y
sudo apt autoremove -y
sudo apt autoclean -y
cd /
sudo chmod 777 /usr/share/opencpn 
sudo chmod 777 /usr/share/opencpn/* 
sudo chmod 777 /usr/share/opencpn/*.*
rm -rf /usr/share/opencpn
sudo chmod 777 /home/USER/.opencpn 
sudo chmod 777 /home/USER/.opencpn/* 
sudo chmod 777 /home/USER/.opencpn/*.*
rm -rf /home/USER/.opencpn
exit
sudo reboot now

USER is the user displayed in the command windows in the Raspberry pi.

after restarted RasPi:

sudo apt update
apt list --upgradable -a
sudo apt full-upgrade -y
sudo apt install opencpn -y
sudo apt install glew-utils -y
sudo apt install opencpn-sglock-arm64 -y
sudo apt autoremove -y
sudo apt autoclean -y
sudo reboot now

• great care with the saved opencpn.conf, you can copy in /home/USER/.opencpn after the installation, but if the program crashes just delete it and restart the program setting up from zero.
• after restarted start with setup of opencpn and check that everything is working.
• connect all devices
• copy the saved navobj.xml to /home/USER/.opencpn
• save the configuration
• install charts
• start installing plugins needed one by one and check for proper operation of plugin and program.
• and if everything is fine, had fair winds and nice sailing.

Added. Thanks.

https://opencpn.org/wiki/dokuwiki/do...asic:faq:crash

[BlackSea]

SCNR
What @Corsair63 writes unfortunately does not speak for his good knowledge of Linux. It's just confusing what it says
@rgleason you would be well advised not to publish this

[rgleason]

Originally Posted by BlackSea

SCNR
What @Corsair63 writes unfortunately does not speak for his good knowledge of Linux. It's just confusing what it says
@rgleason you would be well advised not to publish this

Ok, I will do that, but can you take some time and get it "RIGHT" for all of us?
What exactly do you think is confusing, inaccurate, improper, misleading, etc.?

You acknowledge he has good knowldege of Linux.

[rgleason]

@Corsair63
Do you have some editing for us here for Linux?
https://opencpn.org/wiki/dokuwiki/do...tall_for_linux


It has been suggested not to publish this, by someone who has not offered why it should not be published.

[Corsair63]

Originally Posted by rgleason

@Corsair63
Do you have some editing for us here for Linux?
https://opencpn.org/wiki/dokuwiki/do...tall_for_linux


It has been suggested not to publish this, by someone who has not offered why it should not be published.

I'm not very conversant on Linux, but reading instructions manuals I did that, at least for install and worked to me.

the first part (clean-up) I haven't test but it's what I should do.

in my message I said that if anyone is not agreed with it, I'm open to learn and it's not any problem for me to correct it.

[BlackSea]

It has been suggested not to publish this, by someone who has not offered why it should not be published.

Thanks rick, very nice of you not to even mention nickname. That was me.
Why did I guess that? Ok, I'll try to explain


I start with “uninstall”

sudo su

OK. I translate into human language. make me a superuser(god) (partialy agree)

sudo apt autoremove opencpn -y
sudo apt autoclean opencpn -y
sudo apt autoremove -y
sudo apt autoclean -y

1. If I am already superuser, why should I explicitly enter each command to be executed as superuser? (prefix "sudo" for each command)

2. "autoremove opencpn" ?

Check "man 8 apt" what makes this option

cd /
sudo chmod 777 /usr/share/opencpn
sudo chmod 777 /usr/share/opencpn/*
sudo chmod 777 /usr/share/opencpn/*.*

Ouch. Why?
Fundamental lack of understanding of permissions for files and directories under Linux/Unix and how wildcards work.

sudo chmod 777 /home/USER/.opencpn
sudo chmod 777 /home/USER/.opencpn/*
sudo chmod 777 /home/USER/.opencpn/*.*

same as above

sudo reboot now

"now" is superfluous

the first part (clean-up) I haven't test but it's what I should do.

and then beginners are supposed to copy and paste it?

[BlackSea]

My suggestion for "clean uninstall" would be the following. Applies to Debian/Ubuntu
1. Backup your OpenCPN configuration

$ mv ~/.opencpn ~/.opencpn.bak

2. Determine which OpenCPN packages are installed

 $ dpkg --get-selections | grep opencpn
opencpn                        install
opencpn-data                install

3. Delete packages from step 2

$ sudo apt-get purge opencpn opencpn-data

4. Delete local installed plugins

$ rm -rf ~/.local/lib/opencpn

5. Delete binaries that were brought by plugins. For example

$ rm ~/.local/bin/{oexserverd,OCPNsenc,libsgl*}

[rgleason]

Dear Blacksea, thank you for showing us. It is much appreciated!
I will make changes to Corsair63's effort later today, and hope you will have a chance to review and correct my mistakes too. Thanks Corsair for the good old college try!

[rgleason]

Ok second draft is done.
https://opencpn.org/wiki/dokuwiki/do...asic:faq:crash

[Corsair63]

Hi Rick/Blacksea,

thanks for the correction,

Please let me know if I'm wrong:

$ mv ~/.opencpn ~/.opencpn.bak                  = Backup OpenCPN configuration
$ dpkg --get-selections | grep opencpn          = List installed OpenCPN packages
  opencpn                     install
  opencpn-data                install
$ sudo apt-get purge opencpn opencpn-data       = Delete OpenCPN packages
$ rm -rf ~/.local/lib/opencpn                   = Delete local installed plugins
$ rm ~/.local/bin/{oexserverd,OCPNsenc,libsgl*} = Delete binaries for plugins. Example.
$ reboot

as far as I see all command are done as per superuser, so the block of commands should start with

sudo su

of course starting from that commands with sudo is redundant but doesn't harm.

about using chmod 777 without wildcard and with wildcards, I had experienced sometimes that files inside folder still had no permission for "pi" user, that's why I did it to prevent it, and neither able to edit nor delete.
because I do not use to work on the RasPi (just in case) as "su", I do as "pi", to avoid "touch" untouchable files/folders.

[BlackSea]

as far as I see all command are done as per superuser, so the block of commands should start with

sudo su

NO! You don't need this anymore
You need "sudo" only once for purging of packages

[rgleason]

Originally Posted by BlackSea

NO! You don't need this anymore
You need "sudo" only once for purging of packages

Ok I've added that. How does it look now. Thanks Corsair!
https://opencpn.org/wiki/dokuwiki/do...asic:faq:crash

[Aldebaran17]

A few comments from my side:

in a parallel thread @BlackSea helped me to fix a problem.

Some comments from my side:
1. The recipe reported for Linus works and can be used, even by somebody who is virtually iliterate in Linux. So, I can support his suggestion to fix problems.

2. For me personally, it would be helpful to get some hints, what these crpytic Linux commands do and why the may be helpful. Again, this applies to me: I am very reluctant to follow a recipe, which I do not understand, if I have no clew, why it is a good recipe.

A sentence like: a possible source of trouble is in inconsistent install, caused by using multiple or inconsistent, possibly outdated, sources when updating previously. This can be fixed.

3. On the OpenGL issue: I remember, that at some point it was helpful to edit the conf file. There were two settings regarding OpenGL, only one is accessible to the user via the GUI. Ist that still an issue?

4. I am contemplating a while, what to recommend for MacOS. As a user for a couple of years i do not remember any case, where I had issues with my Mac install. Sometimes, there are (or there were) issues while beta-testing versions or plugins, but there was never ever a need to do a clean reinstall. And once I had an hardware issue (USB-C connector not working any more and o-chart dongle could not be recognized). But besides from that, no issues.
One reason maybe, that the application with all libraries and stuff is packaged, so the normal user cannot possibly mess this up, it can not be inconsistent as in my current Pi issue. You could mess up using the terminal command line interface, but a normal user does not do that.

I added a sentence, which reflects my knowledge, just to have something written there.

Manfred