[00:41] <RAOF> desrt: Hey, how would you like your client logging integration?
[00:42] <RAOF> (As in: how would you like messages from libmirclient to be presented to you)
[10:29] <alan_g> alf__: it isn't urgent, but as no-one "owns" USC could you please review this at a convenient point? https://code.launchpad.net/~alan-griffiths/unity-system-compositor/migrate-to-mir-Server-API/+merge/240566
[10:33] <alf__> alan_g: sure
[11:13] <mlankhorst> what do I need for setting up lightdm correctly to run unity8 on a normal ubuntu install?
[11:17] <alan_g> mlankhorst: http://unity.ubuntu.com/mir/using_mir_on_pc.html (I hope it is up to date - I've not used if for ages)
[11:18] <mlankhorst> i don't think it is
[11:21] <alan_g> What happens?
[11:22] <alan_g> mzanetti: IIRC you've used unity8 desktop recently. ^^
[11:23] <mlankhorst> I've installed unity8-desktop-session-mir, but it fails to spawn a native mir session
[11:23]  * mzanetti reads
[11:24] <mzanetti> mlankhorst: hmm... that should work. I didn't do anything special.
[11:24] <mzanetti> mlankhorst: try to first log in into a unity7 session, then logout again and relogin to the unity8 session
[11:24] <mzanetti> that seems to improve chances of a successful start
[11:24] <mzanetti> it is still a bit flaky
[11:25] <mzanetti> mlankhorst: I've heard of people with nvidia cards having issues. I'm using an Intel one
[14:22] <desrt> RAOF: 'just use the journal'?
[14:22] <desrt> RAOF: otherwise i guess a callback is fine
[14:22] <mlankhorst> btw does the unity8 session run fullscreen on mir?
[14:25] <greyback> mlankhorst: yes it does
[14:25] <mlankhorst> so if I create a Xmir window there, it will be hidden by the u8 session?
[14:30] <greyback> yes, if that mir client is connecting to unity-system-compositor. But if you connect it to unity8 (MIR_SOCKET=$SDG_RUNTIME_DIR/mir_socket) it should appear in unity8
[14:30] <greyback> you'll need to append "--desktop_file_hint=/usr/share/applications/some-desktop-file.desktop" to the process, else it won't be accepted
[14:31] <greyback> as unity8 is strict, and requires either upstart to launch the app, or else that command line arg appended to the command
[14:35] <mlankhorst> ah
[14:35] <mlankhorst> would that explain the broken pipe? :P
[14:41] <mlankhorst> where can I find that in the source :p
[14:46] <greyback> that policy is defined in lp:qtmir:/src/modules/Unity/Application/application_manager.cpp:ApplicationManager::authorizeSession
[14:49] <mlankhorst> ok
[14:49] <mlankhorst> thanks
[14:53] <seb128> hey
[14:53] <seb128> is it possible to start a demo mir server somewhere while keeping the an xorg/unity7 session running?
[14:54] <seb128> I tried to "sudo mir_demo_server_shell --vt 1" and switch to vt1 but I couldn't come back (or there is a bug with my i965 which bugged the machine)
[14:55] <greyback> seb128: that used to work, lemme try
[14:56] <seb128> greyback, thanks
[15:00] <greyback> seb128: yep worked here
[15:01] <greyback> seb128: ctrl+alt+backspace quits the mir server
[15:01] <greyback> as it tends to ignore Crtl+C in the console that started it
[15:02] <seb128> greyback, thanks
[15:02] <seb128> greyback, can you ctrl-alt-f1 ctrl-alt-f7 to switch between mir and unity7?
[15:02] <greyback> seb128: yes
[15:06] <seb128> greyback, k, thanks for that and for the email ;-)
[15:06] <greyback> seb128: thought it might be handy
[15:07] <seb128> it is indeed :-)
[15:07] <greyback> seb128: while I've got you, somehow unity7 isn't showing up as an option in my lightdm Greeter. Only unity8 is there. ubuntu-desktop is installed. Any ideas?
[15:07] <seb128> greyback, install ubuntu-session
[15:07] <desrt> seb128: getting the server working is another issue...
[15:08] <desrt> seb128: you need to change ownership of the socket and symlink it to the correct location in your user's xdg_runtime_dir (or set env variables to work around)
[15:08] <greyback> seb128: it is installed
[15:09] <seb128> greyback, weird then, is "unity" installed?
[15:09] <greyback> yep, it is
[15:09] <seb128> hum
[15:09] <greyback> I'm a tad confused
[15:09] <greyback> but it's not end of world, it's my unity8 desktop machine anyway
[15:09] <seb128> do you have anything useful in /var/log/lightdm/ ?
[15:09] <seb128> x-0-greeter.log
[15:10] <seb128> desrt, do you know if there is a wikipage or something about the socket thing?
[15:10] <mlankhorst> that the greeter doesn't use mir makes things hard for me. :P
[15:10] <desrt> seb128: no.  i don't.
[15:10] <desrt> seb128: unfortunately this is sort of something that everyone has to discover for themseelves....
[15:10] <desrt> seb128: also: you need to run the server as root
[15:11] <seb128> desrt, the email I crossed had those instructions
[15:11]  * desrt has burned half an hour or so figuring these things out, twice (after having forgot the first round)
[15:11] <seb128> sudo mir_demo_server_shell --vt 1
[15:11] <seb128> sudo env XDG_RUNTIME_DIR=/run/user/1000 MIR_SOCKET=/tmp/mir_socket
[15:11] <desrt> oh.  nice.
[15:11] <seb128> the second command is missing the <command>
[15:11] <desrt> that's a strange combination of environment variables :)
[15:11] <seb128> but you are saying that's not going to be enough?
[15:11] <desrt> you need to change ownership of the socket if you wnat to connect as a normal user
[15:12] <seb128> k
[15:12] <seb128> I'm fine running the command under sudo
[15:12] <seb128> but thanks for the hint
[15:12]  * desrt has had a couple of outstanding requests to improve the situation here...
[15:12] <desrt> seb128: 'don't gtk as root' ;)
[15:12] <seb128> desrt, on a test laptop EDONTCARE ;-)
[15:13]  * greyback has todo item to write up this stuff, sorry hasn't got it done
[15:13] <seb128> that would be useful
[15:13] <seb128> http://unity.ubuntu.com/mir/ doesn't have a lot of useful user informations
[15:14] <mlankhorst> it seems to be hard to run your own unity8 currently..
[15:14] <mlankhorst> at least when not going through lightdm
[15:18]  * desrt is reminded that he has been meaning to file some bugs, and does so: https://bugs.launchpad.net/mir/+bug/1398038 and https://bugs.launchpad.net/mir/+bug/1398039
[15:22] <racarr> Morning
[15:22] <greyback> seb128: extremely messy, but here's the biggest of my notes on unity8/mir http://pad.ubuntu.com/using-mir
[15:28] <seb128> greyback, thanks
[15:29]  * alan_g finds mir doesn't build today
[15:34] <kdub> alan_g|tea, what's not building
[16:22] <seb128> https://errors.ubuntu.com/problem/318a0132ff5aca50838dfffb9bdbe88d1edebf01 is showing on e.u.c for vivid
[16:23] <seb128> hitting abrt in mir_connection_create_surface()
[16:23] <alan_g> kdub: it turns out to be vivid migration detritus
[16:23] <seb128> (just pointing it, dunno if you guys watch e.u.c)
[16:47] <alan_g> seb128: not sure where that report originates, but a test called "createing_surface_on_garbage_connection_is_fatal_Test" forking a process that aborts doesn't seem like anything to worry about
[17:04] <racarr> New rev for mir-event-2.0 :)
[17:09] <seb128> alan_g, right, it's still generating some noise on the error tracker so would be good to fix/disable
[17:12] <alan_g> seb128: I've not looked closely, but we have a number of tests whose purpose is to ensure an abort occurs when required. Are you suggesting that we shouldn't test those scenarios?
[17:12] <seb128> alan_g, hum, no, I just wonder if we could do something to avoid getting e.u.c reports for them
[17:13] <seb128> that's kind of low importance though, so feel free to ignore me ;-)
[17:13] <alan_g> If you can suggest a way to do that in Mir I can follow it up. Otherwise...
[17:14] <seb128> good point
[17:15] <seb128> I'm going to investigate if that's possible, thanks ;-)
[18:28] <kdub> camako, was thinking about how you mentioned that you were looking through the platform code in trying to not tear down the display system on compositor start/stop
[18:29] <kdub> I can point to what android is doing there if that helps
[18:29] <kdub> but it seems to mostly be something the server is doing
[18:29] <kdub> and perhaps some improvement has to be done to the mesa platform too
[18:59] <camako> kdub, thanks. I looked at Android side, and am now looking at the Mesa side which is more involved.
[18:59] <kdub> camako, yeah, the android side its easy to keep the display around... iirc, the mesa side has some complication with VT's
[19:03] <racarr> camako: Thanks for your comments on event-2.0 will get back toyou right after lunch
[22:32] <RAOF> desrt: Oh, I was wrong about how much done eventloop fds is; it's much closer to finished than I thought :)