mirror of
https://github.com/JakeStanger/mpd-discord-rpc.git
synced 2026-07-11 08:15:27 +01:00
[GH-ISSUE #138] mpd-discord-rpc.service doesn't reconnect if discord is restarted. #298
Labels
No labels
bug
enhancement
help wanted
package
pull-request
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
JakeStanger/mpd-discord-rpc#298
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @codeiimon on GitHub (Jun 17, 2024).
Original GitHub issue: https://github.com/JakeStanger/mpd-discord-rpc/issues/138
When the mpd-discord-rpc is enabled, the doesn't automatically connect to discord if it is run after or if the client is restarted. Rather
systemctl --user status restart mpd-discord-rpc.serviceoutputs this error:The current way i fix this is by restarting the service with discord using the command vesktop %U && systemctl --user restart mpd-discord-rpc.service. Its a bit hacky tho, and I would rather not have to do this.
It also runs this indefinitely, creating a massive journalctl log file full of errors. I'm not sure if that was the intention, but it'd be nice if there was a cleaner implementation.
I'm Currently on NixOS 24.05.
@42willow commented on GitHub (Nov 2, 2024):
I'm also on 24.05 with mpd-discord-rpc v1.7.2
For me it automatically reconnects to discord after the client is launched but uses a huge amount of processing power and creates the errors you described indefinitely when the discord client is not running

When discord is running it is fine though.
Seems to be related to #137
@JakeStanger commented on GitHub (Nov 16, 2024):
This does not occur for me on v1.7.3 or latest -git. The
discord-presencecrate responsible for (re-)connecting was updated several times during this period. Can you ensure you are on the latest version and check if this is still an issue please.EDIT: CPU problems were resolved, looks like it does not reliably re-connect on -git so looking at that now.
@JakeStanger commented on GitHub (Feb 13, 2025):
Resolved by
59f7ddf291