Retroarch Build 1.9.0 installed vía snap without network

[Suigetsu52]

To begin with, I'm running on Deepin OS 15.11 amd64, which is a derivative of Debian. Networking is perfectly fine, but RetroArch seems to be isolated from any network communication (or it may be not reaching the server it is intended to).

Rummaging through the settings I found the subsection Updater, in which the Buildbot Cores URL has set: "http://buildbot.libretro.com/nightly/linux/x86_64/latest/" and the Buildbot Assets URL has set: "http://buildbot.libretro.com/assets/".

I actually don't know if it's corectly set, but if there's a chance of being wrong, maybe that info can be useful.

[hizzlekizzle]

You might try installing the snap package with the --classic flag, which should give it access to the rest of the system outside of its sandbox. You could also try connecting some plugs/interfaces, as the default ones don't seem to always work as they once did...

[Suigetsu52]

You might try installing the snap package with the --classic flag, which should give it access to the rest of the system outside of its sandbox. You could also try connecting some plugs/interfaces, as the default ones don't seem to always work as they once did...

Today I tried that, but I don't really know what you mean about connecting some plugs/interfaces, I tried to look for things to change in the retroarch.cfg file, but I don't really know where to look for, the only thing I noticed that may or may not have to do in some way with the issue is a line in that file that says network_cmd_enable = "false".

On the other hand, installing with the --classic flag just triggered a warning at the end of the installation which said Warning: flag --classic ignored for strictly confined snap retroarch leading to the same installation process as the last time, resulting in RetroArch once again isolated from all network communication.

[Suigetsu52]

Today I checked the info tab in the main menu, then I entered the Network Information subsection, there I found 3 different network interfaces, (lo, enp1s0 & wlp2s0), the thing is, the Network interfaces in which my PC has an actual internet connection are wlan0 & eth0, meaning that I probably need to add at least one of those interfaces to the app, but I'm not sure how.

Also, I noticed a line in retroarch.cfg that states: wifi_driver = "null", which may have something to do with it not detecting the wifi network

[hizzlekizzle]

i meant the interfaces/plugs that are used to poke holes in the snap sandbox confinement: https://snapcraft.io/docs/supported-interfaces

You can see the ones that we attempt to connect by default here: https://github.com/libretro/retroarch-snap/blob/master/snapcraft.yaml#L36
I would suggest trying to connect some likely ones, like network and/or network-bind, by doing: sudo snap connect retroarch:[plug-name]

[Suigetsu52]

i meant the interfaces/plugs that are used to poke holes in the snap sandbox confinement: https://snapcraft.io/docs/supported-interfaces

You can see the ones that we attempt to connect by default here: https://github.com/libretro/retroarch-snap/blob/master/snapcraft.yaml#L36
I would suggest trying to connect some likely ones, like network and/or network-bind, by doing: sudo snap connect retroarch:[plug-name]

I did sudo snap connect retroarch:network and tested, nothing changed, then I used sudo snap connect retroarch:network-bind and restarted retroarch, also, same result.

[gouchi]

Hi,

All your snap packages can't access network or only RA snap package ?

Maybe there is an issue with snapd version suggested by those threads.

Will it be possible to make a test with Deepin 20 ?

Thank you.

[Suigetsu52]

Hi,

No, I installed (some time ago) Whatsie via snap which actually worked perfectly.

There may be an actual issue with snapd, I think I have not tested enough with different snaps.

Right in this moment I think I'm not able to switch to Deepin 20 (due to my PC resources), but I'll try with a live install and check how it goes.

[gouchi]

@Suigetsu52 Did you have the opportunity to make some test ? So that we can close this issue if it is fixed.