https://bugs.kde.org/show_bug.cgi?id=400788
Vlad Zagorodniy changed:
What|Removed |Added
Resolution|--- |FIXED
Version Fixed In|
https://bugs.kde.org/show_bug.cgi?id=400788
Vlad Zagorodniy changed:
What|Removed |Added
Assignee|kwin-bugs-n...@kde.org |vladz...@gmail.com
--- Comment #19 from Vlad
https://bugs.kde.org/show_bug.cgi?id=400788
--- Comment #18 from Vlad Zagorodniy ---
Other 2 options:
* Do cleanup when aboutToFinishCompositing is emitted;
* Move https://github.com/KDE/kwin/blame/master/composite.cpp#L406-L407 up (so
effect windows outlive effects).
--
You are receiving this
https://bugs.kde.org/show_bug.cgi?id=400788
--- Comment #17 from Vlad Zagorodniy ---
(In reply to Martin Flöser from comment #16)
> Option 2 sounds cleaner to me
Okay then, I'll go with it. :-)
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=400788
--- Comment #16 from Martin Flöser ---
Option 2 sounds cleaner to me
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=400788
--- Comment #15 from Vlad Zagorodniy ---
Compositor doesn't let AnimationEffect to cleanup gracefully, so KeepAliveLock
and PreviousWindowPixmapLock can have dangling pointers.
There are 2 potential ways to fix it:
* emit deletedRemoved in
https://bugs.kde.org/show_bug.cgi?id=400788
Vlad Zagorodniy changed:
What|Removed |Added
Resolution|WAITINGFORINFO |---
Status|NEEDSINFO
https://bugs.kde.org/show_bug.cgi?id=400788
--- Comment #13 from Vlad Zagorodniy ---
(In reply to Patrick Silva from comment #12)
> open compositor kcm
> change vsync setting
> click "Ok" button
> crash...
Thanks, I'll try to reproduce the crash by following these steps.
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=400788
--- Comment #12 from Patrick Silva ---
open compositor kcm
change vsync setting
click "Ok" button
crash...
crash is NOT reproducible if I click "Apply" instead "Ok" button
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=400788
--- Comment #11 from Vlad Zagorodniy ---
Probably either FAding Popups or Fade effect causes the crash.
Could you please describe how to reproduce the crash? (I had no luck in
reproducing the crash)
--
You are receiving this mail because:
You are
https://bugs.kde.org/show_bug.cgi?id=400788
--- Comment #10 from Patrick Silva ---
Version
===
KWin version: 5.14.80
Qt Version: 5.11.2
Qt compile version: 5.11.2
XCB compile version: 1.13
Operation Mode: Xwayland
Build Options
=
KWIN_BUILD_DECORATIONS: yes
KWIN_BUILD_TABBOX:
https://bugs.kde.org/show_bug.cgi?id=400788
--- Comment #9 from Vlad Zagorodniy ---
qdbus org.kde.KWin /KWin supportInformation
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=400788
--- Comment #8 from Vlad Zagorodniy ---
@Patrick Silva Could you please also post output of
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=400788
--- Comment #7 from Patrick Silva ---
backtrace generated on neon dev unstable
Thread 1 "kwin_wayland" received signal SIGSEGV, Segmentation fault.
0x55b8ce7bcd90 in ?? ()
(gdb) thread apply all bt
Thread 9 (Thread 1068.1106):
#0
https://bugs.kde.org/show_bug.cgi?id=400788
--- Comment #6 from Vlad Zagorodniy ---
(In reply to Patrick Silva from comment #5)
> Currently any change in compositor kcm is crashing Wayland session.
Hmm, kwin_wayland doesn't crash for me.
Could you please post the backtrace?
--
You are
https://bugs.kde.org/show_bug.cgi?id=400788
Patrick Silva changed:
What|Removed |Added
CC||bugsefor...@gmx.com
--- Comment #5 from
https://bugs.kde.org/show_bug.cgi?id=400788
--- Comment #4 from Bug Janitor Service ---
Dear Bug Submitter,
This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular
https://bugs.kde.org/show_bug.cgi?id=400788
--- Comment #3 from Vlad Zagorodniy ---
First of all, you have to re-package kwin so it has debug symbols. See
https://wiki.archlinux.org/index.php/Debug_-_Getting_Traces#CMAKE_.28KDE.29_applications
* sudo pacman -S asp
* asp export kwin
* cd kwin
https://bugs.kde.org/show_bug.cgi?id=400788
--- Comment #2 from tro...@free.fr ---
How do I do that on Archlinux ?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=400788
Vlad Zagorodniy changed:
What|Removed |Added
Status|REPORTED|NEEDSINFO
Resolution|---
20 matches
Mail list logo
