Bug with Launcher under Linux with dev23 - not able to start fs-uae binary

Hey guys, I think there is a new bug in dev23.

If I start fs-uae-launcher in my Documents/FS-UAE folder everything is fine, but starting it in my home dir for example fails with the following error:

FSUAE.start_with_args: [u'/tmp/tmpTmkIO_.fs-uae']
current dir (cwd): /mnt/encrypted/home/aceman
using fs-uae executable: ./fs-uae
[u'./fs-uae', u'/tmp/tmpTmkIO_.fs-uae']
Traceback (most recent call last):
File "/usr/lib64/python2.7/site-packages/fs_uae_launcher/ui/LaunchDialog.py",
line 90, in handler_thread
self._handler_thread()
File "/usr/lib64/python2.7/site-packages/fs_uae_launcher/ui/LaunchDialog.py",
line 99, in _handler_thread
self.handler.run()
File "/usr/lib64/python2.7/site-packages/fs_uae_launcher/LaunchHandler.py",
line 105, in run
self.start()
File "/usr/lib64/python2.7/site-packages/fs_uae_launcher/LaunchHandler.py",
line 552, in start
process, config_file = FSUAE.start_with_config(config)
File "/usr/lib64/python2.7/site-packages/fs_uae_launcher/FSUAE.py", line 24,
in start_with_config
return cls.start_with_args(args), config_file
File "/usr/lib64/python2.7/site-packages/fs_uae_launcher/FSUAE.py", line 38,
in start_with_args
proc = subprocess.Popen(args, env=env, **kwargs)
File "/usr/lib64/python2.7/subprocess.py", line 679, in __init__
errread, errwrite)
File "/usr/lib64/python2.7/subprocess.py", line 1249, in _execute_child
raise child_exception
OSError: [Errno 13] Keine Berechtigung
__close_event

I think the try to start the fs-uae binary with "./fs-uae" fails. If I am in my FS-UAE folder there is a "fs-uae" without the "./" and it starts just fine

greetings, mike

[nexusle]

*** Deleted ***

[FrodeSolheim]

Hi, the launcher tries to start ./fs-uae if it finds it in the current directory, this is really just used for testing during development.

Perhaps you have a "fs-uae" folder in your home directory? The launcher just checks for the existence of the path "./fs-uae", not whether it is a directory or a file (will fix that).

Originally Posted by FrodeSolheim

Hi, the launcher tries to start ./fs-uae if it finds it in the current directory, this is really just used for testing during development.

Perhaps you have a "fs-uae" folder in your home directory? The launcher just checks for the existence of the path "./fs-uae", not whether it is a directory or a file (will fix that).

Ah yes, that must be it. I have a softlink in my home-directory from FS-UAE to Documents/FS-UAE, because somehow fs-use tries to save/load some stuff directly under ~/fs-use (not everything though) and I was too lazy to find out why until now.

Guess its time to take a closer look to that ;-)

[FrodeSolheim]

This problem should not occur with the newly released FS-UAE (Launcher) 2.1.24!