Package Details: ib-tws 1:10.33.1c-1

Git Clone URL: https://aur.archlinux.org/ib-tws.git (read-only, click to copy)
Package Base: ib-tws
Description: Electronic trading platform from discount brokerage firm Interactive Brokers (IBKR)
Upstream URL: http://interactivebrokers.com/
Licenses: custom
Submitter: benalexau
Maintainer: benalexau
Last Packager: benalexau
Votes: 43
Popularity: 0.32
First Submitted: 2013-01-30 06:21 (UTC)
Last Updated: 2024-12-20 01:01 (UTC)

Latest Comments

« First ‹ Previous 1 .. 13 14 15 16 17 18 19 20 21 Next › Last »

dgerdem commented on 2017-07-02 23:11 (UTC)

I'm getting a checksum failure when I try to install. the tws-latest script fails its checksum after it downloads. I am running Manjaro, if it matters.

emphire commented on 2017-06-24 01:21 (UTC)

I already had it installed but tried installing ffmpeg2.8 as well. I'm not sure how to reproduce it but if I hear any sounds I'll let you know.

benalexau commented on 2017-06-24 00:20 (UTC)

I've never seen that error, but I found libavcodec.so and libavformat.so in package ffmpeg. Perhaps you could try installing that? If it works please comment here and I'll update the optdepends.

emphire commented on 2017-06-24 00:10 (UTC)

While running I received a dialog saying "Your system is missing codecs for audio playback. Please install GLIB 2.28, libavcodec53 and libavformat53 for Ubuntu Linux 12.04 or equivalent". Any idea what packages I would need to install for that? If we can sort out which ones maybe they can be added as optdepends.

smfsh commented on 2017-06-13 17:35 (UTC)

Looks good now! Thank you so much for your help on this!

benalexau commented on 2017-05-31 01:22 (UTC)

@Mills00013 and @goodboy, this is now fixed. I didn't detect it earlier as I principally use IB Controller and it runs IB Gateway, and IB Gateway was not impacted. The root case was TWS (but not IB Gateway) now require JavaFX and other features in Oracle JRE. As such I have amended the package to now install and use the IB-provided Oracle JRE in a TWS-specific private directory. Would you please confirm this resolves your issue? Thanks.

smfsh commented on 2017-05-30 16:22 (UTC)

I'm running into the same issue that goodboy was running into with the launch hanging on "Processing startup parameters". I did setup ib-controller, but I might be missing how it's supposed to help. Doesn't the controller just suppress the UI into a (windowless) server mode? I'd like to be able to demo the interface which is obviously not super accessible when the interface is in a virtual frame buffer. I feel like I've got to be missing something obvious here.

benalexau commented on 2017-01-12 02:18 (UTC)

I'd suggest the ib-controller AUR package. It is designed to run TWS as a systemd service, including authentication files with secure permissions by default etc.

goodboy commented on 2017-01-12 02:13 (UTC) (edited on 2017-01-12 02:14 (UTC) by goodboy)

Thanks for the explanation benalexau. I've tried starting ib-tws in demo mode and it keeps hanging after the splash screen displays "Processing startup parameters...". Any ideas?

benalexau commented on 2017-01-11 22:29 (UTC)

All AUR packages are hosted in an AUR-specific Git repository. Details are at https://wiki.archlinux.org/index.php/Arch_User_Repository. You can access any AUR's repository via clicking the "View Changes" link at the top of the package's AUR page. Thanks for reporting the checksum issue. Our friends at Interactive Brokers released 962.2c at least twice, each with different hash codes. My scripts (themselves in the aforementioned AUR repository) run daily and only update the AUR package if both the "latest" tarball and the version number extracted from the associated execution log differ from the existing PKGBUILD. Given IB failed to increment the version number despite releasing a tarball with different contents, this explains why the package was not updated to reflect the new hash code. I wish IB would follow best practice and include a version number in the HTTP path, and treat file releases as immutable (ie have a staging environment to test and promote releases, incrementing the version number if a release was promoted in error). Until then we have to struggle with these hacky workarounds...

« First ‹ Previous 1 .. 13 14 15 16 17 18 19 20 21 Next › Last »