discord-screenaudio
discord-screenaudio copied to clipboard
Cannot unmute microphone
The unmute button is unresponsive in and out of call, and then checking voice & video settings, there is a message with red text reading
you do not have any input devices enabled. You must grant Discord access to your microphone
clicking the bold text which should grant that access does nothing either
this means the microphone is permanently locked to muted.
I get the same error. Maybe it's because of its displaying the web contents in the application and then normally in the browser you would allow the website to be able to access microphone?
Maybe it's because of its displaying the web contents in the application and then normally in the browser you would allow the website to be able to access microphone?
Hm it should accept all of the permission requests it gets automatically: https://github.com/maltejur/discord-screenaudio/blob/master/src/discordpage.cpp#L144-L146
I sadly can not reproduce this issue at all. Maybe this error is caused by something on your system? For example, no microphone plugged in or you have disabled the microphone permisson in Flatpak.
Can confirm this issue on Arch Linux, lastes Kernel version as of now
I sadly can not reproduce this issue at all. Maybe this error is caused by something on your system? For example, no microphone plugged in or you have disabled the microphone permisson in Flatpak.
I am using the package from the AUR as stated in the install instructions. https://aur.archlinux.org/packages/discord-screenaudio
I am also on Arch Linux like @Fabxx, so this might be an issue related to Arch? or maybe since arch gets updates faster, because of a new package that's causing this issue. I am on kernel: 6.1.5-arch2-1
well i can try to test with VMs on other distros, but btw i've noticed a weird behavior, the webcam device with integrated microphone when attached is detected as "default" and it detects the voice, you just don't have the permission to use it.
Decided to try debugging the issue. So started launching the app from the terminal, and somehow now it just works. I have no idea what caused it to work now. The only thing that i noticed being printed to the console when the mic still wasn't working was this:
discord-screenaudio[53164]: [userscript] Cannot locate Mute/Deafen/Settings button container, please report this on GitHub
maybe this has something to do with it, or maybe its just normal.
I am also using Arch and it works fine for me, so Arch itself does not seem to be the problem.
Cannot locate Mute/Deafen/Settings button container, please report this on GitHub
This is an issue with the keybind function I should fix too, but it doesn't seem to be the problem.
Do you both have pipewire-pulse
installed? Maybe that could be it.
Do you both have pipewire-pulse installed? Maybe that could be it.
yes:
$ paru -Q | grep -i pipewire
kpipewire 5.26.5-1
lib32-pipewire 1:0.3.64-1
pipewire 1:0.3.64-1
pipewire-alsa 1:0.3.64-1
pipewire-audio 1:0.3.64-1
pipewire-jack 1:0.3.64-1
pipewire-pulse 1:0.3.64-1
This is my paru output instead
@Sveske-Juice what about systemctl --user status pipewire-pulse.service
what about systemctl --user status pipewire-pulse.service
$ systemctl --user status pipewire-pulse.service
● pipewire-pulse.service - PipeWire PulseAudio
Loaded: loaded (/usr/lib/systemd/user/pipewire-pulse.service; disabled; preset: enabled)
Active: active (running) since Sat 2023-01-14 11:37:45 CET; 3h 32min ago
TriggeredBy: ● pipewire-pulse.socket
Main PID: 1800 (pipewire-pulse)
Tasks: 2 (limit: 38358)
Memory: 134.6M
CPU: 25.042s
CGroup: /user.slice/user-1000.slice/[email protected]/session.slice/pipewire-pulse.service
└─1800 /usr/bin/pipewire-pulse
jan 14 11:37:45 Sussybox systemd[1286]: Started PipeWire PulseAudio.
The microphone works now for me. But didn't work yesterday (i found out about this yesterday and decided to try it out). Maybe its because i rebooted and now it works?
What about my case where i have only pipewire and this is it's status?
@Sveske-Juice nice to hear that it works now. Did you install any of the pipewire packages yesterday? Maybe thats why you needed to reboot.
@Fabxx try installing pipewire-pulse
and enabling it (systemctl --user enable --now pipewire-pulse.service
). Then also maybe reboot as we have seen :D
Did you install any of the pipewire packages yesterday?
They were already installed, but they were updated when I updated my system yesterday but if i remember correctly i rebooted
@Fabxx
Have you followed https://wiki.archlinux.org/title/PipeWire#Installation?
you have to have the following packages installed
pipewire
pipewire-pulse
wireplumber
pipewire-alsa
after that you can just reboot and the service will start automatically
@Sveske-Juice what happens now is that discord can hear the audio but it doesn't have permissions to use it again.
also i can't screenshare too when this happens
UPDATE: even by installing the mentioned xdg package, the yellow warnings disappear, but still i can't do anything
Do sound work?
What does it print when running discord-screenaudio
from the terminal?
@Sveske-Juice
this might be an issue related to Arch?
Came here from the issue mentioned above since I'm sure it's related to the "allow microphone" popup not appearing at all. It's very important that I'm on Arch linux latest kernel as today (I'm away from my PC). So it's very likely to be an Arch issue.
Also tried tot install the flatpak version with no success
Fixed by installing pipewire-pulse
. Maybe OP @maltejur should add it to the pkgbuild in the AUR?
If someone finds it useful, here is my audio-related packages installed:
libpulse 16.1-3
pipewire-pulse 1:0.3.65-6
pipewire 1:0.3.65-6
pipewire-alsa 1:0.3.65-6
pipewire-audio 1:0.3.65-6
pipewire-jack 1:0.3.65-6
alsa-firmware 1.2.4-2
alsa-lib 1.2.8-1
alsa-plugins 1:1.2.7.1-1
alsa-utils 1.2.8-1