-
Notifications
You must be signed in to change notification settings - Fork 227
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
Bugged microphone #273
Comments
@Jolonte
from what I could gather from all the conversations like in #254, some server of lawl, the creator of NoiseTorch has been compromised. and there may be things the attacker hid in NoiseTorch, which is why removing NoiseTorch is recommended for now. so far nothing malicious has been found in NoiseTorch tho and NoiseTorch is probably fine |
Ok, thank you very much for the feedback, well, I hope everything can be solved and nothing bad happens. I don't know if it was an isolated case (of the mic), at least nobody else reported an issue about it, but it is still buggy, in that case do I need to reinstall the drivers? |
I had same a problem. I fixed it by restarting pulseaudio. |
Okay, how could I do that? |
Pulseaudio can be restarted by running |
So I tried another way, with the following command: This returned the following error: and after: So I decided to install pulseaudio via terminal, which again gave me an error :(
|
Oh right, with some research I found out that Pop OS does not use pulse audio, but rather Pipewires Pulse 🤡. To reset it just use the following commands: or for some other distributions: Then just delete this folder and reboot. |
Makes sense, I wasn't sure if PopOS went with Pipewire for 22.04 or not. For what it's worth, restarting Pipewire can be done as follows:
I believe that logging in and out should be good enough as well, given that pipewire should be a user service, but rebooting won't hurt :) |
It really worked!!! I'm even more relieved :D Well, I would like to thank everyone here for their support anyway. I hope others have been helped with this as well. My sincere thanks, I will be closing this issue. About NoiseTorch, I hope it will be back to normal soon, I'll be looking for an alternative to it until things get back to normal. |
Hello everyone, well, I'm a little lost about what happened, but my microphone started getting buggy (understand buggy as, popped and inaudible).
I was using noise torch normally but I decided to enter its repository, which contained some instructions to uninstall it, so I did.
I don't know if these 2 facts correlate, but I would like to know why uninstall this program that until recently was normal. If you can explain to me what really happened, thank you!
Another thing, I'm using Pop OS 22.04, it's my first Linux distribution, however when I was going to update the program, in a proper option, a "modal" appeared saying that my section didn't start correctly and also asked for my password, well I don't know if this is normal, even because it's my first distribution but when I clicked on update, it said that the update failed.
The text was updated successfully, but these errors were encountered: