Open shelson opened 3 years ago
Building the snap from the github source - added a bind for bind-file: $SNAP/usr/share/libdrm/amdgpu.ids
which quietened that error down (not useful in a generic world I'm sure, but trying to remove variables).
The major thing now is that it can't load the radeonsi module, which is part of the open source driver stack, but not the AMD driver stack. Given the snap is built in a VM i'm starting to get the feeling that I'm SOL as the VM will never be aware of the AMD driver differences?
Just to confirm, went back to the drivers from ppa:oibaf/graphics-drivers
and zoom-client works perfectly again.
I'm sorry nobody else replied. Thanks for posting. It was useful to me.
I've been using the zoom-client snap for a couple of weeks with no issues (Ubuntu 20.04.1) , and then was brave(^H^H^H^silly) enough to mess with the graphics drivers on my system, installing the AMD supplied drivers
amdgpu-pro-21.20-1271047-ubuntu-20.04
. After this zoom-client attempts to start, opening the initial window but immediately crashes.As a point of comparison if I directly install the zoom deb it does work, but when I resize the window the window contents become totally distorted and I'm wondering if there's some software rendering in play :shrug:
Here are the logs for
snap
installed zoom-client:Here are the logs from dpkg installed zoom:
I noted snap installed zoom-client was complaining about a missing file, which is on the filesytem, but I think snap does some kind of sandboxing?
radeonsi
being missing also doesn't seem inspirational - I'm pretty sure this module existed pre-AMD-official-drivers. Maybe this is where things are coming unstuck? The AMD driver page at https://www.amd.com/en/support/kb/faq/amdgpu-installation claimsPro opengl
is installed, but I'm not clueful enoguh to know how to know if it's enabled.The simplest answer would be to go back to the open-source drivers I guess, but I'm interested to understand if it's fixable as I'm in a learning mood - happy to assist where I can :)