Skip to content
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

Exit Code 1? #138

Closed
zack93rh opened this issue Sep 22, 2015 · 9 comments
Closed

Exit Code 1? #138

zack93rh opened this issue Sep 22, 2015 · 9 comments

Comments

@zack93rh
Copy link

So I kept running into the "InsecurePlatform" error when I would launch streams using livestreamer and finally managed to fix that earlier today. However, now the twitch gui is broken and keeps saying "Error: Couldn't Launch the Stream" with "Exit Code 1" as the description. I imagine this has something to do with me reinstalling livestreamer, but I don't really know how to fix it. I've tried deleting the GUI application and the application support folder and reinstalling, but no dice. Has this come up before? Sorry if this is a common/stupid problem, but I'm still kind of a code noob.

@bastimeyer
Copy link
Member

Are you sure you have fixed your livestreamer installation?
The error is being thrown at this line and is caused by an error of the livestreamer process during the version validation.

Please run these commands from the shell and see if there are any errors (which most likely will be):
livestreamer --version --no-version-check (the validation command)
livestreamer twitch.tv/CHANNEL best (stream test command)

Btw, you don't need to remove/delete the GUI, as it will just execute these kind of commands and is not related to any of these livestreamer errors...

@zack93rh
Copy link
Author

Validation command result: livestreamer 1.12.2 (that's all it spit out)
Stream test: works fine.

The plugin is working fine currently, it seems.

@bastimeyer
Copy link
Member

What's the exit code of the process?

On *nix systems (and using a bash-like shell):
livestreamer --version --no-version-check; echo $?
On Windows systems:
start /wait livestreamer --version --no-version-check & echo %ERRORLEVEL%

The plugin is working fine currently, it seems.

Are you talking about the twitch plugin of livestreamer?

@zack93rh
Copy link
Author

http://imgur.com/a/FPraB

That's what I'm dealing with. The plugin itself will launch no problem, but the GUI won't open any streams and spits out that exit code.

@bastimeyer
Copy link
Member

Yes, right, because livestreamer is exiting with status code 1 (code > 0 => error) during the validation. The output log is actually irrelevant...
Run livestreamer --version --no-version-check &>/dev/null; echo $? to see if it exits correctly.

The validation was broken in the v0.9.2 release (see #121), so maybe there is another yet undiscovered issue...

Also: Github allows you to paste/drag images directly into the textarea, so you don't need to use external image hosters

@zack93rh
Copy link
Author

Oh, sweet! I'm still figuring out github. Hopefully one day I'll learn enough code to actually do something with it.

And yup, running that put out a 0. And I remember the validation breaking, but it seemed that was fixed once I reinstalled the plugin/made sure Python was updated.

@bastimeyer
Copy link
Member

And yup, running that put out a 0.

Are you sure you are running the same livestreamer executable as the GUI does? which livestreamer tells you the absolute path when you are just calling livestreamer.
On OSX, the application is unable to read from $PATH, so multiple fallback paths needed to be set. Please check in these paths for another livestreamer executable and see if it returns an error. If it does, go to the settings menu in the GUI and set the path to the one which livestreamer returned, so you are executing the working one when opening streams.

Other than that, I don't know what would cause this issue. It would mean, that the GUI would cause livestreamer to exit with an error, but executing it from the bash would not, and that doesn't make sense to me.

@zack93rh
Copy link
Author

That fixed it! Thanks for all the help!

And I should note that the GUI didn't appear to be exiting the plugin itself, it simply wouldn't seem to load it. Like immediately upon clicking the stream, it would go to that error screen.

@bastimeyer
Copy link
Member

yw

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants