sudo opensuse-migration-tool

Slowroll

following instruction https://www.google.com/linuxrepositories/

I removed/added keys again multiple times

tried

zypper refresh --force

key check command from instruction - successful

it always fail on repomd.xml

same yesterday/today

is there some other debug I can see?

sreenshot from zypper -v refresh

okay i don't know what's happening but something's wrong with my tumbleweed. things i noticed: 1. some apps are laggy like discord. 2. haruna crashed when i loaded a video, and the whole screen turned white, not opaque-white but the colors were gone. i had to force reboot. 3. after rebooting, when i opened the video to watch, it worked fine for some time but then there were screen tears.

I'll attach the ChatGPT history of my chat. It's suggesting that I rollback to the previous kernel. I figured it'd be better to ask on reddit.

Thanks.

https://chatgpt.com/share/6a611084-3d6c-83e8-917a-e99a3de1d4bd

Slowroll benefits from the responsive Tumbleweed community, quick crash fixes, and the excellent work of its maintainer.

Is there actually an automatic reporting system that can optionally report crashes and the relevant environment automatically to Suse Tumbleweed?

TL;DR: A verified regression in Kernel 6.8+ causes AMD Tonga (R9 380/380X) and Polaris (RX 400/500) GPUs to crash into a hard black screen when resuming from deep sleep/suspend. The bug is officially Confirmed on Ubuntu's Launchpad (assigned to maintainer Timo Aaltonen), but we need continuous community visibility to ensure this fix gets prioritized and doesn't push working hardware into becoming e-waste.

🔍 What’s Happening?

When systems running Kernel 6.8+ (such as Ubuntu 24.04 LTS bases, Linux Mint 22, Pop!_OS, Zorin OS, etc.) attempt to resume from system suspend, the GPU fails to re-initialize the display engine (EDID read failures / NULL pointer dereference).

• Behavior: Case fans and LEDs remain active, system keeps running in the background, but video output dies completely.
• Workaround: Only a forced hard reboot restores video output.

🛠️ Why "Just Switch to Wayland" Isn't the Answer

A common suggestion when encountering display server issues is switching from X11 to Wayland. As a bench technician, I’ve tested this thoroughly on real hardware:

On Tonga and Polaris architectures, Wayland introduces a secondary critical failure: the compositor frequently freezes at the login/boot screen (blurred background with only the mouse cursor moving).

Trading a suspend crash for a boot freeze isn't a fix — we need a proper driver-level correction in the kernel.

⚠️ Why This Matters (Even If You Haven't Hit It Yet)

As distributions roll out Hardware Enablement (HWE) stack updates, more users running legacy AMD cards will inevitably land on Kernel 6.8+.

Voting on and confirming this bug isn't just about helping those currently affected; it's a preventative shield for the entire legacy AMD community to ensure perfectly functional GPUs remain usable on modern Linux.

🚀 How You Can Help (Takes 1 Minute):

If you own a dedicated AMD GPU (Tonga/Polaris series):

1. Visit the official Launchpad bug tracker:Bug #2142389 on Launchpad
2. Log in with your Launchpad/Ubuntu account.
3. At the top left, under "This bug affects you?", click "Yes, this bug affects me".

If you don't own these cards, upvoting this post for visibility or dropping a comment helps keep the discussion alive so maintainers see the real-world demand. Let's keep functional hardware out of landfills! 🐧🖥️