-
-
Notifications
You must be signed in to change notification settings - Fork 1.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unable to run from Snap on Ubuntu Core #16730
Unable to run from Snap on Ubuntu Core #16730
Comments
RetroArch can run without an X-server via DRM/KMS, but I doubt the snap package has permissions to do such a thing. Would it be possible to download and run an AppImage on there instead? |
After some research, I think, to achieve that RetroArch snap package need to be build as a Ubuntu Frame (IoT) client.... |
It's weird. RetroArch definitely works in wayland, and according to that doc, any wayland-compatible program should run fine :/ EDITed with debug build of RetroArch:
|
Fix #57 solves the issue described by @kyvaith and now runs successfully in DRM/KMS mode on Ubuntu Core (but I could not pick up a working input driver on my VM) But RetroArch cannot run on Ubuntu Frame even with the standard build #16730 (comment). On Ubuntu Desktop 20.04 i can run RetroArch version 1.7.3 on Ubuntu Frame. But last commits worked on Weston, Sway but not Ubuntu Frame. |
Sure, go for it :) |
@kyvaith Could you please try the latest version from the |
Unfortunately, this was a one-weekend project for me and has long since been implemented and deployed on Batocera Linux. |
@hizzlekizzle This should be fixed in the latest changes. Could you test and close this if the issue doesn't reproduced? |
I don't even remember how I tested this lol I'll see if I can do it in a VM or something. |
Description
Trying to run from Snappy Ubuntu Core using
sudo snap install retroarch
Expected behavior
RetroArch starts imidietly and works
Actual behavior
Don't start. Manually doing sudo retroarch gives:
Cannot autolaunch D-Bus without X11 $Display
Version/Commit
Newest stable
Environment information
The text was updated successfully, but these errors were encountered: