Re: No sound after update

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Tue, 20 Sep 2022 11:00:13 +0200
andreas.fournier@xxxxxxxxxx wrote:

> On Tue, 2022-09-20 at 10:38 +0200, fedora wrote:
> > Don't you need to start pipewire as the normal user? i.e.
> > 
> > [host@non-root-user]$ systemctl restart pipewire-pulse.service
> > --user  
> 
> ah, right. When run as a normal user that command succeeds and in the
> log I can find
> 
> systemd[2290]: Stopping pipewire-pulse.service - PipeWire
> PulseAudio... systemd[2290]: Stopped pipewire-pulse.service -
> PipeWire PulseAudio. systemd[2290]: Started pipewire-pulse.service -
> PipeWire PulseAudio. rtkit-daemon[1231]: Successfully made thread
> 62005 of process 62005 (/usr/bin/pipewire-pulse) owned by '1000' high
> priority at nice level - 11.rtkit-daemon[1231]: Successfully made
> thread 62014 of process 62005 (/usr/bin/pipewire-pulse) owned by
> '1000' RT at priority 20. juno pipewire-pulse[62013]: 536870912
> 
> But still no audio.
> 
> Also tried 'aplay -D plughw:2,0 <audio file>'. No audio was produced.

This should have worked, if you have a speaker connected to the out
port on the on board sound device (the green one).  Headphones will
also work.  To pursue this further, start pavucontrol-pulseaudio, go to
the third tab, output devices, and run the above command again. Do
you see sound being sent to the device?  Do you hear it?  If you do,
your sound is working, but you have a configuration issue

If you don't, go to the last tab of pavucontrol-pulseaudio, and turn off
the built in audio.  Run the above command again.  Is there sound?
Yes?  The problem is in pipewire.  No, maybe the volume isn't high
enough.  Run
alsamixer -c 2
and raise the volume on the first bars until they are just in the
red.  Then, run the above command again.  Is there sound?  Yes?  Sound
is working but somehow the volumes were too low.  No?  I'm out of
ideas.  Given the data you showed, the built in audio should be
producing sound if everything is configured properly (as I've
described).

You can set up and try a new user, but be sure that you have logged out
your current user before you try with the new user.  The first user to
log in gains total control over pipewire / pulseaudio unless it is
being run as a server, which is not the default.
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue



[Index of Archives]     [Older Fedora Users]     [Fedora Announce]     [Fedora Package Announce]     [EPEL Announce]     [EPEL Devel]     [Fedora Magazine]     [Fedora Summer Coding]     [Fedora Laptop]     [Fedora Cloud]     [Fedora Advisory Board]     [Fedora Education]     [Fedora Security]     [Fedora Scitech]     [Fedora Robotics]     [Fedora Infrastructure]     [Fedora Websites]     [Anaconda Devel]     [Fedora Devel Java]     [Fedora Desktop]     [Fedora Fonts]     [Fedora Marketing]     [Fedora Management Tools]     [Fedora Mentors]     [Fedora Package Review]     [Fedora R Devel]     [Fedora PHP Devel]     [Kickstart]     [Fedora Music]     [Fedora Packaging]     [Fedora SELinux]     [Fedora Legal]     [Fedora Kernel]     [Fedora OCaml]     [Coolkey]     [Virtualization Tools]     [ET Management Tools]     [Yum Users]     [Yosemite News]     [Gnome Users]     [KDE Users]     [Fedora Art]     [Fedora Docs]     [Fedora Sparc]     [Libvirt Users]     [Fedora ARM]

  Powered by Linux