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

No sound in debian buster (10) #3532

Closed
subproc opened this Issue Feb 4, 2018 · 3 comments

Comments

Projects
None yet
3 participants
@subproc

subproc commented Feb 4, 2018

Qubes OS version:

R4.0

Affected TemplateVMs:

debian 10 (buster)


Steps to reproduce the behavior:

upgrade a debian 9 template to debian 10

Expected behavior:

working sound

Actual behavior:

there's no sound

General notes:

i've switched to buster-testing repo in qubesR4.0 source list but with no luck

Related issues:

it seems the pulseaudio issues like it there was in past template update, but using

user@debian-9:~$ sudo bash
root@debian-9:/home/user# cd /usr/lib/pulse-11.1/modules
root@debian-9:/usr/lib/pulse-11.1/modules# ln -s ../../pulse-10.0/modules/module-vchan-sink.so .

doesn't do the trick

it needs something like in #3454

@marmarek

This comment has been minimized.

Show comment
Hide comment
@marmarek

marmarek Feb 14, 2018

Member

Try updating again, there should be updated package.

Member

marmarek commented Feb 14, 2018

Try updating again, there should be updated package.

@subproc

This comment has been minimized.

Show comment
Hide comment
@subproc

subproc Feb 17, 2018

thanks, tracking stable repo there's still no audio, but with testing repo it's working

subproc commented Feb 17, 2018

thanks, tracking stable repo there's still no audio, but with testing repo it's working

@andrewdavidwong

This comment has been minimized.

Show comment
Hide comment
@andrewdavidwong

andrewdavidwong Feb 18, 2018

Member

Closing this as "resolved." If you believe the issue is not yet resolved, or if anyone is still affected by this issue, please leave a comment, and we'll be happy to reopen this. Thank you.

Member

andrewdavidwong commented Feb 18, 2018

Closing this as "resolved." If you believe the issue is not yet resolved, or if anyone is still affected by this issue, please leave a comment, and we'll be happy to reopen this. Thank you.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment