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
{{ message }}
This repository has been archived by the owner on Jul 9, 2021. It is now read-only.
When I close Foobar, Discord still says that I'm listening to the song...
I also found out that it was still in the Task Manager running in the background when I closed Foobar
And, as long as it is in the Task Manager, I can't restart Foobar ; I have to manually kill the task, and only after that, Discord stops telling that I listen to the song, and I am now able to open Foobar again...
It could be caused by another component, but as it stays on Discord, it might be a bug of your component...
Foobar, and Discord are up to date, and I'm using Windows 7 SP1 x64. Hope this could help improving your component ;)
The text was updated successfully, but these errors were encountered:
I found out that unchecking the "Show last song instead of 'stopped' " still changes the status to stopped when Foobar is closed...
...and unchecking "show whether song has stopped" (and "Show last song..." one) stops it to display in Discord (as it should), but somehow still lets it run in the background and prevent me to launch Foobar again until I kill the task...
(ShareX is my screen-capturing software)
When I close Foobar, Discord still says that I'm listening to the song...
I also found out that it was still in the Task Manager running in the background when I closed Foobar
And, as long as it is in the Task Manager, I can't restart Foobar ; I have to manually kill the task, and only after that, Discord stops telling that I listen to the song, and I am now able to open Foobar again...
It could be caused by another component, but as it stays on Discord, it might be a bug of your component...
Foobar, and Discord are up to date, and I'm using Windows 7 SP1 x64. Hope this could help improving your component ;)
The text was updated successfully, but these errors were encountered: