You are not logged in.
Heya.
I'm the kind of person who prefers to install his games in a specific folder on another drive, because it's way better to separate my games from my root drive so I could manage them without any risk. The thing is that this philosophy doesn't seem to be as much present on Linux than it is on Windows (asking myself why), so in the case of OpenMW, I needed to download the prebuilt folder in order to put it in the Morrowind folder of my SSD.
Since now, it worked very well, with no problems. But I recently updated my PC and realized that OpenMW wasn't longer able to be launched, the terminal giving me this error:
./openmw.x86_64: error while loading shared libraries: libosg.so.132: cannot open shared object file: No such file or directory
It felt very weird to me because normally, my version of OpenMW should be able to be autonomous. After a little look in the libraries folder, I saw by myself that the asked library was not missing. What's happening? How could I say to the game to continue to use its own libraries instead of looking at the ones present on my root partition?
Last edited by byjove01 (2021-05-09 06:32:34)
Offline
The thing is that this philosophy doesn't seem to be as much present on Linux than it is on Windows (asking myself why),
short answer : package managers prevent conflicts between installed applications well.
You may find https://en.wikipedia.org/wiki/Package_manager interesting.
I suggest to keep that discussion out of this thread as I expect it to het up quickly .
Incase you do want to follow up on it, I suggest you start another thread in Off-Topic board (threads in there are blocked from search engines which can be a good thing)
Continuing with the issue .
I needed to download the prebuilt folder
libosg.so.132
That library version is rather old, it comes from openscenegraph 3.4.2 I guess ?
Please clarify where that prebuild folder came from[1] as there are many ways to download openmw stable versions [2].
Apart from that , show the full output from terminal upon starting.
The ./openmw.x86_64 suggests you use some kind of wrapper script to start it, post its contents also.
[1] archlinux repo openmw package switched to osg 3.65 before 0.46 was released , and uses openmw to start so you're clearly not using that.
[2] https://openmw.org/downloads/
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Offline
byjove01 wrote:I needed to download the prebuilt folder
libosg.so.132
That library version is rather old, it comes from openscenegraph 3.4.2 I guess ?
Please clarify where that prebuild folder came from[1] as there are many ways to download openmw stable versions [2].
Apart from that , show the full output from terminal upon starting.
The ./openmw.x86_64 suggests you use some kind of wrapper script to start it, post its contents also.[1] archlinux repo openmw package switched to osg 3.65 before 0.46 was released , and uses openmw to start so you're clearly not using that.
[2] https://openmw.org/downloads/
I download this prebuilt version from OpenMW's website and put my game data in it. I couldn't guarantee at 100% you're right about openscenegraph, but I think there's a lot of chances it's the case.
I'm not using a wrapper script, I just directly launch the compiled executable that was named "openmw.x86_64".
I launched it this way by the terminal in order to get a better output but the error I posted in the first post is the only thing I got...
[1]Nope, I don't use the repo because as I said, my OpenMW equals to prebuilt binaries taken from the website so I could put them on another drive.
[2]site file repository -> linux-> generic -> and now you know where I taken my prebuilt binaries.
Offline
I just directly launch the compiled executable that was named "openmw.x86_64".
That executable is not supposed to be run directly.
Is there a file useqt5 in your install directory [1] ?
If not, create it with
$ touch useqt5
After that try starting openmw or openmw-launcher .
[1] the presence of that file determines whether openmw will use the librariries compiled against qt5 in its lib-qt5 folder or the ones in its lib folder .
The stuff in lib-qt5 version performs better and is the only supported option for post-0.46 .
Last edited by Lone_Wolf (2021-05-04 12:43:37)
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Offline
I just directly launch the compiled executable that was named "openmw.x86_64".
That executable is not supposed to be run directly.
Is there a file useqt5 in your install directory [1] ?
If not, create it with$ touch useqt5
After that try starting openmw or openmw-launcher .
[1] the presence of that file determines whether openmw will use the librariries compiled against qt5 in its lib-qt5 folder or the ones in its lib folder .
The stuff in lib-qt5 version performs better and is the only supported option for post-0.46 .
Ok for the [1] point. So indeed, it's possible to put a package built this way to use local libraries instead of system shared ones...
The command you gave me worked, but the created script doesn't do anything, it seems like it's empty. Maybe it's normal because I don't know the touch cmd, but actually you made me realize I can't launch OpenMW from anywhere.
I tried to launch the OpenMW launcher and the "open-mw-qt54" executable but it still didn't work. You say this executable is not made to be directly launched by the user, guess you're right, but it did work first times, and it wasn't creating any problems.
Offline
The openmw.x86_64 requires some setting up to be able to find the librairies it needs, that is done in the openmw / openmw-launcher scripts.
useqt5 is indeed empty, it's only purpose is to have a simple method to tell the script to use the qt5 librairies.
I did forget openmw / openmw-launcher are not in $PATH and won't be found by shell / bash .
Does
./openmw
work from openmw dir ?
If not, post ouput of ls -l openmw-dir
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Offline
The openmw.x86_64 requires some setting up to be able to find the librairies it needs, that is done in the openmw / openmw-launcher scripts.
useqt5 is indeed empty, it's only purpose is to have a simple method to tell the script to use the qt5 librairies.
I did forget openmw / openmw-launcher are not in $PATH and won't be found by shell / bash .
Does
./openmw
work from openmw dir ?
If not, post ouput of ls -l openmw-dir
Didn't work +
-rwxr--r-- 1 byjove byjove 512 8 juin 2020 bsatool
-rwxr-xr-x 1 byjove byjove 187664 8 juin 2020 bsatool-qt5.x86_64
-rwxr-xr-x 1 byjove byjove 247976 8 juin 2020 bsatool.x86_64
-rw-r--r-- 1 byjove byjove 186612 8 juin 2020 CHANGELOG.txt
drwxr-xr-x 4 byjove byjove 4096 21 juin 2020 data
-rw-r--r-- 1 byjove byjove 4816 8 juin 2020 'DejaVu Font License.txt'
-rwxr--r-- 1 byjove byjove 512 8 juin 2020 esmtool
-rwxr-xr-x 1 byjove byjove 776864 8 juin 2020 esmtool-qt5.x86_64
-rwxr-xr-x 1 byjove byjove 903200 8 juin 2020 esmtool.x86_64
drwxr-xr-x 2 byjove byjove 4096 26 déc. 13:07 fontconfig
-rw-r--r-- 1 byjove byjove 165298 8 juin 2020 gamecontrollerdb.txt
drwxr-xr-x 3 byjove byjove 4096 20 juin 2020 lib
drwxr-xr-x 2 byjove byjove 4096 20 juin 2020 lib-qt5
-rw-r--r-- 1 byjove byjove 35145 8 juin 2020 LICENSE.txt
-rwxr--r-- 1 byjove byjove 512 8 juin 2020 niftest
-rwxr-xr-x 1 byjove byjove 544344 8 juin 2020 niftest-qt5.x86_64
-rwxr-xr-x 1 byjove byjove 704008 8 juin 2020 niftest.x86_64
-rwxr--r-- 1 byjove byjove 510 8 juin 2020 openmw
-rw-r--r-- 1 byjove byjove 28088 8 juin 2020 openmw.cfg
-rwxr--r-- 1 byjove byjove 628 8 juin 2020 openmw-cs
-rw-r--r-- 1 byjove byjove 0 8 juin 2020 openmw-cs.cfg
-rw-r--r-- 1 byjove byjove 65168 8 juin 2020 openmw-cs.png
-rwxr-xr-x 1 byjove byjove 9521096 8 juin 2020 openmw-cs-qt5.x86_64
-rwxr-xr-x 1 byjove byjove 11289200 8 juin 2020 openmw-cs.x86_64
-rwxr--r-- 1 byjove byjove 534 8 juin 2020 openmw-essimporter
-rwxr-xr-x 1 byjove byjove 1177464 8 juin 2020 openmw-essimporter-qt5.x86_64
-rwxr-xr-x 1 byjove byjove 1416872 8 juin 2020 openmw-essimporter.x86_64
-rwxr--r-- 1 byjove byjove 534 8 juin 2020 openmw-iniimporter
-rwxr-xr-x 1 byjove byjove 255976 8 juin 2020 openmw-iniimporter-qt5.x86_64
-rwxr-xr-x 1 byjove byjove 325160 8 juin 2020 openmw-iniimporter.x86_64
-rwxr-xr-x 1 byjove byjove 528 8 juin 2020 openmw-launcher
-rwxr-xr-x 1 byjove byjove 1500544 8 juin 2020 openmw-launcher-qt5.x86_64
-rwxr-xr-x 1 byjove byjove 1689568 8 juin 2020 openmw-launcher.x86_64
-rw-r--r-- 1 byjove byjove 61332 8 juin 2020 openmw.png
-rwxr-xr-x 1 byjove byjove 12897584 8 juin 2020 openmw-qt5.x86_64
-rwxr--r-- 1 byjove byjove 524 8 juin 2020 openmw-wizard
-rwxr-xr-x 1 byjove byjove 841520 8 juin 2020 openmw-wizard-qt5.x86_64
-rwxr-xr-x 1 byjove byjove 958144 8 juin 2020 openmw-wizard.x86_64
-rwxr-xr-x 1 byjove byjove 15496008 8 juin 2020 openmw.x86_64
-rw-r--r-- 1 byjove byjove 287 8 juin 2020 org.openmw.cs.desktop
-rw-r--r-- 1 byjove byjove 287 8 juin 2020 org.openmw.launcher.desktop
-rw-r--r-- 1 byjove byjove 7657 8 juin 2020 README.md
-rw-r--r-- 1 byjove byjove 1022 8 juin 2020 README.packagecontents.txt
drwxr-xr-x 5 byjove byjove 4096 20 juin 2020 resources
-rw-r--r-- 1 byjove byjove 31118 8 juin 2020 settings-default.cfg
-rwxrwxrwx 1 byjove byjove 0 4 mai 21:16 useqt5
Offline
ls output looks normal.
Output of
$ file ./openmw
$ ps -p $$
Does
sh ./openmw
work ?
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Offline
ls output looks normal.
Output of
$ file ./openmw $ ps -p $$
Does
sh ./openmw
work ?
Yes, this time it works now. I don't know why exactly, but seems you were right about the direct executable not being made for that. I guess I'll just redirect my Lutris shortcut to the launch script now. Thanks you!
Offline
The only reason i can think of why sh ./openmw worked but ./openmw didn't is something weird/wrong in the setup of your shell .
If you post the output of the file & ps command I asked , we can look further in to that.
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Offline
The only reason i can think of why sh ./openmw worked but ./openmw didn't is something weird/wrong in the setup of your shell .
If you post the output of the file & ps command I asked , we can look further in to that.
As you want!
"file ./openmw" =>
./openmw: POSIX shell script, ASCII text executable
"ps -p $$" =>
PID TTY TIME CMD
78194 pts/2 00:00:00 bash
Offline
Looking normal, ./openmw and ./openmw-launcher should have worked fine.
Don't think it's worth spending more time on though.
Please prepend [Solved] to the thread title (edit first post, you may have to delete some of it to make room for it)
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Offline
Looking normal, ./openmw and ./openmw-launcher should have worked fine.
Don't think it's worth spending more time on though.
Please prepend [Solved] to the thread title (edit first post, you may have to delete some of it to make room for it)
Did it, thanks again!
Offline