For Chromium users:
Can you verify if either of
snap remove chromium
snap install --beta chromium
or
snap remove chromium
snap install --channel internal-libdrm chromium
fixes the issue?
Note: A refresh will *not* work for the first case, it really needs to
be removed and installed
Is there any known workaround for the spotify breakage? It has been
broken for quite a while now...
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/2004532
Title:
Hardware
** Changed in: chromium-browser (Ubuntu)
Status: Fix Committed => Confirmed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/2004532
Title:
Hardware acceleration broken
This issue affected me as well on Ubuntu 22.04.4, running on a AMD Ryzen
9 7950X3D integrated graphics CPU. Took a late Feb update and it broke.
I tried the various snap yaml modifications + snap try with no success.
Workaround seems to be to run Firefox does work outside of snap:
** Description changed:
- Possible, proposed solutions
-
-
- Option 1: Please install from these channels and report back with
- success or failure.
-
- snap refresh --channel candidate/core22 firefox
-
- Option 2:
-
- chromium --ozone-platform=wayland
-
It looks like this regressed in Chromium (probably when Chromium
switched to core22) judging by LP:2054887. The fix for the lack of
/usr/share/libdrm/amdgpu.ids is currently released on beta and will be
soon in other channels too.
** Changed in: chromium-browser (Ubuntu)
Status: Fix
I thought the whole point of Snap cores is that its supposed to be more
resistant to issues like this?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/2004532
Title:
Hardware
Is you want to make this permanent on Firefox you can go to about:config
and change:
browser.preferences.defaultPerformanceSettings.enabled -> false
layers.acceleration.disabled -> true
And Firefox will start without gpu acceleration (until MATE supports
Wayland, I hope).
--
You received this
To all MATE-Desktop users: there is not Wayland support.
The only way to execute Firefox and Chromium snaps is by disabling gpu
support:
$ firefox --safe-mode
$ chromium --disable-gpu
Or install the packages outside snap. Firefox appimage works.
--
You received this bug notification because
Ubuntu 22.04.3 LTS
I have AMD integrated graphics. AMD Ryzen 5 7600 6-Core Processor.
I'm using the mesa packages from ppa
//ppa.launchpadcontent.net/oibaf/graphics-drivers/ubuntu/
firefox and chromium is completely gibberish rendering. completely unusable.
I tried the different snaps from here.
Marking Firefox as fix released as well since now Firefox is on core22
and that was confirmed in earlier comments to solve the problem. Please
reset if observed otherwise.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser
Santiago, Spotify is proprietary, there is nothing for us to do. You
have to request them to update their base from core20 to core22.
According to 'snap info spotify', their contact link is
https://community.spotify.com/t5/Desktop-Linux/bd-p/desktop_linux.
** No longer affects: snapd (Ubuntu)
Spotify snap is also broken (see the attached image). I looked into
journalctl and found this (look at the line that mentions amdgpu):
abr 21 19:47:47 Corsair audit[43725]: SECCOMP auid=1000 uid=1000 gid=1000 ses=3
subj=snap.spotify.spotify pid=43725 comm="spotify"
Good! Marking it as fixed then, thank you again for reporting back.
** Changed in: chromium-browser (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
Hi Nathan,
I can confirm hardware acceleration is now working in Chromium browser
version 114.0.5735.198 (Official Build) snap (64-bit).
Hardware acceleration still DOES NOT work in Firefox version 115.0
(64-bit) Mozilla Firefox snap for Ubuntu canonical-002-1.0.
Using Xorg on Kubuntu 23.04.
This problem should now be solved for Chromium (>=114.0.5735.198).
Please confirm or deny it if you are a Chromium user previously affected
by this bug.
** Description changed:
Possible, proposed solutions
Option 1: Please install from these channels and
** Description changed:
Possible, proposed solutions
- Please install from these channels and report back with success or
- failure.
+ Option 1: Please install from these channels and report back with
+ success or failure.
- snap refresh --channel
Yann, your screenshots are not accessible to me. For firefox, could you
share `about:support` with and without `MOZ_ENABLE_WAYLAND` ?
We have had several reports as well that got duped to
https://bugzilla.mozilla.org/show_bug.cgi?id=1828196
** Bug watch added: Mozilla Bugzilla #1828196
Could this be affecting Telegram too? Look at the line
```
abr 25 09:24:24 Corsair telegram-desktop_telegram-desktop.desktop[2613107]:
/usr/share/libdrm/amdgpu.ids: Permission denied
```
here: https://github.com/telegramdesktop/tdesktop/issues/26225
** Bug watch added: Telegram Desktop Github
- chromium --ozone-platform=wayland is a workaround for Chromium
- MOZ_ENABLE_WAYLAND=1 firefox is a workaround for Firefox.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
** Attachment added: "Mozilla Firefox on Gnome Wayland"
https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/2004532/+attachment/5667227/+files/Capture%20d%E2%80%99%C3%A9cran%20du%202023-04-22%2012-16-35.png
--
You received this bug notification because you are a member of Desktop
Packages,
I've upgraded to Ubuntu 23.04 (Lunar Lobster), and I'm affected as well,
with Mozilla Firefox (from snap), and with Chromium (from snap too).
** Attachment added: "Chromium under Gnome Wayland"
Thanks for the additional data points, that is much appreciated.
** Description changed:
+ Possible, proposed solutions
+
+
+ Please install from these channels and report back with success or
+ failure.
+
+ snap refresh --channel candidate/core22 firefox
+
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-amdgpu/+bug/2016435
Any chance my problem is related to this (Kubuntu 23.04)? My Firefox crashed
constantly.
I also observed the same issue with my KDE Neon (with Pop!_OS's kernel +
mesarc from this PPA:
Could this be the same bug affecting Firefox and Spotify in Ubuntu
23.04? See https://askubuntu.com/questions/1462899/blurry-distored-
unreadable-snap-apps/1464603#1464603
Here is the terminal output when trying to run Spotify:
```bash
sfn@Corsair:~$ spotify
Gtk-Message: 19:10:13.937: Not
Thanks for testing, that's good news.
CBCM is disabled since the build is not Chrome branded; That diagnostic
message is expected.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
I tried with the edge version and the rendering looks ok now, still some
error messages:
~$ chromium-browser &
[1] 634220
Gtk-Message: 13:45:31.618: Failed to load module "appmenu-gtk-module"
[634220:634220:0420/134531.890979:ERROR:chrome_browser_cloud_management_controller.cc(162)]
Cloud
Any change the edge channel (in which we have now more up to date
libraries) works for you?
sudo snap refresh --edge chromium
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
> Maybe this is helpful - a difference I noticed in the output of chromium
> when run without and with the --disable-gpu flag is that, when run
> without it there is a log line
>
> amdgpu: os_same_file_description couldn't determine if two DRM fds
> reference the same file description.
>
> while
Having this as well, Ubuntu 22.04.2 LTS, 5.15.0-1030-gke. Firefox and
Chrome rendering garbage.
Maybe this is helpful - a difference I noticed in the output of chromium
when run without and with the --disable-gpu flag is that, when run
without it there is a log line
amdgpu:
I have this issue on Xubuntu 22.04.2 LTS, amdgpu and X11.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/2004532
Title:
Hardware acceleration broken for amdgpu/mesa in snap
Hi Ivan,
Unfortunate that it fixes the error message but not the bug...
Anyway many thanks for your helpfulness going out of your way to give
the test fix a go, that's much appreciated.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
Hi Nathan,
Quick update: I have tried modifying Chromium profile file per your
instructions and indeed this silenced the error message. But it had zero
effect on the GPU bug. I also installed updated kernel which arrived
today and observed no changes either.
$ uname -a
Linux xx
On the hardware acceleration front, there has also been recent fixes to
AMD GPUs failing to find drivers. It's probably unrelated to the present
problem, but if you want to try it anyway, it's on the beta/hwacc
channel:
snap install --channel beta/hwacc chromium
--
You received this bug
Given the error message from chromium.log,
> amdgpu: os_same_file_description couldn't determine if two DRM fds reference
> the same file description.
> If they do, bad things may happen!
I think this might be the kcmp's denial fault.
Can you please execute the following commands to whitelist
I also have been affected by this bug.
Firefox browser's gpu acceratation feature is unusable on x11 session.
My GPU:
0b:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Navi
14 [Radeon RX 5500/5500M / Pro 5500M] (rev c5)
OS:
Ubuntu 22.04.2 LTS
--
You received this bug
** Tags added: kivu
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/2004532
Title:
Hardware acceleration broken for amdgpu/mesa in snap
Status in chromium-browser package in
I can confirm this under Gnome as well. Starting a Wayland session, all
works fine. Logging in under Xorg results in this graphical issue for
both Firefox and Chromium.
Same GPU as the initial reporter, however I am on 22.04 and kernel
5.15.0 (stock HWE).
--
You received this bug notification
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: snapd (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: firefox (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
** Changed in: chromium-browser (Ubuntu)
Status: New => Triaged
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/2004532
Title:
Hardware acceleration broken for
# attached below, taken with the chromium browser running
$ journalctl -r | head -n 300 >journal.log
** Attachment added: "journal.log"
https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/2004532/+attachment/5644560/+files/journal.log
--
You received this bug notification because you are a
apport information
** Tags added: apport-collected snap
** Description changed:
Snap packages which use hardware accelerated graphics are broken after
the last routine system upgrade via apt. My system is using AMD Radeon
RX 5500 XT graphics card from ASUS, with stock amdgpu kernel
Thank you for reporting back!
> Sorry for missing pieces of info in my original report.
Don't worry, you even used Apport and provided many useful details.
Apparently, Apport doesn't submit enough information if snapd is its
target. Can you please run
apport-collect -p chromium-browser
Hi Nathan,
Sorry for missing pieces of info in my original report.
I am running KDE/Plasma on Xorg.
And yes, "chromium --disable-gpu" fixes the issue for chromium as well.
I am attaching chromium run log below.
** Attachment added: "chromium.log"
Thanks for the report, Bamywasi.
If disabling hardware acceleration managed to fix your issue for
Firefox, in Chromium it should work too? The command line would be
"chromium --disable-gpu".
Does your KDE runs on Wayland on Xorg? If on Wayland, do you experience
the same bug
- with "chromium
** Package changed: snap (Ubuntu) => snapd (Ubuntu)
** Also affects: firefox (Ubuntu)
Importance: Undecided
Status: New
** Also affects: chromium-browser (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Desktop
47 matches
Mail list logo
