-
Notifications
You must be signed in to change notification settings - Fork 2.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Spotify + MPRIS not working #25587
Comments
Further information from running
Center of attention is the last line; this |
Is your window manager started with |
I have
|
Side note: I really want to commend you @ericonr for your response time with these issues :) You're incredibly responsive and cooperative and it's so awesome to see you active on every issue I post here. Let me know if there's a way to tip you or something. You deserve it. Cheers! |
I had issues like this for a while on void linux. I've found that if you're using elogind, you do not want it started as a system service. Rather, you'll want to install elogind-dbus replacing the traditional dbus package. After that's installed, when dbus starts as a system service, it will start elogind automatically without needing a service. Check htop or a similar program to make sure elogind is actually running too. Read more here in the Void Documentation. Hope this helps! |
@ohlookitsaaron It doesn't seem like that worked for me :( |
This seems to be an issue with how dbus is set up with my AwesomeWM setup. Spotify works correctly with Plasma. I noticed that Spotify wasn't showing notifications when playing a new song with AwesomeWM AND Slack wasn't showing notifications for new messages. But all of these work with Plasma. Finna close this issue and I'll figure out how to get dbus working with awesomewm. I expected it to work just by running awesome from SDDM but I guess it doesn't lol |
Looking at the xsession file for awesomewm, I'm wondering if we should change
Just comparing awesome.desktop with plasma.desktop |
You can't do this unless you make awesomewm depend on I believe systemd distros deal with this by having systemd handle thinigs, but this doesn't happen here. |
Well, turns out it does depend, so it can probably be changed. Idk if this would break how other people are doing their dbus setup, tho. |
So that ended up working? Didn't realize using pulse required one to start their WM with dbus. |
System
Void 5.8.13_1 x86_64 AuthenticAMD uptodate rrrmFFFFFFFFFFFFFFFFF
spotify-1.1.26_2
Expected behavior
On my previous install with Arch Linux, I was able to control Spotify playback with
playerctl
. I'm using awesomewm with keybinds to control audio playback, with commands such asplayerctl play-pause
. These commands work for other MPRIS players like Firefox and MPV with the mpv-mpris plugin.Actual behavior
playerctl
doesn't work with Spotify, and playback information doesn't show up in my muse-status bar either.Steps to reproduce the behavior
Bonus issue: Currently it seems that spotify-1.1.26_1 is unable to be installed correctly/completely from the official nonfree repository:
So I am using the spotify package from my local repository.
playerctl
is installed tooplayerctl play-pause
Here's an extra little bit of information:
(Taken from this issue on the Spotify discussion forums)
The text was updated successfully, but these errors were encountered: