maxiberta / moonlight-snap Goto Github PK

View Code? Open in Web Editor NEW

15.0 3.0 2.0 1.76 MB

The `Moonlight` open-source NVIDIA GameStream client packaged as a snap.

License: MIT License

snap snappy snapcraft ubuntu ubuntu-core linux moonlight nvidia gamestream client

moonlight-snap's People

Contributors

Stargazers

Watchers

Forkers

cgutman q4z1

moonlight-snap's Issues

libvdpau_nvidia.so seems missing

The latest version (1.2.1) seems to be missing the nvidia driver. The flatpak version of Moonlight works fine.

wayland - snapping with stage qtwayland5

Hi there,

it took me quite this day to just add one important line to the yaml and successfully build the snap on Ubuntu 19.04. (experimenting with wayland instead of x11 for my Gnome).

git diff snap/snapcraft.yaml
diff --git a/snap/snapcraft.yaml b/snap/snapcraft.yaml
index 6e653b0..8a59307 100644
--- a/snap/snapcraft.yaml
+++ b/snap/snapcraft.yaml
@@ -2,7 +2,7 @@ name: moonlight
base: core18
title: Moonlight
version: master
-version-script: git -C parts/moonlight-qt/build/ describe --tags --long | sed "s/^v//"
+version-script: git -C /root/parts/moonlight-qt/build/ describe --tags --long | sed "s/^v//"
adopt-info: moonlight-qt
grade: devel
confinement: strict
@@ -65,6 +65,7 @@ parts:
- qml-module-qtquick-controls2
- qml-module-qtquick-layouts
- qml-module-qtquick-window2
+ - qtwayland5
- mesa-va-drivers
- mesa-vdpau-drivers
- libvdpau-va-gl1

(see q4z1@0d55df2)

Using multipass together with snapcraft is the solution ... but anyway ... I did that ;)

Here is the strange thing:

Starting the successfully built and installed snap with -platform wayland results in an error:

+ case "$SNAP_ARCH" in
+ ARCH=x86_64-linux-gnu
++ glxinfo
++ grep 'OpenGL vendor'
+ VENDOR='OpenGL vendor string: Intel Open Source Technology Center'
+ export VDPAU_DRIVER_PATH=/snap/moonlight/x2/usr/lib/x86_64-linux-gnu/vdpau
+ VDPAU_DRIVER_PATH=/snap/moonlight/x2/usr/lib/x86_64-linux-gnu/vdpau
+ export LIBVA_DRIVERS_PATH=/snap/moonlight/x2/usr/lib/x86_64-linux-gnu/dri
+ LIBVA_DRIVERS_PATH=/snap/moonlight/x2/usr/lib/x86_64-linux-gnu/dri
+ [[ OpenGL vendor string: Intel Open Source Technology Center == \N\V\I\D\I\A ]]
+ [[ OpenGL vendor string: Intel Open Source Technology Center == \X.\O\r\g ]]
+ exec /snap/moonlight/x2/usr/bin/moonlight -platform wayland
...snip... lot of Fontconfig warnings/errors ...snip...
00:00:00 - SDL Info (0): Compiled with SDL 2.0.8
00:00:00 - SDL Info (0): Running with SDL 2.0.8
00:00:00 - Qt Warning: QSocketNotifier: Can only be used with threads started with QThread
00:00:00 - SDL Info (0): Detected Wayland. Performance may be worse than X11.
00:00:00 - Qt Debug: Using Wayland-EGL
00:00:00 - Qt Warning: EGL not available
00:00:00 - Qt Info: Found "gamecontrollerdb.txt" at ":/data/gamecontrollerdb.txt"
00:00:00 - SDL Info (0): Loaded 149 new gamepad mappings
00:00:00 - SDL Error (0): Failed to create window for hardware decode test: failed to create a window surface
00:00:00 - Qt Info: Found "gamecontrollerdb.txt" at ":/data/gamecontrollerdb.txt"
00:00:00 - SDL Info (0): Loaded 149 new gamepad mappings
00:00:00 - Qt Debug: Using the 'xdg-shell-v6' shell integration
00:00:00 - Qt Debug: Current Moonlight version: "1.0.1"
00:00:00 - Qt Fatal: Failed to create OpenGL context for format QSurfaceFormat(version 2.0, options QFlagsQSurfaceFormat::FormatOption(), depthBufferSize 24, redBufferSize -1, greenBufferSize -1, blueBufferSize -1, alphaBufferSize -1, stencilBufferSize 8, samples -1, swapBehavior QSurfaceFormat::SwapBehavior(DoubleBuffer), swapInterval 1, profile QSurfaceFormat::OpenGLContextProfile(NoProfile))
Abgebrochen (Speicherabzug geschrieben)

