Package Details: retroarch-standalone-service 2-14

Git Clone URL: https://aur.archlinux.org/retroarch-standalone-service.git (read-only, click to copy)
Package Base: retroarch-standalone-service
Description: Systemd service and user to run Retroarch in stand-alone mode
Upstream URL: None
Keywords: libretro retroarch standalone
Licenses: MIT
Submitter: JulianXhokaxhiu
Maintainer: JulianXhokaxhiu
Last Packager: JulianXhokaxhiu
Votes: 3
Popularity: 0.000025
First Submitted: 2016-06-22 13:01
Last Updated: 2020-08-27 20:12

Latest Comments

1 2 3 Next › Last »

dantob commented on 2020-08-26 03:43

retroarch has its own logging priority options available in settings (for both cores and retroarch itself), is -v 2>&1 >&/home/retroarch/debug.log actually necessary?

JulianXhokaxhiu commented on 2020-08-25 10:51

@njordan: Wouldy you be so kind to make a PR over here? https://github.com/julianxhokaxhiu/AUR

So I could then pull your commit once merged and push it over here, with all the credits deserved :)

Thank you!

njordan commented on 2020-08-25 07:33

I have a patch that includes support for aarch64.

https://github.com/njordan64/retroarch-standalone-service/commit/b36e4d7bed0615ec8df53843ff63e8b63b0cbc8e

The change to retroarch-standalone.cfg may not be needed. The second change to the xinitrc file causes it to shutdown if retroarch exits successfully (you chose quit from the menu). On a crash it would just login again and restart retroarch.

telewook commented on 2020-08-19 16:12

This package ultimately led to a non-working KDE after LightDM login. Originally the service attempted to start but would hang in "pre-start" and never successfully start. This also happened after stopping the service and attempting to start it again. I made an edit to /usr/lib/sysusers.d/retroarch-standalone.conf (hyphen to group id) and rebooted.

After the reboot, I could login via lightdm but then received the error:

Could not sync environment to dbus

The DE doesn't start after this. Worse, accessing another tty via Ctrl+Alt+F4 (or any number of function keys) didn't work. I've never seen Arch screwed up enough to disallow access to another tty.

Booting the kernel via grub2 into single user mode and systemctl doesn't show the retroarch-standalone-service unit, at all. After trying a few things, removing the service package finally allowed me to reboot and login as usual:

yay -R retroarch-standalone-service

I'd be willing to do more testing but probably not for a few days as I need the machine functioning.

JulianXhokaxhiu commented on 2020-08-15 12:41

@dantob Thank you! I've double checked the sysusers.d documentation and indeed the syntax has changed, so I did integrate your suggestion in the new version of this package. I hope it will be fine now.

@all Thank you for using this :) I appreciate all the feedbacks in here, and I'm glad you find this useful. This was created to fullfil my own needs for a RetroBox I had built and I wanted to use only for this purpose, on top of ArchLinux ARM but also ArchLinux. Although as I do not use this anymore actively, let me know if you encounter any issue or if you have ideas on getting this better.

Cheers!

dantob commented on 2020-08-15 08:53

fix for retroarch-standalone.sysuser should be this

u retroarch - "Retroarch user" /home/retroarch /sbin/nologin

analca3 commented on 2020-08-11 22:10

Hi, I had the same problem as @honzor, same solution applied. The home folder was not set (checked with cat /etc/passwd) so I solved it using sudo usermod -d /home/retroarch retroarch and everything is working now :). Thanks for the good work!

berturion commented on 2020-05-27 16:55

Thanks @JulianXhokaxhiu. No issue. I just want to make retroarch writing files as another group nas and having the group writable permission on them. If I put :

[Service]
Group=nas
UMask=007

The files are correctly written with the nas group but permissions are incorrect, they have -rw-r----- instead of -rw-rw----. And I don't understand which part of the setup changes that.

JulianXhokaxhiu commented on 2020-05-27 14:02

@berturion The Umask logic is governed by Retroarch itself. The unit just starts RA with the user retroarch and group retroarch. All the rest if left to RA itself. Have you got any issue in particular that you need to mangle with the UMask?

berturion commented on 2020-05-26 20:06

Hello, can someone help me to find a way to change umask of files created by retroarch service please ? I tried a systemd unit override with :

[Service]
UMask=007

But it doesn't work. Anyway to set umask in the .xinitrc file? Other solutions?

Thanks.