Bonjour,
I have some sound problems on my f40:
1- sound works with some applications like audacious or vlc or kaffeine but it does not work from sources via firefox or chromium
2- I have an usb camera with a mic and this mic is not detected by skype for instance...
All this was working "before" (sound-web, mic) what stupidity could I have done? And how can I correct this?
Thank you.
On Tue, 2025-01-28 at 12:18 +0100, François Patte wrote:
I have some sound problems on my f40:
1- sound works with some applications like audacious or vlc or kaffeine but it does not work from sources via firefox or chromium
2- I have an usb camera with a mic and this mic is not detected by skype for instance...
All this was working "before" (sound-web, mic) what stupidity could I have done? And how can I correct this?
Obvious question: Have you rebooted?
If you've done some updates and not rebooted, that can lead to things like that. (Other updates don't require it, that's why some people don't notice problems after some updates.)
Are the apps that still have sound ones where you have configured them for a specific sound device output, rather than left them just using a system default?
If you have multiple devices that could be a sound output, it's possible the wrong one is selected.
Skype is a bit of law unto itself regarding sound, and can require fiddling with the program from time to time. Especially if there's more than one choice for sound devices.
On one of my systems there is the internal sound card, that's unused. And a HDMI monitor which has audio, and that's where my speakers are connected. There is a tiny bit of smarts, somewhere, that can detect when things are plugged in (to either), and it usually gets it right. Though is likely to get it wrong if my monitor isn't working when I logged in.
Another system has the internal sound card (again unused), a HDMI monitor with internal speaker (which is my usual sound output), and an outboard USB audio device which I don't use unless I'm editing or listening to music. When I switch that on, I usually have to manually configure the sound system to use it instead of my monitor. Rarely is it picked by default, even if I have been using it earlier on and left it switched on.
Le 2025-01-29 00:46, Tim via users a écrit :
On Tue, 2025-01-28 at 12:18 +0100, François Patte wrote:
I have some sound problems on my f40:
1- sound works with some applications like audacious or vlc or kaffeine but it does not work from sources via firefox or chromium
2- I have an usb camera with a mic and this mic is not detected by skype for instance...
All this was working "before" (sound-web, mic) what stupidity could I have done? And how can I correct this?
Thank you for your answer.
Obvious question: Have you rebooted?
If you've done some updates and not rebooted, that can lead to things like that. (Other updates don't require it, that's why some people don't notice problems after some updates.)
Of course I rebooted! When I cannot find a solution to a problem, I always reboot with the secret hope that things will go better afterwards...
Sound is (for me) mysterious under linux: so many settings whose meaning is not always clear.
My problem seems to be solved and it is a mystery why! I came accross someone's post who had the same problem as mine and an answer suggested to check this:
systemctl --user status pipewire-pulseaudio pipewire wireplumber
I did it and I got :
Unit pipewire-pulseaudio.service could not be found
(the two others were enabled and running)
So I tried to install pipewire-pulseaudio but dnf answered that pipewire-pulseaudio conflicted with pulseaudio. Since I had nothing to lose I added --allowerasing and pipewire-pulseaudio was installed and... the problem was solved. Hurray!
But the mystery remains because:
systemctl --user status pipewire-pulseaudio
still returns: "Unit pipewire-pulseaudio.service could not be found"
But it is installed:
rpm -qa | grep pulseaudio returns:
alsa-plugins-pulseaudio-1.2.12-1.fc40.x86_64 vlc-plugin-pulseaudio-3.0.21-15.fc40.x86_64 xfce4-pulseaudio-plugin-0.4.9-1.fc40.x86_64 pulseaudio-libs-16.1-8.fc40.x86_64 pulseaudio-libs-glib2-16.1-8.fc40.x86_64 pulseaudio-utils-16.1-8.fc40.x86_64 pipewire-pulseaudio-1.0.9-1.fc40.x86_64 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Who can understand this!
Anyway thank you! I'm keeping my fingers crossed that the problem doesn't return...
On 30 Jan 2025, at 10:19, François Patte francois.patte@mi.parisdescartes.fr wrote:
Who can understand this!
The service name is wrong.
Here are the pipewire services I see running.
pipewire-pulse.service loaded active running PipeWire PulseAudio pipewire.service loaded active running PipeWire Multimedia Service pipewire-pulse.socket loaded active running PipeWire PulseAudio pipewire.socket
Barry
On Thu, 2025-01-30 at 11:18 +0100, François Patte wrote:
So I tried to install pipewire-pulseaudio but dnf answered that pipewire-pulseaudio conflicted with pulseaudio. Since I had nothing to lose I added --allowerasing and pipewire-pulseaudio was installed and... the problem was solved. Hurray!
Pulseaudio was a (slightly) older audio system, pipewire being its replacement. And there's a pipewire-pulseaudio go-between that can pretend it's pulseaudio for apps that won't work unless they believe they're using pulseaudio.
So, you go the old way and at some stage it'll get abandoned, or you go the new way and find something that they haven't got ready yet.
Your install with allowing erasing would appear to have removed pulseaudio for the pipewire system, instead (since it complained about it not being compatible with pulseaudio). Which would be what I'd have expected you to have in the first place on Fedora 40.
On my Fedora 40 installation I have:
rpm -qa *pipewire*|sort
pipewire-1.0.9-1.fc40.x86_64 pipewire-alsa-1.0.9-1.fc40.x86_64 pipewire-gstreamer-1.0.9-1.fc40.x86_64 pipewire-jack-audio-connection-kit-1.0.9-1.fc40.x86_64 pipewire-jack-audio-connection-kit-libs-1.0.9-1.fc40.x86_64 pipewire-libs-1.0.9-1.fc40.x86_64 pipewire-pulseaudio-1.0.9-1.fc40.x86_64 pipewire-utils-1.0.9-1.fc40.x86_64 vlc-plugin-pipewire-3-2.fc40.x86_64
rpm -qa *pulseaudio*|sort
pipewire-pulseaudio-1.0.9-1.fc40.x86_64 pulseaudio-libs-16.1-8.fc40.x86_64 pulseaudio-libs-glib2-16.1-8.fc40.x86_64 pulseaudio-utils-16.1-8.fc40.x86_64 vlc-plugin-pulseaudio-3.0.21-15.fc40.x86_64
And if I do a
rpm -ql pipewire-pulseaudio
to see what files it contains, I can see that the pipewire-pulseaudio service is called:
pipewire-pulse.service
Just to confuse you.
Then, if I do:
systemctl --user status pipewire-pulse pipewire wireplumber
I get:
● pipewire-pulse.service - PipeWire PulseAudio Loaded: loaded (/usr/lib/systemd/user/pipewire-pulse.service; disabled; preset: disabled) Drop-In: /usr/lib/systemd/user/service.d └─10-timeout-abort.conf Active: active (running) since Thu 2025-01-30 09:31:12 ACDT; 22h ago TriggeredBy: ● pipewire-pulse.socket Main PID: 2007 (pipewire-pulse) Tasks: 3 (limit: 18552) Memory: 2.5M (peak: 3.0M) CPU: 26ms CGroup: /user.slice/user-1000.slice/user@1000.service/session.slice/pipewire-pulse.service └─2007 /usr/bin/pipewire-pulse
Jan 30 09:31:12 fluffy systemd[1611]: Started pipewire-pulse.service - PipeWire PulseAudio.
● pipewire.service - PipeWire Multimedia Service Loaded: loaded (/usr/lib/systemd/user/pipewire.service; disabled; preset: disabled) Drop-In: /usr/lib/systemd/user/service.d └─10-timeout-abort.conf Active: active (running) since Thu 2025-01-30 09:31:12 ACDT; 22h ago TriggeredBy: ● pipewire.socket Main PID: 1987 (pipewire) Tasks: 3 (limit: 18552) Memory: 6.6M (peak: 7.1M) CPU: 51ms CGroup: /user.slice/user-1000.slice/user@1000.service/session.slice/pipewire.service └─1987 /usr/bin/pipewire
Jan 30 09:31:12 fluffy systemd[1611]: Started pipewire.service - PipeWire Multimedia Service.
● wireplumber.service - Multimedia Service Session Manager Loaded: loaded (/usr/lib/systemd/user/wireplumber.service; enabled; preset: enabled) Drop-In: /usr/lib/systemd/user/service.d └─10-timeout-abort.conf Active: active (running) since Thu 2025-01-30 09:31:12 ACDT; 22h ago Main PID: 2000 (wireplumber) Tasks: 6 (limit: 18552) Memory: 10.2M (peak: 10.6M) CPU: 300ms CGroup: /user.slice/user-1000.slice/user@1000.service/session.slice/wireplumber.service └─2000 /usr/bin/wireplumber
Jan 30 09:31:12 fluffy systemd[1611]: Started wireplumber.service - Multimedia Service Session Manager. Jan 30 09:31:12 fluffy wireplumber[2000]: wp-internal-comp-loader: Loading profile 'main' Jan 30 09:31:12 fluffy wireplumber[2000]: spa.bluez5: BlueZ system service is not available Jan 30 09:31:12 fluffy wireplumber[2000]: wp-device: SPA handle 'api.libcamera.enum.manager' could not be loaded; is it installed? Jan 30 09:31:12 fluffy wireplumber[2000]: s-monitors-libcamera: PipeWire's libcamera SPA plugin is missing or broken. Some camera types may not be supported. Jan 30 09:34:26 fluffy wireplumber[2000]: m-dbus-connection: WpDBusConnection:0x559b445b03e0 DBus connection closed: Underlying GIOStream returned 0 bytes on an async read Jan 30 09:34:26 fluffy wireplumber[2000]: m-dbus-connection: WpDBusConnection:0x559b445b03e0 Trying to reconnect after core sync Jan 31 08:19:14 fluffy wireplumber[2000]: spa.bluez5: BlueZ system service is not available
There's some warnings logged there about unimportant things (I have no bluetooth hardware on that PC, etc).
This system is using pipewire, with the support for things that expect to use pulseaudio. And it works reasonably well, though I don't do a great deal of audio work on it.
My take on the first two services being "disabled" but "active" is that they aren't something that's running all the time since boot-up, but are run on-demand.
Le 2025-01-30 23:20, Tim via users a écrit :
On Thu, 2025-01-30 at 11:18 +0100, François Patte wrote:
So I tried to install pipewire-pulseaudio but dnf answered that pipewire-pulseaudio conflicted with pulseaudio. Since I had nothing to lose I added --allowerasing and pipewire-pulseaudio was installed and... the problem was solved. Hurray!
Pulseaudio was a (slightly) older audio system, pipewire being its replacement. And there's a pipewire-pulseaudio go-between that can pretend it's pulseaudio for apps that won't work unless they believe they're using pulseaudio.
<couic>
Hi,
Since I solved this problem, rkhunter bores me with "Suspicious file types found in /dev:"
/dev/shm/lttng-ust-wait-8
If I ask lsof to see what uses this "suspicious" file, I get : COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME wireplumb 2505 fp mem REG 0,24 4096 2 /dev/shm/lttng-ust-wait-8
Is it a really "suspicious" file? And, if not, why rkhunter is not aware of these kinds of files?
Shall I whitelist it without any danger?
Thank you.
On Sun, 2025-02-09 at 10:52 +0100, François Patte wrote:
Since I solved this problem, rkhunter bores me with "Suspicious file types found in /dev:"
/dev/shm/lttng-ust-wait-8
If I ask lsof to see what uses this "suspicious" file, I get : COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME wireplumb 2505 fp mem REG 0,24 4096 2 /dev/shm/lttng-ust-wait-8
Is it a really "suspicious" file? And, if not, why rkhunter is not aware of these kinds of files?
Shall I whitelist it without any danger?
You might want to change the subject line, some people don't read every message posted and someone with the answer to a rkhunter query may not see your message.
I see *old* data about them:
https://www.linuxquestions.org/questions/linux-security-4/suspicious-rkhunte...
https://unix.stackexchange.com/questions/227184/what-is-dev-shm-lttng-ust-wa...
As a general answer, those (rkhunter) kind of programs are always after-the-fact. Any time there's a change in how a system works, or a new exploit in the wild, they don't know about it until they're updated. And some things, like transient files, mightn't be possible to categorically declare them to always be safe, or risky.
In a case like this, I don't necessarily mean a "dnf update" to your install. But probably that the program itself needs a change in how it works. There's every chance that you might have to ask the question directly with rkhunter's support. And they could easily turn around and say it's a unique quirk of Fedora, and they should manage the problem.
That's one problem with using protective software like them (rkhunter, ABRT, SELinux troubleshooter, anti-virus, etc). You have to know how to deal with its results to actually be able to use it. When people don't, they go around deleting files they shouldn't, allowing things they shouldn't, or just ignoring all the things they warn about.
-
Barry -
François Patte -
Tim