=== salem_ is now known as _salem [01:55] Hi guys quick question then I'll bother you no more. [01:55] Is Unity free, as in could competing distros use it as their desktop? [02:02] It's OK I think I sorted it. Thank-you. === _salem is now known as salem_ === salem_ is now known as _salem [04:20] was there any work/branch yet on bug #1181717 ? (not seeing, just checking) reportedly hurts working on saucy. [04:20] bug 1181717 in Unity "compiz crashed with SIGSEGV in g_object_unref()" [Critical,Triaged] https://launchpad.net/bugs/1181717 === zniavre__ is now known as zniavre [09:39] Saviq, getting some new output which I'm not sure the cause of on ./run [09:39] file:///usr/lib/i386-linux-gnu/qt5/qml/Ubuntu/Components/Button.qml:95: Unable to assign [undefined] to QString [09:39] Are you aware of what might be causing this? === pete-woods1 is now known as pete-woods === alan_g is now known as alan_g|tea === alan_g|tea is now known as alan_g [11:29] sil2100, didrocks: ping? [11:30] veebers: pong [11:30] didrocks: Hi, looks like I introduced a couple of 'small' errors in my recent Autopilot update :-\ [11:31] didrocks: if I put up a MP could you eyeball it and Ok it please? [11:31] veebers: argh, you need regressions tests it seems :) [11:31] veebers: thomi would review it? [11:31] didrocks: it appears the tests that I ran weren't exhastive enough [11:31] didrocks: normally, but that would have to wait until our morning as I'm sure he's AFK for the night [11:31] veebers: yeah, better to wait, but first thing tomorrow first [11:32] for him and you please :) [11:32] veebers: so that it's picked by daily release [11:33] didrocks: sure thing. Again, sorry :-P [11:33] no worry, but please have regression tests! :) [11:33] veebers: pong! [11:33] veebers: sorry, I'm theoretically on holiday today ;) [11:34] sil2100: oh sorry to bother, I was going to bug you to Ok a MP but didrocks thought that it should wait for thomi :-) [11:34] veebers: just poke me with a review if you have one, or send me an e-mail and I'll take a look [11:34] sil2100: coolio [11:35] veebers: it would be generally good if thomi would also review it, as he is the one with much more experience, but no problem for me to take a look ;) Thanks! [11:45] Trevinho: hey, not the issue I meant the other day, but related on "the marker doesn't do the right thing": http://people.canonical.com/~didrocks/tmp/marquer_in_air.png [11:46] didrocks: mh.. are you using daily? [11:47] Trevinho: no, the version in saucy, which isn't the latest one [11:47] I saw it in raring too [11:47] didrocks: I've made a change just after the raring release that should fix it, but i don't know if it made into saucy yet [11:48] Trevinho: ah ok, probably not [11:48] we didn't have any landing in saucy yet :/ [11:48] seb128: not sure, I didn't check.. but we neither have a sru for raring.. [11:48] yeah, thanks to the interleaving of autopilot 1.3 [11:49] Trevinho, the SRU is in the queue, infinity said he would review it tomorrow [11:49] Trevinho, btw did the libreoffice menu background issue got fixed in the stable serie? [11:50] seb128: 7.0 autolander is not merging... [11:50] still [11:51] why not? [11:51] still same error: [11:51] /tmp/buildd/unity-7.0.0daily13.05.08~13.04bzr3322pkg0raring16/UnityCore/MusicPreview.cpp:70:66: error: 'unity_protocol_music_preview_play_uri' was not declared in this scope [11:51] for all the 7.0 branches, and it's not caused by unity.. [11:51] hum? [11:51] I think that libunity in 7.0 is messed [11:52] but I don't know exactly against what is building [11:52] shrug [11:52] they merged the new scope work without branching [11:52] it uses libunity-dev_6.90.2daily13.05.01.1ubuntu.unity.nextbzr224pkg0raring3_amd64.deb [11:53] yes, that's the problem I guess [11:53] didrocks, ^ who is in charge of that? sil2100? [11:53] seb128: yep, sil2100 [11:53] sil2100, ^ [11:54] * Trevinho really would have preferred better communication when the 100 scopes landed... [11:54] Trevinho: thosrt and pstolowski didn't tell you? [11:54] come on guys :/ [11:55] Looking [11:55] I wasn't aware like most of us [11:56] Trevinho: I thought bregma and thorst as some communication meeting? [11:56] if not, seems that it's something they should set up [11:57] Ok, my fault as well, could have noticed that there's no 'raring' branch for libunity ;/ [11:57] Shit [11:57] sil2100: sorry, we were discussiong about this also few days ago, but probably we didn't made our voice to get you... [11:58] Trevinho: I think we need to prepare a 7.0 branch now actually [11:58] sil2100: hum, so the stack configuration was done, but not that? [12:02] didrocks: actually, I see there's libunity/raring [12:02] So it should be ok [12:02] I wonder if it's not just the local upstream repo for the upstream merger which is screwed [12:02] mmrazik: you do separate the repos depending on stack, right? [12:02] or just depending on releases? [12:02] Probably, since it's all ok in the config [12:03] I guess everything is melt in the local package repo for upstream merger [12:03] Trevinho: you should track with them, I just the ppas, they are good, so it's not at our level ^ [12:04] didrocks: so are the local 7.0 branches messed? [12:04] Trevinho: not the branch, nor the ppa, but I guess the upstream merger melt the local repo for merging things [12:05] which is in the PS QA's team hand [12:05] ah [12:05] seb128: FYI ^ [12:05] sil2100: I have this (but if you could hang off OK-ing it for the moment please: https://code.launchpad.net/~veebers/autopilot/fix_cleanup_errors_1185790/+merge/166494 [12:05] didrocks, k, thanks [12:05] Does anyone know how to disable line-wrapping in thunderbird? [12:06] Since even with mail.wrap_long_lines it's still wrapping lines ;/ [12:08] Ah [12:08] didrocks: the local repos? [12:08] they are per stack [12:08] AFAIK [12:18] sil2100, i heard that there was some armhf-releated hanging of libunity, could you point me somewhere with a log? [12:19] mmrazik: are you sure? seems they have a 7.0 branch and tels that it's taking the 100 scopes branches [12:19] well, I'll let you check with them :) [12:21] didrocks: otp. will have a look in a sec [12:25] didrocks: looks like I missed sil2100, I'll leave a note for thomi, he should be on in ~8 hours or so [12:25] (re: the MP) [12:25] veebers: ok, perfect, thanks! [12:28] didrocks: nw, now i'm off to bed o/ [12:28] veebers: have a good night :) [12:29] Trevinho, didrocks: do you have a link to jenkins job failing? [12:29] * didrocks let that for Trevinho, you don't need me :) === mmrazik is now known as mmrazik|afk [13:10] pstolowski, So I'm a bit confused. I thought you guys had a fix for the autopilot failures. [13:11] tedg: we identified some failures to be AP bug, but we don't have any conclusion for hud failures [13:11] pstolowski, Hmm, okay. Can you file bugs so that we can track them? [13:15] tedg: i'm in the sprint on IOM and too busy atm to do that.. can you or somebody from your team take a look if these are real HUD failures or some a test/AP problem, and take care of bugs? [13:16] pstolowski, Well, I don't have a team :-) Triaging phone "emergencies" right now, but I can put it in the queue. [13:22] cyphermox, It seems that we didn't get a daily release of HUD last night. Do you know where I can check to see what happened? https://code.launchpad.net/~indicator-applet-developers/hud/trunk.13.10 [13:28] andyrock: anyone looking at bug #1181717 yet? I understood it's hurting the ability to do work (when using unity) in saucy [13:28] bug 1181717 in Unity "compiz crashed with SIGSEGV in g_object_unref()" [Critical,Triaged] https://launchpad.net/bugs/1181717 [13:34] greyback: mzanetti: standuping? [13:34] didrocks: nic-doffay: ↑↑ [13:34] coming [13:34] Trevinho: or is that actually bamf bug, not unity, and should be retriaged? ^ [13:35] tsdgeos: i'm on a vendor call atm [13:35] oka [13:36] dednick, ^ === mmrazik|afk is now known as mmrazik [13:37] Mirv, should not be unity's fault [13:37] maybe bamf or glib [13:38] and I can't reproduce building bamf from sources === _salem is now known as salem_ [13:48] andyrock: infinity suspected that the glib upgrade triggered bugs, but that it's a legimate double-free bug that just surfaced with the glib update [13:48] that reportedly was found in ubiquity at least with the glib upgrade [13:49] Mirv, in that case it's bamf [13:49] Trevinho, ^^^ [13:58] tedg: my guess is it failed tests... [13:58] I can't seem to reach jenkins for now [13:58] as soon as I can get to the interface I'll be able to tell you more [14:01] cyphermox, That's impossible, my tests are impervious to failure. ;-) [14:01] Cool, ping me if you find anything. [14:03] hey, your tests were doing great after we fixed autopilot ;) [14:03] tedg: sorry for slow response... it would be great if you could just spend a few minutes looking into AP fail logs for hud tests and add comments to the spreadsheet [14:03] brb, need to restart to test something [14:04] mmrazik: sorry I was out for lunch, one is at https://jenkins.qa.ubuntu.com/job/unity-7.0-raring-amd64-autolanding/16/console [14:04] Mirv: about that crash, I've been looking a little, but as andyrock said it's a little tricky as it doesn't fail when building from src.... (nor there are warnings) [14:06] Trevinho: mhm.. it seems to be misconfigured [14:06] fginther: can you please have a look on the local_archive settings for unity in head and raring? [14:06] Mirv, Trevinho yeah I don't get it building from src [14:07] fginther: AFAIKT they should not be using the same local repo but for some reason they are configured to do so [14:07] fginther: so the 100scopes stuff affects landing of unity 7.0 (raring) === salem_ is now known as _salem [14:14] mmrazik, looking [14:15] thanks fginther [14:32] Can anyone else get to the internal Jenkins? [14:32] tedg: no, see the engineering list [14:33] Hmm, okay. [14:42] bregma, hey stephen, would it be possible to have someone assigned on this? https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1181717 [14:42] Launchpad bug 1181717 in Unity "compiz crashed with SIGSEGV in g_object_unref()" [Critical,Triaged] [14:43] Cimi, several people are already looking at it, it'll get assigned after the discussion is over [14:44] bregma, good to hear people are looking at it! [15:05] pstolowski, Turned them into bugs here: https://bugs.launchpad.net/hud/+bugs?field.tag=autopilot [15:11] tedg: awesome, thanks. whom can I pester to work on them? ;) [15:16] pstolowski, Let me try to figure out who should own them next :-) [15:16] pstolowski, Not sure who to assign Unity 7 ones to. bregma likes bugs. :-) [15:17] no no no [15:28] kenvandine: mind launching webcreds? it couldn't build [15:28] tedg: poke [15:28] kenvandine: mangers is back [15:28] magners* [15:28] didrocks, How do we know what version of HUD these tests last passed with? I mean, is Unity the only thing changing here or are we talking about a new HUD version as well? [15:29] tedg: hud didn't publish because indicators didn't publish [15:29] keyou maybe want to look at friends :) [15:29] cyphermox, Mmm, oh, wait, you're not my wife! [15:29] is there anything hud needs from the indicators, or the other way around? [15:29] I mean, can I independently publish hud safely? [15:29] kenvandine: ^ [15:29] cyphermox, ? [15:29] cyphermox, Yeah, it just pulls from them. [15:31] o.O? [15:31] yay... jenkins is up :) [15:31] I was just making real sure ;) [15:38] cyphermox, Just FYI, we'll be able to unravel the HUD and indicators more next month. Once we get to using manifest files for them, HUD will just read those. [15:38] There should be no hard dependencies at that point. [15:41] didrocks, mind doing a review? [15:41] https://code.launchpad.net/~ken-vandine/cupstream2distro-config/settings_uoa_dest/+merge/166537 [15:42] kenvandine: should be ppa: daily-build-next [15:42] * kenvandine fixes [15:42] kenvandine: let's try to keep daily-build-next -> next and daily-build -> distro to not blurry the lines :) [15:42] (even if that would work) [15:43] didrocks, pushed [15:44] kenvandine: approved, feel free to deploy :) [15:46] thx [15:52] didrocks, so there has been a manual upload for g-c-c-s to saucy, with a backport from trunk. would it be better for me to fix the changelog in trunk or just force manual publication and forget about the missing changelog entry? [15:53] feels weird to lose a changelog entry, but then again it was already fixed in trunk :) === mmrazik is now known as mmrazik|afk [16:10] charles_, I didn't realize I had an action item here, can I give it to you? :-) https://blueprints.launchpad.net/ubuntu/+spec/client-1303-ubuntu-touch-porting [16:10] charles_, I think it makes sense when you're blowing up the power indicator anyway. [16:17] guys there's a problem with run_on_device [16:17] something is installing ninja [16:17] and i can't use run_on_device anymore since cmake complains i'm asking for a different generator than the old time [16:17] or maybe i had crap in there and that's the problem [16:18] now that we keep /home between flashes [16:29] bregma, So this one seems like Unity updating the search string it's giving to HUD (thus it's updating the results) but not updating the visible string. [16:29] https://bugs.launchpad.net/hud/+bug/1185858 [16:29] bregma, So I'm thinking that's a Unity bug. [16:29] Launchpad bug 1185858 in Unity HUD "HUD adding non-visible characters to search string" [Undecided,New] [16:29] I don't think we should be checking for visibility of characters in the backend. === greyback is now known as greyback|food === alan_g is now known as alan_g|life [16:50] kenvandine: you have to backport it [16:50] kenvandine: the changelog commit [16:50] ok [16:50] kenvandine: it's a security and forcing won't be do anything :) === greyback|food is now known as greyback === greyback is now known as greyback|away === greyback|away is now known as greyback === malin_ is now known as Malinux [21:27] aha, regression... scrolling over the sound icon while the dash is open, closes it. [21:27] bschaefer, ^ [21:27] that's in 13.04 [21:28] om26er, you mean to change the volume? [21:28] * bschaefer hecks [21:28] * bschaefer checks* [21:28] om26er, well yeah, clicking on it closes it as well [21:28] bschaefer, yes, [21:29] bschaefer, scrolling should not close the dash, that was not happening in 12.10 [21:29] om26er, could you make a bug and assign me :) [21:29] om26er, the problem was I had to do some funky things to the dash cause of the window buttons and launcher icons size changing... [21:33] bschaefer, bug 1186026 [21:33] bug 1186026 in unity (Ubuntu) "Scrolling over the sound icon closes the dash" [Medium,New] https://launchpad.net/bugs/1186026 [21:33] om26er, thanks, cause what i do is if the mouse is over the indicators at all, and we get an event we close the dash [21:34] * bschaefer didn't think about scrolling... [21:34] om26er, thanks for pointing that out! [21:34] bschaefer, np :) === greyback is now known as greyback|away === hggdh_ is now known as hggdh