Youtube - Colour switching/glitching since update on 3rd September

English Multimedia
1

Hello! Since I updated (sudo zypper dup) on 3rd September, Youtube has been experiencing odd visual playback with the colours are switching strangely. I have recorded a video from my browser to demonstrate rather than me trying to describe it: https://k00.fr/ygtu2ytq

If I disable hardware acceleration, the issue goes away.
If I enter my snapshot from 2nd September, the issue goes away.
The issue remains in other browsers with acceleration as well.
I’ve not noticed any issues anywhere else such as when gaming or general web browsing, it seems to be only when using youtube.

I am unsure which information is relevant, I do not use Packman and rely on a Flatpak of Firefox (and begrudgingly, Edge). I have an AMD 9070XT.

My most recent snapshots are from these times:

677  │ pre    │       │ Wed 02 Sep 2026 08:03:06 BST │ root │   6.89 MiB │ number  │ zypp(zypper)            │ important=yes
678  │ post   │   677 │ Wed 02 Sep 2026 08:03:45 BST │ root │ 448.00 KiB │ number  │                         │ important=yes
679  │ pre    │       │ Wed 02 Sep 2026 08:05:07 BST │ root │ 192.00 KiB │ number  │ zypp(zypper)            │ important=yes
680- │ post   │   679 │ Wed 02 Sep 2026 08:05:09 BST │ root │ 400.00 KiB │ number  │                         │ important=yes
681  │ pre    │       │ Thu 03 Sep 2026 08:05:08 BST │ root │  11.64 MiB │ number  │ zypp(zypper)            │ important=yes
682  │ post   │   681 │ Thu 03 Sep 2026 08:06:06 BST │ root │  13.53 MiB │ number  │                         │ important=yes
683  │ pre    │       │ Sat 05 Sep 2026 08:53:25 BST │ root │  17.61 MiB │ number  │ zypp(zypper)            │ important=yes
684  │ post   │   683 │ Sat 05 Sep 2026 08:54:31 BST │ root │   3.64 MiB │ number  │                         │ important=yes

(680 being the most recent one with no issues, all newer ones exhibit the problem)

The original video from my recoding is here (with a timestamp): https://youtu.be/tXZ-OP6kpLs?si=_U1AzTp1qYYzieVh&t=175

Here are the repos I have configured:


# | Alias                            | Name                                   | Enabled | GPG Check | Refresh
--+----------------------------------+----------------------------------------+---------+-----------+--------
1 | download.opensuse.org-non-oss    | Main Repository (NON-OSS)              | Yes     | ( p) Yes  | Yes
2 | download.opensuse.org-oss        | Main Repository (OSS)                  | Yes     | ( p) Yes  | Yes
3 | download.opensuse.org-tumbleweed | Main Update Repository                 | Yes     | ( p) Yes  | Yes
4 | openSUSE-20260103-0              | openSUSE-20260103-0                    | No      | ----      | ----
5 | repo-debug                       | openSUSE-Tumbleweed-Debug              | No      | ----      | ----
6 | repo-openh264                    | Open H.264 Codec (openSUSE Tumbleweed) | Yes     | ( p) Yes  | Yes
7 | repo-source                      | openSUSE-Tumbleweed-Source             | No      | ----      | ----

Any help on this issue would be appreciated, though I suspect this is merely a bad update, though I’ve been unable to find anyone else complaining about this problem anywhere.

2

In snapshot 20260901 I see kernel-firmware-amdgpu (20260717 -> 20260829) and possibly glibc (2.43 -> 2.44) that might have an impact on what you see.
Maybe locking those two and upgrading can narrow down the suspect list.

3

Thanks, locking kernel-firmware-amdgpu and updating everything else does not exhibit the problem (aka, it’s “fixed”), so it may be this kernel update that has caused it for me. I did also attempt to lock glibc, but as expected there are many dependencies and it was beginning to look like a minefield, so I only locked the amdgpu update.

I’ll probably stick on this for a while until a future update and see if it has been fixed.

4

There is a new build of the same version here: kernel-firmware-amdgpu-20260829-2.1.noarch.rpm if you like tweaking…
Otherwise a bug report at bugzilla.opensuse.org might be the way to go (same username and password as here for the Forums).

1 Like
5

Bug filed: https://bugzilla.opensuse.org/show_bug.cgi?id=1279434

6

I checked kernel 20260904 but it has the same issue, so it seems as though it’s a problem further upstream.
Someone else reported an identical issue a few days ago whilst using Fedora: https://gitlab.freedesktop.org/drm/amd/-/work_items/5764

It’s now a waiting game to see if someone can resolve it.

7

I can confirm this issue (at least in my case) has been resolved in the latest snapshot which contains kernel-firmware-amdgpu 20260926-1.1.

8

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.