Flatpak app doesn't launch - CEF cache held by running process

[theMimolet]

Describe the bug

I wanted to launch Sable
But it didn't launch
So I tried to launching Sable with flatpak run and it printed this error :

failed to build tauri application: Err(Runtime(CreateWebview("CEF cache /var/home/samuel/.var/app/moe.sable.client/cache/moe.sable.client/cef is held by running process 2 (SingletonLock); close that instance or configure a distinct cache_path/identifier")))

Reproduction

1. You open Sable
2. It actually doesn't open
   (I don't actually know why this is happening)

Expected behavior

Sable launches

Platform and versions

1. OS : Linux (Bluefin F44.20260825) with GNOME
2. Browser : Flatpak app
3. Sable Version : 1.21.0

Additional context

No response

[Kooper16]

I had this happens too. Deleting the lock file fixed it for me for now.
rm ~/.var/app/moe.sable.client/cache/moe.sable.client/cef/SingletonLock

[Kooper16]

Small update: You have to do this every reboot. It seems like Sable doesn't release all files during the shutdown process.

[TheCourierNV]

I am also affected by this, and I can add that the only way to not trigger this bug is to close the app by using the "quit" button in the tray icon.

Any other way (AFAICT) will not clean up the lock and require the user to manually delete ~/.var/app/moe.sable.client/cache/moe.sable.client/cef/SingletonLock

[sphh]

I had the same problem. I had the following configuration active:

• Desktop>Window>Close button keeps Sable running

After disabling it, I can now close and restart Sable without deleting the lock file!