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.

[manikey123]

Please assign to me @sschiessl-bcp

[sschiessl-bcp]

Can you describe the steps to reproduce?

[manikey123]

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

[sschiessl-bcp]

How to reproduce?

[manikey123]

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

[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
#123 (comment)

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

[sschiessl-bcp]

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