I tried the flatpack installation before - without having this error. That is why I decided to try it out with snap which allows me to keep my gtk styles.

@maxiberta Do you have an idea what that error can be about?

mDNS broken with AppArmor denials for AF_NETLINK since update to Qt 5.14

Since the edge snap updated to Qt 5.14, I'm seeing the log full of AF_NETLINK errors (from Qt itself, since Moonlight never creates netlink sockets). It also seems to be correlated with loss of automatic mDNS auto-discovery functionality.

The messages also repeat every 10 seconds which happens to be the interval that QMdnsEngine sends mDNS queries, so that further indicates something mDNS-related is going wrong. I'm not seeing any of Moonlight's expected outbound mDNS queries in Wireshark.

I tried to snap run --gdb moonlight to determine the source of the messages but Qt failed to load the xcb platform plugin and wouldn't initialize under GDB.

Interestingly, I noticed this problem both with core20's native Qt and core18+Neon PPA.

Installing with --devmode fixes both the AF_NETLINK denials and mDNS autodiscovery.

Stdout from moonlight:

00:07:00 - Qt Critical: Could not create AF_NETLINK socket (Permission denied)
00:07:00 - Qt Critical: Could not create AF_NETLINK socket (Permission denied)
00:07:00 - Qt Critical: Could not create AF_NETLINK socket (Permission denied)
00:07:00 - Qt Critical: Could not create AF_NETLINK socket (Permission denied)
00:07:00 - Qt Critical: Could not create AF_NETLINK socket (Permission denied)
00:07:10 - Qt Critical: Could not create AF_NETLINK socket (Permission denied)
00:07:10 - Qt Critical: Could not create AF_NETLINK socket (Permission denied)
00:07:10 - Qt Critical: Could not create AF_NETLINK socket (Permission denied)
00:07:10 - Qt Critical: Could not create AF_NETLINK socket (Permission denied)

The following message is spammed over and over dmesg:

[43929.065137] audit: type=1400 audit(1589559656.939:5446): apparmor="DENIED" operation="create" profile="snap.moonlight.moonlight" pid=27398 comm="moonlight" family="netlink" sock_type="dgram" protocol=0 requested_mask="create" denied_mask="create"
``

Core20: VDPAU broken on AMD GPUs

I noticed in my testing that Moonlight seems to be unable to find the VDPAU driver on Core20 with an AMD GPU. The Core18-based Snap seems to work fine.

Failed to open VDPAU backend libvdpau_radeonsi.so: cannot open shared object file: No such file or directory

The problem seems to be the following lines in va-wrapper:

elif [[ $VENDOR == *"X.Org"* ]]; then
  export VDPAU_DRIVER_PATH="/usr/lib/$ARCH/vdpau/"
fi

I'm not sure what that was intending to do. I don't think that path would ever be accessible from within a strictly confined Snap. The correct path is $SNAP/usr/lib/$ARCH/vdpau which is what would be used if the above code was not present at all.

