So I have been trying to debug the issue I’m having with the latest Campfire AppImage on Linux. The issue pertains the clipboard events or how Campfire handles clipboard copy/pasting.
Pasting addresses into the wallet works. Copying on the other hand doesn’t seem to work as intended. When I go to copy from the wallet lets say a new seed or a spark/transparent address and try to paste it into a Text Editor it doesn’t paste until I close the wallet.
Anyhow I enabled debugging in the logs and don’t see what I should look for?
To me this feels like it might be an issue with Wayland which I’m also using but it doesn’t make sense how pasting into the wallet works but not coping and pasting from the wallet?
I read somewhere that flutter has some issues with Wayland?
Also I just want to say thank you to the Firo Team and Stack Wallet Team for the nice wallet. I have been going back and forth between QT and Campfire. While I know Campfire is mainly for mobile, but I feel it works great for a nice lightweight wallet on Linux.
There is other issues like understanding how it opens the default browser to open the explorer but for right now I would like to solve this one if I can.
I first tried and tested campfire with Debian Xfce in virtualbox. It uses X11 and I don’t recall this issue so that’s what makes me to believe it’s most likely Wayland related.
Issues with clipboard pasting and opening block explorer links only occur when using the torsocks[1] shell wrapper to launch the AppImage.
Ok so I tried WAYLAND_DISPLAY=wayland-0 ./campfire-v2.0.4.Appimage and I thought it was the fix to the issue(s) but, it’s looking more like it has to do with the torsocks wrapper and how it works with the AppImage/Wayland. Which could involve system calls that get blocked or altered in the torsocks environment.
I feel stupid cause now trying it again, it works fine launching by itself ./campfire-v2.0.4.Appimage.
To get tor working I had to use torsocks torsocks -i ./campfire-v2.0.4.Appimage which led to these two issue(s). The two issues being clipboard pasting not working correctly as mentioned and Tor Browser not being able to open links to the block explorer error:
/usr/local/lib/tails-run-tor-browser-in-flatpak: 30: exec: sudo: Operation not permitted`
Torsocks intercepts and redirects system calls, potentially blocking or altering access to local IPC mechanisms (e.g., Wayland’s socket-based communication). If the app relies on these for display connections, torsocks could treat them as restricted resources, causing failures in clipboard or link handling.
Even WAYLAND_DISPLAY=wayland-0 torsocks -i ./campfire-v2.0.4.Appimage wouldn’t effect the handling of the torsocks wrapper env.
I originally would only be able to use it by using the torsocks wrapper command torsocks --isolate ./campfire-v2.0.4.Appimage and I would be able to sync and send no issue despite it erroring out in logs in terminal. The GUI would show the green and status connection loading from yellow to green. Obviously the built in Tor connection would work since there is no way to select a different running tor instance like in this case the one running on local host via the typical socks port 9050.
Adding manual proxy integration into Campfire would fix this issue, not to mention in some countries or networks using proxy may be the only way to access things (censorship or network configuration). You could set a system wide proxy if not on tails but that might not be ideal. Certain Linux distributions like Tails or others may not work well with using the bundled tor daemon or might be routing another way like a Qube connected via sys-whonix. Hopefully a manual proxy integration is added to Campfire. Just my two cents on the matter.