/srv/irclogs.ubuntu.com/2013/09/11/#ubuntu-mir.txt

RAOFrobert_ancell: If you'd like to test, the ubuntu branch of github.com/RAOF/xserver.git should work for you.00:26
robert_ancellRAOF, awesome, thanks00:26
robert_ancellthat has packaging right?00:26
RAOFYup.00:27
RAOFIt's a simple "DEB_BUILD_OPTIONS=parallel=9" debuild -i -I -us -uc away!00:27
RAOFtvoss_: Around?00:39
kgunnRAOF: you know he's in asia right?00:56
RAOFkgunn: Yes, which is why he might be around :)01:01
tvoss_RAOF, yup01:07
* robert_ancell ->lunch01:07
RAOFtvoss_: So, I'd like to raise https://code.launchpad.net/~raof/mir/prebump-abi-for-lifecycle-cookie/+merge/184703 and the associated platform-api change http://bazaar.launchpad.net/~raof/platform-api/update-for-lifecycle-cookie/revision/149 again :)01:08
RAOFduflu: Good morning!01:09
dufluRAOF: Morning; goodish01:10
robotfuelhttps://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1218815 this bug needs triage.01:20
ubot5Launchpad bug 1218815 in xserver-xorg-video-ati (Ubuntu) "[radeon] Graphic glitches and screen corruption (vertical lines) on XMir surfaces only" [Critical,Triaged]01:20
duflurobotfuel: It is triaged already. What are you aiming for? :)01:23
robotfuelhaving it assigned to someone.01:24
robotfuelduflu:01:24
robotfuel^01:24
duflurobotfuel: Ah, yes. I think RAOF thinks he knows the answer. Although a proper fix might require enhancements to Mir first01:25
RAOFYeah, throw it here.01:25
robotfuelduflu: if it was medium or high I could see it not being assigned while there are critical bugs. but all critical bugs should have someone assigned to it, even if it's just the project lead. :)01:27
duflurobotfuel: I disagree. Too often bugs are assigned to people who have other things on their plate. The bug never gets started or taken up by anyone else because it looks like it belongs to someone already01:27
dufluRAOF: Are you _sure_ you need a scanout flag for that?01:29
RAOFduflu: To do it correctly, yes.01:29
RAOFduflu: That flag doesn't need to be a *guarantee* that it'll be scanned out, but it does need to indicate that this buffer needs to be treated as if it could be scanned out.01:30
RAOFWe really need the same for intel, it's just that intel can make a reasonable guess as to whether it might be scanned out or not. Radeon can't.01:30
dufluRAOF: Yeah. So why/how is the stride info we have wrong? Why wouldn't we just fix that?01:30
RAOFBecause it's not stride.01:30
dufluUmm, pitch01:30
duflu?01:31
RAOFIt's not pitch, either. It's bound up with how the tiling is arranged.01:31
dufluUgh01:31
RAOFRight01:31
dufluDamn DDXs01:31
robotfuelduflu: that's what the in progress flag is for in status, if your team wants to do differently then I am okay with that.01:31
RAOFRadeon *is* a bit of a fan of crazily duplicating code and hoping that everyone's using the same stuff.01:32
RAOFBut, as we found, it's the same for Intel - scanout needs to be handled a bit specially.01:32
dufluRAOF: When I started (and finished) bypass support, I had no idea the DDXen would play with the hardware this much :P01:33
dufluI thought I knew what a "client" was. But that's not true for XMir01:33
RAOFI suspect we'll need to do similar things in the Mir EGL platform; we might just not have hit the problems yet.01:34
dufluLess likely. I actually tested it all with EGL on intel + radeon + nouveau01:36
* RAOF could really do with a working second monitor01:59
dufluAdmittedly, I have never needed two. Just happened to buy one for the old office, and brought it home when I left02:05
RAOFUrgh, wow. This is messed up on radeon.02:24
RAOFBut, of course, I can't reproduce the graphical glitches.02:25
RAOFBecause that would make things too easy.02:25
RAOFduflu: The environment variable to disable bypass was MIR_BYPASS=0, right?02:39
dufluRAOF: Yes. Just need to make sure the variable makes it though to the USC process :)02:39
duflu*through02:40
RAOFOk, so radeon exhibits damage problems in multihead.02:45
RAOFAnd also exhibits that "you need to VT switch to get Mir to send new buffers with bypass" problem that we had earlier.02:46
dufluRAOF: I noticed bypass did make bug 1211700 worse. But the bug itself existed before bypass02:57
ubot5bug 1211700 in Mir "[radeon] [nouveau] Unthrottled EGL clients cause Mir to slow, sometimes to a halt" [High,New] https://launchpad.net/bugs/121170002:58
RAOFThat wouldn't be exposed by XMir; XMir *is* throttled.02:58
RAOFWell, ish.02:58
RAOFAlthough XMir is kinda unthrottled, that bug would not be what's affecting XMir, because XMir is idle, waiting in select() when you gdb into it.02:59
dufluRAOF: I had some ideas on how to relieve the problem a while back. And I have nouveau hardware that reproduces it easily. Just wasn't a priority compared to the other issues03:00
RAOFYeah.03:00
RAOFAlthough, to some extent, it's a combination of correct behaviour and insufficient kernel smarts.03:01
dufluYeah Maarten started talking about GPU threads and scheduling on the GPU. It's a whole new world03:06
RAOFBasically what we want is a deadline scheduler for the GPU.03:08
dufluRAOF: Extending MirBufferPackage.... that shouldn't break any ABIs right?03:09
RAOFCorrect.03:10
RAOFAs far as I can tell.03:10
dufluWe get it by pointer03:10
dufluwhich is good03:10
RAOFBecause we allocate them ourselves.03:10
dufluExcept that we return the pointer by parameter from a function with returns void. Which is weird03:10
RAOFYeah, because reasons.03:10
RAOFActually, why do we have that idiom?03:11
dufluRAOF: I think it was a mistake which we overlooked at the time. Returning a pointer as the function result would have been slightly nicer03:12
smspillazduflu: RAOF: isn't MirBufferPackage allocated by the client?03:12
smspillazor am I thinking of something else03:12
RAOFsmspillaz: Not anymore03:12
RAOFIt was03:12
duflusmspillaz: How? It's returned as "type **x"03:12
smspillazRAOF: does this mean I have to change all my code again ? :(03:12
duflusmspillaz: It's not changing03:12
RAOFsmspillaz: A little bit, yes.03:12
smspillazRAOF: when did this change happen?03:13
RAOFduflu: At one point it was a client-allocated MirBufferPackage * that got passed in.03:13
dufluOh03:13
dufluUmm, then Sam's client code shouldn't build so long as warnings are errors... ?03:13
smspillaz  MirBufferPackage *surface_buffer;03:14
smspillaz  mir_surface_get_current_buffer (impl->surface, &surface_buffer);03:14
smspillazlooks like I wrote the gtk+ stuff after that change :)03:14
RAOF:)03:14
dufluCool03:15
RAOFYay kernel builtin edids!03:24
jrryay!03:24
robert_ancellRAOF, I can confirm the input works switching between two sessions - just need to get it switched up to VT switching away from all sessions04:17
RAOFrobert_ancell: That just requires hooking up in unity-system-compositor, right?04:30
robert_ancellRAOF, mostly exposing it from Mir05:00
RAOFRight, as expected.05:00
RAOFOooh.05:36
RAOFInteresting.05:36
RAOF*that's* definitely racy...05:37
RAOFShould be pretty difficult to hit, though?05:37
duflu??05:47
RAOFduflu: Hey, we're always going to be triple buffering, right?05:48
dufluRAOF: Nope. That's kind of a bug. We will and should switch to double when possible05:48
RAOFAt the *moment* we always triple buffer, yes?05:48
RAOFI'm just doing a by-hand verification of my damage tracking logic.05:48
dufluRAOF: Yes, kind of... If the client is slow enough then SwitchingBundle might only hand out 205:49
dufluRAOF: BTW, I removed all the damage and age tracking and that bug remained. It's not in the damage tracking AFAIK05:49
RAOFduflu: Oh, we get the damage_for_current_buffer *after* we submit the previous buffer. So, in the unlikely event that X gets preempted and the swap completes before the next line we'll clear the damage from the wrong place.05:50
dufluRAOF: Sounds similar to my first theory. I now forget why I stopped believing it05:52
RAOFBecause you removed all the damage tracking and the bug remained? :)05:52
dufluRAOF: Maybe...05:52
dufluRAOF: I mean I got rid of age tracking and set the dirty region to the whole xmir_win (or empty)05:53
dufluThen the bug remains. But if you never allow dirty to be empty then the bug will be hidden05:53
RAOFRight. Because you just continually render05:54
dufluRAOF: Boo... Mesa requires MirBufferPackage never grows:05:55
duflumir_advance_colour_buffer(struct dri2_egl_surface *surf)05:55
duflu{05:55
duflu   MirBufferPackage buffer_package;05:55
duflu   if(!surf->mir_surf->surface_advance_buffer(surf->mir_surf, &buffer_package))05:55
dufluI can work around it I think05:56
RAOFduflu: Oh. Yay for having two distinct APIs for exactly the same thing05:56
robert_ancellduflu, racarr, kdub, alf_ hikiko - meeting05:59
robert_ancellkgunn too05:59
kgunn:)05:59
=== chihchun_afk is now known as chihchun
hikikoit seems i am alone in the hangout :) rejoining06:01
robert_ancellhikiko, we're there!06:01
hikikoquestion: :)06:24
hikikois magic sysrq disabled on kernel?06:24
robert_ancellhikiko, it works for me06:24
dufluGood question. It never works for me. But I likely get it wrong06:24
robert_ancellI use it frequently when the VTs break06:24
hikikorobert_ancell, how did you enable it? in /proc/sysrq?06:25
robert_ancellfor me: hold down alt+PrintScr, then s-u-b06:25
robert_ancellhikiko, I don't think I've done anything to enable it06:25
hikikoyes, I know but it's a laptop here and sysrq doesnt work so I was wondering if I have to do something:/06:25
hikikooh no :D it worked now :D thanks robert_ancell06:26
robert_ancellhikiko, np06:27
hikikoI was trying with s u g/h :)06:27
robert_ancellhikiko, you can check in dmesg if any SysReq events have occurred06:27
robert_ancellbye all06:28
duflu_Ha. Works now :)06:29
=== duflu_ is now known as duflu
alf_RAOF: what's the process for getting Mesa updates in the archive? Are they picked up automatically from your github branches?06:29
hikiko\m/06:30
RAOFalf_: No, I do that manually.06:38
=== alf_ is now known as alf|xmir_devel
mlankhorstalf|xmir_devel: ping07:06
alf|xmir_develmlankhorst: pong07:35
mlankhorstalf|xmir_devel: can you help me reproduce the issue? what branches etc do I need07:39
alf|xmir_develmlankhorst: follow the instructions from https://lists.ubuntu.com/archives/mir-devel/2013-September/000376.html07:50
alf|xmir_develmlankhorst: for mesa you can use the https://github.com/afrantzis/mesa/tree/egl-platform-mir-egl-image-i965-experiment branch07:50
mlankhorstok07:50
alf|xmir_develmlankhorst: for mir use lp:~afrantzis/mir/spike-nested-gbm-egl-image-hack as noted in the mail, I have updated it remove the stray dup()07:51
alf|xmir_develmlankhorst: the mesa branch contains the i965 changes which you may want to remove or change, and also in platform_mir.c don't forget to set USE_DUP and USE_PRIME to the values you want07:52
mlankhorstalf|xmir_devel: oh using drm bus id is a bad idea, best to open dev directly, but unrelated to your issue :P07:54
mlankhorstRAOF: https://bugs.freedesktop.org/show_bug.cgi?id=60182 with fix it seems :p08:09
ubot5Freedesktop bug 60182 in DRM/Radeon "X.Org Server terminate when I close video player" [Critical,New]08:09
mlankhorstalf|xmir_devel: oh btw test seems to fail when I try building mir there..08:15
mlankhorstThe following tests FAILED:08:16
mlankhorst         10 - acceptance-tests.TestNestedMir.* (Failed)08:16
mlankhorst         55 - unit-tests.GBMGraphicBufferBasic.* (Failed)08:16
alf|xmir_develmlankhorst: yes, don't worry, it's because I have updated/hacked the code without updating the tests08:16
mlankhorstok08:16
alan_galf|xmir_devel: @"mlankhorst: I actually see a dup() in NestedMir... I will get rid of this and check what is going on" - the frontend code closes FDs after sending them to the client to avoid resource leaks.08:22
mlankhorstalan_g: then why is that dup needed at all?08:23
alf|xmir_develalan_g: right, the point is that we should be opening a new drm fd instance, not duping the drm fd we use in the platform08:24
mlankhorstpretty much08:24
alf|xmir_develalan_g: I have hacked a fix in lp:~afrantzis/mir/spike-nested-gbm-egl-image-hack for testing purposes, but we need to find a better way to do it.08:24
alan_galf|xmir_devel: Shall I leave you to it? Or get involved?08:26
alf|xmir_develalan_g: If you can take a look at the latest commit in lp:~afrantzis/mir/spike-nested-gbm-egl-image-hack, and come up with a better design for it, it would be great. Right now I am passing an auth_magic std::function to NativePlatform::initialize which is platform-specific in the sense that it is only needed on GBM.08:30
alf|xmir_develalan_g: (but it is not urgent, we first need to solve the egl image problem before any of this is usable on trunk)08:33
mlankhorstok I've merged the branch against 9.2 and built the packages :P08:33
alan_galf|xmir_devel: OK, I was going to look at tidying some of the "nested" code that has landed, and then look at the differences between what kdub landed on trunk for android and what we had on the gbm spike.08:35
alan_gThis fits into the latter category08:35
alf|xmir_develalan_g: sounds good08:35
=== alf|xmir_devel is now known as alf|probable_pow
=== alf|probable_pow is now known as alf|power_outage
* alan_g wonders: "Prisoner Of War"08:37
ollicompositor wars...08:43
mlankhorstalf|power_outage: fwiw, nested mir works for me on nouveau, I'll try on intel..08:51
mlankhorstok crash, weeeee09:02
hikikoquestion:09:06
hikiko131 [ 473.381] (==) Depth 24 pixmap format is 32 bpp09:06
hikiko132 [ 474.356] (==) FBDEV(0): Backing store disabled09:06
hikiko133 [ 474.358] (EE) FBDEV(0): FBIOPUTCMAP: Invalid argument09:06
hikikoI get this failsafe log09:06
hikikowhen xmir crashes09:06
hikikoand i wonder if someone knows what it means (I find different explanations here and there) + I am trying to understand if this caused the crash or it is a result of the crash or irrelevant09:08
RAOFhikiko: That'd just be the failsafe X log. That gets started if X crashes on startup for some reason.09:14
hikikoso, it's totally irrelevant09:14
hikikoisn't it?09:14
RAOFYeah.09:15
dufluhikiko: fbdev is the fallback driver of last resort. It does not support Mir (yet) and means the real driver failed to start USC09:15
hikikocool :)09:15
RAOFThat'll only happen *after* you crash the original X :)09:15
dufluSo long as fbdev isn't crashing too09:15
hikikoit isnt09:15
hikikoand another question: sometimes I restart lightdm and instead of starting X with xmir it starts X09:17
hikikoif I restart many times09:17
hikikoand I have no clue why I dont get a crash at that point09:19
dufluhikiko: In theory, X is meant to start in legacy mode *every time* Mir (unity-system-compositor) fails to start09:19
hikikoif I just run restart lightdm too many times at somepoint X starts instead of X -mir09:19
hikikooh09:20
dufluhikiko: We always (1) Try Mir and if that fails (2) Start legacy X09:20
dufluIf (2) fails then that's a new bug09:20
hikikobut if 2 fails then09:20
hikikowe start Mir or X?09:20
dufluhikiko: If (2) fails then that's a new bug no one has logged yet. Sounds important :)09:21
hikikowhat happens is:09:21
hikiko(in some cases)09:21
hikikoI run restart lightdm many times and mir restarts ok with no crash09:21
hikikoat some point I restart and X starts09:22
hikiko(no crash)09:22
hikikoand then if I restart lightdm09:22
hikikoMir will start and crash09:22
dufluhikiko: If Mir crashes then look in /var/log/lightdm/unity-system-compositor.log for the cause. Hopefully it's a bug we already know about09:23
hikikook :)09:23
hikikothanks duflu RAOF09:24
dufluNo problem09:24
mlankhorstalf|power_outage: does the nested mir server only use a single drm fd?09:42
mlankhorstscrew it, I'm going to make the kernel tell me why ENOENT happens09:47
mlankhorst[  105.467925] [drm] unknown target object for relocation 709:50
mlankhorst 2: 2 (batchbuffer)@0x000000e0 -> 7 (region)@0x00000000 + 0x0000000009:51
mlankhorstodd09:52
mlankhorstwhich is from intelAllocateBuffer09:53
alan_gmlankhorst: the nested mir uses a drm fd for two things: to init gbm and to send to clients that init gbm. I got the second from the first using dup() because FD sent to clients get closed automatically), but IIUC alf|power_outage changed that...09:53
mlankhorst ====== Created gbm_bo 0x7f2e340026f0 0x7f2e340026f0 with image 0x7f2e34002740 handle: 7 screen: 0x72d390 ======09:54
mlankhorstwhich no longer exists, it seems..09:54
mlankhorstalan_g: yes, and each client needs their own instance of the drm fd09:54
mlankhorstelse really really bad things(TM) will happen09:54
* alan_g already knows he got it wrong09:55
mlankhorstalan_g: the question is.. does non-nested mir share its own drm fd too?09:58
alan_gmlankhorst: no, it uses drmOpen()09:59
mlankhorstok good.. still things are messing up somewhere :P10:00
alan_gmlankhorst: if it helps the host mir uses int mggh::DRMHelper::get_authenticated_fd() to get the FD it passes out. (I've not yet looked at alf|power_outage nested code)10:02
mlankhorsthm in this case it seem likely isolated to the nested server only now for sure10:06
alf|power_outagealan_g: it's almost the same code, with the difference that we need to ask the host mir server to auth the magic cookie (since the nested mir is non DRM master)10:06
alf|power_outagemlankhorst: ^^10:06
=== alf|power_outage is now known as alf_
* duflu goes to create some culinary splendour10:08
* alan_g goes to make some tea10:11
* RAOF decides that his manual review of the XMir damage logic suggests that it's sound, and EODs.10:11
mlankhorstalf_: my only conclusion is that nested mir and master mir share the drm fd..10:17
mlankhorstand I'm damned sure that's the case10:18
mlankhorstsee http://paste.debian.net/38295/10:19
mlankhorstLinux kernel complains relocation target 7 no longer exists..10:19
mlankhorstoh no, in this case it was 610:21
mlankhorsthm damn wtf is going on :P10:21
alf_mlankhorst: that is what I have been wondering for a few days now :)10:22
mlankhorstok so intel does enable bo re-use..10:30
mlankhorstmeh lets kill that off first10:31
mlankhorstoh i see10:34
mlankhorstprobably intel bug..10:34
mlankhorst ====== platform_mir: dri2 swap buffers: before flush ======10:34
mlankhorst 0: 8 (prime)10:34
mlankhorst 1: 9 (vb)10:34
mlankhorst 2: 2 (batchbuffer)@0x00000010 -> 8 (prime)@0x00000000 + 0x0000000010:34
mlankhorst 2: 2 (batchbuffer)@0x00000094 -> 8 (prime)@0x00000000 + 0x0000000010:34
mlankhorst 2: 2 (batchbuffer)@0x000000e0 -> 6 (region)@0x00000000 + 0x0000000010:34
mlankhorst 2: 2 (batchbuffer)@0x00000174 -> 9 (vb)@0x00000000 + 0x0000000010:35
mlankhorstthere is a relocation for 6, but that bo is not mentioned on the validation list10:35
mlankhorstit's still a valid bo, afaict10:35
mlankhorstso now to figure out why relocation is failing like that :P10:39
=== alan_g is now known as alan_g|afk
=== alan_g|afk is now known as alan_g
mlankhorstalf_: ah, intel has an internal cache that gets re-used for flink..11:22
alan_galf_: what's the state of the art branch for nested/gbm?11:36
alan_glp:~afrantzis/mir/spike-nested-gbm-egl-image-hack?11:36
alf_alan_g: ~afrantzis/mir/spike-nested-gbm-egl-image-hack yes11:37
alan_galf_: OK to top-approve lp:~alan-griffiths/mir/cleanup-NativeAndroidPlatform?11:39
alf_alan_g: I am OK, although I haven't tested it on an Android device, but it seems harmless.11:40
=== alf_ is now known as alf|xmir-devel
=== alan_g is now known as alan_g|lunch
mlankhorstalf|xmir-devel: definitely some memory corruption going on, no idea what exactly though12:01
=== hikiko is now known as hikiko|lunch
=== chihchun is now known as chihchun_afk
=== alan_g|lunch is now known as alan_g
mlankhorsthuh wtf12:46
alf|xmir-develmlankhorst: ?12:51
mlankhorstalf|xmir-devel: hitting some very weird bug, it's probably in intel but I don't see why it's doing whatever it is it's doing..12:55
mlankhorstoh finally some sense..13:00
mlankhorst(gdb) print bo->bufmgr13:01
mlankhorst$6 = (drm_intel_bufmgr *) 0x6580d013:01
mlankhorst(gdb) print bo->bufmgr13:01
mlankhorst$5 = (drm_intel_bufmgr *) 0x63628013:01
mlankhorstwhy are there 2 drm_intel_bufmgrs ?13:01
mlankhorstseriously..13:03
mlankhorstgbm can create a screen, egl probably creates a separate screen or something13:07
mlankhorst#7  0x00007ffff3d821be in gbm_create_device (fd=16) at ../../../../src/gbm/main/gbm.c:15613:08
mlankhorst#8  0x00007ffff61d3dea in eglInitialize (dpy=0x64e3b0, major=0x7fffffffe1f8, minor=0x7fffffffe1fc) at ../../../../../src/egl/main/eglapi.c:31713:08
mlankhorstso eglInitialize and gbm_create_device13:08
alf|xmir-develmlankhorst: perhaps that's why dupImage doesn't work at all, and we need to create a new image for the Mir EGL screen (USE_DUP=0)?13:15
mlankhorstalf|xmir-devel: no you really need to get rid of the separate copy13:16
mlankhorstRAOF wrote the code, he may know how to do that..13:16
alf|xmir-develmlankhorst: which code?13:17
mlankhorstthe 'screen' comes from mir13:18
mlankhorstbut you're creating the gbm without any knowledge of it13:19
alf|xmir-develmlankhorst: I guess we could go the other way too, as I think platform_drm does... use the dri2 info from GBM to set up the EGL dri2.13:20
mlankhorstthat's the thing you should do13:20
mlankhorstdoes that kill off the platform_mir by any chance? :P13:20
mlankhorstprobably not, but in any case mir probably needs to know about the gbm screen and use it13:22
alf|xmir-develmlankhorst: no, we have our own native display and window types13:22
mlankhorstspecifically13:23
mlankhorst   if (!dri2_create_screen(disp))13:23
mlankhorst      goto cleanup_dpy;13:23
mlankhorstthat line is wrong13:23
=== hikiko|lunch is now known as hikiko
mlankhorstplease don't make such hard to debug problems in the future13:24
mlankhorst:P13:24
mlankhorst(and I checked git blame, so I know it was you)13:27
alf|xmir-develmlankhorst: I need to talk to RAOF tomorrow, to see how we can move ahead with this, since I think that it involves some significant changes in platform mir and the information we pass to platform mir from mir (right now it is just the drm fd)13:28
mlankhorstsure13:28
mlankhorstand you're welcome, please try to give me easier problems next time ;)13:29
alf|xmir-develmlankhorst: thank you :) I really appreciate your time and effort!13:29
mlankhorstafter that dupimage will work correctly and flink vs w/e doesn't matter13:31
mlankhorstis there anything else using gbm? :P13:32
alf|xmir-develmlankhorst: the display subsystem is using gbm internally, but that's using platform_drm so no problems there13:34
alf|xmir-develmlankhorst: (in host mir)13:34
alan_galf|xmir-devel: it sounds like you understand the problem (if not the solution)?13:37
mlankhorstwell there were 2 problems, but seems so :p13:38
mlankhorstother problem was sharing drm fd13:40
kgunnmlankhorst: \o/13:50
sil2100kgunn: hi!13:53
sil2100kgunn: we have a critical bug in Mir related to intel (most probably) - could you guys take a look at that and check if it's indeed a Mir issue? Or maybe something wrong with the intel driver?13:53
sil2100kgunn: https://bugs.launchpad.net/mir/+bug/122388913:53
ubot5Launchpad bug 1223889 in Mir "Mir crashing on Intel drivers - memory corruption in /usr/bin/X" [Critical,New]13:53
* kgunn looks13:54
=== chihchun_afk is now known as chihchun
sil2100kgunn: if you need some more logs besides lightdm.log, x.log and unity-system-compositor.log then this is the last chance ;p Since I need to restart the container, as it's dead13:55
kgunnsil2100: go ahead13:55
kgunnsil2100: so this is effectively the ppa from daily-build ??13:56
kgunnjust curious how we potentially bisect13:56
=== dandrader is now known as dandrader|afk
kgunn....and ironically mlankhorst was working on intel mem corruption a moment ago....same thing ?13:57
sil2100kgunn: yes, this is using the current daily-build PPA contents, at least for the mir parts13:57
mlankhorstkgunn: only affected nesting13:57
mlankhorstafaik xorg-server doesn't use gbm13:57
kgunnmlankhorst: was worth a hope :)13:57
kgunnalf|xmir-devel: ...i don't want wreck your train of thot, but could you take a closer look at https://bugs.launchpad.net/mir/+bug/122388913:58
ubot5Launchpad bug 1223889 in Mir "Mir crashing on Intel drivers - memory corruption in /usr/bin/X" [Critical,New]13:58
kgunnsince RAOF & duflu are sleeping13:59
kgunnsil2100: i assume this means usc/mir/xmir are held up13:59
alf|xmir-develalan_g: mlankhorst: yes (more or less), but I am not clear of the details of the solution yet... it is complicated because we need to pass to the "client" version of EGL platform mir information that only a server has (e.g. gbm_device*)14:00
sil2100kgunn: well, yes, and it's also a bit inconvinient as because it causes an X crash, it breaks our intel machine, so it blocks up the whole release queue - since the broken, X-less intel machine is hanged until timeout or until someone notices to abort manually...14:00
mlankhorstalf|xmir-devel: not really.. server doesn't need egl platform mir. Only nested client does. :P14:01
sil2100kgunn: so essentially this problem breaks and slightly blocks all other packages, because it's breaking our test architecture14:01
kgunnsil2100: is there a simple way to roll back the ppa to be based on the "previous" version of u-s-c/mir/xserver-xorg-video-intel  that was working for you14:02
alf|xmir-develmlankhorst: that's what I mean, a client (nested mir) needs to pass information to Mesa that is server related (gbm_device*)14:02
alf|xmir-develmlankhorst: remember we are doing server buffer allocation14:03
sil2100kgunn: sadly not really... we would have to know what revision caused the failure, revert, rebuilt etc. - worse if the intel upload causes the problems14:04
sil2100kgunn, didrocks: if you don't mind, I'll skip mirslave release this tick14:08
sil2100kgunn, didrocks: we know it's broken and at least it won't break all other stacks :) We can run it later14:09
kgunnsil2100: so you're saying that standalone X intel is fine with this xserver-xorg-video-intel...right ?14:10
sil2100kgunn: yes, it's only happening when mir is used apparently14:11
sil2100Would have to see locally on my machine if the crash is happening, but there's so many things pending...14:11
kgunnsil2100: just for bisecting...we know that yesterday, had no problems....and this morning...we have problems right ?14:11
kgunnmeaning...we must have pushed something in xmir/mir/xserver-xorg-video-intel w/in last 24 hours that caused this14:12
sil2100kgunn: let me check that, since we had some 'other' problems yesterday, but I'll check - from what I know it only happened today14:12
kgunnsil2100: that would be really helpful to know....when the last good combo was14:13
sil2100kgunn: bad news is... we didn't have a successful run yesterday as well, but not because of an X crash14:14
sil2100kgunn: we DNS-resolve problems, so no release happened14:15
kgunnok but maybe last friday was ok?14:15
kgunnsil2100: ^14:15
sil2100kgunn: the last successful run was on the 6th, then the infra errors started happening14:15
sil2100kgunn: yes, it seems we didn't have a successful run since libmirclient3 was introduced ;p14:16
sil2100I mean, just today seems to be the first time the tests are actually ran14:16
kgunnsil2100: hmmm....could be14:17
kgunnbut the build order took care of that sort of thing i thot14:17
=== dandrader|afk is now known as dandrader
mlankhorstkgunn: please just valgrind ;P14:22
mlankhorstit's there for a reason! :D14:22
mlankhorstmake /etc/X11/X2 with these contents: #!/bin/bash14:22
mlankhorstexec /usr/bin/valgrind --show-reachable=yes --track-fds=yes --leak-check=full --error-limit=no --freelist-vol=500000000 --track-origins=yes --leak-resolution=high --malloc-fill=ef --free-fill=df /usr/bin/Xorg "$@" -core -verbose 10 &>>/var/log/valgrind.log14:23
mlankhorstand install xserver.*dbg14:26
mlankhorstsymlink /etc/X11/X to it, /etc/X11/X must stay a symlink :p14:27
alf|xmir-develkgunn: I will try to reproduce/investigate a bit later14:29
kgunnalf|xmir-devel: i assume you understand 'how to' what mlankhorst just said :)14:31
racarrMorning!14:39
kgunnmornin'14:41
=== alan_g is now known as alan_g|tea
=== 3JTAAEL6B is now known as tvoss
tvosshey guys :)14:48
=== jono is now known as Guest91193
didrockssil2100: ack14:51
racarrhey tvoss :)14:53
tvossracarr, o/14:53
racarrtvoss: Will you be in Lexington?14:56
tvossracarr, nope, unfortunately not :/14:56
racarrAww14:58
ricmmracarr: ping14:58
ricmmracarr: how are we doing with the DPMS-android stuff14:58
ricmmis there an API in place in Mir yet or not? if not, I'll need some of your aid to reach the hwcomposer hal directly from powerd14:58
ricmm:)14:58
tvossricmm, kdub might be able to help, too14:59
ricmmright just wondering as we had this discussion last week and there was a quick testing that was gonna happen14:59
ricmmso, if it hasnt happened then I'll make the call of doing direct powerd->hal access for the screen control14:59
ricmmuntil theres a problem the_shell_display_power_controller() or whatever under android, heh15:00
ricmman interface, not a problem, sorry15:00
racarrricmm: Pong!15:00
racarrricmm: There is an API in place15:00
ricmmracarr: awesome15:00
ricmmwhich one is it? got a landing rev? sorry15:00
racarrricmm: Part of the display configuration API15:00
racarrno worries! lemme find it15:00
racarralso standup? No one else is there15:01
ricmmdarn that one is complicated15:01
hikikoi am racarr15:01
hikikobut i see nobody else :p15:01
hikikolet me relogin again15:01
=== alan_g|tea is now known as alan_g
ricmm105415:01
hikikoracarr, still alone :)15:01
alan_gI see no-one too15:01
kgunni see alan15:02
alan_gI see kgunn15:02
racarrricmm: 105415:02
racarrricmm: The impl isn't landed due to a series of issues with doing it over IPC15:02
hikikoracarr, we are all at the same hangout!15:02
racarrs/landed/proposed15:02
racarrhikiko: Can you give me the link?15:02
ricmmyea thats what im just seeing15:02
racarrCAlendar link isn't working for me15:02
ricmmif theres no impl then I cannot use it15:02
ricmmracarr: can you point me to the HAL interface you were planning to use?15:03
racarrricmm: hwcomposer.h blank/unblank15:03
racarrricmm: It all works actually for android, I can propose the android impl asap15:03
ricmmgbm is the one thats broken?15:04
ricmmwell to be fair I might do the direct powerd access as theres no short-term plan for the shell policy enacter15:04
ricmmso it will still have to be powerd15:04
ricmmsimpler to do powerd -> hal instead of powerd -> dbus -> shell -> hal15:05
racarrMir has to know to stop rendering, etc though, and dieally wouldn't report this as errors15:05
racarractually I can sort of make15:05
racarrGBM work the problem is it's over15:05
racarrwell let me explain in just a few minutes15:05
racarrstandup :)15:05
ricmmok15:06
=== chihchun is now known as chihchun_afk
kgunnalf|xmir-devel: i was just wondering aloud to robert if this https://code.launchpad.net/~robertcarr/mir/dpms-support-api/+merge/181884 might have been the issue15:11
kgunnbut....the build stacks should'be taken care of it15:11
kgunnnew api, but no new impl....should'be just rebuilt15:11
kgunnalan_g: assume you had a problem....can you rejoin hangout?15:19
kgunnalan_g: racarr wanted to chat about ipc wrt dpms15:19
alan_gkgunn: no - just no interest in the followup conversation15:19
ricmmracarr: ping, got a minute now then?15:38
ricmmkgunn: does that mean that the discussion didnt happen? :)15:39
kgunnricmm: we're discussing mir ipc wrt dpms atm on a hangout15:39
ricmmawesome15:39
didrockskgunn: hey! yesterday I asked to not migrate the libmirclient ABI15:42
didrocksas asac and I are trying to get the unity8 on Mir15:42
didrocksand once again, the transition was done…15:42
didrocksit's the 3rd time that happens from the Mir team that we ask to not do risky things and this happen15:43
kgunndidrocks: who did you ask?15:43
didrocksnow all dailies are busted15:43
didrockscan check the logs15:43
ricmmdidrocks: it was bumped?15:43
didrockskgunn: the last 2 times, you were in the loop IIRC15:43
didrocksricmm: to libmirclient315:43
ricmmdarn15:43
didrockslet me check for that one15:43
didrockskgunn: robert_ancell15:44
didrocks2013-09-10 17:33:56     robert_ancell_  didrocks, the mirclient3 transition?15:44
didrocks2013-09-10 17:45:52     didrocks        robert_ancell: urgh, transition?15:44
didrocks2013-09-10 17:45:58     didrocks        robert_ancell: no transition right now please15:44
didrocks2013-09-10 17:46:09     didrocks        asac tries to get unity-mir on15:44
kgunndidrocks: ok15:44
ricmmdidrocks: unity-mir doesnt depend on libmirclient3, only qtubuntu/platform-api -> apps15:44
didrocksit's the 3 times on 3 when we ask the Mir team to be cautious and it seems we are unheard15:44
ricmmerr, mirclient in general15:45
didrocksI'm *really* unimpressed15:45
ricmmdidrocks: what room are you in?15:45
kgunndidrocks: ....cause we did screw up on libmirclient2...no mir-devel mail (someone screamed)...15:45
kgunndidrocks: then...we did diligence https://lists.ubuntu.com/archives/mir-devel/2013-September/000373.html15:45
didrocksricmm: right, but the drivers are depending on it15:45
kgunndidrocks: but no one replied on mir-devel15:45
didrockskgunn: you know, we deliver in ubuntu15:45
didrockskgunn: ubuntu-devel would be the first step15:45
didrocksand checking with the integration team would have been great15:45
didrocksand when the integration team tells "please no", listening to them would be good15:46
kgunndidrocks: i thot agreement was mir-devel15:46
didrockskgunn: I'm not on that last15:46
didrockskgunn: I can't be on all upstream ML15:46
didrockslist*15:46
kgunndidrocks: yes...chatting with robert A on irc...i would've thot would take care15:46
kgunndidrocks: ok...so now, ubuntu-dev....if we mail out a warning on that...that is where you want to see it ?....is there another mail for "integration team"15:47
kgunn?15:47
didrockskgunn: it's the main ubuntu ML15:47
didrocksso everyone is supposed to read it15:47
kgunndidrocks: ok, just trying to make sure...when libmirclient4 happens we dont f up again....so ubuntu-dev...right?15:48
didrockskgunn: right ubuntu-dev, and as it's a packaging change, pinging the integration team15:48
didrocksso that they can review it15:49
kgunndidrocks: integration team being you, mirv, sil ? anyone else?15:49
didrockskgunn: ~ubuntu-unity as per https://wiki.ubuntu.com/DailyRelease/FAQ#What.27s_needed_to_be_done_when_proposing_a_branch_or_reviewing.3F15:50
kgunnhttps://launchpad.net/~ubuntu-unity <- didrocks15:51
didrockskgunn: right15:52
racarrricmm: Ok so the DPMS issue is the IPC API doesn't work but that';s only for xmir15:54
racarrso if you want I can try and propose an android impl soon (should take like 2-3 hours of work to finish it off)15:55
racarrthat will work via in server APIs15:55
didrockskgunn: discussing with asac15:55
didrockswe revert the change now15:56
kgunndidrocks: ack...compiling note to the team for permanence....sorry it happened15:57
=== tkamppeter_ is now known as tkamppeter
didrockskgunn: thanks16:03
=== dandrader is now known as dandrader|lunch
sil2100kgunn: is the revert taking place now? If not, I'll revert it myself if needed, as we want to have this resolved ASAP16:17
ricmmracarr: please do, but that wont really land anytime soon into a released image16:18
ricmmracarr: but we need it in there one way or another :) will ping you in a couple hours to see how we are doing16:19
didrockssil2100: ok, it seems kgunn isn't available, we already agree on the revert, please do16:24
sil2100ACK16:25
kgunndidrocks: can we still help win you time ?16:32
didrockssil2100: did you do it? ^16:33
kgunnracarr: can we back out the libmirclient3 change ?16:33
didrockskgunn: only backing out that one before next tick (so in the next 10 minutes) will help16:33
kgunndidrocks: sil2100 ...this is the correct one right ?16:35
kgunnhttps://code.launchpad.net/~robertcarr/mir/dpms-support-api/+merge/18188416:35
sil2100didrocks: compiling16:35
kgunnsil2100: thanks16:35
sil2100I need to test build my revert16:35
sil2100kgunn: yeah, that's the one, I made a revert and checking if it builds16:36
kgunnsil2100: thanks...i was going to pull & update myself if needed...16:36
didrocksthanks kgunn and sil210016:36
* didrocks continues on unity8/unity-mir meanwhile16:37
kgunnalways a bit dangerous to have managers touching code16:37
didrocksheh16:38
sil2100Build already daaamn! *hastes his bzr bd*16:40
jono_kgunn, hey16:44
jono_when do we plan on switching on Mir by default in 13.10?16:44
kgunnour goal  is next week sept 19, we have key bugs to address next week we have16:45
kgunna sprint in lexington16:45
kgunnto try to kill off the ones we consider "make xmir default" blockers16:46
kgunnjono_: ^16:46
jono_kgunn, perfect16:47
jono_thanks :-)16:47
jono_kgunn, how is everything going?16:47
jono_frantic I assume :-)16:47
kgunnjono_: yeah...frantic is a decent description (w/o swear words that is)16:48
jono_lol16:48
jono_:-)16:48
kgunnsil2100: gotta mp yet ? lemme know i'll top approve17:05
sil2100kgunn: I have it up, but it's not building correctly on my system - I have some unresolved symbol, need to check if it's a result of the changes or not17:05
sil2100kgunn: https://code.launchpad.net/~sil2100/mir/revert_libmirclient3/+merge/18511017:05
sil2100kgunn: could you maybe try?17:05
kgunnsil2100: will do (switching machines)17:06
kgunnracarr: ^ mind being a savvy set of mir-team eyes on this one https://code.launchpad.net/~sil2100/mir/revert_libmirclient3/+merge/18511017:06
=== alan_g is now known as alan_g|EOD
sil2100racarr: I'm gettin the following error: /opt/tmp/canonical/stacks/tmp/build-area/mir-0.0.10+13.10.20130904/obj-x86_64-linux-gnu/bin/unit-tests: symbol lookup error: /opt/tmp/canonical/stacks/tmp/build-area/mir-0.0.10+13.10.20130904/obj-x86_64-linux-gnu/bin/unit-tests: undefined symbol: eglCreateImageKHR17:07
sil2100racarr: you know if this could be caused by the revert?17:08
sil2100racarr: or is there something just wrong on my system17:08
kgunnsil2100: are you building for arm or amd64 ?17:10
kgunnoh sorry...i see x86_6417:10
sil2100Yes, building locally, since cross-building would take even more time17:11
kgunnsil2100: right...but target build is amd64....not arm right ?17:11
kgunnsil2100: is mesa &  xserver-xorg-video-intel driver up to date17:12
sil2100kgunn: that's why I wanted you to try and build it locally on your machine just in case ;) I'm building lp:mir right now, if that fails as well then it's not the revert's fault17:13
kgunnsil2100: i suspect its unrelated...no gl code touched in that libmirclient3 code change17:14
bschaefersil2100, mines defined here:17:16
bschaefereglext.h:84:EGLAPI EGLImageKHR EGLAPIENTRY eglCreateImageKHR (EGLDisplay dpy, EGLContext ctx, EGLenum target, EGLClientBuffer buffer, const EGLint *attrib_list);17:16
bschaeferpossibly missing an update to egl :)17:16
sil2100bschaefer: right, lp:mir failed as well here ;)17:18
bschaefer:), sorry, just saw the undefined symbol and looked it up17:19
sil2100bschaefer: but interesting, my libegl1-mesa is up-to-date!17:20
sil2100And libegl1-mesa-dev as well ;p17:21
bschaefer  Installed: 9.2-1ubuntu1?17:21
sil21009.2-1ubuntu1, yes17:21
bschaefersil2100, hmm it should be  dpkg -L libegl1-mesa-dev17:22
bschaeferinstalling it...17:22
sil2100I have eglCreateImageKHR in the header as well, but hmmm17:22
bschaefero...then that is indeed strange17:22
sil2100I wonder what's up ;) bschaefer does lp:mir build for you normally?17:22
sil2100kgunn: but anyway, if it builds for you, let's approve it17:23
bschaefersil2100, let me check!17:23
sil2100CI will build it as well and only merge if it's ok17:23
* bschaefer can also check libmesa to see if that function is defined or not...17:23
sil2100bschaefer: thanks!17:23
sil2100Maybe EGL_EGLEXT_PROTOTYPES is undefined on my system ;p17:23
bschaeferpossibly! Its just having problems linking right? Sooo it must not be finding where its defined...strangly17:24
bschaefersil2100, mine compiles fine17:26
* bschaefer does a complete rebuild17:26
kdubi can check too17:26
bschaefersil2100, I also just did a dist-upgrade a bit ago17:26
kgunnbuilding...17:28
bschaefersil2100, possibly trying a --reinstall on libegl1-mesa-dev?17:28
sil2100Could you guys also check if https://code.launchpad.net/~sil2100/mir/revert_libmirclient3 is fine?17:28
sil2100bschaefer: will try, strange thing!17:29
sil2100But I got used to my system having build problems17:29
kdubsil2100, looking it over17:29
sil2100kdub: thanks ;)17:29
bschaefernp, I can merge it in with trunk mir and build it to check as well17:29
sil2100There's a merge, if anyone can help kgunn reviewing that and approving - we need to revert that as per didrocks decision (and the many many problems we have because of that)17:29
kgunndamn slow machine....50% thru17:33
kdubsil2100, i approved it, small comment17:33
kgunnsil2100: if i build ok, i'll run a client demo for sanity...if all ok, i'll top aprove17:34
kgunn80%...17:39
kgunnlike watching paint dry17:39
bschaefermy branch compiled, i can run some demos for sanity as well17:40
kgunnbschaefer: you so speedy...please do17:40
bschaefer:)17:41
kgunnbschaefer: you must be on an i717:41
sil2100:)17:42
bschaeferkgunn, nope an i5, but seems to work well :)17:42
bschaeferi wish!17:42
bschaeferkgunn, demos are working fine! (also forgot about the flashing one...)17:42
kgunnlinking...drumroll please17:43
* bschaefer doesn't know how to express that in IRC17:44
kgunnall done17:44
kgunnbschaefer: i know...i miss noise making in office17:44
bschaeferkgunn, well i've never worked in an office, but I can imagine its a bit easier :)17:45
sil2100kdub: approved the code perspective17:48
sil2100bschaefer: does the branch I pointed work for you?17:48
bschaefersil2100, yup!17:48
kgunnsil2100: bschaefer kdub racarr ...built, and worked for demos...i feel good17:48
kgunnready for me to approve17:48
sil2100kgunn: could you top-approve? Thanks!17:48
kgunnsil2100: roger that17:49
sil2100Thanks guys!17:49
kgunnsil2100: done...and no thank you...sorry for the poop-storm17:50
kgunnsil2100: gonna go eat & exercise... bschaefer & kdub  got your back if you need it i'm sure...17:56
* bschaefer will be around for a while...18:01
racarrI am trying to understand this libmirclient3 stuff18:18
racarr1. How can I not fuck things up in the future.18:18
racarr2. What is meant by problems and how is it expected that this will fix them?18:18
=== dandrader|lunch is now known as dandrader
racarrLunch18:43
racarrback19:26
kgunnbschaefer: everything ok? verizon decided i shouldn't have interenet for the last little while19:33
ricmmracarr: ping19:33
* kgunn hears verison19:33
* kgunn hearts verizon even19:34
bschaeferkgunn, everythings been quite19:34
kgunnexcept ricmm pining...we ok ricmm ?19:34
ricmmwe ok, just reaching out to robert19:34
bschaeferhopefully everything is :)19:34
ricmmsee if he has had any progress on the DPMS for android impl19:34
ricmmas he had said 2-3 hours19:34
ricmma few hours back19:34
ricmmits the last piece of the puzzle from your team, so far19:35
ricmm;)19:35
kgunnah yes...19:38
kgunnmmm.... racarr might be lunching19:39
racarrricmm: Pong19:43
racarrricmm: Ok great, so yes I am working on it now half done but there is a problem! which I was waiting to ask kgunn about19:44
racarrThe API got reverted.19:44
racarrkgunn: I don't understand what happened.19:44
racarrkgunn: I don't understand what happened. 1. How do I not mess it up in the future. 2. What were the problems? 3. How is this supposed to fix them19:45
kgunnracarr: not your fault19:45
kgunnracarr: #1 - see the email i sent to team19:45
racarrwhoops had some up arrow = repeating myself XD19:46
racarrI'm not actually THAT confused :)19:46
kgunn#2 - didrocks asac and ricmm asked for libmirclient3 not to land until unity-mir was in...19:46
racarroh I missed that...I was waiting on it earlier19:46
racarrOh. I see now19:46
kgunn#3....i honestly didnt get it either...i think cause they were using daily-build ppa's somehow ?19:46
kgunnif total rebuild...it should be ok...but maybe they weren't doing that19:47
racarrOk. I understand more now :) sorry about missing the email.19:47
racarrthe MR to revert it cites issues on intel on the desktop, etc19:47
racarrwhich really sounds like we have some sort of19:47
racarrinfrastructure or roll out error19:47
racarrbecause I dont think the change can break anything besides through ABI19:48
kgunnracarr: agreed19:48
kgunnagain...you did nothing wrong....and followed what i thot was the right way (email on mir-devel)...19:48
kgunnno worries....19:48
kgunnwe'll get it right on libmirclient419:48
kgunn:)19:48
racarr:D thanks19:49
=== dandrader is now known as dandrader|afk
racarrI feel like it's worth trying to figure out what happened though with things being broken on the desktop19:49
racarrMore of a thought than a feeling I guess :p19:49
kgunnme & bschaefer built locally....then sil2100 could not...something about not finding eglCreateImageKHR19:51
kdubnothing should really link directly to that function19:51
racarrhmm...now I am remembering I saw that once in the last few weeks19:51
racarrhow did I resolve it19:51
kgunnracarr: so i think....when didrocks & ricmm say they have a green image w/o libmirclient3....you could then push the dpms + libmirclient3 to provide the fix19:52
racarrI think I dist upgraded19:52
racarrHow will we get a green image without screen blanking -.-19:52
kgunneverything else minus screen blanking19:52
ricmmracarr: the green image is not feature-complete Mir19:52
racarrok19:52
kgunni would guess19:52
ricmmits just SF with all the Mir stuffed landed but not enabled19:52
racarroh. good idea19:52
kgunnricmm: but don't we want some level of sanity test result of the mir-enabled in the same image as well ?19:53
ricmmso whatever you need to depend on for DPMS, use it19:53
racarrI didn't understand that :)19:53
ricmmplus, its a server API, no?19:53
ricmmshouldnt impact mirclient19:53
racarrehhh19:53
ricmmnot that I mind about mirclient, the problem with that one was desktop-related19:53
ricmmbut it held up the whole pipeline19:53
racarrI guess it could be masked from mirclient19:53
racarrits a client API too (for xmir)19:53
ricmmthat sounds wrong19:54
kgunnmmm right...thanks ricmm forget touch will be sever side19:54
racarr! that's the bit I don't understand how did it trigger19:54
ubot5racarr: I am only a bot, please don't think I'm intelligent :)19:54
racarrproblems on the desktop?19:54
racarr...no worries ubot519:54
kgunnricmm: xmir is a native client19:54
ricmmmirclient was bumped but that required a rebuild of everything and its mom19:54
ricmmwhich caused problems as we had the pipeline stalled for the unity stuff19:55
kgunnricmm: did we rebuild for its dog & brother too ?19:55
racarroh19:55
ricmmcousins too19:55
kgunn:)19:55
ricmmagain, im not that familiar with the mirclient blockage, as I said... more desktop related than not :)19:55
racarrOk. So the pipeline was stalled for other stuff19:55
racarrmakes sense :)19:55
kgunndidrocks: you on ?19:55
didrockskgunn: spammed with pings, yeah19:55
racarrricmm: That makes enough sense :D I was worried that it was failing in some way that wasn't related to just ABI or some such19:56
racarrand trying to track down what was happening19:56
kgunndidrocks: sorry to add to the noise...so...question is, when can we try to push libmirclient3 again...19:56
kgunndidrocks: no one understands why it failed....19:56
didrockskgunn: no19:56
racarrricmm: Working on DPMS, just need to patch some support in to demo-server for a test, and go through the whole dance of updating my phone, etc.19:56
didrockskgunn: we try to have an image out19:56
kgunndidrocks: thanks...nice clear anser19:56
didrockskgunn: once the image is done19:57
didrocksand we have as well indicators in19:57
didrockswe can reput libmirclient319:57
didrocksIF as an upstream, you handle the whole transition19:57
didrocksto not block everyone19:57
ricmmracarr: please do, about the phone updating it should be enough to flash -pending and update from the ubuntu-unity/daily-build ppa19:57
ricmmI'll bother you again in a while ;)19:57
kgunndidrocks: thanks... we will pend on you saying its ok to go again...sound ok ??19:57
didrockskgunn: perfect19:58
didrockskgunn: probably tomorrow TBH19:58
didrockskgunn: workarounding the latest Mir added a bunch of complication19:58
didrocksso still building things19:58
kgunndidrocks: that's fine...i think racarr has a way fwd for dpms in touch....so we're only delaying xmir19:58
didrocksok, good :)19:58
kgunndidrocks: i'm so sorry...i will punch myself in the face later as punishment :-/19:59
didrockskgunn: well, on that one, you're not to blame ;)19:59
didrockskgunn: but we need to discuss on process when the team is planning to transition19:59
didrocksas it affect multiple pieces, there are things to do19:59
didrocksand there is a process on the FAQ page20:00
didrocksthat I wish your team would follow ;)20:00
didrockshttps://wiki.ubuntu.com/DailyRelease/FAQ#I_need_to_break_an_API.2BAC8-ABI20:00
kgunndidrocks: yep...got it...and team should be aware & i'll reiterate20:00
kgunnin person next week20:00
didrocksthanks20:00
didrocksI won't stay in Boston, lucky you! ;)20:00
* kgunn probably doesn't punch as hard as didrocks...thanks goodness didrocks leaves boston20:01
* ricmm has been trying to find a flight for a while20:01
ricmmthere are none20:01
didrockskgunn: ahah ;)20:01
=== dandrader|afk is now known as dandrader
racarrred light of dweath on nexus 4...it does this sometimes when it runs out of battery hardcore though21:02
racarrback to the lightning bolt and battery thing! Yay not bricked21:14
kdubracarr, yeah, that happens fairly often to me, never had a brick yte21:17
kdubrsalveti, in the 'android-platform-headers' package, would it be difficult to add the hwcomposer.h and hwcomposer_defs.h from libhardware?22:44
RAOFGrah.23:38
RAOFWhy does radeon suddenly work today?23:38
RAOFI'm all ready to debug bypass and multi-monitor...23:44
RAOFOh.23:44
RAOFBecause it's not running Mir.23:44

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!