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
framebuffer not usable / no terminal input after exiting stella #1985
Comments
I know that the audio driver for some reason caused a black screen with certain video plugins with mupen64plus as well but likely unrelated to the framebuffer issue at hand |
That's unrelated. |
Could this be related to the mupen64plus.cfg having changes overwritten after mupen64plus is launched and closed? |
I don't think so. It's likely related to the things mentioned in the ticket. |
Just FYI on this. I am no developer and don't know linux terribly well, but my ttyecho script at http://www.humbug.in/2010/utility-to-send-commands-or-data-to-other-terminals-ttypts/ allows commands to be sent to the terminal. I don't know if that means it isn't a frame buffer issue |
mupen64plus seems ok here when exiting now - will update original issue. |
On my stretch testing build, I'm unable to reproduce any problem after repeatedly running & closing stella. When you say "unusable state", do you mean a black screen? For my setup, instead of disabling the fb blank, I still use this commit that I had previously submitted: psyke83@561036b Maybe stella is triggering a framebuffer blank on exit, which is why I don't see the problem? If it's not that, then perhaps SDL 2.0.6 fixed it, or some other update to stretch's packages fixed it. |
SDL 2.0.6 must have done the job. I've tested this with Jessie and it doesn't seem to be an issue any more. |
Just retested this. Still an issue here. Screen isn't blank. Just after exiting emulation station no keyboard input seems to work. Not tested against latest Stella code though. |
May be different causes, but exiting
mupen64plus andstella leaves framebuffer in an unusable state.This didn't use to happen with mupen64plus- could be:Changes in mupen64plus code.mupen64plus seems to be ok from my most recent testing
The text was updated successfully, but these errors were encountered: