Hi,
since upgrading to F42 my kwin crashes (consistently, always). As soon as the login screen should appear, it doesn't. There is a stacktrace from kwin_wayland in the logs.
This is on a Lenovo Thinkpad p14s, Intel ARC graphics.
Downgrading kwin to 6.3.4-1 "fixes" the issue (but is of course only valid as a temporary workaround; I can't stay on 6.3.4-1 forever).
I filed a bug here: https://bugzilla.redhat.com/show_bug.cgi?id=2362072 a few days ago, but did not get a response yet, so I thought I'd ask here.
for a little more detail and the stacktrace, see the bug report.
Any clues? Anybody else experiencing this?
Thanks!
On Tue, Apr 29, 2025 at 2:40 PM Vincent Schut via kde kde@lists.fedoraproject.org wrote:
Hi,
since upgrading to F42 my kwin crashes (consistently, always). As soon as the login screen should appear, it doesn't. There is a stacktrace from kwin_wayland in the logs.
This is on a Lenovo Thinkpad p14s, Intel ARC graphics.
Downgrading kwin to 6.3.4-1 "fixes" the issue (but is of course only valid as a temporary workaround; I can't stay on 6.3.4-1 forever).
I filed a bug here: https://bugzilla.redhat.com/show_bug.cgi?id=2362072 a few days ago, but did not get a response yet, so I thought I'd ask here.
for a little more detail and the stacktrace, see the bug report.
Any clues? Anybody else experiencing this?
It looks like Jan Grulich has already addressed this in yesterday's updates. :)
On 30/04/2025 12.25, Neal Gompa via kde wrote:
On Tue, Apr 29, 2025 at 2:40 PM Vincent Schut via kde kde@lists.fedoraproject.org wrote:
Hi,
since upgrading to F42 my kwin crashes (consistently, always). As soon as the login screen should appear, it doesn't. There is a stacktrace from kwin_wayland in the logs.
This is on a Lenovo Thinkpad p14s, Intel ARC graphics.
Downgrading kwin to 6.3.4-1 "fixes" the issue (but is of course only valid as a temporary workaround; I can't stay on 6.3.4-1 forever).
I filed a bug here: https://bugzilla.redhat.com/show_bug.cgi?id=2362072 a few days ago, but did not get a response yet, so I thought I'd ask here.
for a little more detail and the stacktrace, see the bug report.
Any clues? Anybody else experiencing this?
It looks like Jan Grulich has already addressed this in yesterday's updates. :)
Yes, indeed, this was fixed and explained in the bug report.