Error: Couldn't load project data at path ".". Is the .pck file missing?

[NiPfi]

On launching the burrito.x86_64 on my OpenSUSE Tumbleweed system, I get the following error:

Error: Couldn't load project data at path ".". Is the .pck file missing?
If you've renamed the executable, the associated .pck file should also be renamed to match the executable's name (without the extension).

As far as I could tell from looking it up, it seems to be some issue with Godot's embedded "pck" resources not being found. It might be an export issue, but it might as well require a Godot update.
Is anybody else experiencing this?

[AsherGlick]

I have not run into this error with burrito before. Burrito is packaged with the .pck bundled inside the executable. Is it possible that your system is not proving permissions to write the temporary file? That is just a wild guess. You might have some luck trying to search for this error generically in the godot ecosystem, someone has probably run into something like that before in some other project.

[NiPfi]

Interestingly, the previous release doesn't have this issue

[Masgalor]

I use Tumbleweed myself and while I have never seen this error I had a lot of strange things happening before I started to build it myself. After all the official release is built on Ubuntu 20.04 with Godot 3.3.2, that is so much behind Tumbleweed, it is almost ancient.

Do you get this error from the latest pre-compiled release 1.4 or do you build it yourself from master?

Anyway, if you want an easy solution, I have a ready to install package for Tumbleweed.
It is version 1.4 with some of my own patches on top, you can find it at SUSE OBS.

[AsherGlick]

What! 2020 was just a few... months... ago.......... right!?

In reality though, the godot package being built on an older version of ubuntu should not be a huge issue because, in theory, nothing in godot is compiled against OS libraries. It is an issue for the other binaries however because of how glibc compatibility works, which is why we intentionally use an older OS.

It would be interesting to figure out what is causing this issue though in case it is something we can fix.

[Masgalor]

Yeah you caught me being a little too dramatic. :)

I can not reproduce this error on my system.
The binary from the release section throws several errors but not that one mentioned here and it is not crashing.

I will try to reproduce this after @NiPfi tells us where he got the binary from.

[NiPfi]

@Masgalor I took the latest release from this here GitHub page, which is Alpha 1.4

[NiPfi]

The version built on OBS works fine, so I'll be trying that one. Thanks for the info!