https://bugs.kde.org/show_bug.cgi?id=463716
--- Comment #8 from betami...@posteo.de ---
(In reply to David Edmundson from comment #7)
>
> *** This bug has been marked as a duplicate of bug 463385 ***
Thank you.
I see that the fix for this bug has narrowly missed the window for becoming a
part
https://bugs.kde.org/show_bug.cgi?id=463716
David Edmundson changed:
What|Removed |Added
Resolution|--- |DUPLICATE
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=463716
--- Comment #6 from betami...@posteo.de ---
(In reply to Vlad Zahorodnii from comment #5)
> The backtraces have no debug symbols, can you install debuginfod and run
> coredumpctl gdb again? https://wiki.archlinux.org/title/Debuginfod for more
> info
I
https://bugs.kde.org/show_bug.cgi?id=463716
--- Comment #5 from Vlad Zahorodnii ---
The backtraces have no debug symbols, can you install debuginfod and run
coredumpctl gdb again? https://wiki.archlinux.org/title/Debuginfod for more
info
--
You are receiving this mail because:
You are watching
https://bugs.kde.org/show_bug.cgi?id=463716
--- Comment #4 from betami...@posteo.de ---
Here is another one:
https://www.mediafire.com/file/zxmztvu4jx7kglb/core.kwin_wayland.1000.d837a63a6d2b48f6b45d9335b821fd6b.6339.167273561500.zst/file
(gdb) bt
#0 0x77a872bb8ea4 in
https://bugs.kde.org/show_bug.cgi?id=463716
--- Comment #3 from betami...@posteo.de ---
(In reply to David Edmundson from comment #2)
> We need the kwin coredump to do anything useful. Can you try to attach it.
>
> Running `coredumpctl gdb kwin_wayland`
>
> Then "bt" should hopefully give a
https://bugs.kde.org/show_bug.cgi?id=463716
David Edmundson changed:
What|Removed |Added
CC||k...@davidedmundson.co.uk
--- Comment #2
https://bugs.kde.org/show_bug.cgi?id=463716
--- Comment #1 from betami...@posteo.de ---
I have tried narrowing down what the issue might be and have found that adding
"intel_iommu=on" to my kernel's boot options causes it to happen in 100% (or
close to that) of the cases.
My normal boot options
