So I ran the command without sudo: flatpak update \ It turns out that I only need to run flatpak update as sudo if I had installed the application globally. I Googled around and found this issue from 2020 which described my problem exactly. This was confusing because I already knew by checking flatpak list that Spotify was in fact installed. So I ran that command: sudo flatpak update \ According to the documentation at time of writing, I downgrade an application by running: sudo flatpak update \ I went about downgrading to that version. I picked a command hash from a week ago, which was a known good version I had been using. I piped into less because the command spat out a lot of output and I only wanted to see the beginning, the most recent commits. So I ran it like this: flatpak remote-info -log flathub | less Following the flatpak docs at time of writing, it instructed me to look through the commit log with this command: flatpak remote-info -log flathub So I went about downgrading the application. Troubleshooting Downgrading SpotifyĪt first I thought that there was a regression introduced by Spotify. My Spotify was installed with Flatpak, but that’s basically transparent to the user when installing via Pop!_Shop. All of the keyboard shortcuts I tried to get it into windowed mode failed, but I could Alt-Tab to a different window. After re-launching the client, it was stuck in fullscreen. Today I updated my Spotify client via Pop!_Shop in Pop!_OS.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |