-
Notifications
You must be signed in to change notification settings - Fork 17
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Issues with AppImage on Bazzite Deck OS #74
Comments
Just tested the same on my archlinux desktop and it doesn't even try to start. Not sure why tho. |
Hi, dfu-util ispackaged in the appimage with pineflash. Would you be able to run pineflash from the command line and send any output here? Thanks |
Yeah, it just hangs there until I kill it. No output anywhere. EDIT: On my archlinux desktop instead: |
Strace log on my arch linux machine: Seems a bug in the wayland api call that the graphic backend uses. |
Interesting, in that case I'm not really sure what do do. You mention you are using bazzite, is that an immutable distro? When running the appimage could you ls the contents of /TMP and see if there is a folder named pineflash or similar? Also could you confirm whether you have a v1 pinecil or v2? As for the arch machine you can use the native package in the meanwhile. That should work. In regards to the Wayland issue that is strange and something I have encountered myself on my machine, a temporary solution is to unset the WAYLAND_DISPLAY variable which will cause it to fall back to xwayland, not ideal but as a temporary solution it works. Unfortunately I have no experience with direct Wayland calls and I'm pretty unqualified to fix it if it is an upstream issue with the library I'm using. I can try updating the version used but that may take some time depending on how many breaking changes there are. |
Interesting, it's not the wayland call. Something is quite broken, not sure what tho. New strace: For bazzite, I'll check shortly, but from a quick look in strace nothing popped up as strange. |
I can confirm that if I build these from scratch they both works 100% fine, besides requiring root on Fedora 39 immutable (but it might be a SeLinux problem, to be honest). Something is broken in the appimage itself then. |
Interesting |
Could you test the latest appimage from version 0.5.5? |
Yup, on my KDE ArchLinux system it opened immediately with no fuss this time. It also detected it without running with sudo/anything else. Great job and thanks for reminding me by pinging, I already had forgotten that this problem happened in the first place :P I'll test on Silverblue shortly and update this bug report shortly. Thanks again for your work, Marco. |
Awesome, glad to hear. Thanks for doing the test 👍 |
Getting this on fedora
|
Similar issue on the latest 0.5.5 on Manjaro (Arch derivate):
|
What is your glibc version (pacman -Qs glibc) |
Thank you for the swift response!
I have installed the arch package successfully. I just wanted to use the AppImage since this is a tool I would just use once and do not want to keep having to (manually) update on my machine. |
For whatever reason, pineflash will lock up using one single core completely each time I try to start up the AppImage file.
I've forked the project and compiled it myself and the UI now opens fine. The program though did not detect my iron until I've ran the program with sudo (might be a SeLinux permission problem tho). Another potential issues is that you assumes that the user already have dfu-util installed and if it's not it will not work for flashing the device (unless you provide already a binary build in the AppImage itself).
I'm installing it now to test if then this software will work for flashing my update.
Great job regardless for creating a native ui using Rust as a base language and not just use Electron again for it, my RAM appreciate the effort :)
Marco.
The text was updated successfully, but these errors were encountered: