Hacker News new | ask | show | jobs
by vetinari 957 days ago
Maybe if you told us, how to replicate this show stopping bug so we could it try ourselves, someone could fix it then. Wayland being the problem or not.
2 comments

Not the OP, but happens to me too. Steps to replicate: put your laptop to sleep (suspend) and try to wake it up (resume). You end up with a black screen. Often times, you can SSH into your laptop, but the screen remains unresponsive. Only hard reset helps.

There are many reports of such bug. It's common on Wayland, but happens on X11 to some folks. The only constant is it happens on devices with Nvidia cards.

I tried pretty much everything and I gave up on solving it.

I didn't even have to do anything. Just boot after a fresh install and wait a minute or two. Three generation of all Intel laptops. I uploaded some logs, but people were utterly uninterested or hostile.
It has nothing to do with Wayland though, based on the description. Wayland used the base kernel API to manage the display. That is probably broken on your given device.

X11 often gets patched by a proprietary nvidia blob (the nvidia driver), which uses a separate, non-standard, X-specific API.

May be. As i wrote: Intel gpus. All I know is the problem was gone with an X session and nobody at the distro or some boards showed any interest. Not a good way to make sure code works methinks.
I did, there was no interest.
I'm curious, because I have machines with Intel GPUs from different vendors and of various generations (from Ivy Bridge, through Kaby Lake up to the Raptor Lake) and I've never seen such a bug.
I was too, but I'm not an expert and at the end of the day I need to get work done. It's up to Wayland devs to care about covering the 1001 edge cases (and thus have a process for user reports) or not.