$ apt policy anydeskįrom the output, we can get the version of AnyDesk installed on Kali Linux. sudo apt -y update & sudo apt -y install anydeskĬonfirm package installation. Install AnyDesk on Kali Linux using the apt package manager. curl -fsSL |sudo gpg -dearmor -o /etc/apt//anydesk.gpg Step 3: Install AnyDesk on Kali Linux Import AnyDesk GPG key for signing APT packages. Sudo apt install -y gnupg2 curl Step 2: Add AnyDesk repository Kali LinuxĪdd AnyDesk repository to Kali Linux: sudo sh -c 'echo "deb all main" > /etc/apt//anydesk.list' So I'd guess there's something in the Mesa/Intel stack that isn't playing nice with whatever Cinnamon uses for that screen recording function - that points more toward a GTK/ Xorg issue with the way Mesa handles framebuffer access, or something to that effect (my core competencies don't include a high level of detail on the Mesa/driver stack).Update APT packages installed on your Kali Linux: sudo apt update So from what I see here, Intel hardware (and thus driver stack) is the only place I'm seeing this bug. I use the Mesa/Radeon drivers on the AMD system, Mesa (only option) on Intel, and proprietary on Nvidia. So basically I am seeing this on Intel GPU, but not on AMD, and I would wager it wouldn't happen on an Nvidia GPU. Let's be clear about the Intel/Nvidia setup on my laptop - Optimus has the Intel GPU connected to the display directly, so even if you're using the Nvidia GPU, it's passing it's output to the Intel Chip, so you are never outputting from the Nvidia GPU directly to the display (unless you use the HDMI port, but I don't have that configured in a way I can easily test for this). In the other direction, I was able to easily reproduce the problem. With the AMD workstation as server, I had no problems other than the expected lag using a utility like this - none of the glitchy, texture "disappearing" that has been reported here.
I just tested two scenarios, using my laptop (Intel/Nvidia - Optimus) and an AMD APU (CPU/GPU) workstation.
0 kommentar(er)
