<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body><table border="1" cellspacing="0" cellpadding="8">
<tr>
<th>Bug ID</th>
<td><a class="bz_bug_link
bz_status_NEW "
title="NEW - Weston master causes mouse input to stop working with wl_shell applications"
href="https://bugs.freedesktop.org/show_bug.cgi?id=97892">97892</a>
</td>
</tr>
<tr>
<th>Summary</th>
<td>Weston master causes mouse input to stop working with wl_shell applications
</td>
</tr>
<tr>
<th>Product</th>
<td>Wayland
</td>
</tr>
<tr>
<th>Version</th>
<td>unspecified
</td>
</tr>
<tr>
<th>Hardware</th>
<td>All
</td>
</tr>
<tr>
<th>OS</th>
<td>Linux (All)
</td>
</tr>
<tr>
<th>Status</th>
<td>NEW
</td>
</tr>
<tr>
<th>Severity</th>
<td>normal
</td>
</tr>
<tr>
<th>Priority</th>
<td>medium
</td>
</tr>
<tr>
<th>Component</th>
<td>weston
</td>
</tr>
<tr>
<th>Assignee</th>
<td>wayland-bugs@lists.freedesktop.org
</td>
</tr>
<tr>
<th>Reporter</th>
<td>bluescreen_avenger@verizon.net
</td>
</tr></table>
<p>
<div>
<pre>Created <span class=""><a href="attachment.cgi?id=126719" name="attach_126719" title="The log of Weston with WAYLAND_DEBUG=server, and standarddialogs connected to it">attachment 126719</a> <a href="attachment.cgi?id=126719&action=edit" title="The log of Weston with WAYLAND_DEBUG=server, and standarddialogs connected to it">[details]</a></span>
The log of Weston with WAYLAND_DEBUG=server, and standarddialogs connected to
it
It seems to be a very weird issue with Qt 5.7.x and Qt 5.8 when using QtWayland
with the default wl_shell integration (doesn't seem to happen when it's using
xdg_shell, but xdg_shell is not the default for QtWayland without an env var
(and EFL if you export EFL_WAYLAND_DONT_USE_XDG_SHELL=1, I was able to
replicate this, however the only EFL application that I know of, and have that
actually utilizes child windows is the elementary_test that comes with EFL)
I can replicate this by even unsetting QT_WAYLAND_DECORATION, and
KDE_FULL_SESSION to get minimal Qt.
I can test with an example client, standarddialogs
<a href="https://quickgit.kde.org/?p=qt%2Fqtbase.git&a=tree&h=ffe4a1df1c641df4b3738887d02214082aa7aa12&hb=25e9bde2d665866f7a9a40d1ed3aa8fabcf2ac2f&f=examples%2Fwidgets%2Fdialogs%2Fstandarddialogs">https://quickgit.kde.org/?p=qt%2Fqtbase.git&a=tree&h=ffe4a1df1c641df4b3738887d02214082aa7aa12&hb=25e9bde2d665866f7a9a40d1ed3aa8fabcf2ac2f&f=examples%2Fwidgets%2Fdialogs%2Fstandarddialogs</a>
With standarddialogs, I start the application up, open, and then close a
dialog, and then leave the mouse pointer on the main surface. After a few
seconds, the cursor changes to a busy cursor, and it stops responding to mouse
input, as if though it's not responding to wl_pings (where the whole window
becomes draggable).
The whole surface stops responding to mouse input.
It does however appear to respond to Keyboard input, I can press tab to move
the selection around, and press space to press a button to open another dialog.
The dialog seems to respond to input, but the main surface that stops
responding to mouse input, never responds to it again</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>