I don’t know about tensorflow issues, but JetPack can act as a front end to both flashing and extra package installs. If you’ve flashed with JetPack3.2, then you should have L4T R28.2 (currently the most recent release). You can uncheck flash and manage packages at any time…this is a full Ubuntu 16.04 installation when you install L4T R28.2.
You should keep the Jetson updated. There can be an issue with the libglx.so library being overwritten by one of the standard packages, but this is not often and is easily fixed (especially if you fix before rebooting after a package update).
To test if packages are ok and current (not overwritten) you can run this command:
sha1sum -c /etc/nv_tegra_release
The only file I know of which might get overwritten (and would be listed as OK or not in the above command) is:
There is a copy of this file which would never be harmed by regular package updates (and the one which is is rare). This file can be used to restore the other:
If you forget which, then just read “/etc/nv_tegra_release”, this is where the checksums are listed.
Example to restore:
sudo cp /usr/lib/aarch64-linux-gnu/tegra/libglx.so /usr/lib/xorg/modules/extensions/libglx.so
…use this to overwrite the bad copy with the good copy.
If the Jetson is rebooted with the wrong file, then the GUI will fail. Consoles and ssh will still work. The scp command (a subset of ssh) can still copy from one location to another remotely if you don’t have a console.
Someone else will have to comment on tensorflow, but keep your Jetson operating system updated with the usual package tools.