https://bugs.kde.org/show_bug.cgi?id=385397
--- Comment #7 from Martin Flöser ---
(In reply to Martin Flöser from comment #4)
> I'll backport my patch to the 5.11 branch. So will be fixed with 5.11.0
Have to correct that one. 5.11.0 was already tagged, so one week later with
5.11.1
Thanks for t
https://bugs.kde.org/show_bug.cgi?id=385397
--- Comment #6 from Mate Soos ---
Wow, thanks! Great work :) Owe you a beer! Let me know if you are coming to CCC
(34C3) conf. Cheers,
Mate
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=385397
Martin Flöser changed:
What|Removed |Added
Latest Commit||https://commits.kde.org/kwi
|
https://bugs.kde.org/show_bug.cgi?id=385397
Martin Flöser changed:
What|Removed |Added
Flags||Wayland+, X11-
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=385397
--- Comment #4 from Martin Flöser ---
I'll backport my patch to the 5.11 branch. So will be fixed with 5.11.0
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=385397
--- Comment #3 from Mate Soos ---
Created attachment 108189
--> https://bugs.kde.org/attachment.cgi?id=108189&action=edit
hwinfo output
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=385397
--- Comment #2 from Mate Soos ---
Cool, thanks for picking this up. I was pretty happy I could run valgrind to be
honest. It's nice trace I think.
Using:
msoos@msoos: pacman -Qs "kwin*"
[...]
local/kwin 5.10.5-1 (plasma)
An easy to use, but flexib
https://bugs.kde.org/show_bug.cgi?id=385397
--- Comment #1 from Martin Flöser ---
which exact version are you running? I fixed a crash related to your backtrace
just the other day.
The memmove warnings look like false-positives to me, the invalid read is
directly related to your crash.
--
You
