Snap exception on LD_LIBRARY_PATH

Hallo, I installed snap 5.0 (removing previous 4.0 installation) and allowed upgrades from the network.
But when I start snap I get the following exception:

The environment variable LD_LIBRARY_PATH does not contain the current folder ‘.’. Its value is ‘/opt/snap/bin/…/./jre/jre/lib/amd64:/opt/snap/bin/…/./jre/jre/lib/i386:/opt/seadas-7.4/lib:’.

This happens on both slackware and centos installation.
(simply trying to access the paths show where is the error:
$ cd /opt/snap/bin/…/./jre/jre/lib/amd64
bash: cd: /opt/snap/bin/…/./jre/jre/lib/amd64: No such file or directory
$ cd /opt/snap/bin/…/./jre/lib/amd64
$ pwd
/opt/snap/jre/lib/amd64

----)

Thanks for any hint

Mario

See gpt: spurious log messages on linux #80. This should not prevent you from using snap and gpt. The workaround suggested in issue #80 will silence the messages. You should be aware that there could be a security risk to this workaround (some nasty user puts a malicious library in a directory that becomes your “current folder”).

I don’t understand “SEVERE” nature of not having dot in your LD_LIBRARY_PATH.
Nor do I understand why SNAP (or GDAL) thinks dot should be in your LD_LIBRARY_PATH.
Now, 3 years later, we still receive:
"SEVERE: org.esa.s2tbx.dataio.gdal.activator.GDALDistributionInstaller: The environment variable LD_LIBRARY_PATH does not contain the current folder ‘.’. "
Maybe someone can fix this so that novice users are not confused.

This should no longer happen starting SNAP 8.