You are not logged in.

#1 2024-02-15 19:32:19

ymi
Member
Registered: 2024-02-15
Posts: 2

[SOLVED] playerctl stopped working

Playerctl reports no players found. It was previously working fine. I tried the debugging/troubleshooting steps mentioned on official doc.

I start my Sway session with .bash_profile and use dbus-run-session to start it.

exec dbus-run-session sway --unsupported-gpu > $HOME/.local/state/sway/stdout 2> $HOME/.local/state/sway/stderr

Neither Firefox (youtube video) nor Spotify playback info is visible via playerctl. (using official packages for firefox and spotify-wayland from aur for spotify)

How do i fix it?

Last edited by ymi (2024-02-16 03:54:54)

Offline

#2 2024-02-15 19:59:49

V1del
Forum Moderator
Registered: 2012-10-16
Posts: 21,923

Re: [SOLVED] playerctl stopped working

Don't use dbus-run-session that will logically and expectedly break things. What you should be doing is wrapping sway in a script and run https://github.com/altdesktop/playerctl … art-issues beforehand.

Last edited by V1del (2024-02-15 20:01:12)

Offline

#3 2024-02-16 03:10:06

ymi
Member
Registered: 2024-02-15
Posts: 2

Re: [SOLVED] playerctl stopped working

Thanks V1del, removing dbus-run-session part from my bash profile worked.

My confusion came from wiki mentioning to start with dbus-run-session,

For screen sharing to work properly, you might also need to start Sway using dbus-run-session sway

Probably it applies for users using seatd and not systemd-login based start up.

On another note, how do i mark this thread solved?

Offline

#4 2024-02-16 03:16:26

bybrl
Member
Registered: 2024-02-12
Posts: 9

Re: [SOLVED] playerctl stopped working

Add [solved] to the title.

Offline

Board footer

Powered by FluxBB