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

Steam Launcher sleeper script fails to recognise Steam closure after a recent Steam update (probably) #34

Open
Juppstein opened this issue May 3, 2023 · 6 comments

Comments

@Juppstein
Copy link

Juppstein commented May 3, 2023

As of about 3 days ago or so the script watching Steam fails to notice when I close Steam. Since nothing has been done on the side of Kodi in regards to updates, at least from what I know, I assume something got changed in a recent Steam update. Since no error messages are generated its a bit hard for me to give you a relevant log file I guess :) But if you want me to test things out, I'm all in.

Running Kodi 19 under Ubuntu 22.04 LTS

@Juppstein Juppstein changed the title sleeper script fails to recognise Steam closure after a recent Steam update (probably) Steam Launcher sleeper script fails to recognise Steam closure after a recent Steam update (probably) May 3, 2023
@teeedubb
Copy link
Owner

teeedubb commented May 5, 2023

I just tested on my system and its working OK - are you running a beta version of steam? Thats the first thing that comes to mind

Edit, just saw youre running ubuntu, I checked on windows, ill check on ubuntu and update

@Juppstein
Copy link
Author

Hi! Did you have the time to check on this?

@teeedubb
Copy link
Owner

teeedubb commented Jun 1, 2023

I just tested with ubuntu 22.04.2 with the stable and beta releases of steam and both are working when exiting steam and exiting steam bpm to steam dm.

Can you run the script from a terminal (command to use for your system will be in the kodi debug log file), watch for any error messages or abnormalities and let me know if you find anything.

@Juppstein
Copy link
Author

I tested it today and now it suddenly works x__x . Which is very strange because I did nothing and it did not work as of two days ago. Since you did not push an update for your addon I must assume that somehow one of the recent Steam beta updates must have fixed the problem.

@Juppstein
Copy link
Author

OK, the report from back in May seems to have been a fluke, since that one day after Kodi does not start up again after Steam has been closed. I tried removing/reinstalling the addon to no avail. I don't really see something coming up in the Kodi logs, given that the script is not generating entries there since Kodi is not running at that particular time. Is there anything else that I could do to help this get puzzled out?

@teeedubb
Copy link
Owner

Has this been fixed with the latest release containing your changes?

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