flathub / com.spotify.Client

https://flathub.org/apps/details/com.spotify.Client
68 stars 34 forks source link

Doesn't Launch: Chromium has locked the profile #286

Closed SudoVanilla closed 1 week ago

SudoVanilla commented 1 week ago

For those who are having an issue with Chromium locking the profile to prevent file corruption, you are probably getting the following output:

korbs@ship-of-theseus:~$ flatpak run com.spotify.Client
[spotifywm] attached to spotify
[spotifywm] attached to spotify
[spotifywm] attached to spotify
[7:7:0617/153036.999909:ERROR:process_singleton_posix.cc(353)] The profile appears to be in use by another Chromium process (7) on another computer (framework-13). Chromium has locked the profile so that it doesn't get corrupted. If you are sure no other processes are using this profile, you can unlock the profile and relaunch Chromium.
[7:7:0617/153036.999959:ERROR:message_box_dialog.cc(146)] Unable to show a dialog outside the UI thread message loop: Chromium - The profile appears to be in use by another Chromium process (7) on another computer (framework-13). Chromium has locked the profile so that it doesn't get corrupted. If you are sure no other processes are using this profile, you can unlock the profile and relaunch Chromium.
[7:7:0617/153037.000051:ERROR:main_runner.cc(261)] ContentMainRun failed with exit code 21

Solution

You'll need to delete a file named SingletonLock that is found in the Spotify folder for Flatpak apps. This is usually found in the .var folder in your home location. For my sake, it was at:

/home/korbs/.var/app/com.spotify.Client/cache/spotify/SingletonLock

So to delete, you would either go to the file in your file manager and then delete it, or you can run the command:

rm /home/YOUR_USERNAME/.var/app/com.spotify.Client/cache/spotify/SingletonLock

(change YOUR_USERNAME)

Why did it lock?

I'm aware of why Chromium(aka Spotify) decided to lock the profile. This can be caused if you've decided to change the hostname of your computer, also known as your computer's name. This is what I did recently and rebooted the system the next day with Spotify locking it's profile file.

As shown in the output in the top of the issue, it says "The profile appears to be in use by another Chromium process (7) on another computer (framework-13)", 'framework-13' is the previous hostname I had.

Hope this helps!