Chromium using libxml from other packages?

[anike...@iiitd.ac.in]

I have been using Chromium for a long time now, and I recently installed Vivado, on Linux. Since then, chromium fails to start, giving an error like this:

/usr/lib/chromium/chromium: /opt/Xilinx/SDx/2018.2/lib/lnx64.o/Default/libstdc++.so.6: version `GLIBCXX_3.4.23' not found (required by /usr/lib/chromium/chromium)

/usr/lib/chromium/chromium: /opt/Xilinx/SDx/2018.2/lib/lnx64.o/libxml2.so.2: no version information available (required by /usr/lib/chromium/chromium)

/usr/lib/chromium/chromium: /opt/Xilinx/SDx/2018.2/lib/lnx64.o/libxml2.so.2: no version information available (required by /usr/lib/chromium/chromium)

/usr/lib/chromium/chromium: /opt/Xilinx/SDx/2018.2/lib/lnx64.o/libxml2.so.2: no version information available (required by /usr/lib/chromium/chromium)

/usr/lib/chromium/chromium: /opt/Xilinx/SDx/2018.2/lib/lnx64.o/libxml2.so.2: no version information available (required by /usr/lib/chromium/chromium)

/usr/lib/chromium/chromium: /opt/Xilinx/SDx/2018.2/lib/lnx64.o/libxml2.so.2: no version information available (required by /usr/lib/chromium/chromium)

/usr/lib/chromium/chromium: /opt/Xilinx/SDx/2018.2/lib/lnx64.o/libxml2.so.2: no version information available (required by /usr/lib/chromium/chromium)

/usr/lib/chromium/chromium: /opt/Xilinx/SDx/2018.2/lib/lnx64.o/libxml2.so.2: no version information available (required by /usr/lib/libavformat.so.58)

/usr/lib/chromium/chromium: /opt/Xilinx/SDx/2018.2/lib/lnx64.o/libxml2.so.2: no version information available (required by /usr/lib/libavformat.so.58)

/usr/lib/chromium/chromium: /opt/Xilinx/SDx/2018.2/lib/lnx64.o/libxml2.so.2: no version information available (required by /usr/lib/libavformat.so.58)

/usr/lib/chromium/chromium: /opt/Xilinx/SDx/2018.2/lib/lnx64.o/libxml2.so.2: no version information available (required by /usr/lib/libbluray.so.2)

/usr/lib/chromium/chromium: /opt/Xilinx/SDx/2018.2/lib/lnx64.o/libxml2.so.2: no version information available (required by /usr/lib/libbluray.so.2)

It looks like Chromium is trying to use Vivado's libxml, which sounds strange. Is there a solution to fix this problem?

P.S. This question is ported from here. I thought I should post this on the official channel, and I am not sure that the reddit's sub is official.

[Adam Rice]

Sounds like you are using a version of Chromium from your Linux distribution. Try running 

LD_LIBRARY_PATH= /usr/bin/chromium

to locally undo any modifications Vivado may have made to your LD_LIBRARY_PATH environment variable.

--
--
Chromium Discussion mailing list: chromium...@chromium.org
View archives, change email options, or unsubscribe:
http://groups.google.com/a/chromium.org/group/chromium-discuss

[anike...@iiitd.ac.in]

I had installed Chromium from the chromium package, for Arch.

You are right. I was looking over some scripts executed by Vivado, which involves over-writing the `LD_LIBRARY_PATH` variable.

I reset the `LD_LIBRARY_PATH` variable to `/usr/bin/chromium`, however I wonder if that will not affect Vivado's functioning. Can I use separate variables for each of them? Or add multiple paths with using the `:` as a separator.

[anike...@iiitd.ac.in]

I looked over Vivado's scripts again, and found that it was appending to the $LD_LIBRARY_PATH variable, and not over-writing it. Even I tried to manually over-write it, however Chromium doesn't seem to separate the paths from the variables. 

This may sound weird, but it sounds like a bug. Maybe you can try it on your machine. Try appending to $LD_LIBRARY_PATH, and try to start chromium on your system.

[Adam Rice]

I think obeying LD_LIBRARY_PATH is the intended behaviour, as that is how other software behaves and it can be useful in some scenarios.

Instead of changing LD_LIBRARY_PATH globally, you can change it only when you run Chrome by setting an empty value on the command-line, like this

LD_LIBRARY_PATH="" chromium

Probably if you change LD_LIBRARY_PATH globally, Vivado will stop working.

[anike...@iiitd.ac.in]

That's not what I meant, though. I am changing the variable locally, when I execute chromium. 

However, my doubt was that shouldn't chromium look for it's own libxml path in the LD_LIBRARY_PATH (which is separated by a ':' delimiter)? Just like the $PATH variable, it should extract the required path from the variable value.

Please excuse me, if am being buggy (no pun), but I am just curious about this new thing.

[Adam Rice]

However, my doubt was that shouldn't chromium look for it's own libxml path in the LD_LIBRARY_PATH (which is separated by a ':' delimiter)? 

It will load the first libxml it sees, scanning LD_LIBRARY_PATH from left to right.