Open polymorphito opened 1 year ago
Does the issue persist in 2.1.0?
Hi, sorry for the delay. The problem described above appeared with IOTA Firefly 1.7.1 to be precise. With Shimmer Firefly 2.1.0 it even occurs earlier while opening the (existing) profile: right after finishing profile setup, before dashboard loading.
Error message:
client: error sending request for url (https://api.shimmer.network/api/core/v2/info): error trying to connect: tcp connect error: Das Netzwerk ist nicht erreichbar (os error 101)
And there's a new problem with 2.1.0: It seems to use GPU-acceleration? My machine is quite old an crashes reliably and fast with programs using hardware acceleration : / Is there a possibility to start 2.1.0 without the acceleration?
I know you guys are working very hard on the shimmer thing and tor isn't your priority atm so it wouldn't matter at all if answering takes some time. We can postpone it if you want :)
We won't be prioritizing getting FF to work with Tails over TOR due to our current roadmap (although it's a very interesting task).
To run FF without GPU-acceleration (the default for all electron apps), I can only recommend building it from source with the following line added here:
app.disableHardwareAcceleration()
To build from source, you can follow the guide here.
For now we won't do this in the production version, since it degrades the animations we have.
Additionally, we could follow the same approach as Signal:
Platform
Desktop
Version
1.7.1
Description
Firefly AppImage is running smooth under Tails Linux. But there are connection problems with TOR. No possibility to set Socks5 Proxy to 127.0.0.1:9050 like e.g. in Bitcoin Core.
A guy from IOTA on Discord told it could be an communication issue of Firefly/IOTA nodes to TOR and suggested to develop an INXS module for HORNET to make sure it can work over TOR.
Expected behaviour
Getting smooth Firefly connectivity over TOR (under Tails Linux)
Actual behaviour
Problems to get wallet updated. After updating the wallet with regular connection, the correct balance occurs even with TOR.
Can the issue reliably be reproduced?
Yes
Steps to reproduce the issue
No response
Operating System
Linux
Diagnostics
No response
Developer Profile
No
Profile Type
Software (Stronghold)
Staking
None
Crash Status
None of the above
Error Messages
No response
Error Logs
No response
Duplicate declaration
Code of Conduct