Bug 46629 - [bug] should weston set WAYLAND_DISPLAY variable for weston-desktop-shell (based on --socket argument)
Summary: [bug] should weston set WAYLAND_DISPLAY variable for weston-desktop-shell (ba...
Status: RESOLVED FIXED
Alias: None
Product: Wayland
Classification: Unclassified
Component: weston (show other bugs)
Version: unspecified
Hardware: Other All
: medium minor
Assignee: Wayland bug list
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-02-25 17:19 UTC by nerdopolis1
Modified: 2012-07-31 18:55 UTC (History)
0 users

See Also:
i915 platform:
i915 features:

Attachments

Description nerdopolis1 2012-02-25 17:19:43 UTC 
The problem is right now that when you try to run weston nested under a main weston server, you have to set WAYLAND_DISPLAY for the nested display, and the --socket for the display name for the nested one.  After starting nested weston, weston-desktop-shell in the nested weston display has the WAYLAND_DISPLAY variable for the main display, which makes any programs launched from the nested shells icons appear in the main display instead of the nested one.

My thought is that weston should set WAYLAND_DISPLAY variable to what is specified to --socket to the child process.
Comment 1 Kristian Høgsberg 2012-07-31 18:55:56 UTC 
Yup, makes sense.

commit 3df6384c3a6f3f56a16873b63fdbc731f2ccfadb
Author: Kristian Høgsberg <krh@bitplanet.net>
Date:   Tue Jul 31 14:54:48 2012 -0400

    compositor: Set WAYLAND_DISPLAY if we're given a --socket argument
    
    This lets us run multiple compositors (nested or on different VTs).
    
    https://bugs.freedesktop.org/show_bug.cgi?id=46629

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.