-
-
Notifications
You must be signed in to change notification settings - Fork 55
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
[BUG] Flatpak, x86/ARM electron exited with code: 7 #433
Comments
Seeing the same thing on a Librem 5 running PureOS. |
Confirmed, same here on pinephone with arch-linux plasma-mobile. |
Could it be that this is an issue coming from Electron only allowing, per default, 6 connections per host? From what I understand, the communication between the axolotl backend and frontend is done with WebSockets. Electron offers a https://www.electronjs.org/docs/api/command-line-switches#--ignore-connections-limitdomains https://github.com/electron/electron/blob/master/shell/common/options_switches.cc#L260 |
Did some initial testing, and I am starting to believe that this issue is not related to Electron, but to the go-helper Another method might be to provide a known working Electron as a bundle bundle and not rely on downloading it at startup. https://github.com/asticode/go-astilectron-bundler We do have a QT version of the Flatpak which can be used, which does not rely on Electron. That could potentially be seen as a workaround as well. https://github.com/nanu-c/axolotl/blob/main/docs/INSTALL.md#qt-version |
Doesn't seem like existing flatpak can switch over to the Qt version on the fly. |
Unfortunately the Qt version doesn't work either for me on the pinephone. |
+1 on Failed to start on Mobian Pinephone |
I am seeing the same issue on Artix Linux with the Flatpak I just downloaded. |
The flatpak builds on flathub are currently outdated (v0.9.9 vs v1.0.9 ) and broken. There is WIP MR for fixing that. |
The work on a new Flathub release is completed, and in the coming days there will be a new, updated, Axolotl Flathub version ready to install (using the latest Axolotl release, v1.1.0) This release not only uses the latest and greatest of the axolotl and axolotl-web projects, but also includes the new libraries and perhaps most importantly, bundles Electron with the installer instead of installing it when first started as was the case previously. To test this build already, install it from the testing repository:
|
Seems like the bug Log from x86 Arch Linux - installed via flatpak
Log from PinePhone (DanctNix) - installed via extracted arm64.deb releasePKGBUILD used: https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=axolotl-bin
And lastly I tried the to run the flatpak version on my Pinephone. There it hang for 45 seconds after the Log from PinePhone (DanctNix) - installed via flatpak
|
Thanks for getting back! To rule out local issues with Electron, can you start it without Axolotl? $HOME/.var/app/org.nanuc.Axolotl/data/vendor/electron-linux-amd64/electron https://github.com/nanu-c/axolotl/issues/433 Additionally, just as to allow for a better understanding of your systems, what Desktop Environment do they use, and are you using Wayland or not? |
x86 Arch Linux - installed via flatpakI'm using XFCE4 with xorg.
PinePhone (DanctNix) - installed via flatpakI'm using Phosh with wayland.
When started via ssh:
When started in a terminal on the phone:
QuestionsIs the folder |
Flatpak Axolotl on Fedora 36, KDE Plasma and Wayland. Basically the save behavior as the last comment except for the STDOUT:
|
#985 will switch from electron to tauri |
Description
On Manjaro and Manjaro ARM, running the flatpak results in crash before any sort of UI can load:
Steps to Reproduce
.desktop
file orflatpak run
Expected behavior: [What you expect to happen]
Axolotl running.
Actual behavior: [What actually happens]
Axolotl crashes.
Versions
Please provide the Version as written in
Settings->About Axolotl
N/A
Device
What device or OS are you using?
Manjaro/Manjaro ARM
Link to Debug Log
Please provide a link to debug from ~/.cache/upstart/application-click-textsecure.nanuc_textsecure*.log
Be careful it contains sensible data
N/A (Can't find it in
.var/app/org.nanuc.Axolotl
dir, doesn't seem like Axolotl got to the point of generating the log; no equivalents on host home folder outside flatpak)The text was updated successfully, but these errors were encountered: