Bug 2405284 - Corrupted graphics, broken acceleration on some AMD APUs/GPUs with Chromium 141.0.7390.65
Summary: Corrupted graphics, broken acceleration on some AMD APUs/GPUs with Chromium 1...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: chromium
Version: 43
Hardware: x86_64
OS: Linux
unspecified
urgent
Target Milestone: ---
Assignee: Than Ngo
QA Contact: Fedora Extras Quality Assurance
URL: https://discussion.fedoraproject.org/...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2025-10-21 06:36 UTC by Federico Leva
Modified: 2026-08-14 12:29 UTC (History)
6 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2026-08-14 12:07:16 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
/etc/chromium/chromium.conf with chromium-141.0.7390.54-1.fc41.x86_64 (2.12 KB, text/plain)
2025-10-22 15:03 UTC, Federico Leva
no flags Details

Description Federico Leva 2025-10-21 06:36:24 UTC
Chromium 141.0.7390.65 is unusable on my AMD A8-7600 PC, while chromium-141.0.7390.54-1 works just fine. Immediately at launch, the window displays some graphic corruption like green bands, and input is so laggy I can barely type "about://gpu". These errors appear to be related:

```

    $ LANG=en_US chromium-browser
    Warning: ../src/amd/vulkan/radv_physical_device.c:2041: Device ‘/dev/dri/renderD128’ is not using the AMDGPU kernel driver: Invalid argument (VK_ERROR_INCOMPATIBLE_DRIVER)
    [11692:11729:1013/154641.544102:ERROR:google_apis/gcm/engine/registration_request.cc:291] Registration response error message: DEPRECATED_ENDPOINT
    Warning: maxDynamicUniformBuffersPerPipelineLayout artificially reduced from 500000 to 16 to fit dynamic offset allocation limit.
    Warning: maxDynamicStorageBuffersPerPipelineLayout artificially reduced from 500000 to 16 to fit dynamic offset allocation limit.
    [11754:11754:1013/154641.567985:ERROR:ui/gl/egl_util.cc:92] EGL Driver message (Error) eglCreateContext: Requested version is not supported
    Warning: eglCreateContext failed with EGL_BAD_ATTRIBUTE

        While trying to discover a BackendType::OpenGL adapter.
        at CheckEGL (../../third_party/dawn/src/dawn/native/opengl/UtilsEGL.cpp:98)

    Warning: maxDynamicUniformBuffersPerPipelineLayout artificially reduced from 72 to 16 to fit dynamic offset allocation limit.
    Warning: maxDynamicStorageBuffersPerPipelineLayout artificially reduced from 64 to 16 to fit dynamic offset allocation limit.

```

The functioning version only prints these (not in this order).

```

ERROR:components/dbus/xdg/request.cc:165] Request cancelled by user.
ERROR:components/viz/service/gl/exit_code.cc:13] Restarting GPU process due to unrecoverable error. Context was lost.
ERROR:content/browser/gpu/gpu_process_host.cc:970] GPU process exited unexpectedly: exit_code=8704
ERROR:google_apis/gcm/engine/registration_request.cc:291] Registration response error message: DEPRECATED_ENDPOINT
ERROR:gpu/command_buffer/service/shared_image/shared_image_factory.cc:940] CreateSharedImage: could not create backing.
ERROR:gpu/command_buffer/service/shared_image/shared_image_manager.cc:389] SharedImageManager::ProduceSkia: Trying to Produce a Skia representation from a non-existent mailbox.
ERROR:gpu/ipc/client/command_buffer_proxy_impl.cc:128] ContextResult::kTransientFailure: Failed to send GpuControl.CreateCommandBuffer.
ERROR:ui/base/accelerators/global_accelerator_listener/global_accelerator_listener_linux.cc:285] Failed to call BindShortcuts (error code 4).
ERROR:ui/ozone/platform/wayland/gpu/gbm_pixmap_wayland.cc:83] Cannot create bo with format= RGBA_8888 and usage=Scanout|Rendering|Texturing
ERROR:ui/ozone/platform/wayland/gpu/gbm_pixmap_wayland.cc:83] Cannot create bo with format= RGBA_8888 and usage=Texturing

```

The discussion at https://discussion.fedoraproject.org/t/wayland-and-chromium-brave-gpu-acceleration-is-suddenly-broken-videos-hella-laggy/167520/18 has different users with slightly different issues, it's not clear if the root cause of my issue is the same as theirs.

Reproducible: Always

Steps to Reproduce:
1. Install chromium 141.0.7390.65 on an AMD A8-7600
2. Launch chromium
Actual Results:
Warnings about acceleration printed, graphics corrupted.

Expected Results:
No graphic corruption

Additional Information:
There were some problems with AMD A8-7600 in mesa drivers version 25.0, which were since resolved. The issue did not appear in connection with a mesa upgrade and a downgrade didn't help. Using an earlier kernel also didn't help. I've not tried switching away from Wayland.

My system information:

$ uname -a
Linux a88x 6.16.10-200.fc42.x86_64 #1 SMP PREEMPT_DYNAMIC Thu Oct  2 19:23:55 UTC 2025 x86_64 GNU/Linux
$ rpm -qa *mesa-dri*
mesa-dri-drivers-25.1.9-1.fc42.x86_64
$ chromium-browser --version
Chromium 141.0.7390.65 Fedora Project
$ lsmod | grep amdgpu 
amdgpu              20701184  0
amdxcp                 12288  1 amdgpu
gpu_sched              65536  1 amdgpu
drm_panel_backlight_quirks    12288  1 amdgpu
drm_buddy              32768  1 amdgpu
drm_ttm_helper         16384  2 amdgpu,radeon
ttm                   135168  3 amdgpu,radeon,drm_ttm_helper
drm_exec               12288  2 amdgpu,radeon
i2c_algo_bit           20480  2 amdgpu,radeon
drm_suballoc_helper    20480  2 amdgpu,radeon
drm_display_helper    327680  2 amdgpu,radeon
cec                   106496  2 drm_display_helper,amdgpu
video                  81920  2 amdgpu,radeon
$ inxi -Gx
Graphics:
  Device-1: Advanced Micro Devices [AMD/ATI] Kaveri [Radeon R7 Graphics]
    driver: radeon v: kernel arch: GCN-2 bus-ID: 00:01.0
  Display: wayland server: Xwayland v: 24.1.8 compositor: kwin_wayland
    driver: X: loaded: radeon unloaded: fbdev,modesetting,vesa dri: radeonsi
    gpu: radeon resolution: 1920x1080~60Hz
  API: EGL v: 1.5 drivers: kms_swrast,radeonsi,swrast platforms:
    active: gbm,wayland,x11,surfaceless,device inactive: N/A
  API: OpenGL v: 4.5 vendor: amd mesa v: 25.1.9 glx-v: 1.4
    direct-render: yes renderer: KAVERI (radeonsi ACO DRM 2.50
    6.16.10-200.fc42.x86_64)
  API: Vulkan v: 1.4.313 drivers: llvmpipe surfaces: N/A devices: 1
  Info: Tools: api: clinfo, eglinfo, glxinfo, vulkaninfo
    de: kscreen-console,kscreen-doctor wl: wayland-info x11: xdriinfo,
    xdpyinfo, xprop, xrandr

Comment 1 Than Ngo 2025-10-22 12:44:05 UTC
I have made some changes in /etc/chromium/chromium.conf in version 141.0.7390.65, It could be that this change causes problem in your case.

Could you please attach your /etc/chromium/chromium.conf file here so i can have a look at it?

Thank you!

Comment 2 Federico Leva 2025-10-22 15:03:52 UTC
Created attachment 2110470 [details]
/etc/chromium/chromium.conf with chromium-141.0.7390.54-1.fc41.x86_64

