[kwin] [Bug 442990] Crash in KWin::Toplevel::setOutput()

https://bugs.kde.org/show_bug.cgi?id=442990 Nate Graham changed: What|Removed |Added Version Fixed In||5.23 -- You are receiving this mail because:

[kwin] [Bug 442990] Crash in KWin::Toplevel::setOutput()

https://bugs.kde.org/show_bug.cgi?id=442990 Zamundaaa changed: What|Removed |Added Latest Commit|https://invent.kde.org/plas |https://invent.kde.org/plas

[kwin] [Bug 442990] Crash in KWin::Toplevel::setOutput()

https://bugs.kde.org/show_bug.cgi?id=442990 Zamundaaa changed: What|Removed |Added Resolution|--- |FIXED Status|ASSIGNED

[kwin] [Bug 442990] Crash in KWin::Toplevel::setOutput()

https://bugs.kde.org/show_bug.cgi?id=442990 --- Comment #11 from Matej Mrenica --- (In reply to Nate Graham from comment #10) > Since this bug report is about KWin crashing, let's get a new one for > plasmashell once this is fixed. It might also just be Bug 420160? Yes, it seems to be the same

[kwin] [Bug 442990] Crash in KWin::Toplevel::setOutput()

https://bugs.kde.org/show_bug.cgi?id=442990 Nate Graham changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED

[kwin] [Bug 442990] Crash in KWin::Toplevel::setOutput()

https://bugs.kde.org/show_bug.cgi?id=442990 --- Comment #9 from Matej Mrenica --- Your proposed change fixes this issue mostly. Session/kwin doesn't crash anymore and the internal screen is activated. But, plasmashell still crashes and there isn't a coredump generated. -- You are receiving

[kwin] [Bug 442990] Crash in KWin::Toplevel::setOutput()

https://bugs.kde.org/show_bug.cgi?id=442990 --- Comment #8 from Matej Mrenica --- (In reply to Zamundaaa from comment #7) > Yes it should, although KScreen should also already be turning the output on. > > If I interpret this correctly your setup is having the internal display > disabled, with

[kwin] [Bug 442990] Crash in KWin::Toplevel::setOutput()

https://bugs.kde.org/show_bug.cgi?id=442990 --- Comment #7 from Zamundaaa --- Yes it should, although KScreen should also already be turning the output on. If I interpret this correctly your setup is having the internal display disabled, with the external one used? Is that also the situation

[kwin] [Bug 442990] Crash in KWin::Toplevel::setOutput()

https://bugs.kde.org/show_bug.cgi?id=442990 --- Comment #6 from Matej Mrenica --- Looking at the proposed changes, it looks like it would fix the issue of laptop screen not being turned on if an external monitor is unplugged? Because that's something I was considering reporting. -- You are

[kwin] [Bug 442990] Crash in KWin::Toplevel::setOutput()

https://bugs.kde.org/show_bug.cgi?id=442990 --- Comment #5 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/plasma/kwin/-/merge_requests/1486 -- You are receiving this mail because: You are watching all bug changes.

[kwin] [Bug 442990] Crash in KWin::Toplevel::setOutput()

https://bugs.kde.org/show_bug.cgi?id=442990 Zamundaaa changed: What|Removed |Added CC||xaver.h...@gmail.com --- Comment #4 from Zamundaaa

[kwin] [Bug 442990] Crash in KWin::Toplevel::setOutput()

https://bugs.kde.org/show_bug.cgi?id=442990 Nate Graham changed: What|Removed |Added CC||n...@kde.org -- You are receiving this mail

[kwin] [Bug 442990] Crash in KWin::Toplevel::setOutput()

https://bugs.kde.org/show_bug.cgi?id=442990 --- Comment #3 from Vlad Zahorodnii --- Not sure how kwin can crash in Toplevel::setOutput(). Either the window is deleted, which is strange as the stacking order should not contain dangling pointers, or the output is destroyed, which is also weird

[kwin] [Bug 442990] Crash in KWin::Toplevel::setOutput()

https://bugs.kde.org/show_bug.cgi?id=442990 David Edmundson changed: What|Removed |Added CC||k...@davidedmundson.co.uk --- Comment #2

[kwin] [Bug 442990] Crash in KWin::Toplevel::setOutput()

https://bugs.kde.org/show_bug.cgi?id=442990 Matej Mrenica changed: What|Removed |Added CC||matejm98m...@gmail.com --- Comment #1 from