This happen intermediately. Environment: Image: refkit-image-common-wayland-intel-corei7-64-2017-08-04_06-28-07-build-244.wic.xz Boards: MinnowMax (very frequent), Intel Joule 570 (intermediate, less frequent) Defect Description: After successful bootup and automatically loaded into weston compositor, click on weston-terminal icon does not fire up new terminal. Expected: When click on weston-terminal icon, it will fire up a new weston terminal inside the current weston-compositor. Actual: When click on weston-terminal icon, it does not fire up a new weston terminal inside the current weston-compositor. In fact it is fire up weston terminal inside the weston-compositor in another virtual terminal. (Found that multiple weston-compositors are sharing the same WAYLAND_DISPLAY value)
> In fact it is fire up weston terminal inside the weston-compositor in > another virtual terminal. (Found that multiple weston-compositors are > sharing the same WAYLAND_DISPLAY value) Can you show what is really going on here and how you figured this out? What exactly does "weston-compositor" refer to (weston-launch maybe)?
As this defect happen intermediately (happen more often on MinnowMax). When this defect was detected (click on weston-terminal icon does not fire up new terminal), try to find out which virtual terminal was used at the bootup to launch weston (eg. virtual terminal #2). Switch to different virtual terminal by the key sequence CTL-ALT-F<n> where n is 1-6. For example CTL-ALT-F1 to virtual terminal and then execute weston-launch to fire up a weston-compositor. Try to execute weston-launch on every virtual terminal. When you use weston-launch to fire up a weston-compositor, by default it is without any weston terminal. But you will notice one of the weston-compositor that you fire up contains 1 or more weston terminal. In fact if you go back to the virtual terminal used at the bootup (eg. virtual terminal #2), click on the weston-terminal icon, it will fire up new weston terminal at another virtual terminal (eg. virtual terminal #1). To debug, execute "export" at each weston terminal and observe the "WAYLAND_DISPLAY". I notice 2 of the virtual terminal shared the same "WAYLAND_DISPLAY" value. Please let me know if you can reproduce this.
(In reply to comment #2) > As this defect happen intermediately (happen more often on MinnowMax). When > this defect was detected (click on weston-terminal icon does not fire up new > terminal), try to find out which virtual terminal was used at the bootup to > launch weston (eg. virtual terminal #2). Just to make sure, do you really only have a single weston running at this point (the one started by the init manager), and the terminal just doesn't appear? Or do you already have another weston started somehow? > Switch to different virtual terminal by the key sequence CTL-ALT-F<n> where > n is 1-6. For example CTL-ALT-F1 to virtual terminal and then execute > weston-launch to fire up a weston-compositor. Try to execute weston-launch > on every virtual terminal. So you just call "weston-launch"? I'm a little surprised if it works and XDG_RUNTIME_DIR is set... Can you check what the values of that env var is in the various vt's or mention if you set it yourself? Are you running as root or multiple accounts? > When you use weston-launch to fire up a weston-compositor, by default it is > without any weston terminal. But you will notice one of the > weston-compositor that you fire up contains 1 or more weston terminal. In > fact if you go back to the virtual terminal used at the bootup (eg. virtual > terminal #2), click on the weston-terminal icon, it will fire up new weston > terminal at another virtual terminal (eg. virtual terminal #1). > > To debug, execute "export" at each weston terminal and observe the > "WAYLAND_DISPLAY". I notice 2 of the virtual terminal shared the same > "WAYLAND_DISPLAY" value. > > Please let me know if you can reproduce this. No, I couldn't (I'm not on your hardware and am running poky so not really the same thing). In any case the new westons get a new WAYLAND_DISPLAY.
Refkit work isn't continuing so mark as obsolete.