New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Won't launch #3
Comments
Can you see if the process is running? The sed is trying to fix java window re-homing on wayland, but since its a fresh install, it will fail, but it should still launch the process. If it is running, then it would appear to be the re-homing issue with java apps, through trial and error I found that on an existing install, editing the workspace and removing the Best I can recommend is to kill the process, and relaunch it a few times, I've found that eventually it will launch and after that the workspace editing trick will get it to launch. Unforts with it being closed source there's nothing I can do about fixing the real issue. I've notified ToS support, you might try the same, but linux and non osx unix variants are technically unsupported by them. |
I have the same issue as vanessakindell. I check my processes, and I don't have any open SED processes running. It looks like the home directory is not getting set. Here is my error: flatpak run com.tdameritrade.ThinkOrSwim
|
|
I found a workaround: The whole issue is that the program wasn't given the home folder filesystem access. All you have to do to get it working is install FlatSeal and change that setting and it works. Tested under Pop! OS and Linux Mint. |
The workaround via Flatseal does not work on Fedora 36. |
Hi Vanessa, what exactly did you do in Flatseal to get thinkorswim to run on flatpak? Under the TOS app in flatseal, i went to filesystem and toggled on filesystem=home, but TOS still didn't work. Thanks, |
same issue on manjaro stable channel. |
For everyone who wants to run this flatpak and is running into this issue. There seems to be a disconnect at the installer where the thinkorswim script adds the I was able to handjam the install for the flatpak; testing on Fedora 36
This installer will give you a prompt, during the installation on where to install TOS. Once it's installed into the app, it'll run normally every flatpak run after. |
After doing the config change with flatseal, I then had to open up thinkorswim manually using the terminal. I went to where it was installed (in my case ~/thinkorswim) and just ran ./thinkorswim. I let it do its updates, and after closing and restarting a few times, the desktop shortcut worked for me. However, it doesn't work through the pop os launcher or dock. |
I was able to get the TOS Flatpak working on Pop!_OS 22.04 LTS by following the steps below. I believe the root cause is that the installer script thinkorswim_installer.sh and the executable bundled inside the script assume different defaults for the installation directory. Install the TOS Flatpak
Attempt to run TOS and watch it fail
Give TOS access to your home folder using FlatSeal (this might be optional)Enter the TOS 'container'
Run the TOS installer
Choose a custom installationSet the installation directory to /home/<your_user_directory>/.var/app/com.tdameritrade.ThinkOrSwim/data/thinkorswimExit the TOS 'container'
Start TOS from the GUI or Terminal
|
@SaltyCybernaut great write up, I didn't have to do the FlatSeal permission changing since it should only be touching the flatpak 'container' dir that needs to be updated, dunno how this issue isn't an issue for others! |
OS: System76 Pop!_os
Commands: flatpak install com.tdameritrade.ThinkOrSwim
flatpak run com.tdameritrade.ThinkOrSwim
Result: he installation directory has been set to /home/[my home folder]/thinkorswim.
Extracting files ...
Finishing installation ...
sed: can't read /home/[my home folder]/.var/app/com.tdameritrade.ThinkOrSwim/data/thinkorswim/workspace.*.tos.prod.xml: No such file or directory
/app/bin/thinkorswim: line 15: /home/[my home folder]/.var/app/com.tdameritrade.ThinkOrSwim/data/thinkorswim/thinkorswim: No such file or directory
Nothing loads in the GUI at all.
The text was updated successfully, but these errors were encountered: