Arch Linux User Repository

Small nuance but hey. ib-tws seems to create a (hidden) folder in ~ on each startup. The folder has this kind of name: .yyyymmdd.ib-tws, and has one file in it, which is launcher.log.

Is there any way to set this log folder, so that it stops spamming the home folder?

Bonus question: how easy (or hard) would it be to install and run tb-tws on arm architecture, instead of x64?

@shimi, this is probably due to your shell adding environment variables that aren't available when launching from desktop entries. For a quick test, try creating a user copy of the desktop file and modify it to source your Fish environment:

# Copy the desktop file to your user directory
cp /usr/share/applications/ib-tws.desktop ~/.local/share/applications/

# Modify it to source your Fish config
sed -i 's|Exec=/usr/bin/ib-tws|Exec=/usr/bin/fish -c "source ~/.config/fish/config.fish; /usr/bin/ib-tws"|' ~/.local/share/applications/ib-tws.desktop

# Update the desktop database
update-desktop-database ~/.local/share/applications/
kbuildsycoca5 --noincremental

If that fixes the issue, you can make it permanent by creating ~/.config/environment.d/ib-tws.conf containing the environment variables you need (like JAVA_HOME, PATH additions etc) so desktop entries pick them up automatically. Check what variables Fish is setting with env | grep -E "(JAVA|PATH|LD_LIBRARY)" in your terminal to see what might be missing. Don't forget to remove your user-specific .desktop file and refresh Plasma using the above commands.

This approach avoids modifying the system .desktop files that will get overwritten during future package updates.

I'm having an issue that the application works 100% fine when running ib-tws from the terminal, but there are some bugs if it is executed from the desktop file. I'm using plasma and fish. Any idea why this could be? The desktop file seems to just execute /usr/bin/ib-tws which is also the answer to "which ib-tws" in the terminal.

From the desktop file the app does run but the menus are flaky and exporting to csv from the account menu does not work at all (the file select window just doesn't open). All of this works fine when ib-tws executed from the terminal. Any ideas on why this could be?

    tws-10.35.1f-standalone-linux-x64.sh ... FAILED
==> ERROR: One or more files did not pass the validity check!

Looks like they changed something again without bumping the version

I had the same issue as zwindl. Deleting the director ~/.local/share/i4j_jres and re-building the package fixed it for me.

TWS version 10.34.1c-2 works for me without further actions. Thank you all for help and comments.

@benalexau, ahhh, I see, ibkr maintained its own java runtime, that's the reason why I couldn't affect it by archlinux-java. I deleted the aur cache and the log4j cache, rebuilt it, now it works just fine. Thanks for the help!

@zwindl I suspect there is something problematic with the package when it is being built on your machine. If you have a look at https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=ib-tws#n44 there is logic which attempts to detect the Java bundled with TWS. It has been important for a few years now to use the exact Java that was bundled by IB (historically this package just used shared Java installations, but IB stuck with Java 8 until TWS 10.34.1a and it caused far too many problems to share Java 8). I'd suggest trying to build the package again and reviewing the log messages to see which Java it is detecting from the TWS archive. If you still have issues, please paste the log messages here so I can have a closer look.

@benalexau so weird, the output of /usr/share/ib-tws/jre/bin/java -version on my console prints:

java version "1.8.0_202"
Java(TM) SE Runtime Environment (build 1.8.0_202-b08)
Java HotSpot(TM) 64-Bit Server VM (build 25.202-b08, mixed mode)

After changing the java path to /usr/bin/java (which is java-23-jdk) in /usr/bin/ib-tws manually, run ib-tws again it will report:

WARNING: Unknown module: javafx.web specified to --add-exports
WARNING: Unknown module: javafx.media specified to --add-exports
WARNING: Unknown module: javafx.media specified to --add-exports
WARNING: Unknown module: javafx.media specified to --add-exports
WARNING: Unknown module: javafx.media specified to --add-exports
WARNING: Unknown module: javafx.graphics specified to --add-opens

and hang there.

@zwindl this should not occur. Version 1:10.34.1c-2 provides /usr/bin/ib-tws which now includes --add-opens and --add-exports parameters as required by the new Java 17 shipped in recent TWS distributions. The package ensures /usr/share/ib-tws/jre/bin/java is the same Java as provided in the TWS distribution. If you execute /usr/share/ib-tws/jre/bin/java -version it should report (as of 1:10.34.1c-2) openjdk version "17.0.10.0.101" 2024-04-16 LTS. Java 17 can handle those parameters, so the error message suggests you are executing an earlier version of Java for an unknown reason. If you manage to login to TWS, try Help > About to see which Java it reports there (it should be 17.0.10.0.101 at present).