flathub / flathub/com.spotify.Client

Spotify flatpak doesn't remember last window location/open new windows as centered ignored

Open
#154 31 comments 2 reactions 0 assignees View on GitHub
Dominant language
Python
Stars
113
Forks
41
PR merge metrics
No merged PRs in 30d

Description

Greetings,

First off thank y'all for making this flatpak, it definitely comes in handy many times a day as a music lover, can't appreciate your efforts enough. I've used both .deb and flatpak versions of Spotify in the past, currently using the flatpak version of Spotify. I use GNOME, and have a setting enabled via Gnome Tweaks Tool "center new windows" which for the most part all applications obey and center windows opened in the center of the desktop. I know previous versions of the .deb and flatpak version of Spotify have obeyed this rule, but with one of the recent new versions, Spotify does not open in the center anymore, it always opens in the center, but at a lower angle than what I previously had it as. I'm wondering if this issue can be address or fixed since it appeared to be something that worked before to open Spotify in the center of the desktop or perhaps y'all can set a rule to have the window open in the same spot from it's last time used or like restore last known window position on restart if that makes more sense I hope?

One issue I have noticed also is if I open Spotify, it'll open in the center but shifted down and every time I close it and reopen it, the application will shift down even more. If I open and close it about 2-3 times the window ends up continually shifting to going to the bottom border of my screen, without me having moved the window at all, which makes it very inconsistent and I constantly have to re-drag it up to where I'd like it placed. I do hope this can be address in an update.

This would be very much appreciated as since every time I open Spotify, I have to drag it up since it doesn't align to the center like all my other windows do. Any help would be great and thanks for hearing this out!

Using the latest Spotify flatpak version 1.1.55.498.gf9a83c60 on PopOS 20.04 on GNOME 3.36 with a fully up to date system and currently flatpak version 1.8.5

Below is a few screenshots to show any relevant settings that may help
Gnome Tweaks tool with new windows open in center selected
![Screenshot from 2021-04-14 01-34-37](https://user-images.githubusercontent.com/45135187/114665546-cd7c5c80-9cc2-11eb-9a94-aad7ad96f721.png)
System info showing laptop model and kernel version
![Screenshot from 2021-04-14 01-34-56](https://user-images.githubusercontent.com/45135187/114665568-d2d9a700-9cc2-11eb-8fd5-268969879299.png)
Currently on PopOS with GNOME 3.36.8
![Screenshot from 2021-04-14 01-35-22](https://user-images.githubusercontent.com/45135187/114665587-d705c480-9cc2-11eb-8872-01bd1dd5f812.png)
Spotify opening in the center after I've placed it that way. It won't remember this position upon a restart sadly.
![Screenshot from 2021-04-14 01-41-49](https://user-images.githubusercontent.com/45135187/114666218-9b1f2f00-9cc3-11eb-9384-8c8d8a1e988a.png)
After opening Spotify twice, this is where the window ends up moving to.
![Screenshot from 2021-04-14 01-42-31](https://user-images.githubusercontent.com/45135187/114666239-a07c7980-9cc3-11eb-8198-978ff995b7e3.png)

Contributor guide

No contributing guide indexed for this repository

Research direction

Reproduce the window-position drift on Pop!_OS 20.04 with GNOME 3.36, the Spotify Flatpak 1.1.55.498.gf9a83c60, and Flatpak 1.8.5, using GNOME Tweaks' centered-new-windows setting. Compare repeated launches and restarts to determine whether the behavior belongs to Spotify or the Flatpak environment; done means the window stays centered or restores its last position without drifting.

Written by the indexing model from the issue text.

Assessment

Tech stack
linux
Domain
desktop
Issue type
Bug
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.