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
I've noticed that, once I close FFXIV, or the launcher itself, Steam still reports that I have the game running, even when there's no processes with xiv in their name/args. Steam also cannot force stop this phantom instance of FFXIV through the library page, and the only solution I have found for this is to close Steam and reopen it. Playing other games on Steam does not fix this.
Steps to reproduce
Open Steam and log into Steam Friends
Open XIVLauncher (externally or through Steam, doesn't matter)
Close XIVLauncher
System information
OS: Debian 12 x86_64, reported as Unix 6.1.0.21
Steam: dpkg version 1:1.0.0.75+ds-6
XIVLauncher: flatpak dev.goats.xivlauncher version 1.0.8 from Flathub, self reported as 1.0.8.0 (072480e)
Runtime: reported as 6.0.28
Flatpak: dpkg version 1.14.4-1+deb12u1, self reported as 1.14.4
The text was updated successfully, but these errors were encountered:
We're tracking this issue at #97 as that was our previous work-around to this problem. As your flatpak is an older version you can use the workaround in the FaQ @NotNite linked - gonna close this to not split the conversation
I've noticed that, once I close FFXIV, or the launcher itself, Steam still reports that I have the game running, even when there's no processes with
xiv
in their name/args. Steam also cannot force stop this phantom instance of FFXIV through the library page, and the only solution I have found for this is to close Steam and reopen it. Playing other games on Steam does not fix this.Steps to reproduce
System information
OS: Debian 12 x86_64, reported as
Unix 6.1.0.21
Steam: dpkg version
1:1.0.0.75+ds-6
XIVLauncher: flatpak
dev.goats.xivlauncher
version1.0.8
from Flathub, self reported as1.0.8.0 (072480e)
Runtime: reported as
6.0.28
Flatpak: dpkg version
1.14.4-1+deb12u1
, self reported as1.14.4
The text was updated successfully, but these errors were encountered: