Don't know about it much, but according to strace and logs it look like the user is using intel graphics card and egl is trying to use radeon graphics card, which then results in: Unable to initialize Clutter: No currently active connector found https://bugzilla.redhat.com/show_bug.cgi?id=1200439
Mesa egl does indeed support DRI_PRIME for the wayland backend, however unless DRI_PRIME is set, it uses the same card that the server. I guess either the user has set DRI_PRIME or the equivalent drirc option, or Clutter is incorrectly choosing the radeon card as main card, and initialises wayland with it. I do not believe the bug is Mesa side.
Using the device extensions one will be able to enumerate and select the device they want without the need of X or the DRI_PRIME variable. Jonny Lamb posted a series that implements the "base" - device_enumeration + device_query, a few days ago. [1] http://lists.freedesktop.org/archives/mesa-dev/2015-July/089783.html
(In reply to Axel Davy from comment #1) > Mesa egl does indeed support DRI_PRIME for the wayland backend, > > however unless DRI_PRIME is set, it uses the same card that the server. > I guess either the user has set DRI_PRIME or the equivalent drirc option, > or Clutter is incorrectly choosing the radeon card as main card, and > initialises wayland with it. > > I do not believe the bug is Mesa side. Was digging into the code a bit and you're probably right. It looks like mutter is always using /dev/dri/card0 (which is the radeon in this case) https://git.gnome.org/browse/mutter/tree/src/backends/native/meta-launcher.c#n270
https://bugzilla.gnome.org/show_bug.cgi?id=753434
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.