[GH-ISSUE #779] playerctl volume controls not working correctly #1399

New issue

Open

opened 2026-03-14 14:39:39 +03:00 by kerem · 1 comment

kerem commented

2026-03-14 14:39:39 +03:00

Owner

Originally created by @the-n3kk on GitHub (Jul 20, 2025).
Original GitHub issue: https://github.com/aome510/spotify-player/issues/779

Describe the bug
playerctl volume control doesn't seem to work correctly.
When attempting to increase player volume it doesn't do anything.
Decreasing volume instead sets the volume to 100% - offset value instead of decreasing it by the offset.
Getting current volume always returns 1.0 instead of current volume.
Setting volume to specific value is the only one that seems to be working correctly.
There's no error's / warnings returned from playerctl.

To Reproduce
playerctl --player spotify_player volume 0.1+
nothing happens

playerctl --player spotify_player volume 0.1-
volume is set to 90% (it seems to always set it to 100% - offset)

playerctl --player spotify_player volume
returns 1.0000 instead of actual volume

Expected behaviour
playerctl --player spotify_player volume 0.1+
sets the volume to current volume + 10%

playerctl --player spotify_player volume 0.1-
sets the volume to current volume - 10%

playerctl --player spotify_player volume
returns current volume as a float (0.0-1.0)

Log and backtrace
Backtrace is empty after running commands above. Normal log likewise does not log any events when running those commands.

Screenshots
Probably N/A

Environment

OS: Arch
Application version:$ spotify_player 0.20.6
Application features: default of installing from AUR (according to readme here it's all the features)

Additional context
Not sure what else is there to mention. The playerctl seems to overall be functional in terms of being able to communicate with the app as you can set the value directly, it's just the offsets and getting value that's the issue. If I were to guess the main issue is the volume reporting given the behavior when lowering the volume.
I wanted to map my keyboards media buttons to explicitly control this app, which is where I noticed this issue.

Originally created by @the-n3kk on GitHub (Jul 20, 2025). Original GitHub issue: https://github.com/aome510/spotify-player/issues/779 **Describe the bug** playerctl volume control doesn't seem to work correctly. When attempting to increase player volume it doesn't do anything. Decreasing volume instead sets the volume to 100% - offset value instead of decreasing it by the offset. Getting current volume always returns 1.0 instead of current volume. Setting volume to specific value is the only one that seems to be working correctly. There's no error's / warnings returned from playerctl. **To Reproduce** playerctl --player spotify_player volume 0.1+ nothing happens playerctl --player spotify_player volume 0.1- volume is set to 90% (it seems to always set it to 100% - offset) playerctl --player spotify_player volume returns 1.0000 instead of actual volume **Expected behaviour** playerctl --player spotify_player volume 0.1+ sets the volume to current volume + 10% playerctl --player spotify_player volume 0.1- sets the volume to current volume - 10% playerctl --player spotify_player volume returns current volume as a float (0.0-1.0) **Log and backtrace** Backtrace is empty after running commands above. Normal log likewise does not log any events when running those commands. **Screenshots** Probably N/A **Environment** - OS: Arch - Application version:$ spotify_player 0.20.6 - Application features: default of installing from AUR (according to readme here it's all the features) **Additional context** Not sure what else is there to mention. The playerctl seems to overall be functional in terms of being able to communicate with the app as you can set the value directly, it's just the offsets and getting value that's the issue. If I were to guess the main issue is the volume reporting given the behavior when lowering the volume. I wanted to map my keyboards media buttons to explicitly control this app, which is where I noticed this issue.

kerem added the

bug

label

2026-03-14 14:39:39 +03:00

kerem commented

2026-03-14 14:39:50 +03:00

Author

Owner

@Dragonfly911117 commented on GitHub (Sep 29, 2025):

I've run into the same problem on Garuda Linux (6.16.9-1-cachyos) while trying to control media volume from waybar.

Interestingly, it’s not just spotify_player. I also see the same behavior with my browser — for example:

playerctl -p vivaldi.instance114514 volume

always returns 1.0000, even if I explicitly set it. That makes me suspect it’s more of a playerctl issue than a spotify_player one. I found this related issue: https://github.com/altdesktop/playerctl/issues/319).

As a workaround, I’ve switched to:

spotify_player playback volume [--offset] -- <volume>

Maybe this workaround can also help in your case.

@Dragonfly911117 commented on GitHub (Sep 29, 2025): I've run into the same problem on Garuda Linux (6.16.9-1-cachyos) while trying to control media volume from waybar. Interestingly, it’s not just `spotify_player`. I also see the same behavior with my browser — for example: ```zsh playerctl -p vivaldi.instance114514 volume ``` always returns `1.0000`, even if I explicitly set it. That makes me suspect it’s more of a `playerctl` issue than a `spotify_player` one. I found this related issue: [https://github.com/altdesktop/playerctl/issues/319)](https://github.com/altdesktop/playerctl/issues/319). As a workaround, I’ve switched to: ```zsh spotify_player playback volume [--offset] -- <volume> ``` Maybe this workaround can also help in your case.