> 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
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. And also disabling hardware acceleration on Firefox fixes the issue
as a work around just like in Chromium.
--
You received this bug notification
Okay so doing the remove and then install made the amdgpu error go away,
but now the issue is still present with the below errors
chromium-browser
Gtk-Message: 11:22:24.966: Failed to load module "xapp-gtk3-module"
Gtk-Message: 11:22:24.966: Not loading module "atk-bridge": The functionality
is
** Description changed:
+ Related: LP:2004532.
+
The chromium snap package has a bunch of graphical glitches that makes
the program unusable. This appears to be caused by the snap package
being unable to access the libdrm directory. Below is the output I get
when launching the program. I
I can reproduce the issue if I refresh instead of really reinstalling
the snap, so a bug in Snapd.
Please try
snap remove chromium
snap install --beta chromium
Does the amdgpu.ids error go away now?
If that still doesn't solve the graphical bugs and you have time, it
would also be very
Command output
$ ls -l /usr/share/libdrm
total 0
$ chromium-browser
Gtk-Message: 10:23:13.367: Failed to load module "xapp-gtk3-module"
Gtk-Message: 10:23:13.367: Not loading module "atk-bridge": The functionality
is provided by GTK natively. Please try to not load it.
> I still have the issue after switching to the beta version
123.0.6312.22
Hum... Do you still get the error about the missing file in stderr? Can
you confirm
snap run --shell chromium
ls -l /usr/share/libdrm
lists amdgpu.ids now?
I also built the snap with Libdrm provided by Chromium's
Image of running the beta. works fine with --disable-gpu
** Attachment added: "betaIssue.png"
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2054887/+attachment/5751657/+files/betaIssue.png
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
Here is the output of the commands you asked for. Note this was after I
installed the beta version
snap connections chromium
Interface PlugSlot
Notes
audio-playbackchromium:audio-playback
I still have the issue after switching to the beta version 123.0.6312.22
** Attachment added: "Beta.png"
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2054887/+attachment/5751656/+files/Beta.png
--
You received this bug notification because you are a member of Ubuntu
I can confirm the --disable-gpu argument made chromium work as intended.
I'll give the beta a try. Thank you so much for your help and looking in
to this issue!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Maybe it was perception error, because today I can confirm
/usr/share/libdrm/amdgpu.ids is present in the beta snap. Could you
please confirm the bug (or at least the error message) goes away by
switching to it?
sudo snap refresh --beta chromium
** Changed in: chromium-browser (Ubuntu)
Either the workaround[1] didn't work for Chromium or I managed to botch
my copy of it[2], for /usr/share/libdrm is still empty in the Chromium
beta snap.
[1]
https://git.launchpad.net/~mozilla-snaps/firefox-snap/+git/firefox-snap/commit/?id=00059b6a9aea8e4ce5a239bd9e649f60736dd947
[2]
And Firefox has a work around, which I'm copying to Chromium beta. Once
the fix is confirmed, will be released to other chnnaels.
** Changed in: chromium-browser (Ubuntu)
Status: New => In Progress
** Changed in: chromium-browser (Ubuntu)
Assignee: (unassigned) => Nathan Teodosio
This might be a bug in Snapd: LP:2055273.
--
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:
Grahpical bugs caused by unable to access libdrm
To manage notifications about this bug go
Looks like GPU indeed, can you confirm with --disable-gpu?
What is 'snap list|grep ^gnome' and 'snap connections chromium'?
--
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:
Grahpical
** Description changed:
The chromium snap package has a bunch of graphical glitches that makes
the program unusable. This appears to be caused by the snap package
being unable to access the libdrm directory. Below is the output I get
when launching the program. I have confirmed I have
** Description changed:
- Launching the chromium snap package causes a bunch of graphical glitches
- that makes the program unusable. This cause appears to stem from the
- snap being unable to access the libdrm directory. Below is the output I
- get when launching the program. I have confirmed I
18 matches
Mail list logo