Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Steam still logs FFXIV as active even after closing the launcher or the game #153

Closed
hibiii opened this issue May 29, 2024 · 2 comments
Closed

Comments

@hibiii
Copy link

hibiii commented May 29, 2024

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

  1. Open Steam and log into Steam Friends
  2. Open XIVLauncher (externally or through Steam, doesn't matter)
  3. 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

@NotNite
Copy link
Contributor

NotNite commented May 29, 2024

Steam is unable to detect the process as closing due to (Flatpak shenanigans). We have a workaround with this for older Flatpak versions by setting the parent PID: https://goatcorp.github.io/faq/steamdeck#q-final-fantasy-xiv-doesnt-close-properly--steam-constantly-thinks-final-fantasy-xiv-is-playing

@Blooym
Copy link
Contributor

Blooym commented May 29, 2024

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

@Blooym Blooym closed this as not planned Won't fix, can't repro, duplicate, stale May 29, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants