[07:23] <duflu> mlankhorst: Can (or have you already?) document how to try the new rootless XMir?
[07:24] <duflu> I forget everything I learned from the old xmir
[07:24] <duflu> It was so long ago
[07:56] <mlankhorst> that's fine, it's just a mir application :P
[07:56] <mlankhorst> just add -windowed to it
[07:56] <mlankhorst> but it doesn't work well yet
[08:06] <mlankhorst> or was it -rootless
[08:18] <duflu> mlankhorst: Weird. Why do I not see libxmir.so linking to GL-anything?
[08:18] <duflu> It looks like the old version
[08:19] <mlankhorst> duflu: /usr/bin/Xmir..
[08:19] <duflu> mlankhorst: Not packaged yet then? :)
[08:19] <mlankhorst> ppa:mlankhorst/ppa
[08:19] <duflu> Ah
[08:19] <mlankhorst> still crazy experimental at this point :P
[08:20] <duflu> Kay
[08:20] <mlankhorst> especially windowed mode, until I can control positioning there's not much point to windowed mode since menu's won't work right
[08:20] <duflu> Hmm, I crashed USC. I should log/debug that
[08:21] <mlankhorst> Xmir supports DRI2 (OpenGL) if mesa drivers are found, else it falls back to native EGL
[08:21] <duflu> mlankhorst: Have you looked at Alberto's new API for that?
[08:21] <mlankhorst> not yet
[08:22] <duflu> mlankhorst: BTW I saw Trevinho running the rootless version. It had Composite loaded too. Should probably disable that
[08:22] <duflu> Composite+compiz
[08:23] <mlankhorst> oh that's not rootless
[08:23] <mlankhorst> Xmir can run in a window too, and you can load compiz inside it
[08:23] <duflu> OK
[08:24] <mlankhorst> rootless mode gives each window its own mir window, but that doesn't work right yet
[08:24] <duflu> mlankhorst: OK, looking forward to future Xmir
[08:59] <duflu> mlankhorst: I just realised your menus problem isn't yet solveable (unless you have a mini-compositor in your XMir to avoid creating child surfaces :) ... https://bugs.launchpad.net/mir/+bug/1421572
[09:55] <mlankhorst> duflu: yeah thought so, so I didn't bother yet
[12:26] <alan_g> alf_: I've not tracked through the dependencies yet but was just looking at what happens when a shell wants to reconfigure the display. For reasons that are probably inadequate it first stops the compositor, then applies its changes and then restarts the compositor. But the compositor indirectly depends on the shell (i.e. there's a mutual dependency). Shouldn't the compositor simply be listening to display config changes an
[12:26] <alan_g> d handle them for itself?
[12:33] <alf_> alan_g: The idea was to serialize such reconfigurations in the main loop. Note that we need to stop the compositor because otherwise one of its threads may end up accessing display HW resources that we have reconfigured and cause problems/crashes.
[12:35] <alan_g> alf_: Hmm. That's not what's happening of course. And the way it is - Display::configure(*conf) could notify listeners "change is happening"..."change is done"
[12:36] <alan_g> And the compositor can stop & start accordingly
[12:37] <alan_g> me::WindowManager (for example) doesn't use the main loop for config changes
[12:37]  * alan_g doubts me::WindowManager is a good example of anything though
[12:41] <alf_> alan_g: Ideally we would use the MediatingDisplayChanger (through a new interface suitable for the shell's needs)
[12:43] <alan_g> I was just wondering about that (need to check the dependency graph though as depending on MediatingDisplayChanger which depends on Compositor doesn't avoid the loop I started with.
[12:43] <alan_g> )
[12:47] <alf_> alan_g: Yes, there are two orthogonal aspects here: the dependency loop which you want to break, and ensuring we go through the main loop
[12:48] <alan_g> alf_: OK I've got enough to think about. Thanks. (I feel the design process starting)
[14:05] <tsdgeos> racarr: did you see my last comment on https://code.launchpad.net/~mir-team/qtubuntu/port-to-mirclient/+merge/245164 ?
[14:34] <berz3rk> Hello
[14:34] <berz3rk> can I use Virtualbox with the unity next iso?
[14:34] <berz3rk> if not, can I use my gtx 860m notebook directly from boot (nouveau supports it)
[14:42] <anpok> berz3rk: not yet.. but vmware and kvm work
[14:42] <berz3rk> ok good
[14:42] <berz3rk> i try vmware
[14:42] <anpok> vbox has an out of source driver .. it needs a few bits
[14:48] <berz3rk> alan_g: when I boot vmware, I dont get any graphical user interface
[14:49] <berz3rk> anpok...
[14:49] <berz3rk> failed to create login service or something like that in systemd, but now i just see a white mouse cursor ..
[14:50] <greyback> berz3rk: these are the instructions I used once to test unity8 in VMWare: http://pastebin.ubuntu.com/10205619/
[14:52] <kgunn> i confirm those instructions worked for me too...(however i'm on intel gfx)
[14:52] <greyback> me too
[15:08] <alf_> kgunn: I should add these instruction to our official documentation
[15:14] <kgunn> alf_: yes, please...seems like a good idea