[02:23] <robjh> hi RAOF. theres no error message. though i didnt try starting my own mir server. The actual output of the program is this http://codetidy.com/7590/
[02:26] <RAOF> robjh: Hah. You're running it on lightdm's system-compositor, not unity8.
[02:26] <RAOF> robjh: Since you can see the phone UI that's not going to work :)
[02:26] <robjh> ooh :p
[02:27] <RAOF> robjh: the MIR_SOCKET environment variable has Unity8's value in it.
[02:28] <duflu> Unless you logged in remotely?...
[02:28] <RAOF> You'll then need to pass -- --desktop_file_hint=gedit.desktop (or something like that) in order to defeat Unity8's “security”.
[02:29] <robjh> i can get the enviroment vatiable from the terminal app i bet
[02:29] <RAOF> Yup.e
[02:29] <RAOF> It'll be /run/user/$SOMETHING/mir_socket
[02:30] <robjh> run/user/32011/mir_socket
[02:30] <robjh> so, yep
[02:32] <robjh> It's working! :D
[02:33] <robjh> thanks for the help :)
[02:33] <RAOF> No problem!
[02:34] <RAOF> ThreadSanitizer: reported 356 warnings
[02:34] <RAOF> Yeah, this'll just take a moment...
[07:53] <sturmflut> Looks like our armhf repositories for xenial contain a libmircookie1 package, but its dependency libnettle4 is missing. Who do I ping about this?
[09:12] <zzarr> hello! Is there a way to try unity8 on a computer with a nVidia card?
[09:26] <duflu> zzarr: Yes in theory, however Unity8 on desktop is a bit hit and miss right now. It doesn't seem to be working properly with the latest xenial today
[09:26] <duflu> So I wouldn't go to the trouble of trying it until the recent basic issues are fixed
[09:27] <corn_field> duflu, yeah... unity8 loads but the wallpaper is black and it doesn't load apps :/ i can see the apps opened in the launcher but not on the desktop o_O weird
[09:28] <duflu> It might (should) work better in wily than xenial, but development continues in xenial only.
[09:28] <corn_field> xenial should start beeing not brake from now on :)))
[09:29] <corn_field> broken
[09:31] <zzarr> okey duflu, but will xenial have support?
[09:32] <duflu> zzarr: Yes, xenial is the bleeding edge. wily is frozen, but likely to be frozen at a less broken stage in the past, at a guess
[09:32] <duflu> Then again, it's early for xenial and Ubuntu usually has lots of teething issues like this every cycle
[09:33] <zzarr> okey, duflu thanks for the heads up :)