Faster-whisper-XXL no longer works in Fedora 41

[philthegitter]

Er, I mean Fedora 42. I just upgraded the Fedora version from 41 to 42 and faster-whisper-xxl no longer works, it throws the error:

Traceback (most recent call last):
  File "__main__.py", line 12, in <module>
  File "PyInstaller/loader/pyimod02_importers.py", line 450, in exec_module
  File "ctranslate2/__init__.py", line 21, in <module>
ImportError: libctranslate2-d3638643.so.4.4.0: cannot enable executable stack as shared object requires: Invalid argument
[PYI-64867:ERROR] Failed to execute script '__main__' due to unhandled exception!

[Purfview]

Will be fixed in the next version, meanwhile you can apply fix as there: #495

[philthegitter]

Thanks much. Eagerly looking forward to it. The fix #495,

patchelf --clear-execstack libctranslate2-d3638643.so.4.4.0

doesn't work. Might have something to do with the fact that I'm using the xfce4 spin, not mainline Fedora 42.

[Purfview]

What ldd --version shows?

[philthegitter]

# ldd --version
ldd (GNU libc) 2.41
Copyright (C) 2024 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
Written by Roland McGrath and Ulrich Drepper.

[Purfview]

What execstack -q libctranslate2-d3638643.so.4.4.0 shows?

[philthegitter]

From a fresh install of faster-whisper-xxl (which took about seven tries to download, network issues here this morning):

# execstack -q libctranslate2-d3638643.so.4.4.0
X libctranslate2-d3638643.so.4.4.0
# patchelf --clear-execstack libctranslate2-d3638643.so.4.4.0
# execstack -q libctranslate2-d3638643.so.4.4.0
- libctranslate2-d3638643.so.4.4.0
#

I tried running faster-whisper-xxl both ways, before and after patchelf, same failure:

Traceback (most recent call last):
  File "__main__.py", line 12, in <module>
  File "PyInstaller/loader/pyimod02_importers.py", line 450, in exec_module
  File "ctranslate2/__init__.py", line 21, in <module>
ImportError: libctranslate2-d3638643.so.4.4.0: cannot enable executable stack as shared object requires: Invalid argument
[PYI-63780:ERROR] Failed to execute script '__main__' due to unhandled exception!

Machine is an AMD Ryzen 7 5700U laptop (Acer A315-44P). The faster-whisper-xxl command is being invoked from a line in a bash script which is the AppRun executable file of a ROX-Filer app directory. The bash script appends a timestamp to the filename of a copied image in a tmpfs ramdrive of each video file being transcribed, so that more than one video can be transcribed simultaneously at maximum speed (formerly I was using fw-xxl on a homebuilt dual Haswell Xeon E5-2696v3 tower having 36 physical cores, so 72 threads).

Been using fw-xxl for about a year from this bash script. It ran just fine up through Fedora 41.

The invocation line is:

xterm -hold -geometry 150x24 -e "faster-whisper-xxl --output_dir=/home/admin/Downloads/xxl --model base.en --vad_filter False --output_format txt --verbose=true --device cpu --threads 7 --compute_type int8_float32 --language=English --without_timestamps=true --word_timestamps=false ./$input.'$(cat /tmp/$extensiontosave.txt)'"

[Purfview]

# execstack -q libctranslate2-d3638643.so.4.4.0
- libctranslate2-d3638643.so.4.4.0

That means a patch was successful, so you shouldn't have that error anymore.
I've no idea why you still are getting that error, I'm not so competent at Linux, maybe try to search if there is some another "libctranslate2-d3638643.so.4.4.0" in the system.

Another solution would be to downgrade your glibc 2.41 to 2.40, just in case backup your system before doing this.

[philthegitter]

Bullseye. Ya nailed it, partner.

There are two copies of libctranslate2-d3638643.so.4.4.0, one each in the subdirs

_xxl_data
and
_xxl_data/ctranslate2.libs

Evidently it's the copy in _xxl_data/ctranslate2.libs which gets looked for first and used. After running the patchelf command on that one, success.

Thanks much.

Hi ho Silver--away!!!

[Purfview]

Nice!

BTW, in GitHub's discussions, you should use "Write a reply" field when continuing conversation instead of adding a new comment.

[philthegitter]

Will do, partner!