Package Details: iota-firefly-wallet 2.0.12-1

Git Clone URL: https://aur.archlinux.org/iota-firefly-wallet.git (read-only, click to copy)
Package Base: iota-firefly-wallet
Description: The IOTA Firefly Wallet
Upstream URL: https://iota.org/
Licenses: Apache
Provides: iota-firefly-wallet
Submitter: runaz
Maintainer: runaz
Last Packager: runaz
Votes: 6
Popularity: 0.000016
First Submitted: 2021-04-05 11:26 (UTC)
Last Updated: 2024-08-06 18:32 (UTC)

Latest Comments

« First ‹ Previous 1 2 3 Next › Last »

TheStochasticMan commented on 2023-03-17 06:20 (UTC)

Apparently v2.x is actually the Shimmer wallet, which is for SMR instead of IOTA (and staking). The official website isn't the most clear on the fact that they're meant for different things, but according to some help I received on Discord, Firefly v2.x isn't so much an upgrade from the v1.x app, so much as an additional app to be used in parallel for interacting with the Shimmer network.

Perhaps this package should continue to track v1.x since it's called iota-firefly-wallet and a new package could be created called shimmer-firefly-wallet or iota-shimmer-firefly-wallet that tracks v2.x

runaz commented on 2023-02-08 23:25 (UTC)

Yes, should be working now. Sorry for the inconvenience!

tsangares commented on 2023-02-08 23:16 (UTC)

Nevermind you figured it out!

tsangares commented on 2023-02-08 23:13 (UTC)

Actually there is an issue the sha is wrong. As seen on https://github.com/iotaledger/firefly/releases/ and I verified it. The sha256 hash is,

$ sha256sum ./firefly-desktop-1.7.1.AppImage 
f984b6e5273ba74796f42ebf94142e2f2258f557a08b0ceeda44a07423635b14

The md5sums for iota-firefly-wallet.desktop is correct: c22e0c2b6cd8941ea147ddc01352858a

It seems the sha512sum in the PKGBUILD is in reference accidentally set to the appimage when it should be set to the `.desktop. I think? I am not that great at PKGBUILD files.

The sha512sum of the .desktop file is:

e7e47f5c99d0536de091204df8eb94fb32471ae550f7861fd0373057af90f8bf4f5aa9fa53ea4fa12303b41bb6a23905d99b751f2c849c3b2c67735a66780714  ./iota-firefly-wallet.desktop

And the sha512 of the appimage is,

9c3faab3cfacba7375c5a23f7933f4966871fae5e76dccbf0e6fcf41aae3f04c8a0d08de3f8aac6b9aafa083b85dea7c403f6a716fe43878bc138e608bbbc41f  ./firefly-desktop-1.7.1.AppImage

Hope this helps!

runaz commented on 2023-02-08 23:09 (UTC)

@tsangares thank you; my pleasure

I've just updated the PKGBUILD because the last commit included a wrong hash. You may have to clear cache if you already downloaded the broken PKGBUILD.

tsangares commented on 2023-02-08 22:48 (UTC)

@runaz Thank you for your responsiveness! You are incredible! Keep up the good work; we as a community of arch linux users and IOTA enthusiasts love you.

zerophase commented on 2022-10-17 23:47 (UTC) (edited on 2022-10-17 23:49 (UTC) by zerophase)

@runaz that works. I get the same command line messages, but without the GPU one. Any idea how to get it working with the sandbox?

runaz commented on 2022-10-15 13:59 (UTC)

@zerophase could you try starting the application with the command line argument --no-sandbox

zerophase commented on 2022-10-14 18:16 (UTC)

@runaz I received:

(iota-firefly-wallet:1880561): Gtk-WARNING **: 13:13:08.974: Theme parsing error: gtk.css:6:18: The 'gtk-key-bindings' property has been renamed to '-gtk-key-bindings' 13:13:09.174 › Checking for update 13:13:09.408 › Update for version 1.6.5 is not available (latest version: 1.6.5, downgrade is disallowed). (node:1880695) Electron: Loading non-context-aware native module in renderer: '/tmp/.org.chromium.Chromium.Ky3fTq'. This is deprecated, see https://github.com/electron/electron/issues/18397. (Use exe --trace-warnings ... to show where the warning was created) [1880561:1014/131311.657322:FATAL:gpu_data_manager_impl_private.cc(415)] GPU process isn't usable. Goodbye. [1] 1880561 trace trap (core dumped) iota-firefly-wallet

runaz commented on 2022-10-09 15:32 (UTC) (edited on 2022-10-09 15:58 (UTC) by runaz)

@zerophase For me the application is working fine. You could try to start the wallet from the console. Maybe you see an error message there?

« First ‹ Previous 1 2 3 Next › Last »