[15:55] <mibofra> kdub, hi
[15:56] <mibofra> I don't know if it will be useful, but I obtain this with unity-system-compositor as server, on egltriangle client http://paste.ubuntu.com/9516997/
[15:58] <mibofra> on unity-system-compositor the compositor doesn't stop
[15:59] <mibofra> anyway, [1418572657.681595] (II) graphics:     [EGL_FRAMEBUFFER_TARGET_ANDROID] : 1 this line
[16:00] <mibofra> a strange thing, if 1 represents the /dev/graphics/fbX where 1 is the number of the device, why it's on 1 and not on 0 (fb0)?
[16:00] <mibofra> *is it on
[16:00] <mibofra> but maybe I'm wrong
[17:25] <mibofra> kdub, are you here?
[17:27] <mibofra> AlbertA, hi
[17:33] <anpok> hm maybe tomorrow
[17:33] <anpok> in which context do you get the exception log?
[17:33] <anpok> is there a communication error and the egltriangle client gets disconnected due to that?
[18:14] <mibofra> anpok, unity-system-compositor and egltriangel demo client
[18:14] <mibofra> I get the log on the server
[18:14] <mibofra> *on unity-system-compositor
[18:19] <anpok> mibofra: but the client still works then?
[18:20] <mibofra> anpok, no
[18:21] <mibofra> anpok, only the mir_demo_standalone_render_to_fb works (and I've tried with weston that works with fbdev-backend backend)
[18:21] <mibofra> (just for curiosity)
[18:24] <anpok> ah ok.. so this is the thing to debug..
[18:25] <anpok> either something strange happens on the client and causes the communication failure or on the server..
[18:25] <anpok> you could enable more client or server reports to see whats going on.
[18:33] <mibofra> anpok, we have been arrived with kdub to the conclusion that the compositor it's launched in another way by the mir_demo_standalone_render_to_fb
[18:33] <mibofra> that works
[18:36] <mibofra> I'm curios to see what happens adding to that demo a server infrastructure and using it instead of the other demo servers