Arch Linux

jakedane

Member

Registered: 2024-04-21

Posts: 3

[SOLVED] Totem no audio since Pipewire 1.2.7

I'm using Gnome Shell 47.2 with Wayland session. Pipewire for audio.

Since upgrading from Pipewire 1.2.6 to 1.2.7 videos in Totem have no audio. Rebooting the system didn't help, nor did recompiling Totem. Videos plays fine in Showtime and VLC.

Any ideas how to diagnose what the problem is with Totem & Pipewire 1.2.7?

edit: turns out the app was muted

Last edited by jakedane (2024-11-28 20:22:34)

V1del

Forum Moderator

Registered: 2012-10-16

Posts: 23,319

Re: [SOLVED] Totem no audio since Pipewire 1.2.7

Totem is going to use gst(-plugin-pipewire) can you "fix" this by uninstalling gst-plugin-pipewire (or is that a hard dep on gnome?)

Other than that launch it in a terminal, post the output.

Last edited by V1del (2024-11-28 14:39:10)

jakedane

Member

Registered: 2024-04-21

Posts: 3

Re: [SOLVED] Totem no audio since Pipewire 1.2.7

Removing gst-plugin-pipewire isn't an option, it's required by other apps on my system (Authenticator, Contacts, Kooha and Snapshot).

Starting totem from a terminal, there is no output. Not until I close it then it shows a "Grilo-CRITICAL: grl_log_valist: assertion 'domain' failed" error.

V1del

Forum Moderator

Registered: 2012-10-16

Posts: 23,319

Re: [SOLVED] Totem no audio since Pipewire 1.2.7

This isn't permanent, it's a suggestion to verify the culprit/correlation.

FWIW on a googler there's apparently an environment to force a certain plugin selection, so try a

GST_DEBUG=*:6 GST_PLUGIN_FEATURE_RANK=pulsesink:MAX totem

Also to bypass the obvious, you double and triple checked totem isn't muted? outputs of

pactl list sinks
pactl list sink-inputs

during attempted playback

Last edited by V1del (2024-11-28 20:10:06)

jakedane

Member

Registered: 2024-04-21

Posts: 3

Re: [SOLVED] Totem no audio since Pipewire 1.2.7

Thank you for the pactl hint! Turns out the app was muted and it's working now.

I don't know what I did between yesterday when it was working and today when it was not, but I jumped to blaming an update