Games wont launch about cartridges HOT 29 CLOSED

Seems to be some upstream issue with flatpak-spawn itself. I'll dick around in an Arch VM and see what the deal is.

i will be on crystal linux in a few days so i will also try it again

from cartridges.

running the launch executable command manually does work

from cartridges.

What do you get when running which xdg-open?

(Edit: You may want to remove your username if it is in the output)

from cartridges.

What do you get when running which xdg-open?

(Edit: You may want to remove your username if it is in the output)

/usr/bin/xdg-open

from cartridges.

What about flatpak enter hu.kramo.Cartridges xdg-open --help while Cartridges is running?

from cartridges.

What about flatpak enter hu.kramo.Cartridges xdg-open --help while Cartridges is running?

flatpak enter hu.kramo.Cartridges xdg-open --help

Usage:
xdg-open [OPTION?] { file | URL }

Help Options:
-h, --help Show help options

Application Options:
--version Show program version

from cartridges.

And when you create a test game entry by using "Add Game" in the plus menu where the command is a normal gui application like gnome-terminal, it works?

from cartridges.

no but entering the execute command this way:

flatpak enter hu.kramo.Cartridges [insert the execute command]

does work

from cartridges.

xdg-open is run on the host, not from inside the Cartridges shell. What's the output of running xdg-open --help on the host?

from cartridges.

xgd-open is run on the host, not from inside the Cartridges shell. What's the output of running xdg-open --help on the host?

xdg-open -- opens a file or URL in the user's preferred
application

Synopsis

xdg-open { file | URL }

xdg-open { --help | --manual | --version }

Use 'man xdg-open' or 'xdg-open --manual' for additional info.

from cartridges.

Does changing xdg-open in the executable to /usr/bin/xdg-open work?

from cartridges.

sorry but what do you mean by that?

from cartridges.

nvm i understood

from cartridges.

Does changing xdg-open in the executable to /usr/bin/xdg-open work?

/usr/bin/xdg-open: line 444: grep: command not found
/usr/bin/xdg-open: line 561: grep: command not found
/usr/bin/xdg-open: line 562: grep: command not found
/usr/bin/xdg-open: line 574: grep: command not found
xdg-open: file 'heroic://launch/2e26af55c1a146e7a939dcc1014fc9fd' does not exist

from cartridges.

Does running xdg-open 'heroic://launch/2e26af55c1a146e7a939dcc1014fc9fd' on the host work?

from cartridges.

Does running xdg-open 'heroic://launch/2e26af55c1a146e7a939dcc1014fc9fd' on the host work?

yes

from cartridges.

What is the output of flatpak enter hu.kramo.Cartridges flatpak-spawn --host echo $PATH?

from cartridges.

Portal call failed: Failed to start command: Failed to execute child process ?echo? (No such file or directory)

from cartridges.

And of flatpak enter hu.kramo.Cartridges flatpak-spawn --host /usr/bin/echo $PATH?

from cartridges.

And of flatpak enter hu.kramo.Cartridges flatpak-spawn --host /usr/bin/echo $PATH?

a ton of paths including my host name. Do i need to post it?

from cartridges.

No. Is /usr/bin included though?

from cartridges.

No. Is /usr/bin included though?

yes

from cartridges.

That's great, because then I have no idea what is going on.

from cartridges.

That's great, because then I have no idea what is going on.

huh, i will soon be reinstalling so better ask now so do you need any more logs?

from cartridges.

no but entering the execute command this way:

flatpak enter hu.kramo.Cartridges [insert the execute command]

does work

@uricot Last question: how about flatpak enter hu.kramo.Cartridges flatpak-spawn --host [insert the execute command]?

from cartridges.

Portal call failed: Failed to start command: Failed to execute child process ?xdg-open? (No such file or directory)

from cartridges.

Seems to be some upstream issue with flatpak-spawn itself. I'll dick around in an Arch VM and see what the deal is.

from cartridges.

@uricot any update on this?

from cartridges.

Closing this because the launching of games has been overhauled and this issue has been inactive. Feel free to reopen it if the issue still persists.

from cartridges.