#1399 [mutter] gnome wayland session killed after locking screen | rhbz#2240457
Closed by blockerbot. Opened by blockerbot.

Bug details: ** https://bugzilla.redhat.com/show_bug.cgi?id=2240457 **
Information from BlockerBugs App:
2240457

Current vote summary

Commented but haven't voted yet: adamwill, tpopela, rstrode

The votes have been last counted at 2023-10-12 22:42 UTC and the last processed comment was #comment-878459

To learn how to vote, see:
https://pagure.io/fedora-qa/blocker-review
A quick example: BetaBlocker +1 (where the tracker name is one of BetaBlocker/FinalBlocker/BetaFE/FinalFE/0Day/PreviousRelease and the vote is one of +1/0/-1)


@halfline , I see you proposed this - do you think it's likely to be commonly encountered? Thanks!

FinalFE +1
for sure. Probably a blocker unless we determine it's only encountered on a rare configuration.

Assuming it isn't too widespread:

FinalFE +1

I've been hit by this for several weeks and I managed to lost plenty of work over that period of time as for me to trigger this bug it's enough to lock the screen whenever I step away from the laptop (habit after all those years in the office).

@halfline , I see you proposed this - do you think it's likely to be commonly encountered? Thanks!

I think that all the people with running the affected AMD platform(s) will hit this with GNOME 45/Fedora 39.

I am sadly not at home at the moment so can't test it on my AMD system, however the issue sounds like a serious one to me, especially if it affects many people running AMD platforms.

FinalBlocker +1

@halfline , I see you proposed this - do you think it's likely to be commonly encountered? Thanks!

Ping @rstrode

Definitely a blocker, locking the screen or leaving the system idle for some time shouldn't result into data loss.

And yes this basically affects all systems using the amdgpu driver as mode setting there can take longer killing the rt thread.

FinalFE +1

Not sure about blocker until we have a better idea about what systems are affected. My Radeon 580 isn't.

i dont know how widespread it is. i believe it affects some Ryzen 7 machines. I do know it's not isolated. it's affected a number of people in various bug trackers

@kparal Radeon 580 is using the radeon driver, not amdgpu.

@kparal Radeon 580 is using the radeon driver, not amdgpu.

It's using amdgpu:

$ lspci -k | grep -A 3 -E "(VGA|3D)"
01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 470/480/570/570X/580/580X/590] (rev e7)
    Subsystem: Sapphire Technology Limited Nitro+ Radeon RX 570/580/590
    Kernel driver in use: amdgpu
    Kernel modules: amdgpu

At this moment it looks like all affected people are using onboard Radeon graphics (inside a Ryzen CPU).

FinalFE +1

Would need more info about how widespread it is to decide if it's really a blocker.

AGREED AcceptedFreezeException

Even if it's just Ryzen APUs, that's still a significant amount of devices and basically all newer AMD based (business) laptops.

FinalBlocker +1

AGREED AcceptedFinalBlocker

The following votes have been closed:

Metadata Update from @blockerbot:
- Issue status updated to: Closed (was: Open)

Release F39 is no longer tracked by BlockerBugs, closing this ticket.

Log in to comment on this ticket.

Metadata