https://bugs.kde.org/show_bug.cgi?id=519934
--- Comment #5 from [email protected] --- (In reply to Zamundaaa from comment #4) > The backtrace suggests it's trying to composite an output it doesn't > actually have a view for. I don't have the slightest clue how it could > happen though. > > > My guess would be that somehow EE2 is trying to check if the application > > that just closed (PoE 2) is active and since its no longer there causes > > issues. That would be my only guess. That said on the rare occasion there > > is time when the KWin doesn't crash with EE2 still running but thats very > > rare. > Is there any difference in the logs between the two situations? > If you disable the window close animations, does that make a difference? Took a second I tested it out without the windows close animations and its still crashing. I am not sure if there are any differences between the logs since I only had access to logs when it crashed. I wonder if its because the EE2 is a transparent overlay? When the game closes it should in theory stop the application but I don't have much context into either linux compositions and how the transparent overlays behave with these kind of interactions. If I close the EE2 before shutting down the PoE2 I dont have any crashes or issues. -- You are receiving this mail because: You are watching all bug changes.
