Bug 11987 - Refkit X11 image: select the "Exit" in twm does not terminate X11 fully
Summary: Refkit X11 image: select the "Exit" in twm does not terminate X11 fully
Status: RESOLVED OBSOLETE
Alias: None
Product: IoT Reference OS Kit
Classification: Yocto Project Subprojects
Component: intel-iot-refkit-platform-support (show other bugs)
Version: 2.4
Hardware: MinnowBoard Max x86
: Undecided normal
Target Milestone: Future
Assignee: Jussi Laako
QA Contact: yeoh ee peng
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2017-08-28 08:13 UTC by yeoh ee peng
Modified: 2018-10-11 19:26 UTC (History)
2 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: No (bug/feature does not impact docs)

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description yeoh ee peng 2017-08-28 08:13:24 UTC 
Environment: 
Image: refkit-image-common-x11-intel-corei7-64-2017-08-04_06-28-07-build-244.wic.xz  
Boards: Intel Joule 570x & MinnowMax


Defect description:
After execute startx and X11 successfully launched, inside the X11 GUI (twm), right click mouse to select the "Exit" in twm does not terminate X11 fully.

Expected:
Once select the "Exit" inside X11 GUI (twm), it will successfully terminate the X11 and return to virtual terminal

Actual:
It only partially terminate the X11, some of the X11 GUI disappeared and X11 windows no longer able to interact with mouse click. But it does not return to virtual terminal.
Comment 1 Jussi Kukkonen 2017-09-05 14:17:57 UTC 
For the record, I can't tell if this is a bug in twm, refkit X session startup or oe-core (but sato manages to exit cleanly so probably not oe-core).

On the other hand, if the twm environment is not meant to be a production thing then this is unlikely to be a very important issue...
Comment 2 Jussi Laako 2017-09-05 14:50:23 UTC 
RefKit doesn't have any customizations for X11/twm (or Wayland/Weston for that matter). It just pulls in packages from oe-core as-is...
Comment 3 Jussi Kukkonen 2017-09-06 08:26:12 UTC 
(In reply to comment #2)
> RefKit doesn't have any customizations for X11/twm (or Wayland/Weston for
> that matter). It just pulls in packages from oe-core as-is...

twm is not in oe-core so the Yocto team hasn't tested it in any way.

The oe-core X session startup is just fault tolerant enough that if there's no /usr/bin/x-session-manager then /usr/bin/x-window-manager is exec'd (and twm provides this) so it is possible that there is no other session handling in refkit.
Comment 4 Jussi Laako 2017-09-07 08:10:09 UTC 
Ahh, yes twm is from meta-oe:
http://git.openembedded.org/meta-openembedded/tree/meta-oe/recipes-graphics/xorg-app/twm_1.0.9.bb

It is of course not intended for any final product, but it is there only so that X11 is functional to some extent.

This is only thing RefKit has regarding X11:
https://github.com/intel/intel-iot-refkit/blob/master/meta-refkit-core/conf/distro/include/refkit-core-x11.inc

Intention is to keep X11 to as bare minimum as possible. Since final products based on RefKit would likely either use meta-qt5 (embedded) or some proprietary graphics framework in a way that there is only single application active/possible, we want to minimize amount/size of things that wouldn't be used anyway.
Comment 5 Richard Purdie 2018-10-11 19:26:55 UTC 
Refkit work isn't continuing so mark as obsolete.