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

[RPi3] Exception OSError #2151

Closed
LodanZark opened this Issue Oct 11, 2017 · 5 comments

Comments

Projects
None yet
3 participants
@LodanZark
Contributor

LodanZark commented Oct 11, 2017

In the terminal, after leaving the retropie_setup.sh, I got this message:
Exception OSError: (9, 'Bad file descriptor') in <module 'threading' from '/usr/lib/python2.7/threading.pyc'> ignored
I'm not sure if it is a result of a recent commit or if it's caused for some faulty config on my side

@joolswills

This comment has been minimized.

Show comment
Hide comment
@joolswills

joolswills Oct 11, 2017

Member

You have provided no information about your set-up - Also please use the forum first for reports / support as detailed when opening a ticket - the forum also provides information of what is required (I'm sure I have mentioned this before to you).

Member

joolswills commented Oct 11, 2017

You have provided no information about your set-up - Also please use the forum first for reports / support as detailed when opening a ticket - the forum also provides information of what is required (I'm sure I have mentioned this before to you).

@joolswills joolswills closed this Oct 11, 2017

@joolswills

This comment has been minimized.

Show comment
Hide comment
@joolswills

joolswills Oct 11, 2017

Member

I managed to reproduce this on my rpi3

@psyke83 Looks like your commit did it #2148

It's a non fatal error, but I will revert your change for now.

Member

joolswills commented Oct 11, 2017

I managed to reproduce this on my rpi3

@psyke83 Looks like your commit did it #2148

It's a non fatal error, but I will revert your change for now.

@psyke83

This comment has been minimized.

Show comment
Hide comment
@psyke83

psyke83 Oct 11, 2017

Contributor

Yes, it was a sys.exit() exception likely caused by repeated calls of signal_handler. Increasing the sleep in the loop would help but no guarantee it would stop this in all cases.

I also tried to make joy2key.py instead pass a signal back to the parent bash process which joy2KeyStart could wait to receive, but didn't have much luck yet. Best to just leave this alone for now as it's just wasting your time.

Contributor

psyke83 commented Oct 11, 2017

Yes, it was a sys.exit() exception likely caused by repeated calls of signal_handler. Increasing the sleep in the loop would help but no guarantee it would stop this in all cases.

I also tried to make joy2key.py instead pass a signal back to the parent bash process which joy2KeyStart could wait to receive, but didn't have much luck yet. Best to just leave this alone for now as it's just wasting your time.

@joolswills

This comment has been minimized.

Show comment
Hide comment
@joolswills

joolswills Oct 11, 2017

Member

I don't like the fact that joy2key is started for commandline stuff anyway - so I think I will change it so it's only started when needed (via retropie-setup or the retropie menu launch module etc)

Member

joolswills commented Oct 11, 2017

I don't like the fact that joy2key is started for commandline stuff anyway - so I think I will change it so it's only started when needed (via retropie-setup or the retropie menu launch module etc)

@joolswills

This comment has been minimized.

Show comment
Hide comment
@joolswills

joolswills Oct 11, 2017

Member

That should mean there is enough delay etc.

Member

joolswills commented Oct 11, 2017

That should mean there is enough delay etc.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment