[amdgpu] Random noise 'static' display after internal display turned off/on

[James Ferguson]

Laptop internal display shows random looking 'static' after it's turned off and then on again. e.g. on suspend/resume, or when plugging/unplugging an external monitor.

This appeared to come after a `dist-upgrade` took the kernel from 5.11.0-44 to 5.13.0-25 (hwe).

Others are seeing this with both NVidia and AMD graphics hardware:
- https://www.reddit.com/r/Ubuntu/comments/s8c83w/laptop_shows_static_screen_after_going_into_lock/
- https://www.reddit.com/r/Ubuntu/comments/s8fit0/please_help_static_noise_display_on_ubuntu_2004/

I use i3 under gnome-flashback, but tried using default Ubuntu/Gnome both X and Wayland, and gnome-flashback/metacity. All showed the same problem.

Also tried an `apt install --reinstall xserver-xorg-video-radeon libdrm-radeon1` for luck - no joy.

Running a 20.04.3 live stick the problem does *not* occur.

System: Thinkpad X13 Gen1
Processor: AMD Ryzen 7 PRO 4750U
System Firmware: 1.35

$ lsb_release -rd
Description: Ubuntu 20.04.3 LTS
Release: 20.04

Happy to assist with investigations.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.13.0-27.29~20.04.1-generic 5.13.19
Uname: Linux 5.13.0-27-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.21
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: i3-GNOME-Flashback:GNOME-Flashback:GNOME
Date: Thu Jan 20 19:37:09 2022
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev d1) (prog-if 00 [VGA controller])
   Subsystem: Lenovo Renoir [17aa:5082]
InstallationDate: Installed on 2021-06-24 (210 days ago)
InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1)
MachineType: LENOVO 20UF0014US
ProcEnviron:
 TERM=screen-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-27-generic root=UUID=5db0269f-fa23-487e-ace8-ba99bca814a8 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/20/2021
dmi.bios.release: 1.36
dmi.bios.vendor: LENOVO
dmi.bios.version: R1CET67W(1.36 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20UF0014US
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40697 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.36
dmi.modalias: dmi:bvnLENOVO:bvrR1CET67W(1.36):bd10/20/2021:br1.36:efr1.36:svnLENOVO:pn20UF0014US:pvrThinkPadX13Gen1:rvnLENOVO:rn20UF0014US:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20UF_BU_Think_FM_ThinkPadX13Gen1:
dmi.product.family: ThinkPad X13 Gen 1
dmi.product.name: 20UF0014US
dmi.product.sku: LENOVO_MT_20UF_BU_Think_FM_ThinkPad X13 Gen 1
dmi.product.version: ThinkPad X13 Gen 1
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.105-3~20.04.2
version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3~20.04.5
version.libgl1-mesa-glx: libgl1-mesa-glx 21.0.3-0ubuntu0.3~20.04.5
version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

[James Ferguson (jamesf)]

Note: I did not report this as an Xorg display issue as it happened when I logged in with Wayland.

[James Ferguson (jamesf)]

The duplication of this to https://bugs.launchpad.net/bugs/1958412 is not appropriate I think.

* I do not have the symptoms described in the other bug
* The workaround described there (remove `quiet` from grub command line, plus `update-grub` of course) does not help, unsuprisingly.

Also the `[amdcpu]` addition to the title seems inappropriate since people seem to have the same issue on NVidia.

To be clear: the other issue is random display noise during boot and shutdown. I do not see that. The other bug does not mention this bug's symptom, which is an unusable display if it's ever turned off and then on again (e.g. by suspend/resume, or external monitor plug/unplug).

[James Ferguson (jamesf)]

To be clear - the display shows static and never returns. This is not a transient issue. The display is only usable from first boot until it is first turned off, after which it only displays static.

So this is a serious bug, especially if you don't have an external monitor, your only option is a hard reset.

[Cortland Mahoney (ckmahoney)]

Good morning,

Chiming in to say that I am experiencing the issue exactly as described.

Going into lock screen or leaving the device idle (no mouse or keyboard input for about 1 minute) is enough to trigger this unique display error.

Here is a link to an unlisted YouTube video, 35 seconds long, showing the buggy display:

https://www.youtube.com/watch?v=Vaqp7alieKk&feature=youtu.be

$ lsb_release -rd
Description: Ubuntu 20.04.3 LTS
Release: 20.04

as OP jamesf said, the internal display can only be recovered by a hard reboot.

Happy to help test solutions, thank you

Cortland

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Joshua Hewitt (sposhua)]

+1, I have the same issue as here, and not #1958412 (grub workaround described there doesn't fix the issue). Though maybe it is marked as duplicate if the underlying issue is the same in both cases...

[James Ferguson (jamesf)]

Trouble with the duplicate status is the other issue has mostly cosmetic consequences and a workaround, while this has neither of those things and it could get lost that this is a critical problem.

It does seem like more than coincidence that the new kernel has brought two (or more) screen-noise problems. I wouldn't be surprised if there is a common underlying issue.

[Peter Berta (peter-berta)]

I have exactly the same issue as here, and not #1958412

[Hawajka Zla (hawajka76)]

I also have the same issue on an AMD RENOIR based system:
I'm attaching output of glxinfo -B.
Kernel version is 5.13.0-27-generic

[Daniel van Vugt (vanvugt)]

This is almost certainly bug 1958412, which was the first to report the static noise regression on the amdgpu driver after kernel 5.13 was introduced to Ubuntu 20.04.

Also ignore all comments that mention Nvidia because GNOME and Ubuntu only uses the primary GPU for shell rendering. Never the secondary GPU.

Having just this bug separate when all the other reports of it are pointing to bug 1958412 probably won't help you.

[yolen (plasmajens)]

I have exactly the same as in https://www.youtube.com/watch?v=Vaqp7alieKk&feature=youtu.be. very serious bug !!

Lenovo t14s, and ryzen

[Aaron Kriegman (broses)]

I'm thinking of trying to roll back my software so that I can continue using my computer until this is fixed. Can anyone recommend which package I should try rolling back, or how I should go about this?

[James Ferguson (jamesf)]

There may be better ways to downgrade the kernel(?), but what I've done is re-install the previous 5.11 kernel:

  sudo apt install linux-image-5.11.0-46-generic linux-headers-5.11.0-46-generic linux-modules-extra-5.11.0-46-generic

Then edit /etc/default/grub to change the GRUB_DEFAULT line to select this kernel by default:

  GRUB_DEFAULT="Advanced options for Ubuntu>Ubuntu, with Linux 5.11.0-46-generic"

and then run `sudo update-grub` and reboot. Now `uname -r` shows 5.11.0-46-generic.

This will lock you on that kernel forever (no security patches!). You should watch these launchpad bugs for changes to know when to undo it. Undo the change by returning /etc/default/grub to having `GRUB_DEFAULT=0` and re-running `sudo update-grub`. Once everything is back to normal you can then `apt purge` the packages above installed with `apt install`.

[Aaron Kriegman (broses)]

Thanks, booting into a different kernel version worked. I installed 5.11.0-46 like you said, but then when I went into advanced options in my boot menu there were three versions listed, so maybe I didn't have to do that. I also didn't bother changing my grub default. I'll just choose my kernel manually every time I restart, and when it's time to go back to normal I just have to stop doing that. Thank you for the advice!

[James Ferguson (jamesf)]

Scanning the duplicates, just to collect some info we have

Bugs mentioning or showing "Static" pattern of display at either boot or suspend, mostly on Renoir 1636

#1959340: Thinkpad X13; [AMD/ATI] Renoir [1002:1636] (rev d1) (same hardware as this bug)
#1958248: HP Envy x360; [AMD/ATI] Renoir [1002:1636] (rev c2)
#1958412: VivoBook_ASUSLaptop TP420UA_TM420UA [AMD/ATI] Device [1002:164c] (rev c2)
#1958631: HP Pavilion Gaming Laptop 15-ec1xxx; [AMD/ATI] Renoir [1002:1636] (rev c6)

"Blinking / Flickering, rather than static reported, devices other than 1636:

#1958523: ???? [AMD/ATI] Stoney [Radeon R2/R3/R4/R5 Graphics] [1002:98e4]
#1958823: LENOVO 82KT IdeaPad 3 "blinking/flickering"; [AMD/ATI] Device [1002:164c] (rev c1)
#1958890: Ideapad 3 "Blinking/Flickering"; [AMD/ATI] Device [1002:164c] (rev c1)

While it has to be a strong probability it's all one issue, there is a bit of a split between static on 1636 devices and blinking/flickering on others. Note the non-1636 bug in the "static" list seems slightly different and the static occurs from different triggers, but then that's hardly surprising with a different device even if it's one issue.

[Kartik Agaram (akkartik)]

I reported #1959340, and to clarify, what I see _could_ be characterized as flickering. I called it "snow" in my report to compare it to the reception from a TV with a terrestrial antenna. Each pixel on the screen seems to get constantly changing rgb values.

One thing I've noticed is that the right side of my 16:9 gets _lines_ with constantly changing rgb values.

I can catch it on video if that's helpful.

[James Ferguson (jamesf)]

@akkartik - I assume yours was the same as my https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.13/+bug/1958591/+attachment/5555993/+files/PXL_20220119_165211771.jpg, since we have I think identical machines.

Personally I'd have assumed anything described as "flickering" to be different, since the underlying screen image is not even visible. But it could be that some of the bugs I listed separately actually saw this "static" / "colored snow" display. I think not everyone sees the vertical bars on the right that we do.

[Kartik Agaram (akkartik)]

True, I can't see anything of the underlying desktop.

[Mariusz (mapniv)]

I made a experiment and I can confirm static noise after waking from suspend.

@jamesf My device model is Lenovo Ideapad 320. You can update your post.

I will copy my other post since we are tracking this bug here: When your computer boots press escape (UEFI boot) or shift (BIOS boot). You may have to try several times to press it in right time. A menu should appear. Choose option 'Advanced options for Ubuntu'. Then choose 'Ubuntu, with Linux 5.11.0-46-generic'.

Then you can follow instructions in post #15 to boot with Linux 5.11.0 by default.

[James Ferguson (jamesf)]

Note I reported this on a Thinkpad X13 Gen 1; Ryzen 7 4750U; [AMD/ATI] Renoir [1002:1636] (rev d1) graphics.

On X13 Gen 2; Ryzen 7, 5850U; [AMD/ATI] Device [1002:1638] (rev d1) graphics, the problem *does not* occur.

[Simon B (skymon)]

Hi,
I have been experiencing the same problem for several days. I have to press escape when I launch my laptop, to display its screen correctly. Otherwise, as mentioned before, I get a multicolored snow. If my screen goes to sleep, it also happens.
I use a Tuxedo computer Pulse, with a Ryzen 7 4800h. Under Kubuntu.

[Daniel van Vugt (vanvugt)]

> Personally I'd have assumed anything described as "flickering" to be different

James, it is common for people reporting bugs to choose their words somewhat inaccurately. "Flicker" is often used by people to describe graphical bugs that are not flicker.

[Petr Helebrant (helebrant)]

Same here, Lenovo T14 with AMD Ryzen 5 PRO 4650U with Radeon Graphics, just snowy screen with blinking lines on right sides...only hw reset helps.

[Petr Helebrant (helebrant)]

OK, I have made the giant leap from kernel 5.13.0.27 to 5.16.4 and the problem is gone...

edit: after all I have ended on 5.15.6 as it's the last one which doesn't brake dependencies in apt for Ubuntu 20.04 caused by non existing and required libssl3 in it's repo...

[Will Pimblett (wjdp)]

Unsure if a "me too" comment is useful, but also having this problem. Using AMD Ryzen 7 PRO 4750U with Radeon Graphics.

Present on 5.13.0-28-generic, fixed by rolling back to 5.11.0-46-generic.

[Daniel Novotny (daniel-novotny)]

I am also affected by this bug on my Lenovo laptop

I have an external monitor plugged in all the time, that means after the display manager starts, the internal monitor is unusable (showing "snow" and lines).

fixed this temporarily by booting 5.11 kernel instead of 5.13

*-display
       description: VGA compatible controller
       product: Renoir
       vendor: Advanced Micro Devices, Inc. [AMD/ATI]
       physical id: 0
       bus info: pci@0000:07:00.0
       logical name: /dev/fb0
       version: d1
       width: 64 bits
       clock: 33MHz
       capabilities: pm pciexpress msi msix vga_controller bus_master cap_list fb
       configuration: depth=32 driver=amdgpu latency=0 mode=1920x1080 visual=truecolor xres=1920 yres=1080
       resources: iomemory:40-3f iomemory:40-3f irq:87 memory:460000000-46fffffff memory:470000000-4701fffff ioport:1000(size=256) memory:fd300000-fd37ffff

[James Ferguson (jamesf)]

Any chance this bug can get assigned and get some attention? An entire generation of Ryzen systems seem to be rendered unusable without holding back the kernel to 5.11.

[Thomas Hunter II (tlhunter)]

I also have this issue on a Thinkpad T14s, AMD Ryzen 7 PRO 4750U.

The issue is not present with kernels 5.9.10 or 5.15.23. It is present with the default kernel from the most recent KDE Neon (5.13).

Here's a short video, it's the same pattern (static and vertical lines on the right) as the other video in this thread:
https://twitter.com/tlhunter/status/1493107390731874305

The pattern is reminiscent to an HDMI desync issue but the vertical lines do make it distinct.

It appeared to affect the laptop screen but not an external display. The static appeared after the screen went to sleep and woke back up, though I don't believe the system went to sleep.

[enaeni (enaeni)]

I also have this issue on a thinkpad L14 with ubuntu Ubuntu 20.04.3 LTS, AMD Ryzen 7 pro.
The issue appears with the kernel linux-image-5.13.0-1022-oem when is waked up from sleep.
The issue is not present with older kernel version. Downgrading to an older version solves the problem.
The laptop becomes useless without an external display.

[yolen (plasmajens)]

I just received an update which seems to have solved the problem on my laptop (tried suspend and resume -> no weird screen). According to /var/log/apt/history.log the latest updates are:

Install: linux-modules-extra-5.13.0-30-generic:amd64 (5.13.0-30.33~20.04.1, automatic), linux-modules-5.13.0-30-generic:amd64 (5.13.0-30.33~20.04.1, automatic), linux-headers-5.13.0-30-generic:amd64 (5.13.0-30.33~20.04.1, automatic), linux-hwe-5.13-headers-5.13.0-30:amd64 (5.13.0-30.33~20.04.1, automatic), linux-image-5.13.0-30-generic:amd64 (5.13.0-30.33~20.04.1, automatic)
Upgrade: linux-headers-generic-hwe-20.04:amd64 (5.13.0.28.31~20.04.15, 5.13.0.30.33~20.04.17), linux-libc-dev:amd64 (5.4.0-99.112, 5.4.0-100.113), snapd:amd64 (2.54.2+20.04ubuntu2, 2.54.3+20.04.1), libarchive13:amd64 (3.4.0-2ubuntu1, 3.4.0-2ubuntu1.1), language-pack-en:amd64 (1:20.04+20210802, 1:20.04+20220211), linux-image-generic-hwe-20.04:amd64 (5.13.0.28.31~20.04.15, 5.13.0.30.33~20.04.17), linux-generic-hwe-20.04:amd64 (5.13.0.28.31~20.04.15, 5.13.0.30.33~20.04.17), language-pack-en-base:amd64

[Daniel Novotny (daniel-novotny)]

the today's update seems to fix the problem for me, too.

Install: linux-modules-extra-5.13.0-30-generic:amd64 (5.13.0-30.33~20.04.1, automatic), linux-modules-5.13.0-30-generic:amd64 (5.13.0-30.33~20.04.1, automatic), linux-headers-5.13.0-30-generic:amd64 (5.13.0-30.33~20.04.1, automatic), linux-hwe-5.13-headers-5.13.0-30:amd64 (5.13.0-30.33~20.04.1, automatic), linux-image-5.13.0-30-generic:amd64 (5.13.0-30.33~20.04.1, automatic)
Upgrade: fdisk:amd64 (2.34-0.1ubuntu9.1, 2.34-0.1ubuntu9.3), cryptsetup-bin:amd64 (2:2.2.2-3ubuntu2.3, 2:2.2.2-3ubuntu2.4), cryptsetup-initramfs:amd64 (2:2.2.2-3ubuntu2.3, 2:2.2.2-3ubuntu2.4), linux-headers-generic-hwe-20.04:amd64 (5.13.0.28.31~20.04.15, 5.13.0.30.33~20.04.17), uuid-runtime:amd64 (2.34-0.1ubuntu9.1, 2.34-0.1ubuntu9.3), libfdisk1:amd64 (2.34-0.1ubuntu9.1, 2.34-0.1ubuntu9.3), libdrm-nouveau2:amd64 (2.4.105-3~20.04.2, 2.4.107-8ubuntu1~20.04.1), linux-libc-dev:amd64 (5.4.0-99.112, 5.4.0-100.113), libegl-mesa0:amd64 (21.0.3-0ubuntu0.3~20.04.5, 21.2.6-0ubuntu0.1~20.04.1), libglapi-mesa:amd64 (21.0.3-0ubuntu0.3~20.04.5, 21.2.6-0ubuntu0.1~20.04.1), libmount1:amd64 (2.34-0.1ubuntu9.1, 2.34-0.1ubuntu9.3), snapd:amd64 (2.51.1+20.04ubuntu2, 2.54.3+20.04.1), ubuntu-advantage-tools:amd64 (27.5~20.04.1, 27.6~20.04.1), libarchive13:amd64 (3.4.0-2ubuntu1, 3.4.0-2ubuntu1.1), util-linux:amd64 (2.34-0.1ubuntu9.1, 2.34-0.1ubuntu9.3), python-apt-common:amd64 (2.0.0ubuntu0.20.04.6, 2.0.0ubuntu0.20.04.7), libxatracker2:amd64 (21.0.3-0ubuntu0.3~20.04.5, 21.2.6-0ubuntu0.1~20.04.1), cryptsetup-run:amd64 (2:2.2.2-3ubuntu2.3, 2:2.2.2-3ubuntu2.4), language-pack-en:amd64 (1:20.04+20210802, 1:20.04+20220211), linux-image-generic-hwe-20.04:amd64 (5.13.0.28.31~20.04.15, 5.13.0.30.33~20.04.17), libgbm1:amd64 (21.0.3-0ubuntu0.3~20.04.5, 21.2.6-0ubuntu0.1~20.04.1), mount:amd64 (2.34-0.1ubuntu9.1, 2.34-0.1ubuntu9.3), linux-generic-hwe-20.04:amd64 (5.13.0.28.31~20.04.15, 5.13.0.30.33~20.04.17), libdrm-amdgpu1:amd64 (2.4.105-3~20.04.2, 2.4.107-8ubuntu1~20.04.1), libblkid1:amd64 (2.34-0.1ubuntu9.1, 2.34-0.1ubuntu9.3), ubuntu-drivers-common:amd64 (1:0.9.0~0.20.04.4, 1:0.9.0~0.20.04.5), python3-distupgrade:amd64 (1:20.04.36, 1:20.04.37), ubuntu-release-upgrader-core:amd64 (1:20.04.36, 1:20.04.37), firefox-locale-en:amd64 (96.0+build2-0ubuntu0.20.04.1, 97.0+build2-0ubuntu0.20.04.1), libspeex1:amd64 (1.2~rc1.2-1.1ubuntu1, 1.2~rc1.2-1.1ubuntu1.20.04.1), libuuid1:amd64 (2.34-0.1ubuntu9.1, 2.34-0.1ubuntu9.3), libdrm2:amd64 (2.4.105-3~20.04.2, 2.4.107-8ubuntu1~20.04.1), libsmartcols1:amd64 (2.34-0.1ubuntu9.1, 2.34-0.1ubuntu9.3), rfkill:amd64 (2.34-0.1ubuntu9.1, 2.34-0.1ubuntu9.3), libgl1-mesa-dri:amd64 (21.0.3-0ubuntu0.3~20.04.5, 21.2.6-0ubuntu0.1~20.04.1), libspeexdsp1:amd64 (1.2~rc1.2-1.1ubuntu1, 1.2~rc1.2-1.1ubuntu1.20.04.1), bsdutils:amd64 (1:2.34-0.1ubuntu9.1, 1:2.34-0.1ubuntu9.3), language-pack-en-base:amd64 (1:20.04+20210802, 1:20.04+20220211), ubuntu-release-upgrader-gtk:amd64 (1:20.04.36, 1:20.04.37), libdrm-intel1:amd64 (2.4.105-3~20.04.2, 2.4.107-8ubuntu1~20.04.1), firefox:amd64 (96.0+build2-0ubuntu0.20.04.1, 97.0+build2-0ubuntu0.20.04.1), libcryptsetup12:amd64 (2:2.2.2-3ubuntu2.3, 2:2.2.2-3ubuntu2.4), libdrm-radeon1:amd64 (2.4.105-3~2...

[James Ferguson (jamesf)]

Excellent - also confirming - current kernel that came through in normal updates fixes the issue. Thank you devs.

    $ uname -r
    5.13.0-30-generic

I posted one option for fixing the machine on 5.11 kernel in comment #15. To undo that:

0. update your packages
1. Restore /etc/grub/default to have the line `GRUB_DEFAULT=0`, then run `sudo update-grub`.
3. Reboot and then confirm the with `uname -r` that you are on 5.13.0-30-generic and the issue is fixed.
4. If all is well, to remove the 5.11 packages so they're not on your system forever: `sudo apt purge --autoremove linux-image-5.11.0-46-generic linux-headers-5.11.0-46-generic linux-modules-extra-5.11.0-46-generic`.

[Mariusz (mapniv)]

That didn't fix the bug in my case. Should I create new bug report?

[Daniel van Vugt (vanvugt)]

Mariusz, I have reopened bug 1958523 for you.

[dusoft (dusoft-staznosti)]

Reported here: https://gitlab.freedesktop.org/drm/amd/-/issues/1923

[Gaurav (gauddasa)]

I am seeing this static since kernel 5.13.0-28 and even now after today's update to kernel 5.13.0-35 the static still appears for a while while rebooting / shutdown.

The issue is same, "Laptop internal display shows random looking 'static' after it's turned off"

This is ASUS Laptop with AMD Ryzen 7 3750H with Radeon Vega Mobile Gfx

[Daniel van Vugt (vanvugt)]

This bug is closed. If you're seeing the problem in kernel 5.13.0-30 or later then please use bug 1958523.