Today I downloaded and installed LO 6.2.5 in my Debian 9.9 ("Stretch", oldstable) system. This is the information in the file /opt/libreoffice6.2/program/versionrc: --- Quote Beginning --- [Version] AllLanguages=en-US BuildVersion= buildid=1ec314fa52f458adc18c4f025c545a4e8b22c159 ExtensionUpdateURL=http://updateexte.libreoffice.org/ExtensionUpdateService/check.Update ReferenceOOoMajorMinor=4.1 UpdateChannel= UpdateID=LibreOffice_6_en-US UpdateURL=https://update.libreoffice.org/check.php?pkgfmt=deb UpdateUserAgent=<PRODUCT> (${buildid}; ${_OS}; ${_ARCH}; <OPTIONAL_OS_HW_DATA>) Vendor=The Document Foundation --- Quote End --- LO Writer does not start in this LO version. This is the output on the command line: --- Quote Beginning --- xxx@yyy:/opt/libreoffice6.2/program$ ./swriter /opt/libreoffice6.2/program/oosplash: error while loading shared libraries: libXinerama.so.1: cannot open shared object file: No such file or directory xxx@yyy:/opt/libreoffice6.2/program$ --- Quote End --- I then located the file libXinerama.so.1 in /usr/lib/x86_64-linux-gnu/, ran as user root "export LD_LIBRARY_PATH=/usr/lib/x86_64-linux-gnu/" and then "ldconfig". As a normal user I inserted the following line in my .basrc file: export LD_LIBRARY_PATH=/usr/lib/x86_64-linux-gnu/ I then logged into KDE again as a normal user and executed: printenv | grep LD_LIBRARY_PATH which returned: --- Quote Beginning --- xxx@yyy:~$ printenv | grep LD_LIBRARY_PATH LD_LIBRARY_PATH=/usr/lib/x86_64-linux-gnu/ xxx@yyy:~$ --- Quote End --- I then tried to start swriter again: --- Quote Beginning --- xxx@yyy:/opt/libreoffice6.2/program$ ./swriter /opt/libreoffice6.2/program/oosplash: error while loading shared libraries: libXinerama.so.1: wrong ELF class: ELFCLASS64 xxx@yyy:/opt/libreoffice6.2/program$ --- Quote End --- swriter does not start. What to do?
My guess would be you downloaded / installed LO in 32bit but have a 64bit system. Since Debian is multi-arch, you can install all the missing, required 32bit libraries, if you really want to run the 32bit LO version, but I suggest to download the packages matching your architecture. Might also be the other way around. file soffice.bin should tell you the architecture of your LO version, any other binary on your system its arch. If I'm correct, please close this bug as RESOLVED, INVALID.
(In reply to Jan-Marek Glogowski from comment #1) > My guess would be you downloaded / installed LO > in 32bit but have a 64bit system. I have a 64-bit system: --- Quote beginning --- xxx@yyy:~$ uname -a Linux yyy 4.9.0-9-amd64 #1 SMP Debian 4.9.168-1+deb9u4 (2019-07-19) x86_64 GNU/Linux xxx@yyy:~$ --- Quote End --- > Might also be the other way around. file soffice.bin should tell you the > architecture of your LO version, any other binary on your system its arch. When I run soffice.bin, then the following is returned: --- Quote beginning --- xxx@yyyy:/opt/libreoffice6.2/program$ ./soffice.bin ./soffice.bin: error while loading shared libraries: libdbus-1.so.3: cannot open shared object file: No such file or directory xxx@yyy:/opt/libreoffice6.2/program$ --- Quote End --- I have downloaded and installed the 64-bit version of LO 6.2.5, if you look at the directory and file names in my download directory: --- Quote beginning --- xxx@yyy:~/Desktop_1/installationsdateien/libreoffice$ ls LibreOffice_6.2.5.2_Linux_x86_deb LibreOffice_6.2.5_Linux_x86_deb_helppack_de.tar.gz LibreOffice_6.2.5.2_Linux_x86_deb_helppack_de LibreOffice_6.2.5_Linux_x86_deb_langpack_de.tar.gz LibreOffice_6.2.5.2_Linux_x86_deb_langpack_de LibreOffice_6.2.5_Linux_x86_deb.tar.gz xxx@yyy:~/Desktop_1/installationsdateien/libreoffice$ --- Quote End --- I installed LO 6.2.5 from within the directories mentioned above using the dpkg command.
You should use package repos instead of trying with dpkg. Indeed, the deb or rpm files are mainly for those maintaining packaging or know how to deal with dependencies. I know it's possible to use a package from another branch. I don't know the details but I suppose you can find them by Googling a bit. Also, just wonder what's the use of the machine? Is it a production server or your personal PC? In first case, I understand you use old stable but don't know why you'd install an Office suite in second case, I understand you want a recent LO version but don't understand why you want to stick to stable which contain old releases.
In fact I installed the packages of the 32-bit version of LO 6.2.5.2, which was not my intention. I detected my fault when I tried to install these packages not in Debian Stretch (Debian 9.9, oldstable), but in Debian Buster (Debian 10.0, stable). When I executed the command "dpkg -i *" in Debian Buster, I got informed that the packages I intended to install where 32 bit, while the target system is a 64 bit system. These packages could not be installed in Debian Buster. I then downloaded the archives of the amdx64 version of LO 6.2.5.2 in Debian Stretch and installed them. Trying to start swriter results in an Application Error on the console. swriter does not start. (In reply to Julien Nabet from comment #3) > You should use package repos instead of > trying with dpkg. > Indeed, the deb or rpm files are mainly > for those maintaining packaging or > know how to deal with dependencies. Thanks for this hint. Yes, indeed, the LO packages belonging to a certain Debian release are adapted to Debian. This can be seen if one looks at the deb file names of these packages, they seem to be special Debian versions of LO. > Also, just wonder what's the use of the machine? > Is it a production server or your personal PC? It is my personal PC. > In first case, I understand you use old stable > but don't know why you'd install an Office suite The oldstable version of Debian (Stretch) gets supported until June 2020, so it is not totally out of date yet. > in second case, I understand you want a recent LO version but don't > understand why you want to stick to stable which contain old releases. My Debian oldstable installation (Stretch) is my productive system. My Debian stable installation (Buster) is my current testing system. I noticed that LO 6.2.5.2, downloaded from the LO web site, runs successfully in Debian stable (Debian Buster). So I will upgrade my oldstable system (Stretch, my productive system) to the stable version (Buster) in order to be able to use LO 6.2.5.2, downloaded from the LO web site, in my productive system. I have put this bug reported to RESOLVED, INVALID, as suggested by Jan-Marek Glogowski.