Error and GUI terminates back to ES when launching RetroPie-Setup direct on machine (libudev?) - but SSH is ok

psyke83

OK, it should be fixed by: https://github.com/RetroPie/RetroPie-Setup/pull/2606 (already merged).

Make sure to kill any leftover joy2key processes after updating the script (or just reboot):

sudo kill $(pgrep joy2key)

movisman

Wow!
I just sat down at my computer to see if there were any updates to this thread - let me update the script and reboot now, and will let you know my findings. I wonder if this will also fix the screwy controls, will soon find out!

Will report back shortly.

Cheers

movisman

@psyke83

That totally fixed the problem, after an update of the script and reboot, all the menus now work within ES or a standalone terminal on the machine directly, and of course SSH works as it did previously. Haven't had it crash out on me yet.

Also the controls are no longer screwy, A and B on the controller now perform 'action' and the dpad correctly navigates around the menu. Just to confirm i'm not going mad, the RetroPie GUI never supported 'action' and 'back' on a controller did it? For some reason I thought in the past I could use A to action a command, and B to go up a menu while in RetroPie-Setup on a controller. It really doesn't matter of course, i'm just curious.

Thank you so much for getting to the bottom of this and fixing it up so rapidly. I am really grateful for all the time you guys spend on the project and helping people like me.

Out of interest - any idea why that would have started happening? Do you think script adjustments caused it, or an OS update caused this strangeness? It certainly wasn't something which happened out of the box when I installed 18.04.1 in November, it was working fine up until fairly recently.

Thanks!

PS. Also - thanks for fixing the "Directory: /usr/src/hid-sony-0.1.1 does not exist." error when updating RetroPie-Setup, I noticed this last night after you pushed one of the commits, and was going to mention it in passing - but it's all good now, I guess the commits you made a few hours ago fixed that too.

psyke83

@movisman

Glad to hear it's sorted, but I think you may be right that it used to be possible to go back using B/circle; it's not working for me now either. There might be an issue with the script that needs to be fixed. Will look at it soon ;)

psyke83

See here: https://github.com/RetroPie/RetroPie-Setup/blob/master/scriptmodules/helpers.sh#L1037

If you change the 0x20 (space code) to 0x1b (escape code), it seems to restore the behaviour that we're expecting. Not sure why it's like this?

xnickygx

I am experiencing this same error when I launch games from ES. I was having the problem outlined above with the Setup menu (running this on Ubuntu 18.04), however after updating the setup script it seems to have corrected that part. I still receive the error:

/opt/retropie/supplementary/runcommand/runcommand.sh: line 961: read: read error: 0: Resource temporarily unavailable
Exception AttributeError: "'Context' object has no attribute '_libudev'" in <bound method Context.del of <pyudev.core.Context object at 0x7f45d18b9e90>> ignored

when launching games. It seems to display the error and try to load the game but I see no video. Sometimes the games will actually run and I can hear them and the controller will respond, but most of the time it appears to just sit at the black screen until i force close everything. I have tried NES, SNES, PSX, N64(oddly this shows the error on the runcommand screen but the game still plays with video), Atari 2600, and Atari 7800. I noticed the RetroPie-Setup issue a couple days ago, but the error when trying to launch games seems to have started today.

mitu

@xnickygx The video part is an unrelated error - I advise you to disable video_threaded (see here) in your RetroArch configuration and try again. If you still have problems with the video, please open a new topic.

xnickygx

@mitu Thanks for that suggestion! That seems to have fixed the video not displaying when launching games. I havent messed with any configs for a while now. I wonder why all of a sudden that stopped displaying video. I think I played the same games either yesterday or the day before without issue. Any ideas?

As for the error message when launching... I am still seeing the error message I posted in the other reply when I launch games. The runcommand screen shows and disappears much faster than it used to and the error is at the bottom of that screen. should I open a new topic for that error or is it related this one?

mitu

@xnickygx said in Error and GUI terminates back to ES when launching RetroPie-Setup direct on machine (libudev?) - but SSH is ok:

@mitu Thanks for that suggestion! That seems to have fixed the video not displaying when launching games. I havent messed with any configs for a while now. I wonder why all of a sudden that stopped displaying video. I think I played the same games either yesterday or the day before without issue. Any ideas?

The default for RetroPie installation was to set video_threaded, however in 18.10 and after an update (last summer) to 18.04 Mesa libs, this parameter seems to be necessary to make RetroArch based emulators work. If you installed RetroPie before the change was added, then the default would have remained.

The 2nd part is handled in this topic, see @psyke83's replies above about why the error is shown. The warning is harmless and you can ignore it for now - it might be fixed in a subsequent update.

xnickygx

@mitu Interesting. I have had RetroPie installed for a few months now and haven't had any issues with the video until today.

In response to the error... perfect. I wont worry about it for now. I guess I just wanted to make sure it wasn't something else since I was seeing it on game launch and not in the RetroPie Setup. thanks again!!

psyke83

This post is deleted!

psyke83

@BuZz

It looks like we might need to add a delay to the runcommand invocation as well?

I implemented python-evdev support into the script: https://github.com/RetroPie/RetroPie-Setup/compare/master...psyke83:joy2key_evdev

Tested it on Ubuntu 18.10, confirmed it to work well and eliminate the need for any delays... and then realized afterwards that Raspbian doesn't have this package :/

It's possible to get on Raspbian via installing python-pip and then installing it that way, but python-pip requires 30MB or so of extra packages. A damn shame :(

movisman

@psyke83

Hi again, just catching up on these, thanks again - it sounds like I've opened a bit of a can of worms by reporting this issue!

Regarding the controllers, I thought that the setup script GUI used to support both action + back, but I just couldn't remember for sure - so i'm glad I mentioned it. Do you still want me to try changing the 0x20 space code to 0x1b escape code for a test? If so, I can do this when I get home from a bit later on (in around 8hrs time) and let you know. Or have you confirmed/fixed it in your code already?

As for the other stuff, do you think the extra 30mb is a major issue for a future RetroPie image? I know it ideally needs to be kept as compact as possible, but I would say even on my Picade machine which is driven by a Pi 2 I wouldn't bat an eyelid that the ISO download is slightly larger than it used to be if I was to update or re-image it. The fact it's under a gig in this day and age is already impressive! But that's just my thoughts, I can see why it needs to be kept super minimal too.

hhromic

@psyke83 said in Error and GUI terminates back to ES when launching RetroPie-Setup direct on machine (libudev?) - but SSH is ok:

@BuZz

It looks like we might need to add a delay to the runcommand invocation as well?

I implemented python-evdev support into the script: https://github.com/RetroPie/RetroPie-Setup/compare/master...psyke83:joy2key_evdev

Tested it on Ubuntu 18.10, confirmed it to work well and eliminate the need for any delays... and then realized afterwards that Raspbian doesn't have this package :/

It's possible to get on Raspbian via installing python-pip and then installing it that way, but python-pip requires 30MB or so of extra packages. A damn shame :(

how about the idea of re-implementing joy2key in C and use libevdev/libudev directly? the binary would be much smaller and elegant than having the python interpreter :)
joy2key doesn't seem to be too complex functionally speaking. In few weeks I will have much more time available and could help with this if interested.