Interface won't load

[sasspaper]

Describe the bug
TUI never loads on startup, requires a seemingly random number of restarts to work. Sometimes I only need to restart once, sometimes 5-6 times before it loads correctly. Music will play normally regardless of whether the UI loaded or not.

To Reproduce
Open spotify-player via kitty (or konsole, it doesn't matter)
Interface doesn't load
Restart several times until it loads correctly

Expected behaviour
Open and display TUI normally.

Log and backtrace
spotify-player-26-06-07-18-3.tar.gz

Screenshots
https://github.com/user-attachments/assets/f2ab1fd7-748a-4d84-8bdc-4d6801db0d83

Environment

• OS: CachyOS
• Application version: v0.23.0
• Application features: cargo install spotify_player --features image

Additional context
I'm only experiencing this on Cachy (Arch based distro). Previously when I was using Nobara (Fedora based distro) the app worked perfectly fine.

[nitayderei]

Edit: Just was lucky a few times after changing this config. Still has the problem...

I have the same issue. foot terminal, openSUSE Tumbleweed, v0.23.0 with image/sixel features.
Music plays fine but no TUI, just a blank screen. Setting cover image to 0 in app.toml fixes it:

cover_img_length = 0
cover_img_width = 0
cover_img_scale = 0.0

[feskslo]

Same exact issue. Spotify_player opens and is blank, non-responsive. Audio playback starts, though. Have to kill the terminal to exit.

Rebuilding and deleting the ~/.cache/spotify-player folder allows the program to function on the first run. No cache -> authenticate on startup -> it works. Close it down, restart spotify_player -> blank screen, terminal hang.

Tested on Fedora 43 with kitty terminal v.0.43.1 and Terminal (ptyxis 49.3), same behaviour.

Logs from hanged session show no errors or warnings out of the ordinary.

On my end, rebuilding spotify_player does not alleviate the problem without also deleting the cache. Tested with standard build features (no image, which has caused issues for me on a previous version).

Tried disabling audio_cache and enable_cover_image_cache as well as enable_audio_visualization, no apparent difference.