flathub / com.play0ad.zeroad Goto Github PK

https://play0ad.com/new-release-0-a-d-alpha-24-xsayarsa/

There is a black rectangle on the top of the window and the pointer of the mouse cursor is offset by that rectangle. So you have to aim higher.

After I forced Wayland with the help of Flatseal it was gone.

It has been quite a while since the last 0 A.D. release (Still working on it, sorry about that) and I was wondering if it was possible for you guys to also provide a bleeding edge flatpack for people that would want to try the dev version?

I tried to install and run this Flatpak for 0.0.24 version of 0 A.D. on Ubuntu 20.04, and I got this:

$ flatpak run com.play0ad.zeroad
/usr/bin/env: ‘bash’: No such file or directory
error: ldconfig failed, exit status 32512

When running in Xwayland (--socket=x11), an SDL environment variable (SDL_VIDEODRIVER=x11) is required to run the game. Please add this environment variable to the Flatpak installation until Wayland is supported.

When upgrading to the latest version, the in-game versioning states that the version is 0.0.26:

but flatpak info com.play0ad.zeroad still prints Version: 0.0.25b

If you launch the game and click "Scenario Editor" it fails to launch. You'll find an error in the game log:

DllLoader: dlopen(/app/lib/libAtlasUI.so) failed: /app/lib/libAtlasUI.so: cannot open shared object file: No such file or directory; dlopen(/app/lib/libAtlasUI_dbg.so) failed: /app/lib/libAtlasUI_dbg.so: cannot open shared object file: No such file or directory;

If we try and run the editor directly with the cmdline flag:

/usr/bin/flatpak run --branch=stable --arch=x86_64 --command=0ad com.play0ad.zeroad -editor

...it crashes but also complains about logging (possibly a separate issue):

Atlas.cpp(46): The Atlas UI was not successfully loaded and therefore cannot be started as requested.
debug.cpp(189): Unable to open crashlog.txt for writing (please ensure the log directory is writable)
Unable to open crashlog.txt for writing (please ensure the log directory is writable)
Location: debug.cpp:189 (debug_WriteCrashlog)

When I install 0ad from the normal RPM repos I can find the required file at /usr/lib64/0ad/libAtlasUI.so. This file just seems to be missing from the flatpak I think?

0 A.D. works great a bunch of different ARM an aarch64 hardware, including recent Raspberry Pis, Chromebooks, MacBook M1, etc. Please publish arm and aarch64 builds. 0.0.23 is included for arm, most ARM laptops and desktops are 64-bit now.

It seems this build has not been updated from several months ago when 23.1 was released (not just 23, this is a re-release). I can connect to the general lobby but it says me that I must update to 23.1 (already in Debian stable repositories).

https://play0ad.com/re-release-of-0-a-d-alpha-23-ken-wood/

Flathub has an alternative channel called flathub-beta (https://flathub.org/beta-repo/flathub-beta.flatpakrepo) which could be used to provide builds of the next 0 A.D. version when it is in the RC state.

Hi all,

I'm running Fedora 37 Workstation. I installed 0AD from Flathub (Flatpak) version 26. The game runs and I can start a game and change settings, but the sound isn't working.

I looked into the sound settings in Gnome while the game is running, and I see "pyrogenesis" in the list of apps with sound output.

I ran it from the terminal, and I see the following lines in the output:

[ALSOFT] (EE) Failed to set real-time priority for thread: Operation not permitted (1)
[ALSOFT] (EE) Failed to set real-time priority for thread: Operation not permitted (1)
Sound: AlcInit success, using OpenAL Soft

Fedora uses Pipewire (with PulseAudio support) by default, and OpenAL-soft is installed.

I checked the Flatpak permissions, and they are set properly.

I was told that SuperTux also uses OpenAL-soft, so I installed it from flathub, and the sound is working without issues. I double-checked the permissions and compared the two; all set correctly, so this is definitely not a permissions issue, and ALSoft works normally from Flatpaks.

I installed 0AD rpm package (same version) from the Fedora repo, and it's working without issues. I also noticed that the Fedora build has a much better performance than this build.

This is most likely a bug in the Flatpak build of 0AD. I don't have another system to reproduce on; I hope the community can help in this.