-
Notifications
You must be signed in to change notification settings - Fork 2
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
Axolotl 1.5.1 Flatpak does not start on Manjaro ARM Plasma Mobile #9
Comments
In the systemd journal, I see |
Thanks for filing the issue! |
Yes, Plasma Mobile always uses Wayland (as does Phosh, by the way). The device is a PinePhone.
|
(The |
That "use of closed network connection while TCP accepting" error message is an error message which I have seen coming back in many different ways. |
This issue is definitely also related to this one: axolotl-chat/axolotl#433 - the question is if it actually is the same issue even. |
Is it the same issue? Probably, assuming the linked issue is actually one issue and not several with the same symptoms. It is said to affect several distros, including Arch Linux ARM, which is closely related to the Manjaro ARM that I am using. |
Is it not the Flatpak's or the Flatpak runtime's job to provide this sort of libraries? Flatpak does not normally use system libraries, does it? |
Running:
works, i.e., it successfully brings up that web page. Not perfectly, the window is not entirely fullscreen (it leaves a border on the top and bottom side that should not be there, it should fill everything except the top and bottom panel, but there is extra border in addition to that) and somewhat blurred (apparently the internal size does not match the displayed size), but it works, whereas Axolotl does not. EDIT: The "border" on the right is actually a scrollbar, it is just the top and the bottom where the windows below shine through because there is more border than required for the panels. |
|
Also, |
(I could compile it from AUR, but I really should not have to. And I doubt that that obsolete library has anything to do with this issue to begin with. Also because a missing library would also show up when running |
For the border, comparing with the screenshot in axolotl-chat/axolotl#433 (comment) , it looks like Electron has hardcoded the larger Phosh panel sizes, leaving empty spaces on Plasma Mobile. But that is not really the issue here, the issue is that Electron on its own starts up, but Electron on Axolotl crashes. |
I have tried a lot of things to debug this:
|
If I run the following:
Axolotl actually comes up! Of course without any of the Flatpak sandboxing. So it does look like the problem is due to the Flatpak sandbox. (And by the way, Axolotl, at least when started that way, does not leave the unused borders between the panels and the window that Electron on its own leaves for some reason.) |
So I have tried this for debugging:
and what leads to the segfault is this:
So I see that, after loading the Electron config, it tries to connect to X11 (not Wayland), the Xauth file appears to not authorize that, then some Ozone error is produced that is unfortunately truncated in the strace and that never reaches stderr because it is filtered by other processes (the string ending with |
I really appreciate your effort and time spent on this! Looking at their solution, they have since adjusted it and now seem to rely on a different flag The Signal flatpak readme also provides some specific notes for Wayland. The difficulty with coming up with the first release of axolotl packaged with Electron was really just getting Electron to start at all within the flatpak environment. As for the ozone flags and the Electron Wayland work, @Ferenc- provided the project with some excellent insights with axolotl-chat/axolotl#468. |
So basically, they are forcing it to use Wayland to prevent errors when attempting to use X11. I guess we can try that too, though it will mean that the Flatpak will no longer run at all on X11 distros/desktops. Where is the |
Yes, that is a slightly convoluted way: it is set during startup by the usage of the axolotl specific |
So I cannot really change that without recompiling the whole thing or poking around in the binary. That is unfortunate. It would be helpful to have some CLI flag and/or environment variable to pass arbitrary Electron switches. (I would have expected I have tried commenting out the |
I got it to start with this hack:
(I actually used I did not have to touch |
Well, it comes up, but it is not usable, because the virtual keyboard does not come up! So I cannot even enter my phone number (the first step of registration). |
Looks like the virtual keyboard issue is not Flatpak-specific though, it also happens if I run Axolotl unsandboxed as per #9 (comment) . It happens even if I change So, since it is not Flatpak-specific, I will have to file that issue separately. Unfortunately, from what I found on the Internet, it is an upstream Chromium issue that affects Chromium and all Electron applications, and nobody seems to have solved it. The only suggested workaround is to manually open the virtual keyboard, which is not possible under Plasma Mobile. (Only Phosh has a gesture for that.) So Axolotl is still unusable for me. :-( |
Looks like the virtual keyboard issue is: https://bugs.chromium.org/p/chromium/issues/detail?id=1039161 – looks like it will be months until this will finally get fixed in upstream Chromium, and then trickle down to Electron and from there to Axolotl. (KWin supports The fix (update the ozone-platform flag) in |
1.6.0 starts up without hacks now, i.e., this bug is fixed. And the latest Plasma Mobile has a workaround for the keyboard issue. (It allows bringing up the keyboard manually for legacy applications that do not implement |
Well, I spoke too soon. I cannot input my phone number because the input field gets other characters instead of digits. (The |
Looks like what I am seeing now is axolotl-chat/axolotl#635. |
I have tried the 1.5.1 Flatpak that was released a few hours ago. Unfortunately, it still does not work:
The first time, I also got a message after
"astikit: worker is now waiting..."
saying[axolotl-electron] Electron App has crashed
, and all the detailed information is unfortunately just{nil}
. That message no longer appeared when retrying.While I might be able to get server mode working (I did with 1.2.0, which also failed to start Electron), the workaround that allows registration to work does not work in server mode, it requires support from the browser and hence works only in the Electron and Qt modes (and the Qt mode is not available on Flathub, is it?).
The text was updated successfully, but these errors were encountered: