Watching videos in Browser show artifacts

Coming from the thread: artifacts when playing videos

I also have these artifacts in my laptop. I used Kinoite where I first started to see the artifacts, now I am on Aurora Linux, both fully updated. This is my inxi -Fzxx:

nxi -FZxx
System:
  Host: Lenovo-Kinoite Kernel: 7.1.4-200.fc44.x86_64 arch: x86_64 bits: 64
    compiler: gcc v: 16.1.1
  Desktop: KDE Plasma v: 6 tk: Qt v: N/A wm: kwin_wayland dm: N/A
    Distro: Fedora Linux 44 (Toolbx Container Image)
Machine:
  Type: Laptop System: LENOVO product: 82RG v: Legion 5 Pro 16ARH7H
    serial: <superuser required> Chassis: type: 10 v: Legion 5 Pro 16ARH7H
    serial: <superuser required>
  Mobo: LENOVO model: LNVNB161216 v: SDK0T76461 WIN
    serial: <superuser required> part-nu: LENOVO_MT_82RG_BU_idea_FM_Legion 5
    Pro 16ARH7H Firmware: UEFI vendor: LENOVO v: JUCN68WW date: 12/05/2024
Battery:
  ID-1: BAT0 charge: 70 Wh (98%) condition: 71.5/80 Wh (89.3%) volts: 15.42
    min: 15.44 model: Celxpert L21C4PC1 serial: 5963 charging:
    status: not charging cycles: 187
  Device-1: hidpp_battery_0 model: Logitech Wireless Keyboard
    serial: 00-00-00-00 charge: normal status: discharging
CPU:
  Info: 8-core model: AMD Ryzen 7 6800H with Radeon Graphics bits: 64
    type: MT MCP arch: Zen 3+ rev: 1 cache: L1: 512 KiB L2: 4 MiB L3: 16 MiB
  Speed (MHz): avg: 1397 min/max: 404/4787 boost: enabled cores: 1: 1397
    2: 1397 3: 1397 4: 1397 5: 1397 6: 1397 7: 1397 8: 1397 9: 1397 10: 1397
    11: 1397 12: 1397 13: 1397 14: 1397 15: 1397 16: 1397 bogomips: 102207
  Flags-basic: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3
Graphics:
  Device-1: NVIDIA GA106M [GeForce RTX 3060 Mobile / Max-Q] vendor: Lenovo
    driver: nvidia v: 610.57.04 arch: Ampere pcie: speed: 2.5 GT/s lanes: 8
    ports: active: HDMI-A-1 empty: DP-7,DP-8,eDP-2 bus-ID: 01:00.0
    chip-ID: 10de:2560
  Device-2: Advanced Micro Devices [AMD/ATI] Rembrandt [Radeon 680M]
    vendor: Lenovo driver: amdgpu v: kernel arch: RDNA-2 pcie: speed: 16 GT/s
    lanes: 16 ports: active: eDP-1 empty: DP-1, DP-2, DP-3, DP-4, DP-5, DP-6,
    Writeback-1 bus-ID: 34:00.0 chip-ID: 1002:1681 temp: 40.0 C
  Display: wayland server: N/A compositor: kwin_wayland driver:
    gpu: amdgpu,nv_platform,nvidia,nvidia-nvswitch display-ID: 0
  Monitor-1: HDMI-A-1 model: Philips 27M1C5500V res: 2560x1440 dpi: 109
    diag: 685mm (27")
  Monitor-2: eDP-1 model: BOE Display 0x0a9b res: 2560x1600 dpi: 189
    diag: 406mm (16")
  API: OpenGL v: 4.6 vendor: amd mesa v: 26.1.5 glx-v: 1.4 es-v: 3.2
    direct-render: yes renderer: AMD Radeon 680M (radeonsi rembrandt ACO DRM
    3.64 7.1.4-200.fc44.x86_64) device-ID: 1002:1681 display-ID: :0.0
  API: EGL Message: EGL data requires eglinfo. Check --recommends.
  Info: Tools: api: glxinfo gpu: nvidia-smi x11: xdriinfo, xdpyinfo, xprop,
    xrandr
Audio:
  Device-1: NVIDIA GA106 High Definition Audio driver: snd_hda_intel v: kernel
    pcie: speed: 2.5 GT/s lanes: 8 bus-ID: 01:00.1 chip-ID: 10de:228e
  Device-2: Advanced Micro Devices [AMD/ATI] Radeon High Definition Audio
    vendor: Lenovo driver: snd_hda_intel v: kernel pcie: speed: 16 GT/s
    lanes: 16 bus-ID: 34:00.1 chip-ID: 1002:1640
  Device-3: Advanced Micro Devices [AMD] Audio Coprocessor vendor: Lenovo
    driver: snd_pci_acp6x v: kernel pcie: speed: 16 GT/s lanes: 16
    bus-ID: 34:00.5 chip-ID: 1022:15e2
  Device-4: Advanced Micro Devices [AMD] Ryzen HD Audio vendor: Lenovo
    driver: snd_hda_intel v: kernel pcie: speed: 16 GT/s lanes: 16
    bus-ID: 34:00.6 chip-ID: 1022:15e3
  API: ALSA v: k7.1.4-200.fc44.x86_64 status: kernel-api
  Server-1: PipeWire v: 1.6.8 status: active (process) with:
    1: pipewire-pulse status: active 2: wireplumber status: active
    3: pipewire-alsa type: plugin 4: pw-jack type: plugin
Network:
  Device-1: MEDIATEK MT7922 802.11ax PCI Express Wireless Network Adapter
    vendor: Lenovo driver: mt7921e v: kernel pcie: speed: 5 GT/s lanes: 1
    bus-ID: 02:00.0 chip-ID: 14c3:0616
  IF: wlp2s0 state: down mac: 22:d4:9d:c9:63:f3
  Device-2: Realtek RTL8111/8168/8211/8411 PCI Express Gigabit Ethernet
    vendor: Lenovo driver: r8169 v: kernel pcie: speed: 2.5 GT/s lanes: 1
    port: 4000 bus-ID: 03:00.0 chip-ID: 10ec:8168
  IF: eno1 state: up speed: 1000 Mbps duplex: full mac: 9c:2d:cd:b9:59:d0
  IF-ID-1: tailscale0 state: unknown speed: -1 duplex: full mac: N/A
  IF-ID-2: tun0 state: unknown speed: 10000 Mbps duplex: full mac: N/A
Bluetooth:
  Device-1: Foxconn / Hon Hai Bluetooth 5.2 Adapter [MediaTek MT7922]
    driver: btusb v: 0.8 type: USB rev: 2.1 speed: 480 Mb/s lanes: 1
    bus-ID: 3-3:3 chip-ID: 0489:e0d8
  Report: rfkill ID: hci0 rfk-id: 2 state: up address: see --recommends
Drives:
  Local Storage: total: 953.87 GiB used: 1.19 TiB (128.0%)
  ID-1: /dev/nvme0n1 vendor: Samsung model: MZVL21T0HCLR-00BL2
    size: 953.87 GiB speed: 63.2 Gb/s lanes: 4 serial: S64NNX0T703907
    temp: 41.9 C
Partition:
  Message: No partition data found.
Swap:
  ID-1: swap-1 type: zram size: 8 GiB used: 0 KiB (0.0%) priority: 100
    dev: /dev/zram0
Sensors:
  System Temperatures: cpu: 41.0 C mobo: 40.8 C gpu: amdgpu temp: 41.0 C
  Fan Speeds (rpm): fan-1: 0 fan-2: 0
Info:
  Memory: total: 16 GiB note: est. available: 14.8 GiB used: 4.28 GiB (28.9%)
  Processes: 446 Power: uptime: 6m wakeups: 0 Init: systemd v: 259
    default: graphical
  Packages: pm: rpm pkgs: N/A note: see --rpm Compilers: gcc: 16.1.1
    Shell: Bash v: 5.3.9 running-in: conmon inxi: 3.3.41

I tried Brave and Firefox, Brave with and without Hardware acceleration and Memory saver (something I found on the internet as a possible cure).

I then booted into the live version of the latest MX-Linux (25-2) and did the same test with Brave and Firefox: no artifacts at all. My AMD GPU now has the driver present in the MX kernel, Nvidia use the Nouveau driver.

Posted by @computersavvy
I cannot tell if you are at that kernel intentionally but the inxi shows that you have the 7.1.4-200 with KDE in use.
Fedora now has has released the 7.1.9-200 kernel for f44 and I suggest a full update before even attempting to troubleshoot.

You also stated that you were using nouveau but inxi shows the nvidia driver in use. Which is the fact and which is not?

You highjacked a topic for another user with different hardware and should really open your own topic so your issue may receive assistance on its own. Even if similar your issue appears to be on different hardware.
Posted by @PG-tips
I cannot tell if you are at that kernel intentionally but the inxi shows that you have the 7.1.4-200 with KDE in use.

Looks like that’s the latest kernel in Aurora - Releases · ublue-os/aurora · GitHub

You also stated that you were using nouveau but inxi shows the nvidia driver in use. Which is the fact and which is not?

As I understood it, the MX Linux install is using nouveau.

As @pg-tips already wrote, the Nouveau driver was used when I used the live version of MX-Linux also with the KDE desktop. I was trying to figure out what it could be, feared the hardware, but since MX-Linux shows the same Youtube video without any artifacts I think I can rule out the hardware. Tried 2 browsers which both have the artifacts so it’s also not that. I had it on Kinoite as well, therefore rebased to Aurora which also shows it. I did not see the kernel difference, did not expect them to be honest.

I can start a new thread, that’s no problem, just found this one which, apart from the hardware, shows the same issue as I have. I guess it’s another sign that it’s not the hardware. My guess would be, but I don’t know the internals of the software or how the screen is built-up, it is something Fedora related.

@computersavvy you wrote about codecs. As I wrote I used Kinoite and am using Aurora at the moment with all applications running as flatpaks. I read they all have the necessary codecs installed so no need to install others. Is this correct?

All the bigbuckbunny videos runs without any problems, very smooth and no artifacts whatsoever.

Some more explanations:
I tried both Brave and Firefox with and without hardware acceleration.
I had these artifacts on a fully updated Kinoite, then rebased to Aurora Linux (apparently with an older kernel) where I now have the same issues.
I have booted into MX Linux, once with the Nvidia GPU selected and once with the AMD GPU selected. In both instances both browsers show no artifacts whatsoever. The MX-Linux tests were done with the same laptop and thus the same hardware.

I do apologize for writing in the other thread, it was not my intention to highjack it, but since the subject and several details mentioned in there are similar I just wrote in that thread.

It’s a regression in linux-firmware 20260810. There’s a fix for it in a new mesa update that has not yet reached Fedora or Flathub.

You can work around the issue by disabling hardware video decode acceleration in your browser.

Yes, I have seen that answer before. Thing is when I do that I need to set the volume to very high to be able to hear anything, especially spoken word, above the fan noise. The Lenovo has terrible settings for fancontrol. When I had known that before I bought it, I would probably not have bought it.

You can also look into downgrading the firmware.

For me, I use Fedora Atomic with bootc, so I just chose to use an image from August 4th to avoid the AMD kernel regressions in 7.1.6-7.1.7 and the linux-firmware regression in 20260810.

Are you getting color banding halfway down the image? If not, I don’t think it is the firmware/mesa issue but some other problem. The firmware issue causes color banding halfway across or 1/3rds of the video like it is divided into before and after comparisons. You can check it here: Making sure you're not a bot!

If that IS your problem, however, Mesa 26.2.1 fixes it as according to bugfixes list:

  • RadeonSI VA-API: vertical color discontinuity / split on YouTube (AV1/VP9) with RX 7900 XTX

Another edit:

There seems to another encoding/decoding related bugfix for Mesa 26.2.1:

  • radeonsi/VCN: HEVC VAAPI encode corrupts P-frames on Van Gogh (gfx1033) since Mesa 26.0 — I-frames and H.264 unaffected

I don’t know if either are related to your issues though.

Disabling av1 encoding in my browser fixed this issue fully (for me), though you should re-enable when the mesa update comes out of course

Right now I don’t have either the health nor time to properly read this page, but I found it by chance, and since I too started seeing some artefacts, I wonder if they look like this:

This is the most obvious kind, but not the worst.
In other parts “bands of compressed, moved pixels over frames” create lanes or grids, while other times the image becomes greener or greyer or bluer…

IF we have the same issue, you too can see the same artefacts in this video.
If it’s instead completely unrelated, then good, I just wanted to help and be helped.

Have a nice day.

Yes, this will be fixed in the next Mesa update. Check my post slightly above. Fix has been merged already, all you need to do is wait. Bodhi says tests for Mesa 26.1.8 has passed already so it will be released any day now :slight_smile:

Yes, that is exactly what I see here. Happy to see it’s been worked upon.

As I wrote above in this post that is what I see.

So now it’s just a matter of waiting for the update to arrive. There are worse things so I will survive.
Thank you all for your answers.

I also get other problems with my laptop. Sometimes the whole screen gets white, returns but looks different. For example lines on a webpage are thicker.
In the logs I see a lot of lines with amdgpu, that’s why I thought it might have something to do with it.

Aug 24 06:30:32 Kinoite-Lenovo kernel: amdgpu 0000:34:00.0: [gfxhub] page fault (src_id:0 ring:24 vmid:7 pasid:52)
Aug 24 06:30:32 Kinoite-Lenovo kernel: amdgpu 0000:34:00.0:  Process brave pid 3352 thread brave:cs0 pid 3383
Aug 24 06:30:32 Kinoite-Lenovo kernel: amdgpu 0000:34:00.0:   in page starting at address 0x0000000000000000 from client 0x1b (UTCL2)
Aug 24 06:30:32 Kinoite-Lenovo kernel: amdgpu 0000:34:00.0: GCVM_L2_PROTECTION_FAULT_STATUS:0x00701431
Aug 24 06:30:32 Kinoite-Lenovo kernel: amdgpu 0000:34:00.0:          Faulty UTCL2 client ID: SQC (data) (0xa)
Aug 24 06:30:32 Kinoite-Lenovo kernel: amdgpu 0000:34:00.0:          MORE_FAULTS: 0x1
Aug 24 06:30:32 Kinoite-Lenovo kernel: amdgpu 0000:34:00.0:          WALKER_ERROR: 0x0
Aug 24 06:30:32 Kinoite-Lenovo kernel: amdgpu 0000:34:00.0:          PERMISSION_FAULTS: 0x3
Aug 24 06:30:32 Kinoite-Lenovo kernel: amdgpu 0000:34:00.0:          MAPPING_ERROR: 0x0
Aug 24 06:30:32 Kinoite-Lenovo kernel: amdgpu 0000:34:00.0:          RW: 0x0
Aug 24 06:30:32 Kinoite-Lenovo kernel: amdgpu 0000:34:00.0: [gfxhub] page fault (src_id:0 ring:24 vmid:7 pasid:52)
Aug 24 06:30:32 Kinoite-Lenovo kernel: amdgpu 0000:34:00.0:  Process brave pid 3352 thread brave:cs0 pid 3383
Aug 24 06:30:32 Kinoite-Lenovo kernel: amdgpu 0000:34:00.0:   in page starting at address 0x0000000000000000 from client 0x1b (UTCL2)
Aug 24 06:30:34 Kinoite-Lenovo kernel: amdgpu 0000:34:00.0: Dumping IP State
Aug 24 06:30:34 Kinoite-Lenovo kernel: amdgpu 0000:34:00.0: Dumping IP State Completed
Aug 24 06:30:34 Kinoite-Lenovo kernel: amdgpu 0000:34:00.0: [drm] AMDGPU device coredump file has been created
Aug 24 06:30:34 Kinoite-Lenovo kernel: amdgpu 0000:34:00.0: [drm] Check your /sys/class/drm/card0/device/devcoredump/data
Aug 24 06:30:34 Kinoite-Lenovo kernel: amdgpu 0000:34:00.0: ring gfx_0.1.0 timeout, signaled seq=26467, emitted seq=26469
Aug 24 06:30:34 Kinoite-Lenovo kernel: amdgpu 0000:34:00.0:  Process kwin_wayland pid 2122 thread kwin_wayla:cs0 pid 2164
Aug 24 06:30:34 Kinoite-Lenovo kernel: amdgpu 0000:34:00.0: Starting gfx_0.1.0 ring reset
Aug 24 06:30:34 Kinoite-Lenovo kernel: amdgpu 0000:34:00.0: Ring gfx_0.1.0 reset failed
Aug 24 06:30:34 Kinoite-Lenovo kernel: amdgpu 0000:34:00.0: GPU reset begin!. Source:  1
Aug 24 06:30:34 Kinoite-Lenovo flatpak[3352]: [68:68:0824/063034.870206:ERROR:gpu/command_buffer/service/shared_context_state.cc:1317] SharedContextState context lost via EXT_robustness. Reset status = GL_INNOCENT_CONTEXT_RESET_KHR
Aug 24 06:30:34 Kinoite-Lenovo flatpak[3352]: [68:68:0824/063034.870474:ERROR:components/viz/service/gl/exit_code.cc:13] Restarting GPU process due to unrecoverable error. Context was lost.
Aug 24 06:30:35 Kinoite-Lenovo kernel: amdgpu 0000:34:00.0: MODE2 reset
Aug 24 06:30:35 Kinoite-Lenovo kernel: amdgpu 0000:34:00.0: GPU reset succeeded, trying to resume
Aug 24 06:30:35 Kinoite-Lenovo kernel: amdgpu 0000:34:00.0: [drm] PCIE GART of 1024M enabled (table at 0x000000F41FC00000).
Aug 24 06:30:35 Kinoite-Lenovo kernel: amdgpu 0000:34:00.0: PSP is resuming...
Aug 24 06:30:35 Kinoite-Lenovo kernel: amdgpu 0000:34:00.0: [gfxhub] page fault (src_id:0 ring:24 vmid:7 pasid:52)
Aug 24 06:30:35 Kinoite-Lenovo kernel: amdgpu 0000:34:00.0:  Process brave pid 3352 thread brave:cs0 pid 3383
Aug 24 06:30:35 Kinoite-Lenovo kernel: amdgpu 0000:34:00.0:   in page starting at address 0x0000000000000000 from client 0x1b (UTCL2)
Aug 24 06:30:35 Kinoite-Lenovo kernel: amdgpu 0000:34:00.0: [gfxhub] page fault (src_id:0 ring:24 vmid:7 pasid:52)
Aug 24 06:30:35 Kinoite-Lenovo kernel: amdgpu 0000:34:00.0:  Process brave pid 3352 thread brave:cs0 pid 3383
Aug 24 06:30:35 Kinoite-Lenovo kernel: amdgpu 0000:34:00.0:   in page starting at address 0x0000000000000000 from client 0x1b (UTCL2)
Aug 24 06:30:35 Kinoite-Lenovo kernel: amdgpu 0000:34:00.0: reserve 0xa00000 from 0xf41e000000 for PSP TMR
Aug 24 06:30:35 Kinoite-Lenovo kernel: amdgpu 0000:34:00.0: RAS: optional ras ta ucode is not available
Aug 24 06:30:35 Kinoite-Lenovo kernel: amdgpu 0000:34:00.0: RAP: optional rap ta ucode is not available
Aug 24 06:30:35 Kinoite-Lenovo kernel: amdgpu 0000:34:00.0: SECUREDISPLAY: optional securedisplay ta ucode is not available
Aug 24 06:30:35 Kinoite-Lenovo kernel: amdgpu 0000:34:00.0: SMU is resuming...
Aug 24 06:30:35 Kinoite-Lenovo kernel: amdgpu 0000:34:00.0: SMU is resumed successfully!
Aug 24 06:30:35 Kinoite-Lenovo kernel: amdgpu 0000:34:00.0: kiq ring mec 2 pipe 1 q 0
Aug 24 06:30:35 Kinoite-Lenovo kernel: amdgpu 0000:34:00.0: [drm] DMUB hardware initialized: version=0x0400004C
Aug 24 06:30:35 Kinoite-Lenovo kernel: amdgpu 0000:34:00.0: ring gfx_0.0.0 uses VM inv eng 0 on hub 0
Aug 24 06:30:35 Kinoite-Lenovo kernel: amdgpu 0000:34:00.0: ring gfx_0.1.0 uses VM inv eng 1 on hub 0
Aug 24 06:30:35 Kinoite-Lenovo kernel: amdgpu 0000:34:00.0: ring comp_1.0.0 uses VM inv eng 4 on hub 0
Aug 24 06:30:35 Kinoite-Lenovo kernel: amdgpu 0000:34:00.0: ring comp_1.1.0 uses VM inv eng 5 on hub 0
Aug 24 06:30:35 Kinoite-Lenovo kernel: amdgpu 0000:34:00.0: ring comp_1.2.0 uses VM inv eng 6 on hub 0
Aug 24 06:30:35 Kinoite-Lenovo kernel: amdgpu 0000:34:00.0: ring comp_1.3.0 uses VM inv eng 7 on hub 0
Aug 24 06:30:35 Kinoite-Lenovo kernel: amdgpu 0000:34:00.0: ring comp_1.0.1 uses VM inv eng 8 on hub 0
Aug 24 06:30:35 Kinoite-Lenovo kernel: amdgpu 0000:34:00.0: ring comp_1.1.1 uses VM inv eng 9 on hub 0
Aug 24 06:30:35 Kinoite-Lenovo kernel: amdgpu 0000:34:00.0: ring comp_1.2.1 uses VM inv eng 10 on hub 0
Aug 24 06:30:35 Kinoite-Lenovo kernel: amdgpu 0000:34:00.0: ring comp_1.3.1 uses VM inv eng 11 on hub 0
Aug 24 06:30:35 Kinoite-Lenovo kernel: amdgpu 0000:34:00.0: ring kiq_0.2.1.0 uses VM inv eng 12 on hub 0
Aug 24 06:30:35 Kinoite-Lenovo kernel: amdgpu 0000:34:00.0: ring sdma0 uses VM inv eng 13 on hub 0
Aug 24 06:30:35 Kinoite-Lenovo kernel: amdgpu 0000:34:00.0: ring vcn_dec_0 uses VM inv eng 0 on hub 8
Aug 24 06:30:35 Kinoite-Lenovo kernel: amdgpu 0000:34:00.0: ring vcn_enc_0.0 uses VM inv eng 1 on hub 8
Aug 24 06:30:35 Kinoite-Lenovo kernel: amdgpu 0000:34:00.0: ring vcn_enc_0.1 uses VM inv eng 4 on hub 8
Aug 24 06:30:35 Kinoite-Lenovo kernel: amdgpu 0000:34:00.0: ring jpeg_dec uses VM inv eng 5 on hub 8
Aug 24 06:30:35 Kinoite-Lenovo kernel: amdgpu 0000:34:00.0: GPU reset(1) succeeded!
Aug 24 06:30:35 Kinoite-Lenovo kernel: amdgpu 0000:34:00.0: [drm] device wedged, but no recovery needed
Aug 24 06:30:35 Kinoite-Lenovo flatpak[3271]: [2:2:0824/063035.878004:ERROR:content/browser/gpu/gpu_process_host.cc:1035] GPU process exited unexpectedly: exit_code=8704
Aug 24 06:30:35 Kinoite-Lenovo kwin_wayland[2122]: 0x3: GL_CONTEXT_LOST in context lost
Aug 24 06:30:35 Kinoite-Lenovo kwin_wayland[2122]: 0x3: GL_CONTEXT_LOST in context lost
Aug 24 06:30:35 Kinoite-Lenovo kwin_wayland[2122]: 0x3: GL_CONTEXT_LOST in context lost
Aug 24 06:30:35 Kinoite-Lenovo kernel: amdgpu 0000:34:00.0: [drm] *ERROR* Failed to initialize parser -125!
Aug 24 06:30:35 Kinoite-Lenovo kwin_wayland[2122]: 0x3: GL_CONTEXT_LOST in context lost
Aug 24 06:30:35 Kinoite-Lenovo kwin_wayland[2122]: 0x3: GL_CONTEXT_LOST in context lost
Aug 24 06:30:35 Kinoite-Lenovo kwin_wayland[2122]: 0x3: GL_CONTEXT_LOST in context lost
Aug 24 06:30:35 Kinoite-Lenovo kwin_wayland[2122]: 0x3: GL_CONTEXT_LOST in context lost
Aug 24 06:30:35 Kinoite-Lenovo kwin_wayland[2122]: 0x3: GL_CONTEXT_LOST in context lost
Aug 24 06:30:35 Kinoite-Lenovo kwin_wayland[2122]: 0x3: GL_CONTEXT_LOST in context lost
Aug 24 06:30:35 Kinoite-Lenovo kwin_wayland[2122]: 0x3: GL_CONTEXT_LOST in context lost
Aug 24 06:30:35 Kinoite-Lenovo kwin_wayland[2122]: 0x3: GL_CONTEXT_LOST in context lost
Aug 24 06:30:35 Kinoite-Lenovo kwin_wayland[2122]: 0x3: GL_CONTEXT_LOST in context lost
Aug 24 06:30:35 Kinoite-Lenovo kwin_wayland[2122]: 0x3: GL_CONTEXT_LOST in context lost
Aug 24 06:30:35 Kinoite-Lenovo kwin_wayland[2122]: 0x3: GL_CONTEXT_LOST in context lost
Aug 24 06:30:35 Kinoite-Lenovo kwin_wayland[2122]: 0x3: GL_CONTEXT_LOST in context lost
Aug 24 06:30:35 Kinoite-Lenovo kwin_wayland[2122]: 0x3: GL_CONTEXT_LOST in context lost
Aug 24 06:30:35 Kinoite-Lenovo kwin_wayland[2122]: 0x3: GL_CONTEXT_LOST in context lost
Aug 24 06:30:35 Kinoite-Lenovo kwin_wayland[2122]: 0x3: GL_CONTEXT_LOST in context lost
Aug 24 06:30:35 Kinoite-Lenovo kwin_wayland[2122]: 0x3: GL_CONTEXT_LOST in context lost
Aug 24 06:30:35 Kinoite-Lenovo kwin_wayland[2122]: 0x3: GL_CONTEXT_LOST in context lost
Aug 24 06:30:35 Kinoite-Lenovo kwin_wayland[2122]: 0x3: GL_CONTEXT_LOST in context lost
Aug 24 06:30:35 Kinoite-Lenovo kwin_wayland[2122]: 0x3: GL_CONTEXT_LOST in context lost
Aug 24 06:30:35 Kinoite-Lenovo kwin_wayland[2122]: 0x3: GL_CONTEXT_LOST in context lost
Aug 24 06:30:35 Kinoite-Lenovo kwin_wayland[2122]: 0x3: GL_CONTEXT_LOST in context lost
Aug 24 06:30:35 Kinoite-Lenovo kwin_wayland[2122]: 0x3: GL_CONTEXT_LOST in context lost
Aug 24 06:30:35 Kinoite-Lenovo kwin_wayland[2122]: 0x3: GL_CONTEXT_LOST in context lost
Aug 24 06:30:35 Kinoite-Lenovo kwin_wayland[2122]: 0x3: GL_CONTEXT_LOST in context lost
Aug 24 06:30:35 Kinoite-Lenovo kwin_wayland[2122]: 0x3: GL_CONTEXT_LOST in context lost
Aug 24 06:30:35 Kinoite-Lenovo kwin_wayland[2122]: 0x3: GL_CONTEXT_LOST in context lost
Aug 24 06:30:35 Kinoite-Lenovo kwin_wayland[2122]: 0x3: GL_CONTEXT_LOST in context lost
Aug 24 06:30:35 Kinoite-Lenovo kwin_wayland[2122]: 0x3: GL_CONTEXT_LOST in context lost
Aug 24 06:30:35 Kinoite-Lenovo kwin_wayland[2122]: 0x3: GL_CONTEXT_LOST in context lost
Aug 24 06:30:35 Kinoite-Lenovo kwin_wayland[2122]: A graphics reset not attributable to the current GL context occurred.
Aug 24 06:30:35 Kinoite-Lenovo kwin_wayland[2122]: 0x3: GL_CONTEXT_LOST in context lost
Aug 24 06:30:35 Kinoite-Lenovo kwin_wayland[2122]: 0x3: GL_CONTEXT_LOST in context lost
Aug 24 06:30:35 Kinoite-Lenovo kwin_wayland[2122]: 0x3: GL_CONTEXT_LOST in context lost
Aug 24 06:30:35 Kinoite-Lenovo kwin_wayland[2122]: 0x3: GL_CONTEXT_LOST in context lost
Aug 24 06:30:35 Kinoite-Lenovo kwin_wayland[2122]: 0x3: GL_CONTEXT_LOST in context lost
Aug 24 06:30:35 Kinoite-Lenovo kwin_wayland[2122]: 0x3: GL_CONTEXT_LOST in context lost
Aug 24 06:30:35 Kinoite-Lenovo kwin_wayland[2122]: 0x3: GL_CONTEXT_LOST in context lost
Aug 24 06:30:35 Kinoite-Lenovo kwin_wayland[2122]: 0x3: GL_CONTEXT_LOST in context lost
Aug 24 06:30:35 Kinoite-Lenovo kwin_wayland[2122]: 0x3: GL_CONTEXT_LOST in context lost
Aug 24 06:30:35 Kinoite-Lenovo kwin_wayland[2122]: 0x3: GL_CONTEXT_LOST in context lost
Aug 24 06:30:35 Kinoite-Lenovo kwin_wayland[2122]: 0x3: GL_CONTEXT_LOST in context lost
Aug 24 06:30:35 Kinoite-Lenovo kwin_wayland[2122]: 0x3: GL_CONTEXT_LOST in context lost
Aug 24 06:30:35 Kinoite-Lenovo kwin_wayland[2122]: 0x3: GL_CONTEXT_LOST in context lost
Aug 24 06:30:35 Kinoite-Lenovo kwin_wayland[2122]: 0x3: GL_CONTEXT_LOST in context lost
Aug 24 06:30:35 Kinoite-Lenovo kwin_wayland[2122]: 0x3: GL_CONTEXT_LOST in context lost
Aug 24 06:30:35 Kinoite-Lenovo kwin_wayland[2122]: 0x3: GL_CONTEXT_LOST in context lost
Aug 24 06:30:35 Kinoite-Lenovo kwin_wayland[2122]: 0x3: GL_CONTEXT_LOST in context lost
Aug 24 06:30:35 Kinoite-Lenovo kwin_wayland[2122]: 0x3: GL_CONTEXT_LOST in context lost
Aug 24 06:30:35 Kinoite-Lenovo kwin_wayland[2122]: 0x3: GL_CONTEXT_LOST in context lost
Aug 24 06:30:35 Kinoite-Lenovo kwin_wayland[2122]: 0x3: GL_CONTEXT_LOST in context lost
Aug 24 06:30:35 Kinoite-Lenovo kwin_wayland[2122]: 0x3: GL_CONTEXT_LOST in context lost
Aug 24 06:30:35 Kinoite-Lenovo kwin_wayland[2122]: 0x3: GL_CONTEXT_LOST in context lost
Aug 24 06:30:35 Kinoite-Lenovo kwin_wayland[2122]: 0x3: GL_CONTEXT_LOST in context lost
Aug 24 06:30:35 Kinoite-Lenovo kwin_wayland[2122]: 0x3: GL_CONTEXT_LOST in context lost
Aug 24 06:30:35 Kinoite-Lenovo kwin_wayland[2122]: 0x3: GL_CONTEXT_LOST in context lost
Aug 24 06:30:35 Kinoite-Lenovo kwin_wayland[2122]: 0x3: GL_CONTEXT_LOST in context lost
Aug 24 06:30:35 Kinoite-Lenovo kwin_wayland[2122]: 0x3: GL_CONTEXT_LOST in context lost
Aug 24 06:30:35 Kinoite-Lenovo kwin_wayland[2122]: 0x3: GL_CONTEXT_LOST in context lost
Aug 24 06:30:35 Kinoite-Lenovo kwin_wayland[2122]: 0x3: GL_CONTEXT_LOST in context lost
Aug 24 06:30:35 Kinoite-Lenovo kwin_wayland[2122]: 0x3: GL_CONTEXT_LOST in context lost
Aug 24 06:30:35 Kinoite-Lenovo kwin_wayland[2122]: 0x3: GL_CONTEXT_LOST in context lost
Aug 24 06:30:35 Kinoite-Lenovo kwin_wayland[2122]: 0x3: GL_CONTEXT_LOST in context lost
Aug 24 06:30:35 Kinoite-Lenovo kwin_wayland[2122]: 0x3: GL_CONTEXT_LOST in context lost
Aug 24 06:30:35 Kinoite-Lenovo kwin_wayland[2122]: 0x3: GL_CONTEXT_LOST in context lost
Aug 24 06:30:35 Kinoite-Lenovo kwin_wayland[2122]: 0x3: GL_CONTEXT_LOST in context lost
Aug 24 06:30:35 Kinoite-Lenovo kwin_wayland[2122]: 0x3: GL_CONTEXT_LOST in context lost
Aug 24 06:30:35 Kinoite-Lenovo kwin_wayland[2122]: 0x3: GL_CONTEXT_LOST in context lost
Aug 24 06:30:35 Kinoite-Lenovo kwin_wayland[2122]: 0x3: GL_CONTEXT_LOST in context lost
Aug 24 06:30:35 Kinoite-Lenovo kwin_wayland[2122]: 0x3: GL_CONTEXT_LOST in context lost
Aug 24 06:30:35 Kinoite-Lenovo kwin_wayland[2122]: 0x3: GL_CONTEXT_LOST in context lost
Aug 24 06:30:35 Kinoite-Lenovo kwin_wayland[2122]: 0x3: GL_CONTEXT_LOST in context lost
Aug 24 06:30:35 Kinoite-Lenovo kwin_wayland[2122]: 0x3: GL_CONTEXT_LOST in context lost
Aug 24 06:30:35 Kinoite-Lenovo kwin_wayland[2122]: 0x3: GL_CONTEXT_LOST in context lost
Aug 24 06:30:35 Kinoite-Lenovo kwin_wayland[2122]: 0x3: GL_CONTEXT_LOST in context lost
Aug 24 06:30:35 Kinoite-Lenovo kwin_wayland[2122]: 0x3: GL_CONTEXT_LOST in context lost
Aug 24 06:30:35 Kinoite-Lenovo kwin_wayland[2122]: 0x3: GL_CONTEXT_LOST in context lost
Aug 24 06:30:35 Kinoite-Lenovo kwin_wayland[2122]: 0x3: GL_CONTEXT_LOST in context lost
Aug 24 06:30:35 Kinoite-Lenovo kwin_wayland[2122]: Could not delete render time query because no context is current
Aug 24 06:30:35 Kinoite-Lenovo kwin_wayland[2122]: Could not delete render time query because no context is current
Aug 24 06:30:45 Kinoite-Lenovo systemd[2015]: Starting grub-boot-success.service - Mark boot as successful...
Aug 24 06:30:45 Kinoite-Lenovo systemd[2015]: Finished grub-boot-success.service - Mark boot as successful.
Aug 24 06:30:46 Kinoite-Lenovo systemd[2015]: Started app-org.kde.konsole@7ec404c2da254706a70c7c6d6a23863b.service - Konsole - Terminal.
Aug 24 06:30:46 Kinoite-Lenovo flatpak[2737]: [06:30:46.383] [DBG] PwPipelineManager::on_destroy_node_proxy: Stream/Output/Audio 107 Brave has been removed
Aug 24 06:30:46 Kinoite-Lenovo flatpak[2737]: [06:30:46.384] [DBG] PwPipelineManager::on_metadata_property: new metadata property: 107, , , 
Aug 24 06:30:46 Kinoite-Lenovo systemd[2015]: Started app-org.kde.konsole-4001.scope.

Is this related to the artifacts on screen or is this something completely different?

Btw, I am back on Kinoite.

This is the last post that I will leave here:

I tested the video on a phone and it doesn’t happen there, but it’s indeed strange because this is basically the only video where I saw any artefact at all.

Welp, we now only have to wait…

I just started getting this bug after updating today. Not sure what update caused it.

I wonder why this bug only seems to specifically affect the RX 7900 XTX? That’s weird. Usually a bug like this seems to go by card generations at the very least.

It’s not just 7900xtx indeed, that’s just what the initial test was performed on. It affects RDNA 3 and 4 at the very least.

Rx 6650 xt here.

Also my computer exploded.

I slept and feel better now (to work on it), but it won’t be easier…

@isaac0clarke I’m sorry you have serious issues with your computer and I hope someone can help you to get it fixed. But please do not promote your topic in other topics: that’s off-topic and blurs/distracts the problem-solving of others.

A general suggestion from my side concerning your topic: cut down the text in your topic, and limit the text to the actual problem. The less text there is, the more people will read it, and the clearer the actual problem will be to them. Especially if people are no English natives, it can be hard to distinguish. Hope that helps. All the best!

I both thought the two issues could be correlated, and also said that “my situation changed”.

My browsers made the PC lag, freeze, and either restart or need an hard reset.

I can’t know how others are experiencing it, and I am not updating my other PCs in fear of the same thing happening.

This morning I installed the latest Kinoite update and, well maybe it is still too early to tell, the Youtube picture quality has improved. Now the artifacts are gone and it’s back too normal.
I will keep watching it and report if something is not good yet.

Thanks to whoever fixed it.

No, I shouted too early. In another video I still see the same artifacts happening, so it seems it is not fixed yet.

Everything looks normal here on Workstation (non-atomic). Here’s the vulkaninfo result:

deviceName         = AMD Radeon RX 7600 (RADV NAVI33)
	driverID           = DRIVER_ID_MESA_RADV
	driverName         = radv
	driverInfo         = Mesa 26.1.8

Can you check if you are indeed on 26.1.8? Do not check it using LACT as that will show you the runtime that flatpak uses, which might be older. The command is:

vulkaninfo --summary

Also, can you send the link to the problematic video so I can double check?

This is what I get as answer:

vulkaninfo --summary
WARNING: [Loader Message] Code 0 : terminator_CreateInstance: Received return code -9 from call to vkCreateInstance in ICD /usr/lib64/libvulkan_dzn.so. Skipping this driver.
WARNING: [Loader Message] Code 0 : ICD for selected physical device does not export vkGetPhysicalDeviceDisplayPlanePropertiesKHR!
WARNING: [Loader Message] Code 0 : ICD for selected physical device does not export vkGetPhysicalDeviceDisplayPropertiesKHR!
==========
VULKANINFO
==========

Vulkan Instance Version: 1.4.341


Instance Extensions: count = 27
-------------------------------
VK_EXT_acquire_drm_display             : extension revision 1
VK_EXT_acquire_xlib_display            : extension revision 1
VK_EXT_debug_report                    : extension revision 10
VK_EXT_debug_utils                     : extension revision 2
VK_EXT_direct_mode_display             : extension revision 1
VK_EXT_display_surface_counter         : extension revision 1
VK_EXT_headless_surface                : extension revision 1
VK_EXT_layer_settings                  : extension revision 2
VK_EXT_surface_maintenance1            : extension revision 1
VK_EXT_swapchain_colorspace            : extension revision 5
VK_KHR_device_group_creation           : extension revision 1
VK_KHR_display                         : extension revision 23
VK_KHR_external_fence_capabilities     : extension revision 1
VK_KHR_external_memory_capabilities    : extension revision 1
VK_KHR_external_semaphore_capabilities : extension revision 1
VK_KHR_get_display_properties2         : extension revision 1
VK_KHR_get_physical_device_properties2 : extension revision 2
VK_KHR_get_surface_capabilities2       : extension revision 1
VK_KHR_portability_enumeration         : extension revision 1
VK_KHR_surface                         : extension revision 25
VK_KHR_surface_maintenance1            : extension revision 1
VK_KHR_surface_protected_capabilities  : extension revision 1
VK_KHR_wayland_surface                 : extension revision 6
VK_KHR_xcb_surface                     : extension revision 6
VK_KHR_xlib_surface                    : extension revision 6
VK_LUNARG_direct_driver_loading        : extension revision 1
VK_NV_display_stereo                   : extension revision 1

Instance Layers: count = 3
--------------------------
VK_LAYER_MESA_device_select Linux device selection layer 1.4.303  version 1
VK_LAYER_NV_optimus         NVIDIA Optimus layer         1.4.341  version 1
VK_LAYER_NV_present         NVIDIA Presentation Layer    1.4.341  version 1

Devices:
========
GPU0:
        apiVersion         = 1.4.354
        driverVersion      = 26.1.8
        vendorID           = 0x1002
        deviceID           = 0x1681
        deviceType         = PHYSICAL_DEVICE_TYPE_INTEGRATED_GPU
        deviceName         = AMD Radeon 680M (RADV REMBRANDT)
        driverID           = DRIVER_ID_MESA_RADV
        driverName         = radv
        driverInfo         = Mesa 26.1.8
        conformanceVersion = 1.4.0.0
        deviceUUID         = 00000000-3400-0000-0000-000000000000
        driverUUID         = 414d442d-4d45-5341-2d44-525600000000
GPU1:
        apiVersion         = 1.4.341
        driverVersion      = 610.57.4.0
        vendorID           = 0x10de
        deviceID           = 0x2560
        deviceType         = PHYSICAL_DEVICE_TYPE_DISCRETE_GPU
        deviceName         = NVIDIA GeForce RTX 3060 Laptop GPU
        driverID           = DRIVER_ID_NVIDIA_PROPRIETARY
        driverName         = NVIDIA
        driverInfo         = 610.57.04
        conformanceVersion = 1.4.3.3
        deviceUUID         = 2fb09eda-d50e-3cc2-4a7f-06c922302a99
        driverUUID         = 9992f558-9329-580d-a9f3-a38ee24bc64d
GPU2:
        apiVersion         = 1.4.354
        driverVersion      = 26.1.8
        vendorID           = 0x10005
        deviceID           = 0x0000
        deviceType         = PHYSICAL_DEVICE_TYPE_CPU
        deviceName         = llvmpipe (LLVM 22.1.8, 256 bits)
        driverID           = DRIVER_ID_MESA_LLVMPIPE
        driverName         = llvmpipe
        driverInfo         = Mesa 26.1.8 (LLVM 22.1.8)
        conformanceVersion = 1.3.1.1
        deviceUUID         = 6d657361-3236-2e31-2e38-000000000000
        driverUUID         = 6c6c766d-7069-7065-5555-494400000000

It looks to me I am using 26.1.8.

Yeah, you are indeed. Can you link me the video you’re having a problem with so I can check as well. Maybe there are edge cases they haven’t detected yet.