The problem with this approach is that when I login to Budgie normally (not through Chrome Remote Desktop), the sound card is no longer seen and Pulseaudio reports 'pa_context_connect() failed: Connection refused'. Essentially, for Chrome Remote Desktop audio to work on XFCE, I just uncommented everything on nf and nf, as I mentioned in my first post. Any help would be and I just tried looking at paprefs and pavucontrol to no avail. I've had a ton of fun installing and tweaking Arch Linux as a first time user, but these issues have proven to be quite difficult to solve. I know these are two different problems, but I think they are very much related. I tried playing around with alsa settings (nf) and PulseAudio's defaults.pa, but so far I still cannot output HDMI audio in my display manager. When I disabled it though, it still didn't work. I initially thought it was an issue with PulseAudio running due to my lingering user that I enabled. While I did manage to make the backgrounds work, I am not hearing any audio from the videos I am playing. Since I was using SDDM and customizing it, I decided to use one of those video background themes.
This leads me to my second, but probably related issue. I was thinking maybe I had to enable PulseAudio as a system-wide daemon or maybe I could not login to the same user twice (Chromoting and locally). I do feel like this is just a matter of tinkering with the PulseAudio settings, but I have had no success so far. However, by doing this, when I login locally from my desktop, no audio device is detected. That worked and Chrome Remote Desktop could then forward audio to whichever device I was Chromoting from. That being said, as instructed from the "crd -help" command, I uncommented all the default PulseAudio configurations on /etc/pulse/nf and /etc/pulse/nf. That allowed me to use Chrome Remote Desktop (installed from the AUR) even from the login screen.
0 kommentar(er)
