https://bugs.kde.org/show_bug.cgi?id=460572
--- Comment #31 from Andrew Udvare ---
I rebuilt Kwin 6.0.90 with normal flags. Running in Wayland. Cannot reproduce.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=460572
dofficialg...@gmail.com changed:
What|Removed |Added
CC||dofficialg...@gmail.com
Ever confi
https://bugs.kde.org/show_bug.cgi?id=460572
Gabriel Ravier changed:
What|Removed |Added
CC||gabrav...@gmail.com
--
You are receiving this
https://bugs.kde.org/show_bug.cgi?id=460572
Sam James changed:
What|Removed |Added
See Also||https://bugs.kde.org/show_b
|
https://bugs.kde.org/show_bug.cgi?id=460572
--- Comment #29 from Andrew Udvare ---
I tried every single -mno-avx512* option until I had all of them set. When all
were set the issue was gone. So really, *any* AVX512 feature in use will cause
this bug. I also tried with Clang and got the same resul
https://bugs.kde.org/show_bug.cgi?id=460572
Sam James changed:
What|Removed |Added
Status|NEEDSINFO |REPORTED
Ever confirmed|1
https://bugs.kde.org/show_bug.cgi?id=460572
Sam James changed:
What|Removed |Added
CC||s...@gentoo.org
--- Comment #28 from Sam James ---
https://bugs.kde.org/show_bug.cgi?id=460572
--- Comment #27 from Andrew Udvare ---
The UBSAN/ASAN output is probably not related. -fno-tree-vectorize does not
resolve the issue with -march=native (or x86-64-v4) which is suprising.
For the last test these were the flags:
CXXFLAGS="-O2 -ggdb -mar
https://bugs.kde.org/show_bug.cgi?id=460572
--- Comment #26 from Andrew Udvare ---
(In reply to Andreas Sturmlechner from comment #24)
> This is the moment where you provide upstream with more information about
> your toolchain and optimisation flags.
More details:
# gcc -v
Using built-in specs
https://bugs.kde.org/show_bug.cgi?id=460572
Nate Graham changed:
What|Removed |Added
Status|REOPENED|NEEDSINFO
Resolution|---
https://bugs.kde.org/show_bug.cgi?id=460572
Andreas Sturmlechner changed:
What|Removed |Added
See Also||https://bugs.gentoo.org/sho
https://bugs.kde.org/show_bug.cgi?id=460572
--- Comment #24 from Andreas Sturmlechner ---
This is the moment where you provide upstream with more information about your
toolchain and optimisation flags.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=460572
Andreas Sturmlechner changed:
What|Removed |Added
Ever confirmed|0 |1
Status|RESOLVED
https://bugs.kde.org/show_bug.cgi?id=460572
--- Comment #23 from Andrew Udvare ---
This bug is actually caused by using --march=native to GCC. Maybe it's specific
to my CPU or how my GCC is built. Regardless, it would seem the code path in
question is sensitive to CPU optimisations. I can compile
https://bugs.kde.org/show_bug.cgi?id=460572
Nate Graham changed:
What|Removed |Added
Status|NEEDSINFO |RESOLVED
Resolution|WAITINGFORINFO
https://bugs.kde.org/show_bug.cgi?id=460572
--- Comment #22 from Andrew Udvare ---
Built Kwin from source (tag v5.27.0) and ran with --replace. The issue does not
appear in that build. The Gentoo build environment must be to blame.
--
You are receiving this mail because:
You are watching all bu
https://bugs.kde.org/show_bug.cgi?id=460572
--- Comment #21 from Andrew Udvare ---
I tried to reproduce this in the developer version of KDE Neon in VirtualBox
and was not able to, even after matching up my settings as much as possible.
I also tried building without -ftree-vectorize but this did
https://bugs.kde.org/show_bug.cgi?id=460572
--- Comment #20 from Andrew Udvare ---
(In reply to Vlad Zahorodnii from comment #18)
> Can you check whether the issue is reproducible in 5.27?
Still happening in 5.27. I rebooted after fully updating my system to ensure
there are no conflicting old s
https://bugs.kde.org/show_bug.cgi?id=460572
Vlad Zahorodnii changed:
What|Removed |Added
Resolution|--- |WAITINGFORINFO
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=460572
--- Comment #18 from Vlad Zahorodnii ---
Can you check whether the issue is reproducible in 5.27?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=460572
--- Comment #17 from Andrew Udvare ---
Worst offender is Chrome. I cannot reliably trigger this issue with Dolphin,
pavucontrol, etc.
When compositing is enabled, after snapping Chrome wants to use the shadow of
the window instead of the real edge of t
https://bugs.kde.org/show_bug.cgi?id=460572
--- Comment #16 from Andrew Udvare ---
It seems only *some* Gtk+ apps get affected. I was able to reproduce the same
issue with dconf-editor but not Filezilla or GIMP. It seems some windows may
have a particular way of drawing that triggers the bug?
--
https://bugs.kde.org/show_bug.cgi?id=460572
--- Comment #15 from Andrew Udvare ---
I am not positive the lines are relevant to this bug because they appear after
resize when the window is not snapped to the left edge of the screen.
--
You are receiving this mail because:
You are watching all bu
https://bugs.kde.org/show_bug.cgi?id=460572
--- Comment #14 from Andrew Udvare ---
(In reply to Vlad Zahorodnii from comment #13)
> > These lines mostly came when resizing Chrome on the right side while it was
> > snapped to the left side of the screen, with compositing enabled.
>
> Do you see
https://bugs.kde.org/show_bug.cgi?id=460572
--- Comment #13 from Vlad Zahorodnii ---
> These lines mostly came when resizing Chrome on the right side while it was
> snapped to the left side of the screen, with compositing enabled.
Do you see them after you've finished resizing chrome?
--
You
https://bugs.kde.org/show_bug.cgi?id=460572
--- Comment #12 from Andrew Udvare ---
The bug seems to be that the theme shadow is being used to figure out where to
have the right-side (E) resize grabber trigger instead of the window edge. This
seems to only happen when snapping the window to the le
https://bugs.kde.org/show_bug.cgi?id=460572
--- Comment #11 from Andrew Udvare ---
Created attachment 155349
--> https://bugs.kde.org/attachment.cgi?id=155349&action=edit
Kwin debug log
kwin_core: Failed to create window pixmap for window 0x10a (mismatched
geometry)
These lines mostly cam
https://bugs.kde.org/show_bug.cgi?id=460572
--- Comment #10 from Andrew Udvare ---
Adding to my previous comment:
This does not fully fix the window. It fixes Chrome it seems (somewhat), but
everything else still thinks it's wider than it is after snapping to the left
even without compositing.
https://bugs.kde.org/show_bug.cgi?id=460572
--- Comment #9 from Vlad Zahorodnii ---
Can you run kwin with
env QT_LOGGING_RULES="kwin*.debug=true"
envvar and attach kwin's output to this bug report please?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=460572
--- Comment #8 from Andrew Udvare ---
(In reply to Vlad Zahorodnii from comment #7)
> What if you toggle compositing? Does the window "fix" itself?
Yes. The window moves to the right a few pixels, to the correct position.
--
You are receiving this ma
https://bugs.kde.org/show_bug.cgi?id=460572
--- Comment #7 from Vlad Zahorodnii ---
What if you toggle compositing? Does the window "fix" itself?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=460572
--- Comment #6 from Andrew Udvare ---
Any thoughts on where I can look to possilbly fix the bug? Kwin source?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=460572
--- Comment #5 from Andrew Udvare ---
I made a new profile to test against just to make sure it's not a configuration
issue. I was able to reproduce the issue in X11 as with my current profile. I
was not able to reproduce the issue in Wayland.
--
You
https://bugs.kde.org/show_bug.cgi?id=460572
--- Comment #4 from Andrew Udvare ---
(In reply to Nate Graham from comment #3)
> Cannot reproduce with Chromium (in either CSD or SSD mode).
>
> Do you have any 3rd-party KWin scripts or effects active?
No KWin scripts enabled. Effects:
Accessibilit
https://bugs.kde.org/show_bug.cgi?id=460572
--- Comment #3 from Nate Graham ---
Cannot reproduce with Chromium (in either CSD or SSD mode).
Do you have any 3rd-party KWin scripts or effects active?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=460572
--- Comment #2 from Andrew Udvare ---
Recently updated and I am still getting the bug.
Two demonstration videos:
https://youtu.be/Qup9ifJSCnc
https://youtu.be/vwKTbOtpEkI
Note where the mouse cursor is vs the window edges after the window is snapped.
https://bugs.kde.org/show_bug.cgi?id=460572
Nate Graham changed:
What|Removed |Added
CC||n...@kde.org
--- Comment #1 from Nate Graham ---
https://bugs.kde.org/show_bug.cgi?id=460572
Andrew Udvare changed:
What|Removed |Added
Summary|Snapped windows to screen |Windows snapped to screen
|ed
38 matches
Mail list logo
