<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 TRANSITIONAL//EN"> <HTML> <HEAD> <META HTTP-EQUIV="Content-Type" CONTENT="text/html; CHARSET=UTF-8"> <META NAME="GENERATOR" CONTENT="GtkHTML/4.8.5"> </HEAD> <BODY> On Sat, 2015-04-11 at 00:33 +0200, Mattias Andrée wrote: <BLOCKQUOTE TYPE=CITE> <PRE> Is there another way to identify which display server is actually running? If not, I propose we add the environment variable REAL_DISPLAY. The value of REAL_DISPLAY should be then name of the environment variable used by the display server that is actually running. For example if Wayland is running with an X compatibility layer, the value of REAL_DISPLAY should be WAYLAND_DISPLAY. </PRE> </BLOCKQUOTE> I think this is backwards. The system is more likely to want to setup the environment for the application rather than the application adapting to the system based on a list. As an example we're discussing supporting current applications that required X on the Ubuntu Desktop when running Mir. If a user is running applications that all can talk to Mir directly we're not going to start any type of X compatibility, there's no reason to have it. If the application needs that X compatibility we'll start that proxy as part of the application startup and the application will start in a world that it has X and it is happy. So, it seems to me, that a better solution is to add a key to the desktop file that is something like: <TT> PerferredDisplayProtocol=mir;x11;wayland;</TT> Then we could also not show applications (or show them disabled or some such) that require a protocol that we can't support on a particular system. Ted </BODY> </HTML>