<html>
<head>
<base href="https://bugs.freedesktop.org/" />
</head>
<body><span class="vcard"><a class="email" href="mailto:dh.herrmann@gmail.com" title="David Herrmann <dh.herrmann@gmail.com>"> <span class="fn">David Herrmann</span></a>
</span> changed
<a class="bz_bug_link
bz_status_NEW "
title="NEW - Weston confuses SIGUSR1 signals from Xwayland and VT switch"
href="https://bugs.freedesktop.org/show_bug.cgi?id=87322">bug 87322</a>
<br>
<table border="1" cellspacing="0" cellpadding="8">
<tr>
<th>What</th>
<th>Removed</th>
<th>Added</th>
</tr>
<tr>
<td style="text-align:right;">CC</td>
<td>
</td>
<td>dh.herrmann@gmail.com
</td>
</tr></table>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - Weston confuses SIGUSR1 signals from Xwayland and VT switch"
href="https://bugs.freedesktop.org/show_bug.cgi?id=87322#c1">Comment # 1</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - Weston confuses SIGUSR1 signals from Xwayland and VT switch"
href="https://bugs.freedesktop.org/show_bug.cgi?id=87322">bug 87322</a>
from <span class="vcard"><a class="email" href="mailto:dh.herrmann@gmail.com" title="David Herrmann <dh.herrmann@gmail.com>"> <span class="fn">David Herrmann</span></a>
</span></b>
<pre>(In reply to Pekka Paalanen from <a href="show_bug.cgi?id=87322#c0">comment #0</a>)
<span class="quote">> Javier complained the other day, that Weston freezes on starting any X11 app
> via Xwayland. I can't recall the details. The Weston log was very
> interesting, though: it showed that as soon as XWM initializes, Weston
> thinks it's leaving the VT.
>
> Looking at the code, I'm surprised it hasn't blown up for anyone else yet.
>
> Weston routinely uses SIGUSR1 for VT-switching signalling. Weston-launch
> watches SIGUSR1, that is not a problem. However, when Weston is started
> without weston-launch, Weston itself may be watching for SIGUSR1:
> - src/launcher-util.c (Weston as root, without logind?)
> - src/logind-util.c (non-root with logind support?)
>
> Those two seem mutually exclusive, but there is a third one:
> - xwayland/launcher.c (for Xwayland server start-up notification)
>
> I guess what happens in Javier's case, is that when Xwayland server starts,
> it sends SIGUSR1 to Weston, which then runs all SIGUSR1 handlers in some
> arbitary order: VT switch and XWM init. This leads to Weston thinking it's
> no longer current, likely refusing all input, and you have a frozen VT.
>
> Seems like something should be moved to another signal number.</span >
Simply switch logind-util.c to use SIGRTMIN+1. Patch is appended.
<span class="quote">>
> (And why does logind-util.c call signalfd() manually instead of
> wl_event_loop_add_signal()?)</span >
I guess back in the days I wasn't aware of wl_event_loop_add_signal(). Feel
free to change it.
Thanks
David</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>