0004115: Servers Won't Start in Doomseeker (Those that require 3.2-alpha plugin)

Notes
(0022794) Zalewa (developer) 2023-03-12 10:31 edited on: 2023-03-12 10:34	1. Do you use the portable mode? 2. Doomseeker creates a shell script next to where it installs the testing binary. 2.1. What happens when you run that script manually? 2.2. Do the contents of the script look ok? 3. If you can compile Doomseeker from scratch, does it still happen in the current head? (source code:'https://bitbucket.org/Doomseeker/doomseeker/src [^]')

(0022798) JAX (reporter) 2023-03-12 19:38	When you say "portable mode," do you mean downloading it manually, or installing it with the terminal? The Zandronum version I have I got from using the terminal, thanks to these instructions:'https://wiki.zandronum.com/Install_Zandronum_on_Ubuntu. [^]' I used the "Installation with packages" method. I'm not quite sure what you mean by "portable mode," sorry. Also, I keep hearing about running scripts. Is there a way I can do that (or set it up so Doomseeker can load both versions 3.1 and 3.2-alpha)? If someone can point me out where that is, it would be greatly appreciated.

(0022799) Zalewa (developer) 2023-03-12 20:11	If you don't know what is portable mode then you're most likely not running it. You can run Doomseeker in portable mode by starting it with `--portable` argument. It won't be running in this mode otherwise. Quote from JAX I'm not the only one that is having this problem. Others are having this issue as well. I don't, so I'll need additional info from you or from those "others" you mention. Since you don't know about the shell scripts, I will try to guide you to provide me some info, but if you wish to continue using Linux, I recommend you to learn more about the terminal, the shell and its scripts. You will eventually run into more problems and fixing them without this knowledge will be hard. There should be a file on your disk: /home/h0ll1s/.local/share/doomseeker/plugins/zandronum/3.2-alpha-r221030-0316.sh Open this file in a text editor and post here its contents. After this, open a terminal window and execute this command: ls -la /home/h0ll1s/.local/share/doomseeker/plugins/zandronum/ Post here the entire output of this command. After this, try running the sh file from before like this: /bin/bash /home/h0ll1s/.local/share/doomseeker/plugins/zandronum/3.2-alpha-r221030-0316.sh Tell me what happens when you do this and what text appears in the terminal window.

(0022800) JAX (reporter) 2023-03-12 20:19	Some other guy had the issue, and had to use scripting to work around it. I'll upload the photo of the other person that had the issue. I had no such luck. I'll try to use what you suggested, thanks. Also to note, I tried running commands in the terminal before, but it only brought up 3.1 Doomseeker, not 3.2-alpha. I'll try what you suggested, though. Thanks.

(0022801) JAX (reporter) 2023-03-12 20:49	Well, I'm having no suck luck, sorry. I have run some successful commands with the terminal, but it's still a learning process. I just don't know why Doomseeker can't just work with the 3.2-alpha out of the box. I'm still adjusting to scripting and everything. I also uploaded a photo of the other person who encountered this issue, but used some form of scripting to work around this. It seems bad luck just happens to follow me in this case. Uffda...

(0022802) Zalewa (developer) 2023-03-12 21:49 edited on: 2023-03-12 21:51	We have discussed this problem in private and the problem is the fmodex .so lib that is provided with the testing release. This lib isn't available anywhere else in the system, and since Doomseeker 1.4.0 doesn't take care to let the testing binary to load the libs from its own directory, the game won't start complaining that it can't find this lib. I've already fixed this for 1.4.1 in a commit some time ago:'https://bitbucket.org/Doomseeker/doomseeker/commits/1e6a2c950e0000afcb8e6762f5054ef4ce506f17 [^]' Doomseeker 1.4.1 will add `export LD_LIBRARY_PATH` to the launcher scripts it creates for the testing releases. This export will be set to point to the directory with the testing release. Previous Doomseeker versions would also create such a launcher script, but without the LD_LIBRARY_PATH export. Attached: libfmodex-wont-find.jpg

This issue is already marked as resolved. If you feel that is not the case, please reopen it and explain why.
Supporters:	No one explicitly supports this issue yet.
Opponents:	No one explicitly opposes this issue yet.

Issue History
Date Modified	Username	Field	Change
2023-03-11 23:46	JAX	New Issue
2023-03-11 23:46	JAX	File Added: Doomseeker-Plugin-Problem.png
2023-03-12 10:31	Zalewa	Note Added: 0022794
2023-03-12 10:34	Zalewa	Note Edited: 0022794	View Revisions
2023-03-12 19:38	JAX	Note Added: 0022798
2023-03-12 20:11	Zalewa	Note Added: 0022799
2023-03-12 20:19	JAX	Note Added: 0022800
2023-03-12 20:21	JAX	File Added: Other-Person-With-Issue-but-Used-Script.png
2023-03-12 20:49	JAX	Note Added: 0022801
2023-03-12 21:49	Zalewa	Note Added: 0022802
2023-03-12 21:49	Zalewa	Status	new => resolved
2023-03-12 21:49	Zalewa	Fixed in Version	=> 1.4.1
2023-03-12 21:49	Zalewa	Resolution	open => fixed
2023-03-12 21:49	Zalewa	Assigned To	=> Zalewa
2023-03-12 21:50	Zalewa	File Added: libfmodex-wont-find.jpg
2023-03-12 21:51	Zalewa	Note Edited: 0022802	View Revisions

Relationships