[Wayland-bugs] [Bug 62910] New: [bug] weston-launch leaves behind defunct procs when killed, hanging ttys

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Fri Mar 29 09:21:19 PDT 2013


https://bugs.freedesktop.org/show_bug.cgi?id=62910

          Priority: medium
            Bug ID: 62910
          Assignee: wayland-bugs at lists.freedesktop.org
           Summary: [bug] weston-launch leaves behind defunct procs when
                    killed, hanging ttys
          Severity: major
    Classification: Unclassified
                OS: Linux (All)
          Reporter: joe.konno at linux.intel.com
          Hardware: All
            Status: NEW
           Version: unspecified
         Component: weston
           Product: Wayland

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

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/wayland-bugs/attachments/20130329/a1a2b60b/attachment.html>


More information about the Wayland-bugs mailing list