[2.0.13 Linux64] No sound ; Downgrade to 2.0.12 works fine

[Tr1cKy]

Arch Linux, Steam native, pipewire with pulseaudio compatibility.

I've confirmed that the issue persists with all mods disabled. There is no sound in the main menu, so I have gathered the logs without loading a save.

I don't see anything obvious when diffing the logs. Both logs mention pulseaudio but the only errors/warnings seem unrelated, mostly to do with the version rollback.

See attached logs for:
2.0.13 - no sound
2.0.12 - good sound

I'd be happy to do additional steps to troubleshoot the cause.

Thank you to the team for all you do.

[qweytr_1]

Maybe you should provide more informations.

For me, with Arch linux, KDE wayland ( with no sddm), for details, installed with

Code: Select all

pacman -S efibootmgr grub intel-ucode\
  plasma-wayland-session plasma-desktop plasma-nm plasma-pa pipewire-pulse dolphin kate konsole firefox rustup libreoffice-fresh-zh-cn\
  fcitx5-rime fcitx5-gtk fcitx5-qt fcitx5-configtool\
  wqy-bitmapfont wqy-microhei wqy-microhei-lite wqy-zenhei\
  bash-completion base-devel vim sudo exa fd cuda cudnn nvidia nvidia-utils

works fine.

Thus it might be some problem unrelated to pipewire-pulse and linux.


BTW you remind me, could you check whether this BUG is reproducable: viewtopic.php?f=7&t=118839

[Tr1cKy]

The issue persists on 2.0.14, though I see that the log line for audio shows more information now.

See attached log

@qweytr_1 I haven't reached Stack inserters yet - but when I get there I will add feedback to your report based on my experience there. It doesn't seem related to this report in any way so I won't mention it here again so as to keep this post on-topic.

[Donion]

Nothing changed between 2.0.12 and 2.0.13 with how we open audio so this doesn't make much sense.
Do you have multiple audio devices on your PC?

[Donion]

You can try changing the audio driver in Sound Settings from default (PulseAudio) to PipeWire. From other user's reports it seems that which works (better) is a coin toss.

[Tr1cKy]

Thank you. I'd assume it should be better option to use Pipewire natively rather than through a compatibility layer.

The issue turns out to have been related to VOLUME, of all things ...

I opened qpwgraph when I first encountered the issue to try understand what was happening - but I didn't have the volume controls open.

With 2.0.13, the audio node in Pipewire was being created with volume set to zero ; downgrading to 2.0.12 it would consistently set the audio node's volume to 100%. For 2.0.13, manually changing the driver to Pipewire and then manually adjusting the volume to 100% seems to be a good permanent fix.

However ... changing it to PulseAudio and restarting Factorio, the volume is again reset to zero.

I'm still confused about this - but at least now I have sound again.

I will continue using Pipewire - however please let me know if you would like me to do any specific troubleshooting steps. There is also a strong chance this is a unique behaviour.

[Donion]

Thank you. I'd assume it should be better option to use Pipewire natively rather than through a compatibility layer.

I'd assume the same, but then there is this 119067.

I will continue using Pipewire - however please let me know if you would like me to do any specific troubleshooting steps. There is also a strong chance this is a unique behaviour.

Yes, I would still recommend using the native driver if possible and it sounds like it's working for you.
Thank you and same for you, please, let me know if you encounter issues again.
(Edit: I'm moving this to resolved, but feel free to post back if the same issue re-appears and you're not able to figure it out)