Skip to content

[Bug]: No audio on any runner, ALSA is always selected but gives no output #3865

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

Open
raimundomartins opened this issue Apr 23, 2025 · 1 comment

Comments

@raimundomartins
Copy link

Describe the bug

No audio was being produced by apps nor winecfg in Test Sound. Audio driver kept being set to ALSA, even though PulseAudio should be preferred in my system. Setting

[HKEY_CURRENT_USER\\Software\\Wine\\Drivers]
"Audio"="pulse"

Caused no driver to be loaded. After seeing the line

F: /tmp/runtime-raimundo/.flatpak/com.usebottles.bottles/xdg-run/pulse is not a symlink to "../../flatpak/pulse" as expected: readlinkat: Invalid argument

in the healthcheck I decided to delete /tmp/runtime-raimundo/.flatpak* and close flatpak helpers. PulseAudio then started working correctly. Note that now that symlink exists, but it points to no directory, so I fail to see the point of needing it.

To Reproduce

I have no idea, this was a clean flatpak install, I was just trying out some Clean prefixes.

Package

Flatpak from Flathub

Distribution

VoidLinux (Linux 6.12.23_1)

Debugging Information

F: /tmp/runtime-raimundo/.flatpak/com.usebottles.bottles/xdg-run/pulse is not a symlink to "../../flatpak/pulse" as expected: readlinkat: Invalid argument
Official Package: true
Version: '51.21'
DE/WM: null
Display:
    X.org: true
    X.org (port): :0
    Wayland: false
Graphics:
    vendors:
        amd:
            vendor: amd
            envs:
                DRI_PRIME: '1'
            icd: /usr/lib/x86_64-linux-gnu/GL/vulkan/icd.d/radeon_icd.x86_64.json:/usr/lib/i386-linux-gnu/GL/vulkan/icd.d/radeon_icd.i686.json
    prime:
        integrated: null
        discrete: null
Kernel:
    Type: Linux
    Version: 6.12.23_1
Disk:
    Total: 100069502976
    Free: 100069343232
RAM:
    MemTotal: 186.4GiB
    MemAvailable: 158.2GiB
Bottles_envs: null

Troubleshooting Logs

Additional context

No response

@raimundomartins
Copy link
Author

I rebooted my computer and ALSA is now the selected driver again with no chance to select PulseAudio. The symlink line in the healthcheck is gone, so I can't do the same thing I did last time. This time I can select the correct output and sound comes out, but still quite inconvenient because it sometimes grabs the output and then pulseaudio doesn't detect it, even though I have ALSA to output to PulseAudio. I thought these days of audio trouble were long gone, but I guess not :(

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant