Does not run on Linux

[bbpolterGAYst]

When running the linux application of gmpublisher, it spits out the following error - gmpublisher: error while loading shared libraries: libsteam_api.so: cannot open shared object file: No such file or directory
This can be 'solved' by setting an LD_LIBRARY_PATH to the folder in which gmpublisher is located in. However, afterwards, a new error appears - gmpublisher: error while loading shared libraries: libwebkit2gtk-4.0.so.37: cannot open shared object file: No such file or directory.

I do have the package for libwebkit2gtk, both regular and development versions. I have no idea what is causing this.

[Xalalau]

Ugly workaround for Ubuntu 24.04 based distros (tested on Linux Mint):

sudo ln -sf /usr/lib/x86_64-linux-gnu/libwebkit2gtk-4.1.so.0 /usr/lib/x86_64-linux-gnu/libwebkit2gtk-4.0.so.37
sudo ln -sf /usr/lib/x86_64-linux-gnu/libjavascriptcoregtk-4.1.so.0 /usr/lib/x86_64-linux-gnu/libjavascriptcoregtk-4.0.so.18

[cd00m]

Thing above fixes one error but then gives another error for libsoup
If you install the libsoup version you get this error

(process:1553063): libsoup-ERROR **: 20:31:43.380: libsoup2 symbols detected. Using libsoup2 and libsoup3 in the same process is not supported.

[JakuWorks]

Thing above fixes one error but then gives another error for libsoup If you install the libsoup version you get this error

(process:1553063): libsoup-ERROR **: 20:31:43.380: libsoup2 symbols detected. Using libsoup2 and libsoup3 in the same process is not supported.

I have the same issue. I haven't found any workarounds myself but here's relevant information from lddtree that could help with solving it
(highlighting only the important parts of the output)

jaku@jakuhost:~/Downloads/gmpublisher_linux64$ lddtree ./gmpublisher
./gmpublisher (interpreter => /lib64/ld-linux-x86-64.so.2)
    libwebkit2gtk-4.0.so.37 => /lib/x86_64-linux-gnu/libwebkit2gtk-4.0.so.37
        libsoup-3.0.so.0 => /lib/x86_64-linux-gnu/libsoup-3.0.so.0
    libsoup-2.4.so.1 => /lib/x86_64-linux-gnu/libsoup-2.4.so.1

[JakuWorks]

Somehow removing the libsoup-2.4.so.1 from the executable's dependencies miraculously fixed the issue. Or at least it did for me.
I used patchelf for this. However this is a very dirty and hacky method.
patchelf --remove-needed libsoup-2.4.so.1 ./gmpublisher

[catperson6real-dev]

(process:40454): libsoup-ERROR **: 19:35:58.846: libsoup2 symbols detected. Using libsoup2 and libsoup3 in the same process is not supported.
Trace/breakpoint trap