https://bugs.kde.org/show_bug.cgi?id=407221
Aleix Pol changed:
What|Removed |Added
Resolution|--- |FIXED
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=407221
Alexander Potashev changed:
What|Removed |Added
CC||aspotas...@gmail.com
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=407221
--- Comment #8 from Roman Gilg ---
Might be the same issue because of the placement calls in the backtrace.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=407221
--- Comment #7 from Vlad Zagorodniy ---
@David Gow please file a separate bug report for that. This and your
backtrace(s) look different.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=407221
--- Comment #6 from David Gow ---
Okay, it seems that I spoke too soon: I just got the hang again.
I have better debug symbols now, so here's an updated (example) stacktrace. As
before, it appears to be an infinite loop in KWin::Placement::placeSmart()
https://bugs.kde.org/show_bug.cgi?id=407221
--- Comment #5 from David Gow ---
I've tried to reproduce this on the latest KWin git (c62650394) over the last
few days, and haven't been able to, so maybe it's fixed. I'd certainly have
expected it to show up by now if it were still happening, though
https://bugs.kde.org/show_bug.cgi?id=407221
David Gow changed:
What|Removed |Added
CC||da...@davidgow.net
--- Comment #4 from David Gow -
https://bugs.kde.org/show_bug.cgi?id=407221
--- Comment #3 from Roman Gilg ---
Don't know what it was back then. Let's wait for it happening again or for
someone else and otherwise close the report.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=407221
--- Comment #2 from Vlad Zagorodniy ---
What's the latest commit in your local master?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=407221
--- Comment #1 from Roman Gilg ---
Just experienced it again. But it's not really a freeze, seems more to be an
endless loop (kwin_wayalnd with 100% cpu load) in the placement routine when
opening a new window.
--
You are receiving this mail because:
10 matches
Mail list logo