> the issue is still present
Then I'm marking this as fixed and restricting its scope to just the
missing amdgpu.ids. The actual rendering issue is already tracked in
LP:2004532.
> with the below errors
Those are expected warnings, they don't relate to the reported issue.
> The following command says that "chromium is already installed
Ah, when you already have the snap installed you use 'snap refresh ...'
instead.
> I am starting to wonder if it is a bug not present in Chromium but in
snap itself. I decided to try Firefox and the issue is present there
too.
Thanks for your proactivity with regards to investigating this bug. The
lack of amdgpu.ids in the snap was indeed caused by snap confinement,
but judging by the stderr we now have all files and libraries reachable,
so a system library such as Mesa could also be playing a role in the
bug.
** Summary changed:
- Grahpical bugs caused by unable to access libdrm
+ Unable to access libdrm
** Changed in: chromium-browser (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2054887
Title:
Unable to access libdrm
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2054887/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
