We are getting to "A user space program can't get a Linux
system down (tm)" land, which leads to suspicion that we are hitting something pretty low level... Let's try to look at it a bit systematically:
Please run opencpn
from the terminal using
opencpn > ~/opencpn_out.log 2>&1
until the system freezes.
Then, after restart as your system got frozen, please run the following from the terminal. The second command will ask for your password as it has to get the info very deep from the system. Then give us the opencpnsi.tar.gz file which will get created in your home directory
sudo dmidecode > /tmp/opencpnsi/dmidecode.txt
lsb_release -a > /tmp/opencpnsi/lsb.txt
dpkg --get-selections > /tmp/opencpnsi/packages.txt 2>&1
dpkg -s opencpn > /tmp/opencpnsi/opencpn_deb.txt 2>&1
cat /etc/apt/sources.list > /tmp/opencpnsi/sw_sources.txt
cat /proc/cpuinfo > /tmp/opencpnsi/cpuinfo.txt
lspci > /tmp/opencpnsi/lspci.txt
glxinfo -v > /tmp/opencpnsi/glxinfo.txt
dmesg > /tmp/opencpnsi/dmesg.txt
tail -n 2000 /var/log/syslog > /tmp/opencpnsi/syslog.txt
cp /var/log/dmesg* /tmp/opencpnsi
mv ~/opencpn_out.log /tmp/opencpnsi
cp ~/opencpn.log /tmp/opencpnsi/opencpn.log
cp ~/.opencpn/opencpn.conf /tmp/opencpnsi
tar -czf ~/opencpnsi.tar.gz -C /tmp/opencpnsi .
rm -rf /tmp/opencpnsi
PM me for e-mail if the file will be big or you don't want to make your system info publicly available.
Also, do I understand it right, that this was not happening with 3.2.0, but is constant with 3.2.1? There are just very few changes, so it would greatly decrease the amount of suspicious places.