(In reply to Than Ngo from comment #1)
> Could you please attach your /etc/chromium/chromium.conf file here so i can
> have a look at it?

Thanks for looking into this! Currently it's like this, but I don't know what it was before I downgraded chromium. Should I test upgrading again?

Comment 3 Federico Leva 2026-01-22 15:26:00 UTC
This is still happening for me in chromium-144.0.7559.59-1.fc43.src.rpm

Comment 4 Fedora Release Engineering 2026-05-06 14:38:08 UTC
This message is a reminder that Fedora Linux 42 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 42 on 2026-05-13.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
'version' of '42'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, change the 'version' 
to a later Fedora Linux version. Note that the version field may be hidden.
Click the "Show advanced fields" button if you do not see it.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora Linux 42 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora Linux, you are encouraged to change the 'version' to a later version
prior to this bug being closed.

Comment 5 Federico Leva 2026-05-06 21:07:57 UTC
This is still present as of chromium-147.0.7727.137-1.fc43. I've not been able to use Chromium ever since I filed this bug report.

Comment 6 Felix Miata 2026-05-07 07:38:01 UTC
I just installed Chromium 147.0.7727.137-1.fc44, 481 MiB in 58 packages, on a test PC with A88X chipset and modestly newer Kaveri APU. It opened up just fine visually to fedoraproject.org/start with user that had never used it before. Note it's running X11 on the amdgpu kernel module rather than the old radeon (enabled via the *cik* cmdline parameters shown by inxi), along with the modesetting display driver instead of radeon. I don't see any visual problems on Youtube or in the forums.

$ inxi -CGMSaz --vs --hostname --za
inxi 3.3.40-00 (2025-11-25)
System:
  Host: ga88x Kernel: 6.19.14-300.fc44.x86_64 arch: x86_64 bits: 64
    compiler: gcc v: 16.0.1 clocksource: tsc avail: hpet,acpi_pm
    parameters: BOOT_IMAGE=/boot/vmlinuz root=LABEL=<filter> noresume
    selinux=0 audit=0 ipv6.disable=1 net.ifnames=0 mitigations=auto
    consoleblank=0 radeon.cik_support=0 amdgpu.cik_support=1
  Desktop: TDE (Trinity) v: R14.1.5 tk: Qt v: 3.5.0 wm: Twin v: 3.0
    with: kicker vt: 7 dm: 1: TDM 2: XDM Distro: Fedora Linux 44 (Forty Four)
Machine:
  Type: Desktop System: Gigabyte product: N/A v: N/A
    serial: <superuser required> Chassis: type: 3 serial: <superuser required>
  Mobo: Gigabyte model: F2A88XM-D3H v: x.x serial: <superuser required>
    uuid: <superuser required> Firmware: UEFI vendor: American Megatrends v: F9
    date: 12/25/2015
CPU:
  Info: model: AMD PRO A10-8750B R7 12 Compute Cores 4C+8G bits: 64 type: MCP
    arch: Steamroller level: v2 built: 2014 process: GF 28nm family: 0x15 (21)
    model-id: 0x38 (56) stepping: 1 microcode: 0x6003106
  Topology: cpus: 1x dies: 1 clusters: 1 cores: 4 smt: <unsupported> cache:
    L1: 256 KiB desc: d-4x16 KiB; i-2x96 KiB L2: 4 MiB desc: 2x2 MiB
  Speed (MHz): avg: 1400 min/max: 1400/3600 boost: enabled scaling:
    driver: acpi-cpufreq governor: schedutil cores: 1: 1400 2: 1400 3: 1400
    4: 1400 bogomips: 28748
  Flags-basic: avx ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
  Vulnerabilities: <filter>
Graphics:
  Device-1: Advanced Micro Devices [AMD/ATI] Kaveri [Radeon R7 Graphics]
    vendor: Gigabyte driver: amdgpu v: kernel alternate: radeon arch: GCN-2
    code: Sea Islands process: GF/TSMC 16-28nm built: 2013-17 ports:
    active: DVI-D-1,HDMI-A-1 empty: VGA-1 bus-ID: 00:01.0 chip-ID: 1002:130f
    class-ID: 0300
  Display: x11 server: X.Org v: 21.1.22 compositor: Twin v: 3.0 driver: X:
    loaded: modesetting dri: radeonsi gpu: amdgpu display-ID: :0 screens: 1
  Screen-1: 0 s-res: 4240x1440 s-dpi: 120 s-size: 897x304mm (35.31x11.97")
    s-diag: 947mm (37.29")
  Monitor-1: DVI-D-1 pos: right model: Dell P2213 serial: <filter>
    built: 2013 res: mode: 1680x1050 hz: 60 scale: 100% (1) dpi: 90 gamma: 1.2
    size: 473x296mm (18.62x11.65") diag: 558mm (22") ratio: 16:10 modes:
    max: 1680x1050 min: 720x400
  Monitor-2: HDMI-A-1 mapped: HDMI-1 pos: primary,left model: Acer K272HUL
    serial: <filter> built: 2018 res: mode: 2560x1440 hz: 60 scale: 100% (1)
    dpi: 109 gamma: 1.2 size: 598x336mm (23.54x13.23") diag: 686mm (27")
    ratio: 16:9 modes: max: 2560x1440 min: 720x400
  API: EGL v: 1.5 hw: drv: amd radeonsi platforms: device: 0 drv: radeonsi
    device: 1 drv: swrast gbm: drv: kms_swrast surfaceless: drv: radeonsi x11:
    drv: radeonsi inactive: wayland
  API: OpenGL v: 4.6 compat-v: 4.5 vendor: mesa v: 26.0.6 note: glxinfo
    missing (EGL sourced) renderer: llvmpipe (LLVM 22.1.4 256 bits), AMD
    Radeon R7 Graphics (radeonsi kaveri ACO DRM 3.64 6.19.14-300.fc44.x86_64)
  API: Vulkan v: 1.4.341 layers: 1 device: 0 type: integrated-gpu name: AMD
    Radeon R7 Graphics (RADV KAVERI) driver: mesa radv v: 26.0.6
    device-ID: 1002:130f surfaces: N/A device: 1 type: cpu name: llvmpipe
    (LLVM 22.1.4 256 bits) driver: mesa llvmpipe v: 26.0.6 (LLVM 22.1.4)
    device-ID: 10005:0000 surfaces: N/A
  Info: Tools: api: clinfo, eglinfo, vulkaninfo x11: xdpyinfo, xprop, xrandr
$
# lspci -nnk | grep -A2 VGA
00:01.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Kaveri [Radeon R7 Graphics] [1002:130f] (rev d7)
        Subsystem: Gigabyte Technology Co., Ltd Device [1458:d000]
        Kernel driver in use: amdgpu
# lsmod | grep -E 'radeo|amdg|vide' | sort
amdgpu              21499904  10
amdxcp                 12288  1 amdgpu
cec                   110592  2 drm_display_helper,amdgpu
drm_buddy              28672  1 amdgpu
drm_display_helper    344064  2 amdgpu,radeon
drm_exec               12288  2 amdgpu,radeon
drm_panel_backlight_quirks    12288  1 amdgpu
drm_suballoc_helper    20480  2 amdgpu,radeon
drm_ttm_helper         20480  3 amdgpu,radeon
gpu_sched              73728  1 amdgpu
i2c_algo_bit           24576  2 amdgpu,radeon
radeon               2514944  0
ttm                   135168  3 amdgpu,radeon,drm_ttm_helper
video                  81920  2 amdgpu,radeon
wmi                    36864  1 video
#

Journalctl is showing a lot of audio-related nasties, but this looks TDE-related, as its builder can't get it built for 44 due to 44's newer gcc version, so this 44 is using the old 43 build of TDE. Running Chromium in IceWM produces no such errors, but neither any sound. :p

Comment 7 Federico Leva 2026-05-07 09:02:36 UTC
Thanks for testing. I'm using wayland and radeon. I tried amdgpu a few months ago, IIRC, and I can try it again if it helps; I won't try going back to X though.

$ inxi -CGMSaz --vs --hostname --za
inxi 3.3.40-00 (2025-11-25)
System:
  Host: a88x Kernel: 6.19.11-200.fc43.x86_64 arch: x86_64 bits: 64
    compiler: gcc v: 15.2.1 clocksource: tsc avail: acpi_pm
    parameters: BOOT_IMAGE=(hd1,gpt2)/vmlinuz-6.19.11-200.fc43.x86_64
    root=UUID=<filter> ro rootflags=subvol=root
    rd.luks.uuid=luks-bdc558b4-9da3-4b8f-82e1-39b3ccc21a2c rhgb quiet
  Desktop: KDE Plasma v: 6.6.4 tk: Qt v: N/A info: frameworks v: 6.25.0
    wm: kwin_wayland vt: 2 dm: SDDM Distro: Fedora Linux 43 (KDE Plasma Desktop
    Edition)
Machine:
  Type: Desktop System: Gigabyte product: N/A v: N/A
    serial: <superuser required> Chassis: type: 3 serial: <superuser required>
  Mobo: Gigabyte model: F2A88XN-WIFI v: x.x serial: <superuser required>
    uuid: <superuser required> Firmware: UEFI vendor: American Megatrends v: F4
    date: 05/28/2014
CPU:
  Info: model: AMD A8-7600 Radeon R7 10 Compute Cores 4C+6G bits: 64 type: MCP
    arch: Steamroller level: v2 built: 2014 process: GF 28nm family: 0x15 (21)
    model-id: 0x30 (48) stepping: 1 microcode: 0x6003104
  Topology: cpus: 1x dies: 1 clusters: 1 cores: 4 smt: <unsupported> cache:
    L1: 256 KiB desc: d-4x16 KiB; i-2x96 KiB L2: 4 MiB desc: 2x2 MiB
  Speed (MHz): avg: 3095 min/max: 1400/3100 boost: enabled scaling:
    driver: acpi-cpufreq governor: schedutil cores: 1: 3095 2: 3095 3: 3095
    4: 3095 bogomips: 24755
  Flags-basic: avx ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
  Vulnerabilities: <filter>
Graphics:
  Device-1: Advanced Micro Devices [AMD/ATI] Kaveri [Radeon R7 Graphics]
    driver: radeon v: kernel alternate: amdgpu arch: GCN-2 code: Sea Islands
    process: GF/TSMC 16-28nm built: 2013-17 ports: active: DVI-D-1
    empty: HDMI-A-1,HDMI-A-2 bus-ID: 00:01.0 chip-ID: 1002:1313 class-ID: 0300
  Display: wayland server: Xwayland v: 24.1.11 compositor: kwin_wayland
    driver: X: loaded: radeon unloaded: fbdev,modesetting,vesa dri: radeonsi
    gpu: radeon display-ID: 0
  Monitor-1: DVI-D-1 model: LG (GoldStar) E2441 serial: <filter> built: 2011
    res: mode: 1920x1080 hz: 60 scale: 100% (1) dpi: 92 gamma: 1.2
    size: 531x299mm (20.91x11.77") diag: 609mm (24") ratio: 16:9 modes:
    max: 1920x1080 min: 720x400
  API: EGL v: 1.5 hw: drv: amd radeonsi platforms: device: 0 drv: radeonsi
    device: 1 drv: swrast gbm: drv: kms_swrast surfaceless: drv: radeonsi
    wayland: drv: radeonsi x11: drv: radeonsi
  API: OpenGL v: 4.5 vendor: amd mesa v: 25.3.6 glx-v: 1.4
    direct-render: yes renderer: KAVERI (radeonsi ACO DRM 2.51
    6.19.11-200.fc43.x86_64) device-ID: 1002:1313 memory: 1000 MiB unified: no
    display-ID: :0.0
  API: Vulkan v: 1.4.341 layers: 1 device: 0 type: cpu name: llvmpipe (LLVM
    21.1.8 256 bits) driver: mesa llvmpipe v: 25.3.6 (LLVM 21.1.8)
    device-ID: 10005:0000 surfaces: N/A
  Info: Tools: api: clinfo, eglinfo, glxinfo, vulkaninfo
    de: kscreen-console,kscreen-doctor wl: wayland-info x11: xdriinfo,
    xdpyinfo, xprop, xrandr

Comment 8 Felix Miata 2026-05-07 14:49:17 UTC
Again on F44:

In (X11) IceWM session running on kernel 6.19.14, amdgpu kernel module, modesetting display driver, and 2560x1440 display, glmark2 score: 1129

Switch to (X11) IceWM session running on kernel 6.19.14, radeon kernel module, radeon display driver, and 2560x1440 display, glmark2 score: 998

Switch to (X11) IceWM session running on kernel 6.19.14, radeon kernel module, modesetting display driver, and 2560x1440 display, glmark2 score: 1000

Switch to (X11) IceWM session running on kernel 6.19.14, amdgpu kernel module, amdgpu display driver, and 2560x1440 display, glmark2 score: 1127

Something else to consider is we both have Gigabyte motherboards with A88X chipsets, so their ages would be rather close if not identical. Yet, my BIOS is 5 versions and 19 months newer than yours, so there might be something to be gained from updating yours.

Yet another: my CPU/APU was available used last month on eBay for under $30USD, and likely still is, along with 2-3 faster CPU models (for more money). 

Still another: my inxi shows minimal CPU activity, while all 4 of your cores are running at 100%.

Comment 10 Federico Leva 2026-08-14 12:29:51 UTC
I've not experienced this issue any more in recent versions, e.g. chromium-151.0.7922.108-1.fc44.x86_64 . I've stopped using chromium though, so I have not tested much.


Note You need to log in before you can comment on or make changes to this bug.