[GH-ISSUE #906] Not rendering properly and loss of keyboard shortcut control after window size changes #1483

New issue

Open

opened 2026-03-14 15:12:37 +03:00 by kerem · 1 comment

kerem commented

2026-03-14 15:12:37 +03:00

Owner

Originally created by @Pommersche92 on GitHub (Jan 3, 2026).
Original GitHub issue: https://github.com/aome510/spotify-player/issues/906

Describe the bug
window size changes lead to improper rendering and loss of control (no keyboard shortcuts work anymore)

To Reproduce

get latest code from git
do a "cargo install --path ./spotify_player --features sixel,fzf,notify,pixelate"
after build and install, run via "spotify_player" in terminal
authenticate if necessary
now you have it running and working flawlessly
change terminal window size
- rendering in terminal is now f'ed up
- all keyboard shortcuts no longer work (only C-c)
- song keeps playing (but no next song will play after current one ends)
- and everything else detailed below with screenshots...

Expected behaviour

ui keeps rendering correctly and adapts to window size changes
keyboard shortcuts keep working as expected

Log and backtrace
only errors logged are at the end of the playback of the current song if the rendering issue already happened. Error is "2026-01-03T23:16:33.832493Z ERROR spotify_player::client: Encountered an error when updating the playback state: http error: request: error sending request for url (https://api.spotify.com/v1/me/player?additional_types=track%2Cepisode)". i believe this is not an actual http error, because until you resize it works flawlessly without any errors and everything works like a charm. therefore i think an error concerning the rendering occurs at the same point when the http spotify request is sent which leads to it being misclassified.

Screenshots

all is good and working correctly
opened second terminal below, now terminal content from spotify-player is no longer rendering correctly

the music keeps playing, but at this point all keyboard shortcuts including "q" to quit are inoperable. C-c still works though.
But spotify-player keyboard shortcuts stay inoperable on restart of the application (in old or new terminal) until i force-quit an open and broken spotify-player session via the Hyprland-Kill-Shortcut (Cmd+Shift+Q). This also happens in floating window mode on resize via window border drag. this does not happen with current version on crates.io (although there nothing functionally related to spotify (search, playback, look at album/artist/song details, etc. works atm)
if i close the new terminal, spotify-player stays rendered incorrectly

this also happens on workspace switching if this entails a window size change, etc. sometimes the size needs to be changed 2-3 times before rendering stops working correctly, but never more than 5 times

Environment

OS: Manjaro, Hyprland, Kernel 6.12.63-1 (refer to screenshot with new terminal to see more)
Application version: current git sources clone (as of January 4th 2026, 00:14:00 CET)
Application features: sixel,fzf,notify,pixelate (but bug also occures when its build with default features)

Additional context
Add any other context about the problem here.

Originally created by @Pommersche92 on GitHub (Jan 3, 2026). Original GitHub issue: https://github.com/aome510/spotify-player/issues/906 **Describe the bug** window size changes lead to improper rendering and loss of control (no keyboard shortcuts work anymore) **To Reproduce** - get latest code from git - do a "cargo install --path ./spotify_player --features sixel,fzf,notify,pixelate" - after build and install, run via "spotify_player" in terminal - authenticate if necessary - now you have it running and working flawlessly - change terminal window size - rendering in terminal is now f'ed up - all keyboard shortcuts no longer work (only C-c) - song keeps playing (but no next song will play after current one ends) - and everything else detailed below with screenshots... **Expected behaviour** - ui keeps rendering correctly and adapts to window size changes - keyboard shortcuts keep working as expected **Log and backtrace** only errors logged are at the end of the playback of the current song if the rendering issue already happened. Error is "2026-01-03T23:16:33.832493Z ERROR spotify_player::client: Encountered an error when updating the playback state: http error: request: error sending request for url (https://api.spotify.com/v1/me/player?additional_types=track%2Cepisode)". i believe this is not an actual http error, because until you resize it works flawlessly without any errors and everything works like a charm. therefore i think an error concerning the rendering occurs at the same point when the http spotify request is sent which leads to it being misclassified. **Screenshots** 1) all is good and working correctly <img width="863" height="1440" alt="Image" src="https://github.com/user-attachments/assets/309024d6-6c60-45ef-a062-e037cb110c67" /> 2) opened second terminal below, now terminal content from spotify-player is no longer rendering correctly <img width="864" height="1440" alt="Image" src="https://github.com/user-attachments/assets/050b7fd4-cbb4-43bb-bed7-40742f342543" /> the music keeps playing, but at this point all keyboard shortcuts including "q" to quit are inoperable. C-c still works though. But spotify-player keyboard shortcuts stay inoperable on restart of the application (in old or new terminal) until i force-quit an open and broken spotify-player session via the Hyprland-Kill-Shortcut (Cmd+Shift+Q). This also happens in floating window mode on resize via window border drag. this does not happen with current version on crates.io (although there nothing functionally related to spotify (search, playback, look at album/artist/song details, etc. works atm) 3) if i close the new terminal, spotify-player stays rendered incorrectly <img width="863" height="1440" alt="Image" src="https://github.com/user-attachments/assets/97afe913-f0cf-4829-8add-80f084590569" /> this also happens on workspace switching if this entails a window size change, etc. sometimes the size needs to be changed 2-3 times before rendering stops working correctly, but never more than 5 times **Environment** - OS: Manjaro, Hyprland, Kernel 6.12.63-1 (refer to screenshot with new terminal to see more) - Application version: current git sources clone (as of January 4th 2026, 00:14:00 CET) - Application features: sixel,fzf,notify,pixelate (but bug also occures when its build with default features) **Additional context** Add any other context about the problem here.

kerem added the

bug

label

2026-03-14 15:12:37 +03:00

kerem commented

2026-03-14 15:12:48 +03:00

Author

Owner

@Pommersche92 commented on GitHub (Jan 3, 2026):

I am not proficient with Rust yet, otherwise i might have tried fixing it myself. If there is however anything else I can do to help, I am happy to.

P.S. when i say above that the current crates.io build does not suffer from this issue, i mean it does not on the exact same rig with same hardware / drivers / peripherals / etc.

@Pommersche92 commented on GitHub (Jan 3, 2026): I am not proficient with Rust yet, otherwise i might have tried fixing it myself. If there is however anything else I can do to help, I am happy to. P.S. when i say above that the current crates.io build does not suffer from this issue, i mean it does not on the exact same rig with same hardware / drivers / peripherals / etc.