Comments
-
Greg Hurrell
Without better information, my guess is that on launching the other app, it initiates a new session and effectively renders the old one (the one started by Synergy) invalid.
There might be a way for Synergy to detect this kind of temporary fault and correct it. The tricky part is distinguishing between temporary failures (which should be retried) and permanent ones (which should not be retried).
Can you try turning on logging of Audioscrobbler events then we can see what error messages are being returned by last.fm.
So like I said, it may be possible to transparently work around this. In the absence of such a workaround the other possibility is to add something to the UI which allows the user to force a re-login (at the moment the only way to do this is clumsy; going into the prefs and making an arbitrary, termporary change to your login details to force Synergy to renegotiate).
Add a comment
Comments are now closed for this issue.