Bug 76665 - Clients are terminated when the parent client application is closed
Summary: Clients are terminated when the parent client application is closed
Status: VERIFIED INVALID
Alias: None
Product: Wayland
Classification: Unclassified
Component: weston (show other bugs)
Version: unspecified
Hardware: Other All
: medium normal
Assignee: Wayland bug list
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-03-26 23:43 UTC by Anu Reddy
Modified: 2014-05-08 17:28 UTC (History)
0 users

See Also:
i915 platform:
i915 features:

Attachments

Description Anu Reddy 2014-03-26 23:43:00 UTC 
When the clients are executed from weston-terminal, closing the terminal terminates the clients. This is a regression.

Steps:
1. Launch Weston
2. Launch Weston-terminal
3. Execute any client application from weston-terminal (e.g. weston-dnd)
4. Close Weston-terminal. Observe both the applications are closed.

Environment:
wayland (master) heads/master-0-g1bf13ae
drm (master) heads/master-0-g1cb5fc7
mesa (master) heads/master-0-g64278b3
libva (master) heads/master-0-ge30e29a
intel-driver (master) heads/master-0-g75a7b09
cairo (master) heads/master-0-gbb17403
libinput (master) heads/master-0-ge49a988
weston (master) heads/master-0-gfe9671e
gstreamer (master) heads/master-0-gf85ce91
Comment 1 U. Artie Eoff 2014-03-31 17:53:14 UTC 
I think this is expected behavior... you can use "nohup" or "disown" which suppress SIGHUP signals so the child program isn't automatically killed when the controlling terminal is closed.

For example:

$ weston-dnd & disown
or
$ nohup weston-dnd &

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.