You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Sometimes, DBus broker returns the name was not "activatable" on session start when spotify-listener starts. For some reason this isn't throwing a DBus error, so the message actually ends up in the track/artist variant instead, which is displayed in polybar.
Unfortunately, the cause of this has been a bit difficult to find, but after some testing I think it might be related to the implicity dependency on the user session dbus-broker service, and its dependencies. You can't just reboot and then start the service manually to reproduce the issue, so it appears to be closely coupled to something happening at session creation.
I've added a service dependency to the spotify-listener service in commit dbc4519 and will monitor over the next couple of days to see if that helps ameliorate the issue. If not, I will set up some extensive DBus comms logging and see if I can identify what's happening more accurately rather than running on a hunch.
The text was updated successfully, but these errors were encountered:
corigne
changed the title
Occasionally, at start: "The name is not activateable." Message Returned by DBus
Occasionally, at session start, "The name is not activateable." message returned by DBus
Apr 23, 2024
Sometimes, DBus broker returns the name was not "activatable" on session start when spotify-listener starts. For some reason this isn't throwing a DBus error, so the message actually ends up in the track/artist variant instead, which is displayed in polybar.
Unfortunately, the cause of this has been a bit difficult to find, but after some testing I think it might be related to the implicity dependency on the user session dbus-broker service, and its dependencies. You can't just reboot and then start the service manually to reproduce the issue, so it appears to be closely coupled to something happening at session creation.
I've added a service dependency to the spotify-listener service in commit dbc4519 and will monitor over the next couple of days to see if that helps ameliorate the issue. If not, I will set up some extensive DBus comms logging and see if I can identify what's happening more accurately rather than running on a hunch.
The text was updated successfully, but these errors were encountered: