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

out of game problem - pioneer does not end when "quit" is executed #4731

Open
Cyborgscode opened this issue Nov 7, 2019 · 4 comments

Comments

@Cyborgscode
Copy link

@Cyborgscode Cyborgscode commented Nov 7, 2019

Package: pioneer-20191009-2.fc29.x86_64

if pioneer is started via a small bash script like this:

$ cat .local/bin/startpioneer

#!/bin/bash

mp3-cmdline '/home/gamer/Dave Lowe - Elite Frontier - Timeshift - Uncle Art Orchestra.mp3' 1>/dev/null 2>/dev/null </dev/null &
env force_s3tc_enable=true SDL_VIDEO_MINIMIZE_ON_FOCUS_LOSS=0 pioneer
killall mp3-cmdline

It does not close the window/screen when quitting until "killall mp3-cmdline" is executed in a different terminal.

I have no explaination, why playing a mp3 with a different programm inside a script, could prevent another program from closing a window/screen.

Pioneer stops working, no interaction is possible any more. But it does not stop.
redirecting 1,2,3,4 to dev/null on both programms does not help either.

Any Ideas here?

@Web-eWorks

This comment has been minimized.

Copy link
Member

@Web-eWorks Web-eWorks commented Nov 8, 2019

...first of all, please remember to use Markdown formatting in your issues - surround a script using three backticks like this:

```bash

# ...

```

Secondly, you do know you can redirect both stdout and stderr with &>/dev/null, right? That's making it a little hard to read the script.

From what I can tell, you're launching mp3-cmdline in the background, running Pioneer, and then killing it when Pioneer closes. There should be no issues here; Pioneer does not (as far as I'm aware) have any issues with background processes, etc. Please check Pioneer's output log for errors, as well as the terminal output from pioneer when started with the script.

@impaktor

This comment has been minimized.

Copy link
Member

@impaktor impaktor commented Nov 13, 2019

Am I correct in thinking that we don't think this is a bug with pioneer, unless logs are shown demonstrating it.

Silence = we can close.

@Cyborgscode

This comment has been minimized.

Copy link
Author

@Cyborgscode Cyborgscode commented Nov 13, 2019

The question i need to answere is: why does it happen with pioneer, not with different tools?

I may not the be fault of pioneer code, it's possible if sitting deep in a framework used.

@impaktor

This comment has been minimized.

Copy link
Member

@impaktor impaktor commented Nov 13, 2019

The question i need to answere is: why does it happen with pioneer, not with different tools?

No, I was more thinking of posting the logs:

Please check Pioneer's output log for errors, as well as the terminal output from pioneer when started with the script.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
3 participants
You can’t perform that action at this time.