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
[BUG] launchctl
errors in start/stop commands on MacOS
#83
Comments
That's my mistake. Forgot to update the value at one place!
Yeah, you'll have to manually edit |
Although, I'm not sure why |
Thanks again!
|
Hmm weird indeed. I don't have access to a Mac so I can only guess the expected behaviour. We'll explore the bug if it happens again some time later. |
Hi, this has happened to me, but not after an update. It happened on the 11th, but I've only just noticed. I updated to latest version, but the issue was still present. Resolved by using MacOS |
launchctl
errors in start/stop commands
launchctl
errors in start/stop commandslaunchctl
errors in start/stop commands on MacOS
This is mostly unrelated to the backlog cleaner, and has to do with the |
Yup, same problem here. macOS 10.15.7. [CalledProcessError] After restart I get: But it doesn't work. And after manually stopping the service I'm unable to start it up again. Last successful scrobble was on the 31st. |
Describe the bug
1.1.0 doesn't seem to be working. I first upgraded from 1.0.0 using
trakts stop
pipx upgrade trakt-scrobbler
trakts start
But
trakts start
givestrakts status
:trakts -V
:According to
pipx list
:I have tried
pipx reinstall-all
/pipx uninstall
+pipx install
as well.Running
trakts autostart enable
seems to have made it run, but it's still printing out 1.0.0 for-V
and giving me the same errors as #82 when trying to clear backlogs.Desktop (please complete the following information):
Log file
Log entries since update:
Click to see log contents
The text was updated successfully, but these errors were encountered: