https://bugs.kde.org/show_bug.cgi?id=383410
Roman Gilg changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://bugs.kde.org/show_bug.cgi?id=383410
--- Comment #17 from Roman Gilg ---
(based on https://wayland.freedesktop.org/ubuntu16.04.html)
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=383410
--- Comment #16 from Roman Gilg ---
You can use my script for compiling (change the rootdir and INST vars to your
liking, an install in /usr/local though makes KWin directly using the compiled
Xwayland on next launch):
#!/bin/sh
#
https://bugs.kde.org/show_bug.cgi?id=383410
Martin Flöser changed:
What|Removed |Added
Severity|major |critical
--- Comment #15
https://bugs.kde.org/show_bug.cgi?id=383410
--- Comment #14 from Roman Gilg ---
I just tried and the problem is still there. KWin log with
WAYLAND_DEBUG=server:
[2240489,397] wl_surface@20.attach(wl_buffer@11, 0, 0)
[2240489,410] wl_surface@20.damage(0, 0, 3840, 2160)
https://bugs.kde.org/show_bug.cgi?id=383410
--- Comment #13 from Martin Flöser ---
Could you please check whether the freeze matches #384441 ?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=383410
--- Comment #12 from Martin Flöser ---
I'm not able to reproduce the problem, could you please add an output of
WAYLAND_DEBUG, so that I can get the actual sequence of commands?
Unrelated found a crash in another test case:
Thread
https://bugs.kde.org/show_bug.cgi?id=383410
--- Comment #11 from Martin Flöser ---
OK, I'll try to adjust the test case for this condition.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=383410
--- Comment #10 from Roman Gilg ---
Thanks for digging into this. You're right that the cursor can't be locked and
confined at the same time.
The Xwayland code works like this: First confine. If then a certain condition
is met
https://bugs.kde.org/show_bug.cgi?id=383410
--- Comment #9 from Martin Flöser ---
Created attachment 107391
--> https://bugs.kde.org/attachment.cgi?id=107391=edit
Patch to autotest
For reference the patch added to the auto test
--
You are receiving this mail because:
You
https://bugs.kde.org/show_bug.cgi?id=383410
--- Comment #8 from Martin Flöser ---
I just created a test case for the situation and this results in:
wl_surface@13: error 1: Surface already constrained
It looks to me like what XWayland does is not valid on Wayland. And I just
https://bugs.kde.org/show_bug.cgi?id=383410
--- Comment #7 from Martin Flöser ---
See http://en.cppreference.com/w/cpp/language/storage_duration
Section "Static local variables"
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=383410
--- Comment #6 from Martin Flöser ---
It's a static initialization: it's only evaluated the first time it's executed
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=383410
--- Comment #5 from Roman Gilg ---
You're sure it's created only once? While s_osd is a static
OnScreenNotification pointer, we still always call create() in osd() and in
create() a new OnScreenNotification instance is created with
https://bugs.kde.org/show_bug.cgi?id=383410
Karl Ove Hufthammer changed:
What|Removed |Added
CC||k...@huftis.org
--
You
https://bugs.kde.org/show_bug.cgi?id=383410
--- Comment #4 from Martin Flöser ---
Looking at the code everything seems fine. The OSD is only created on very
first show (it's a static instance, so no leak). So the problem might be the
change of the Qml prior to actual showing.
https://bugs.kde.org/show_bug.cgi?id=383410
--- Comment #3 from Martin Flöser ---
I'm not sure whether we actually support locking and confining at the same
time, but yeah that's not the problem.
It looks like the OSD just doesn't support being shown multiple times. Or in
https://bugs.kde.org/show_bug.cgi?id=383410
--- Comment #2 from Roman Gilg ---
We get confined and locked probably at the same time, but we setConfined first
in https://cgit.kde.org/kwin.git/tree/pointer_input.cpp#n599, show the confined
OSD and return on
https://bugs.kde.org/show_bug.cgi?id=383410
--- Comment #1 from Martin Flöser ---
So the main point here is that we get both confined and locked?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=383410
Martin Flöser changed:
What|Removed |Added
Component|wayland-generic |input
Flags|
20 matches
Mail list logo