The Core18 Snap fails with the VDPAU_DRIVER_PATH value, then succeeds with $SNAP/usr/lib/$ARCH/vdpau (no clue where it's getting that path)

openat(AT_FDCWD, "/usr/lib/x86_64-linux-gnu/vdpau//libvdpau_radeonsi.so.1", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "/snap/moonlight/870/usr/lib/x86_64-linux-gnu/vdpau/libvdpau_radeonsi.so.1", O_RDONLY|O_CLOEXEC) = 21

The Core20 Snap tries VDPAU_DRIVER_PATH value then a bunch of different library paths before failing:

openat(AT_FDCWD, "/usr/lib/x86_64-linux-gnu/vdpau//libvdpau_radeonsi.so.1", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "/usr/lib/x86_64-linux-gnu/vdpau/libvdpau_radeonsi.so.1", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "/var/lib/snapd/lib/gl/libvdpau_radeonsi.so", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "/var/lib/snapd/lib/gl32/libvdpau_radeonsi.so", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "/var/lib/snapd/void/libvdpau_radeonsi.so", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "tls/x86_64/x86_64/libvdpau_radeonsi.so", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "tls/x86_64/libvdpau_radeonsi.so", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "tls/x86_64/libvdpau_radeonsi.so", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "tls/libvdpau_radeonsi.so", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "x86_64/x86_64/libvdpau_radeonsi.so", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "x86_64/libvdpau_radeonsi.so", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "x86_64/libvdpau_radeonsi.so", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "libvdpau_radeonsi.so", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "/snap/moonlight/880/lib/libvdpau_radeonsi.so", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "/snap/moonlight/880/usr/lib/libvdpau_radeonsi.so", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "/snap/moonlight/880/lib/x86_64-linux-gnu/libvdpau_radeonsi.so", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "/snap/moonlight/880/usr/lib/x86_64-linux-gnu/libvdpau_radeonsi.so", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "/snap/moonlight/880/usr/lib/x86_64-linux-gnu/dri/libvdpau_radeonsi.so", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "/snap/moonlight/880/usr/lib/x86_64-linux-gnu/pulseaudio/libvdpau_radeonsi.so", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)

Is it safe to simply remove those lines in va-wrapper? Presumably they were there for some reason...

glxinfo.txt

Moonlight Snap not working with Nvidia drivers installed (Ubuntu 21.10)

$ snap run moonlight
/snap/moonlight/1411/usr/bin/moonlight: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.33' not found (required by /var/lib/snapd/lib/gl/libEGL.so.1)

This only happens if using proprietary Nvidia driver (470 or 495, doesn't matter). Same thing happened to Telegram and other apps, but Telegrams is already fixed by developers.
https://bugs.launchpad.net/snapd/+bug/1916745

Scrolling crashes on Ubuntu 22.10 (edge)

When using the scroll wheel while streaming on Ubuntu 22.10 using Wayland, a Wayland protocol error is displayed and the stream terminates. The error is: interface 'wl_pointer' has no event 9

It seems to related to the high-resolution scrolling support added in SDL which was pulled into edge with 0774297. My guess is that SDL's Wayland protocol files are newer than than core22's libraries, which leads to some sort of marshalling error when trying to handle these new events.

Since the compositor needs to actually support wl_pointer v8 for SDL to use it, that probably explains why it only affects Ubuntu 22.10.

This probably needs to be addressed on the SDL side, but for now, you can revert 0774297 to fix edge.

Moonlight stopped working after update

Last working version was 870.
Possibly apparmor related, but also segfaults:

00:00:00 - Qt Warning: propsReply "An AppArmor policy prevents this sender from sending this message to this recipient; type="method_call", sender=":1.8159" (uid=1000 pid=28297 comm="/snap/moonlight/975/usr/bin/moonlight " label="snap.moonlight.moonlight (enforce)") interface="org.freedesktop.DBus.Properties" member="GetAll" error name="(unset)" requested_reply="0" destination="org.freedesktop.NetworkManager" (uid=0 pid=1186 comm="/usr/sbin/NetworkManager --no-daemon " label="unconfined")"
00:00:00 - Qt Warning: nmReply "An AppArmor policy prevents this sender from sending this message to this recipient; type="method_call", sender=":1.8159" (uid=1000 pid=28297 comm="/snap/moonlight/975/usr/bin/moonlight " label="snap.moonlight.moonlight (enforce)") interface="org.freedesktop.NetworkManager" member="GetDevices" error name="(unset)" requested_reply="0" destination="org.freedesktop.NetworkManager" (uid=0 pid=1186 comm="/usr/sbin/NetworkManager --no-daemon " label="unconfined")"
00:00:00 - Qt Warning: "Object path cannot be empty"
00:00:00 - Qt Debug: Current Moonlight version: "2.2.0"
Segmentation fault (core dumped)

Dependency updates and libdecor support

Now that SDL 2.0.18 is out with some nice X11 and Wayland fixes, I have bumped the SDL version in the Moonlight Flatpak to 2.0.18 to pick those up. I've also added libdecor, which SDL uses (if available) to draw window borders on Wayland windows. If you could update the Snap to pick those up, I'd appreciate it.

Relevant commits:
flathub/com.moonlight_stream.Moonlight@daea5ec
flathub/com.moonlight_stream.Moonlight@f375b37

There is windows ARM64 binary release but not Linux (in snap)

Is your feature request related to a problem? Please describe.

$ sudo snap install moonlight
error: snap "moonlight" is not available on stable for this architecture
       (arm64) but exists on other architectures (amd64, i386).

Describe the solution you'd like
Wish to see the arm64 binary for Moonlight.

Describe alternatives you've considered
I wish to emphasize that Linux arm64 binary is more needed than Windows, because Windows users can use WOW64 to run x86 binary but Linux users don't have this advantage and have to seek out 64-bit native executables.

Additional context
The computer I am using is Lenovo X13s Snapdragon with Ubuntu 23.04

Use newer version of SDL for better Wayland support

There has been a bunch of work in SDL lately to improve Wayland support (including fixing scroll speed on trackpads, preventing the screensaver from starting when playing with a gamepad, fixing window resize support, fixing key repeat going wild after Alt+Tabbing, fixing mouse pointer hiding on Plasma, and adding keyboard grab which Moonlight uses for system key capture). These haven't made it into an official SDL release but should come out in 2.0.16 in a few months (not that it really matters for our purposes).

Being stuck with Ubuntu 20.04's version of SDL means that we're have much less mature Wayland support, which is problematic on distros using Wayland by default (most distros these days). It also means that the system key capture feature in Moonlight will not work with the Snap (due to the missing Wayland keyboard grab support in SDL), which will probably confuse users.

I've been bundling a new SDL version in the Moonlight Flatpak for a while. If you could do something similar, that would bring better parity with the Flatpak.

I'd recommend sticking with a SDL commit that I've tested Moonlight with like dfa64eadd38a6a8125290dcf121f1bc285e98dad for the stable snaps, but you could use SDL master for edge if you want.

Hardware video decoding not detected on Ubuntu 20.04.6 with X11 and Intel HD graphics

After a year or so without problems, all of a sudden a few days ago the Moonlight snap on my Ubuntu machine with Intel HD integrated graphics starting showing me a warning message about hardware decoding not being detected.

Not sure if the actual issue is related to the snap package, the upstream Moonlight project, or the most recent Ubuntu or kernel updates. I checked the system logs (pasted below), and the lines jumping out at me say "Moonlight not compiled with VAAPI X11 support", then fails to open a VDPAU backend (which maybe isn't even necessary for Intel graphics), before eventually falling back on software decoding via ffmpeg. I see more or less the same info when I run moonlight from a terminal. Hopefully somebody here can provide some insights or point me toward a resolution.

I should also mention that I tried manually installing vainfo and its dependencies to see if it had any effect, and running vainfo correctly shows the current VAAPI version information, but the snap isn't recognizing the system installation of VAAPI.

Apr 01 16:36:41 server moonlight_moonlight.desktop[3136]: 03:03:25 - SDL Info (0): Loaded 266 new gamepad mappings
Apr 01 16:36:41 server moonlight_moonlight.desktop[3136]: 03:03:25 - SDL Info (0): V-sync disabled
Apr 01 16:36:41 server moonlight_moonlight.desktop[3136]: 03:03:25 - SDL Error (0): Moonlight not compiled with VAAPI X11 support!
Apr 01 16:36:41 server moonlight_moonlight.desktop[3136]: 03:03:25 - SDL Error (0): Moonlight not compiled with VAAPI X11 support!
Apr 01 16:36:41 server moonlight_moonlight.desktop[3136]: Failed to open VDPAU backend libvdpau_va_gl.so: cannot open shared object file: No such file or directory
Apr 01 16:36:41 server moonlight_moonlight.desktop[3136]: 03:03:25 - FFmpeg: [AVHWDeviceContext @ 0x7fc1387e1dc0] VDPAU device creation on X11 display :0 failed.
Apr 01 16:36:41 server moonlight_moonlight.desktop[3136]: 03:03:25 - SDL Error (0): Failed to create VDPAU context: -1313558101
Apr 01 16:36:41 server moonlight_moonlight.desktop[3136]: Failed to open VDPAU backend libvdpau_va_gl.so: cannot open shared object file: No such file or directory
Apr 01 16:36:41 server moonlight_moonlight.desktop[3136]: 03:03:25 - FFmpeg: [AVHWDeviceContext @ 0x7fc13803c080] VDPAU device creation on X11 display :0 failed.
Apr 01 16:36:41 server moonlight_moonlight.desktop[3136]: 03:03:25 - SDL Error (0): Failed to create VDPAU context: -1313558101
Apr 01 16:36:41 server moonlight_moonlight.desktop[3136]: 03:03:25 - FFmpeg: [AVHWDeviceContext @ 0x7fc138894780] Cannot load libcuda.so.1
Apr 01 16:36:41 server moonlight_moonlight.desktop[3136]: 03:03:25 - FFmpeg: [AVHWDeviceContext @ 0x7fc138894780] Could not dynamically load CUDA
Apr 01 16:36:41 server moonlight_moonlight.desktop[3136]: 03:03:25 - SDL Error (0): av_hwdevice_ctx_create(CUDA) failed: -1
Apr 01 16:36:41 server moonlight_moonlight.desktop[3136]: 03:03:25 - FFmpeg: [AVHWDeviceContext @ 0x7fc138028840] Cannot load libcuda.so.1
Apr 01 16:36:41 server moonlight_moonlight.desktop[3136]: 03:03:25 - FFmpeg: [AVHWDeviceContext @ 0x7fc138028840] Could not dynamically load CUDA
Apr 01 16:36:41 server moonlight_moonlight.desktop[3136]: 03:03:25 - SDL Error (0): av_hwdevice_ctx_create(CUDA) failed: -1
Apr 01 16:36:41 server moonlight_moonlight.desktop[3136]: 03:03:25 - SDL Error (0): Moonlight not compiled with VAAPI X11 support!
Apr 01 16:36:41 server moonlight_moonlight.desktop[3136]: 03:03:25 - SDL Error (0): Moonlight not compiled with VAAPI X11 support!
Apr 01 16:36:41 server moonlight_moonlight.desktop[3136]: Failed to open VDPAU backend libvdpau_va_gl.so: cannot open shared object file: No such file or directory
Apr 01 16:36:41 server moonlight_moonlight.desktop[3136]: 03:03:25 - FFmpeg: [AVHWDeviceContext @ 0x7fc1387bd380] VDPAU device creation on X11 display :0 failed.
Apr 01 16:36:41 server moonlight_moonlight.desktop[3136]: 03:03:25 - SDL Error (0): Failed to create VDPAU context: -1313558101
Apr 01 16:36:41 server moonlight_moonlight.desktop[3136]: Failed to open VDPAU backend libvdpau_va_gl.so: cannot open shared object file: No such file or directory
Apr 01 16:36:41 server moonlight_moonlight.desktop[3136]: 03:03:25 - FFmpeg: [AVHWDeviceContext @ 0x7fc13814f900] VDPAU device creation on X11 display :0 failed.
Apr 01 16:36:41 server moonlight_moonlight.desktop[3136]: 03:03:25 - SDL Error (0): Failed to create VDPAU context: -1313558101
Apr 01 16:36:41 server moonlight_moonlight.desktop[3136]: 03:03:25 - SDL Info (0): Using SDL renderer
Apr 01 16:36:41 server moonlight_moonlight.desktop[3136]: 03:03:25 - FFmpeg: [h264 @ 0x7fc1385702c0] nal_unit_type: 7(SPS), nal_ref_idc: 3
Apr 01 16:36:41 server moonlight_moonlight.desktop[3136]: 03:03:25 - FFmpeg: [h264 @ 0x7fc1385702c0] nal_unit_type: 8(PPS), nal_ref_idc: 3
Apr 01 16:36:41 server moonlight_moonlight.desktop[3136]: 03:03:25 - FFmpeg: [h264 @ 0x7fc1385702c0] nal_unit_type: 5(IDR), nal_ref_idc: 3
Apr 01 16:36:41 server moonlight_moonlight.desktop[3136]: 03:03:25 - FFmpeg: [h264 @ 0x7fc1385702c0] nal_unit_type: 5(IDR), nal_ref_idc: 3
Apr 01 16:36:41 server moonlight_moonlight.desktop[3136]: 03:03:25 - FFmpeg: [h264 @ 0x7fc1385702c0] nal_unit_type: 5(IDR), nal_ref_idc: 3
Apr 01 16:36:41 server moonlight_moonlight.desktop[3136]: 03:03:25 - FFmpeg: [h264 @ 0x7fc1385702c0] nal_unit_type: 5(IDR), nal_ref_idc: 3
Apr 01 16:36:41 server moonlight_moonlight.desktop[3136]: 03:03:25 - FFmpeg: [h264 @ 0x7fc1385702c0] Decoding VUI
Apr 01 16:36:41 server moonlight_moonlight.desktop[3136]: 03:03:25 - FFmpeg: [h264 @ 0x7fc1385702c0] Format yuv420p chosen by get_format().
Apr 01 16:36:41 server moonlight_moonlight.desktop[3136]: 03:03:25 - FFmpeg: [h264 @ 0x7fc1385702c0] Reinit context to 1280x720, pix_fmt: yuv420p
Apr 01 16:36:41 server moonlight_moonlight.desktop[3136]: 03:03:25 - SDL Info (0): FFmpeg-based video decoder chosen
Apr 01 16:36:41 server moonlight_moonlight.desktop[3136]: 03:03:25 - SDL Info (0): Encoder configured for 4 slices per frame

Snap installation not working

Hello. I installed moonlight via snap. However, I have this error when starting:

$ moonlight 
+ case "$SNAP_ARCH" in
+ ARCH=x86_64-linux-gnu
++ glxinfo
++ grep 'OpenGL vendor'
Error: unable to open display :0.0
+ VENDOR=
+ export VDPAU_DRIVER_PATH=/snap/moonlight/96/usr/lib/x86_64-linux-gnu/vdpau
+ VDPAU_DRIVER_PATH=/snap/moonlight/96/usr/lib/x86_64-linux-gnu/vdpau
+ export LIBVA_DRIVERS_PATH=/snap/moonlight/96/usr/lib/x86_64-linux-gnu/dri
+ LIBVA_DRIVERS_PATH=/snap/moonlight/96/usr/lib/x86_64-linux-gnu/dri
+ [[ '' == *\N\V\I\D\I\A* ]]
+ [[ '' == *\X\.\O\r\g* ]]
+ exec /snap/moonlight/96/usr/bin/moonlight
00:00:00 - Qt Warning: QXcbConnection: Could not connect to display :0.0
00:00:00 - Qt Critical: Could not connect to any X display.

My system is Xubuntu 18.04 64-bit. I have integrated GPU: Intel HD 500.

Snap isn't working on Wayland

I tried starting the Moonlight stable snap (1574) under Wayland on both Fedora 35 and Ubuntu 22.04 Beta.

In both cases, the result was an infinite stream of "Couldn't open plugin directory: No such file or directory" messages that required me to kill -9 moonlight.

00:00:00 - SDL Info (0): Compiled with SDL 2.0.21
00:00:00 - SDL Info (0): Running with SDL 2.0.21
00:00:00 - Qt Info: Warning: Ignoring XDG_SESSION_TYPE=wayland on Gnome. Use QT_QPA_PLATFORM=wayland to run on Wayland anyway.
00:00:00 - Qt Warning: QSocketNotifier: Can only be used with threads started with QThread
00:00:00 - Qt Debug: Using Wayland-EGL
00:00:00 - Qt Info: No translation available for  "en_US"
00:00:00 - SDL Info (0): Detected Wayland
00:00:00 - Qt Warning: qrc:/gui/main.qml:12:1: QML ApplicationWindow: ToolTip must be attached to an Item
00:00:00 - Qt Info: Found "gamecontrollerdb.txt" at ":/data/gamecontrollerdb.txt"
00:00:00 - SDL Info (0): Loaded 202 new gamepad mappings
Couldn't open plugin directory: No such file or directory
Couldn't open plugin directory: No such file or directory
Couldn't open plugin directory: No such file or directory
Couldn't open plugin directory: No such file or directory
Couldn't open plugin directory: No such file or directory
Couldn't open plugin directory: No such file or directory
Couldn't open plugin directory: No such file or directory
Couldn't open plugin directory: No such file or directory
Couldn't open plugin directory: No such file or directory
Couldn't open plugin directory: No such file or directory
Couldn't open plugin directory: No such file or directory
[...]

Manually forcing Qt to run using the X11 backend (passing -platform xcb) does work though, so it seems like maybe something is wrong with how the Qt Wayland plugin is being packaged in the Snap.

Request joystick plug auto-connection

Per @popey 's suggestion on libretro/retroarch-snap#11 we should also request this be autoconnected by default to provide an equivalent user experience to the official Flatpak package.

Once this is done and snapd 2.37 makes it out of bionic-proposed to fix #1 , I will add a link to the website to direct Ubuntu users to this Snap.

@maxiberta as package owner, can you create the forum thread required?

Migrating to Core20

We discussed this a bit in moonlight-stream/moonlight-qt#380 but I'd like to have a longer discussion.

My concern with continuing to rely on Core18 is that we will have issues supporting newer Intel hardware (Coffee Lake, Ice Lake, etc) which are only supported with the new intel-media-driver package that isn't present in Bionic repos. I don't want a few 32-bit users to keep us from supporting users on the latest and greatest hardware. Core18 also has an older version of SDL which has a bug making it unsafe to use our new EGLRenderer on it.

I'm sure we could solve all of this by finding PPAs or building this stuff from scratch, but IMHO it's not worth the effort. If we had to build intel-media-driver, we'd need to also build a newer libva from scratch too. And who knows what other bugfixes we'd be missing in Mesa, other VA drivers, or other libs we don't even know about. I'm worried we may end up chasing bugs that have already been fixed upstream years ago.

What are your thoughts?

h.264 video decoder not detected

Thanks for making this snap!

I've been playing with it on my Ubuntu 18.04 nVidia equipped laptop. It's failing to find the h.264 decoder. I installed vdpau-va-driver and it's still not quite right. Here's the log of it running

alan@hal:~$ moonlight 
+ case "$SNAP_ARCH" in
+ ARCH=x86_64-linux-gnu
++ glxinfo
++ grep 'OpenGL vendor'
+ VENDOR='OpenGL vendor string: NVIDIA Corporation'
+ echo VENDOR: OpenGL vendor string: NVIDIA Corporation
VENDOR: OpenGL vendor string: NVIDIA Corporation
+ [[ OpenGL vendor string: NVIDIA Corporation == *\I\n\t\e\l* ]]
+ [[ OpenGL vendor string: NVIDIA Corporation == *\N\V\I\D\I\A* ]]
+ export VDPAU_DRIVER_PATH=/var/lib/snapd/lib/gl/vdpau
+ VDPAU_DRIVER_PATH=/var/lib/snapd/lib/gl/vdpau
+ exec /snap/moonlight/12/usr/bin/moonlight
00:00:00 - Qt Warning: Qt: Session management error: None of the authentication protocols specified are supported
00:00:00 - SDL Info (0): Loading gamepad mappings from: /snap/moonlight/12/usr/share/Moonlight Game Streaming Project/Moonlight/gamecontrollerdb.txt
00:00:00 - SDL Info (0): Loaded 131 new gamepad mappings
00:00:00 - Qt Warning: propsReply "An AppArmor policy prevents this sender from sending this message to this recipient; type=\"method_call\", sender=\":1.1149\" (uid=1000 pid=24153 comm=\"/snap/moonlight/12/usr/bin/moonlight \" label=\"snap.moonlight.moonlight (enforce)\") interface=\"org.freedesktop.DBus.Properties\" member=\"GetAll\" error name=\"(unset)\" requested_reply=\"0\" destination=\"org.freedesktop.NetworkManager\" (uid=0 pid=3446 comm=\"/usr/sbin/NetworkManager --no-daemon \" label=\"unconfined\")"
00:00:00 - Qt Warning: nmReply "An AppArmor policy prevents this sender from sending this message to this recipient; type=\"method_call\", sender=\":1.1149\" (uid=1000 pid=24153 comm=\"/snap/moonlight/12/usr/bin/moonlight \" label=\"snap.moonlight.moonlight (enforce)\") interface=\"org.freedesktop.NetworkManager\" member=\"GetDevices\" error name=\"(unset)\" requested_reply=\"0\" destination=\"org.freedesktop.NetworkManager\" (uid=0 pid=3446 comm=\"/usr/sbin/NetworkManager --no-daemon \" label=\"unconfined\")"
00:00:00 - Qt Warning: "Object path cannot be empty"
00:00:00 - Qt Debug: Current Moonlight version: "0.8.1"
00:00:01 - SDL Info (0): V-sync enabled
libva info: VA-API version 1.1.0
libva info: va_getDriverName() returns 0
libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/nvidia_drv_video.so
libva info: va_openDriver() returns -1
00:00:01 - SDL Error (0): Failed to initialize VAAPI: -1
Failed to open VDPAU backend libvdpau_nvidia.so: cannot open shared object file: No such file or directory
00:00:01 - FFmpeg: [AVHWDeviceContext @ 0x55e2ec161c40] VDPAU device creation on X11 display :1 failed.
00:00:01 - SDL Error (0): Failed to create VDPAU context: -1313558101
00:00:01 - SDL Info (0): Frame pacing disabled: target 60 Hz with 60 FPS stream
00:00:01 - SDL Info (0): Using SDL software renderer
00:00:01 - SDL Info (0): FFmpeg-based video decoder chosen
00:00:01 - SDL Info (0): Loading gamepad mappings from: /snap/moonlight/12/usr/share/Moonlight Game Streaming Project/Moonlight/gamecontrollerdb.txt
00:00:01 - SDL Info (0): Loaded 0 new gamepad mappings
00:00:10 - Qt Info: "LEGION-PC" is now offline

Feature request: change the audio Device used

Some versions of moonlight have a "--audio" flag on execution that allow the user to specify which hardware device to output sound from. The snap version does not appear to have an easy way for users to change where the audio comes from on the client side (3.5mm jack, HDMI, bluetooth device, or all of the above).

Is this expected behavior for the snap version?