Mic not working in Logitech Brio 4k webcam.

[RLynwood]

I'm not finished with this concern. I still need help. Claydoh or someone else, I hope you haven't dropped this issue.

[claydoh]

I can't stand Gnome.
I don't hate it, and it is good, but it doesn't fit me at all, even after giving it a go numerous times over the years.

I installed Fedora as it has current enough components to fully support my specific Chromebook's hardware, without being Arch. *Buntu 23.10 should support it, except for audio, maybe.

I also wanted to do something different so I installed the "immutable" KDE spin of Fedora Silver blue, aka Kinoite

[claydoh]

I'm not finished with this concern. I still need help. Claydoh or someone else, I hope you haven't dropped this issue.

So what is wrong? What software? Have you tested? If so, how?

The mic seems to work, just need to know what you are trying to use it with, so we can see what u may need to do to tell it to use that mic.

[RLynwood]

A number of things are wrong, which I mentioned above. First, the volume control on my speaker no longer works; I have only one volume sound. Second, when I try to re-select the default setting in Audio--System Settings, I can't. The Profile button's drop-down menu now doesn't have the full list of options it had to begin with; it has only the entry you suggested and I chose, and off. When I was using the default setting, the main speaker's volume control worked. Let's solve these before any more. And thanks for your continued help. This is really critical for one particular purpose which is only a week away. After that, I may not need this device.

Oh, and I most likely will want to discuss your view of Gnome when this problem is completely solved if that'll be ok.

[claydoh]

Show us the settings you see, again, if they are different from those in post #11
Those look completely fine, to me.

But try to force reloading things:
pulseaudio -k && sudo alsa force-reload
If that doesn't work, delete/move/rename ~/.config/pulse, then run the command again.
That will clean out any wonky configs for sound

[RLynwood]

They are different, as I described. Here is the Audio--System Settings:




Now I'll try your cl string and share the results in the next post.

[RLynwood]

Here's the result: "Failed to kill daemon: No such process" I don't understand your instruction string for this case. Do I use the entire string exactly as you wrote it: delete/move/rename .... or chose one of those & run it with the rest of the string?

I couldn't get a shot of those panels with the drop-down button down down.

[claydoh]

delete/move/rename

Quite literally to move that folder, or rename it, or delete it, using dolphin or whatever, before running the command in grey.

Here's the result: "Failed to kill daemon: No such process"

That may be OK here, I dunno.
The full output pasted here, using the "#" button to surround the highlighted text as code will be useful.

You might also try restarting pulseaudio a different way if you keep getting that 'no process' result:

systemctl --user restart pulseaudio

So remove that directory I mentioned, then try
systemctl --user restart pulseaudio

For reference, pulseaudio -k 'kills' the pulseaudio process
It is supposed to restart on its own, though the "Failed to kill daemon" may just indicate otherwise.
alsa force-reload forces the reloading of all the audio drivers
systemctl --user restart pulseaudio restarts the whole system, or some other magic that may or may not be relevant to 22.04 (it does not make my own Jammy system explode or anything)

If this is EXACTLY what you see when you ran the pulseaudio -k && sudo alsa force-reload then the systemctl command should be used.

E: [pulseaudio] main.c: Failed to kill daemon: No such process

If you still get this exact message, show us the status for pulseaudio:

systemctl --user status pulseaudio​

When you reboot next, try selecting a different kernel, just to see if things are any different. Another easy thing to check, to eliminate it as a reason for the woes.

I couldn't get a shot of those panels with the drop-down button down down.

That is always tricky. I open Spectacle, and set a long interval and use the "Select Rectangular Region", then go and do the drop-down action, and wait for the screenshot tool to open. It will freeze the screen for this process, allowing these things to be screenshot (shotted? Shooted??)


I am off to work (job 2), then bed, I can't sneak in a peek at the forums while on Job 1, so there will be long gaps in repliues from me.

Hoping I can nudge some folks with more real knowledge on this topic to chime in.....

[RLynwood]

I'm going to have to do this tomorrow.

[RLynwood]

Sorry, I didn't realize that the slashes meant 'or', that they were alternatives. Another oops; I see that my shots above are not different from those in post 11.04
I'm sorry to say that I don't understand this: "The full output pasted here, using the "#" button to surround the highlighted text as code will be useful." I did re-run that command & got the same result, but when I highlighted it, I got nothing when using the keyboard I pressed Shift-#.
Next, I renamed Pulse to Pulse-original and re-ran the command string you provided in post #20. Exact same result.
Next I ran your first command in post #23, yielding this response:
Failed to connect to bus: $DBUS_SESSION_BUS_ADDRESS and $XDG_RUNTIME_DIR not defined (consider using --machine=<user>@.host --user to connect to bus of other user)
Then I renamed pulse, per your instruction, and re-ran that command string, again yielding the exact same result (immediately above).
Next I removed pulse and re-ran that command, again with the same output.
Next I ran "alsa force-reload", alas yielding the same result.
Finally, I ran "systemctl --user restart pulseaudio" with this result:
Failed to connect to bus: $DBUS_SESSION_BUS_ADDRESS and $XDG_RUNTIME_DIR not defined (consider using --machine=<user>@.host --user to connect to bus of other user)
exactly the same as my 4th line above.

I have to take a break now, will get back to this in a few minutes.

[RLynwood]

You hadn't given the string <pulseaudio -k && sudo alsa force-reload> in your instruction beginning with "If this is EXACTLY what you see ..." so I hadn't run it.
I ran it with the exact result you gave. But I don't know where to put the systemctl in the string above it; can you show me how to use it?
In the mean time, I ran your status request:
Failed to connect to bus: $DBUS_SESSION_BUS_ADDRESS and $XDG_RUNTIME_DIR not defined (consider using --machine=<user>@.host --user to connect to bus of other user)

"Hoping I can nudge some folks with more real knowledge on this topic to chime in....." Yes, indeed. I'll try to follow your instructions for getting the shot of the Audio--System Settings and see what happens.

[RLynwood]

Anyone else who can chime in and help here?

[RLynwood]

Though this didn't work before for some reason, tonight merely selecting 'Line out (Built-in audio analog stero)' sent the sound to the speakers. Until I got this to work again, I've been using 'HDMI / Display port (Built-in Audio digital stereo (HDMI))', which sent the sound to the monitor's speakers. That's where I had no volume control. Now I need to learn how to control the monitor's speakers.

The other issue may be solved, not sure. Now the 'Line Out (Built-in Audio Analog Stereo)''s drop-down menu has the entire original options list. But the 'HDMI / DisplayPort (Built-in Audio Digital Stereo (HDMI))'s profile drop-down menu lists only 'Digital Stereo (HDMI) Output' and OFF. Don't know how to get the full menu list in this one if there was one. Claydoh, can you tell me about this?

[RLynwood]

Claydoh or anyone, my mic is working fine now, I believe, and I know that the camera is working because it show me what it's seeing in a window that comes up when I calll up the guvcview program. But, while Zoom uses the mic, it doesn't see the camera. You said earlier to look for the camera icon just to the left of the web browser's address bar. It isn't there, and I don't know why or how to get Zoom to "see" the camera. Guidance?

[claydoh]

Zoom, the program, or zoom via the web?

If using a web browser, which one?