<html>
<head>
<base href="https://bugs.freedesktop.org/" />
</head>
<body><table border="1" cellspacing="0" cellpadding="8">
<tr>
<th>Priority</th>
<td>medium
</td>
</tr>
<tr>
<th>Bug ID</th>
<td><a class="bz_bug_link
bz_status_NEW "
title="NEW --- - [bug] weston-launch leaves behind defunct procs when killed, hanging ttys"
href="https://bugs.freedesktop.org/show_bug.cgi?id=62910">62910</a>
</td>
</tr>
<tr>
<th>Assignee</th>
<td>wayland-bugs@lists.freedesktop.org
</td>
</tr>
<tr>
<th>Summary</th>
<td>[bug] weston-launch leaves behind defunct procs when killed, hanging ttys
</td>
</tr>
<tr>
<th>Severity</th>
<td>major
</td>
</tr>
<tr>
<th>Classification</th>
<td>Unclassified
</td>
</tr>
<tr>
<th>OS</th>
<td>Linux (All)
</td>
</tr>
<tr>
<th>Reporter</th>
<td>joe.konno@linux.intel.com
</td>
</tr>
<tr>
<th>Hardware</th>
<td>All
</td>
</tr>
<tr>
<th>Status</th>
<td>NEW
</td>
</tr>
<tr>
<th>Version</th>
<td>unspecified
</td>
</tr>
<tr>
<th>Component</th>
<td>weston
</td>
</tr>
<tr>
<th>Product</th>
<td>Wayland
</td>
</tr></table>
<p>
<div>
<pre>If one launches `weston-launch &` and then kills it, `weston-launch` leaves
behind defunct processes and hangs the display. The only way to recover is to
execute `weston-launch` again and "kill it properly"-- specifically, killing
the 'weston' process.
1. Source your environment, ensure no X server running (to force drm backend)
2. From terminal,
weston-launch &
3. Kill it,
killall weston-launch
The expectation is that weston-launch dies gracefully and doesn't leave the
system in an unusable state. This could be a problem if a sysadmin tried to
kill the weston-launch service manually or (possibly) through systemd (latter
is unverified). After killing, display is hung and the only work-around
requires remote access to machine, otherwise system is in an unusable state.
Here are the defunct processes:
$ ps ax | grep weston
28909 tty2 Ss+ 0:00 /wld/master/install/bin/weston
28911 tty2 Z+ 0:00 [weston-desktop-] <defunct>
28914 pts/1 S+ 0:00 grep --color=auto weston
$
The following work-around is only effective sometimes. You have to reboot the
system when, e.g., weston-launch hangs on drm initialization:
1. ssh to hung system
2. Over ssh,
weston-launch &
3. Kill weston,
killall weston</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>