beet Beet hackathon demo - Beet if reopened creates new process ids and the old process ids stay the same (Observed on Linux may be windows users wont face this issue) I needed to manually kill them for the app to work.

Please assign to me @sschiessl-bcp

May 12 '19 22:05 manikey123

Can you describe the steps to reproduce?

May 14 '19 19:05 sschiessl-bcp

Below lines are spawning redundant threads. Resulting in stale UI. That needs to be manually killed. Do suggest recommendation for the below lines. Should they be removed. Then the connection icon wont come. Plz suggest any ideas @sschiessl-bcp

May 29 '19 06:05 manikey123

How to reproduce?

Jun 01 '19 07:06 sschiessl-bcp

Use Linux OS and then start the beet app. Observed that the line keeps frequently repeating.

Jun 08 '19 21:06 manikey123

In order to fix above issue I researched AppImg https://appimage.org/ AppImg is open source. Set ups are handled in the AppImg itself and it would be seamless for Linux users

AppImg is also implemented by Scatter https://get-scatter.com/download

This also helps solve below setups which the user needs to do manually https://github.com/bitshares/beet/issues/123#issuecomment-496310678

Let me know if I can fix using this approach or do suggest any other resolution.

Jun 08 '19 21:06 manikey123

Yes, ideally we would be building AppImage through travis. Please continue

Jun 26 '19 08:06 sschiessl-bcp