=== thumper is now known as thumper-dogwalk === thumper-dogwalk is now known as thumper [04:57] Hi === cpaelzer_ is now known as cpaelzer [05:57] Good morning [07:18] good morning desktopers [07:51] bonjour seb128, ça va ? [07:54] morning all [07:54] hey seb128, thanks for following up on those emails late last night. Much appreciated. [08:02] moin [08:02] hey Laney [08:02] Wow! I got a report from HR about the amount of holiday that people have to use up. It's accurate to 4 decimal places [08:03] TheMuso, you have 6.9992 days to use before the EOY :) [08:03] Please allocate in chunks of 0.0001 [08:03] so don't you *dare* slacking off those missing 69 seconds! [08:04] :DDD [08:06] that's squirrel watching time [08:08] hey pitti willcooke Laney [08:09] willcooke, yw! sounds like it's a known issue with the new qt and Mirv is looking at it, unsure about timing of landing a fix though [08:09] seb128, yeah, reading about that now [08:09] it looks like it's being discussed for a while which doesn't give confidence on a fix landing today [08:09] wondering if we are allowed to declare arm64 not supported [08:10] at least short term [08:10] seb128, did you get an "ok" from Steve about starting the seedings? [08:11] yeah, recommends are fine if unhandled they shouldn't block the iso build [08:11] cool [08:11] but it also mean the session isn't going to end up on the iso until all the depends are sorted out [08:12] We're not far away from having that all sorted I think [08:12] right [08:12] we are not far away from 16.10 either though... [08:13] but yeah things are moving correctly [08:14] seb128: willcooke: actually we're now potentially finding out it's not a Qt issue, althouh some more recompilations to make sure. it seems to happen only on yakkety, not xenial(overlay) despite identical Qt versions -> GCC6, glibc 2.24 related potentially [08:14] or maybe a Qt issue but not with GCC5 [08:14] O_o [08:15] it's a deep rabbit hole [08:15] thanks Mirv [08:15] Mirv, which means we are not any closer from having it resolved? [08:15] just moving the blame to the next component [08:15] if it's a toolchain issue it's going to take a while... [08:16] do we have a fallback option/workaround for 16.10? [08:16] seb128: no, just more information [08:18] willcooke: Urm, is that with all accrued by the end of year, or is that based on current data? [08:18] Hey folks bTW. [08:19] hey TheMuso [08:22] willcooke: Having said that, it sounds about right. [08:23] TheMuso, not really sure. I think it's accrued until the EOY, but they've already taken off the Christmas close down. Anyway, doesn't matter - was just a good example of the ridiculousness [08:23] Oh sure. [08:24] willcooke, speaking of vac, I'm in discussion with Hannah about french counts, they added some extra 10 days it seems unsure why [08:26] seb128, :) It did look kinda "WTF"! [08:26] willcooke, by law we have ~10 days/year to get back because legal work time is 35h/week and we do 40h/week so we get some compensation days, but companies have the choice to give them as vac days or to pay them and until now Canonical always took the option to pay those [08:26] so waiting for a reply on that [08:26] erk, yes, getting paid sounds better [08:26] let me know if I can help [08:26] should be fine, Hannah is on it [08:27] but thanks [08:27] np [08:28] france is the best [08:28] seb128: just move to a decent Country that doesn't complicate things and you just get paid already ;) [08:28] well, in the past, we just got them paid [08:28] just afraid that this year, they changed without noticing the count [08:28] seb128, surely you do about 70h/week? ;) [08:28] and meaning that if we don't take them, they aren't paid, the count will just go to 0 [08:29] seb128: if you don't get an answer before your holidays, maybe willcooke should take it back on his pile of things to enjoy with HR? :) [08:29] hi didrocks! [08:29] hey hey Laney ;) [08:30] how's it going? [08:30] saw a sexy picture of you giving a talk [08:30] ...although it looked like it was in the office [08:31] it was in the office :) [08:31] willcooke: Since I have you here, do you have bug numbers for those tasks you added to trello on my 16.10 board for your dock issue and that other bluetooth bug? I tried to search for an appropriate bug for the latter today but without any luck so far. [08:31] unsure where the picture was, didn't see it :p [08:31] i forgot [08:31] but yeah, was in London last week [08:31] bonjour didrocks, comment vas-tu ? [08:31] sprint? [08:31] TheMuso, I haven't, sorry, but I will do [08:31] pitti: bien, et toi ? [08:31] didrocks: London last week [08:31] willcooke: Ok thanks. [08:31] didrocks: je vais bien aussi, merci ! [08:31] Laney: no, ThingMonk (conference), then 2 days off :) [08:32] and some people in my team decided that I should do a meetup in the evening [08:32] haha [08:32] TheMuso, what should I log them against for now? Pulse? [08:33] didrocks, I should have a reply this week but it's fine either way for me, it's only 10 days, worth case I take december off [08:33] that sounds TERRIBLE! [08:33] (jealous) [08:33] chrisccoulson, hey, you are saying I should get way more days? ;-) [08:33] seb128: well, it's a big change… I have 20 days now and it's quite some cut in the pay (without notice) [08:34] so they could at least have warned [08:34] right [08:45] willcooke: Pulse for bluetooth, alsa-driver for the dock one, because info from alsa-info is needed. [08:46] willcooke: Well it maybe needed, given that it could very well be a kernel bug. [08:46] Just tried reproducing the BT one, and of course I cant [08:46] I'll focus on the dock one [08:46] thanks TheMuso [08:46] Ok cool. [08:46] np [08:57] bah bah de bah [08:57] can't valgrind the asgen [08:58] why not? [08:58] it's mmapping too much [09:02] :-/ === hikiko is now known as hikiko|ln [10:41] http://people.canonical.com/~ubuntu-archive/component-mismatches.svg [10:41] looks fun now [10:45] yeah, was about to mention it [10:45] imagine the noises doko is making :D [10:45] lol [10:45] well it's mostly looking good [10:45] there is little non yellow which isn't a R [10:57] willcooke, ^ that looks good, I send another email but it looks like the ones that need fixing are [10:57] * ubuntu-keyboard still depending on fonts-android [10:58] * u-s-s depending on dbus-property-service (I think that was not on our list, we noted down that it should be made optional but then didn't work on i) [10:58] * address-book-service depending on the buteo stack [10:58] then the ones waiting on security team [10:59] ubuntu-keyboard - elleo was supposed to look at that. Will chase. [11:02] hum, seems like he landed a change in http://launchpadlibrarian.net/280894470/ubuntu-keyboard_0.100+16.10.20160808.1-0ubuntu1_0.100+16.10.20160818-0ubuntu1.diff.gz [11:02] -Depends: fonts-droid-fallback | fonts-droid, [11:02] +Depends: fonts-droid-fallback | fonts-droid | fonts-noto, [11:08] but -noto is in universe as well... [11:11] if they can move to fonts-noto-cjk we win :) [11:11] (as in, no MIR needed) [11:11] indeed! === hikiko|ln is now known as hikiko [12:47] hmm, I misunderstood the release schedule too [12:49] survey day! [12:49] good morning everyone [12:50] hi! [12:52] seb128: Laney: what do you think of bug 1625897 ? [12:52] bug 1625897 in webkit2gtk (Ubuntu) "Update webkitgtk to 2.14.0 in yakkety" [Wishlist,New] https://launchpad.net/bugs/1625897 [12:52] "My organisation genuinely cares about the environment" [12:52] some of these questions... [12:54] laney@nightingale> env | wc -l ~ [12:54] 89 [12:54] STRONGLY DISAGREE [12:55] pollution [12:55] desrt@humber:~$ env | wc -l [12:55] 30 [12:55] try debian [12:55] ......and a ream of "unset .." lines in your bash_profile [12:56] probably most of these were set by me ... [12:56] jbicha: I think it's a fine idea to do after beta 2 [13:09] jbicha, I'm not in the release team, I think we have quite some bugs/issues in yakkety and we should have focussed on fixing those rather than doing version updates recently but that's only my view [13:10] jbicha, also all those packages migrating from cdbs to dh seems late for such changes... [13:14] ok [13:15] good afternoon [13:15] andyrock: hihi [13:15] hey andyrock, how are you? [13:15] oh and hey desrt ;-) [13:15] good morning seb [13:15] cdbs was kinda unstable recently which motivated the pkg-gnome team to finally switch to dh [13:15] my toe is getting better [13:15] :D [13:16] i thought it was a finger? [13:16] * desrt feels like she just learnt something about latin [13:16] and I thought that you could refer to a toe as a finger [13:16] :P [13:16] er. italian. [13:16] at least in Italian you can do it [13:16] :D [13:17] it's same(ish) in esperanto [13:17] a toe is a foot-finger [13:19] jbicha, weird, didn't notice any issue with cdbs and it didn't change much ... anyway rewritting the packaging has potential for bugs and has 0 benefit to users, such changes should get done early in the cycle or at least before ff, not now [13:19] seb128: do you have a list of good candidate bugs for yakkety? [13:19] jbicha, https://bugs.launchpad.net/ubuntu/+bugs?field.tag=rls-y-incoming [13:19] jhodapp, hey! Do you know if mediaplayer-app "just works" on classic Ubuntu deskop under u8? [13:19] willcooke, it does [13:19] jhodapp, sweet! [13:19] willcooke, and also as a snap now too :) [13:19] thanks for filing that MIR jhodapp! [13:20] * seb128 hides [13:20] jhodapp, would you mind filing an MIR for it [13:20] lol [13:20] :)) [13:20] * willcooke hugs jhodapp [13:20] lol [13:20] seb128, for what change? [13:20] jhodapp, I'll send you an email with the details [13:21] willcooke, seb128: lightdm is still triggering a whole load of upstart jobs is that still expected? [13:21] jhodapp, I was mostly joking, see what willcooke said, we are about to get the unity8 session as optional on the desktop iso and we would like to include the mediaplayer so we need it promoted to main [13:21] davmor2, pitti knows better but yes [13:21] I don't think we ever ported it to systemd [13:21] that was blocked on indicators to land or something [13:21] it's late now I guess [13:22] seb128, ah, lol...I was so confused... [13:22] seb128: thanks [13:22] seb128, davmor2: yes, I'm waiting for the indicator silo to land, then I can port the lightdm greeter [13:22] willcooke, thanks, I'd be happy to fill that out [13:22] jhodapp, sorry :-) [13:22] pitti: thanks [13:22] pitti, that still didn't land? [13:22] crazyness [13:22] seb128, no worries :) [13:23] * seb128 thinks we are about to beat edgy [13:23] seb128: no -- I asked tedg a couple of times about the status, but no response yet; I don't know what's blocking it [13:23] ted is busy on doing a snap from the unity8 session [13:23] which is the new thing of the day [13:23] I think [13:24] jhodapp, you got mail [13:24] willcooke, hehe, thanks [13:24] jhodapp, could you send me a link when you've done it [13:24] willcooke, sure [13:24] jhodapp, bear in mind it's not a final decision if we will push for it yet - depends on other work getting done, but would like to get things lined up ready [13:25] willcooke, makes sense [13:32] hi willcooke, I am talking with mterry about the same problem. [13:33] I just want to understand is the "recommend" a problem for buteo packages? [13:33] hey renatu [13:33] seb128, could you speak to renatu, I'm in ameeting and would like this sorting quickly [13:33] willcooke, sure [13:33] thank you [13:34] seb128, hi [13:34] renatu, hey [14:51] wooot, Laney tackling yakkety bugs ;-) [14:53] Trevinho, andyrock, is there any reason https://code.launchpad.net/~azzar1/unity/properly-handle-copy-dialog/+merge/299301 isn't getting reviewed? [14:53] tedg, hey, did you see the ping about indicators/systemd landing? [14:54] Yeah, I was looking at the silo now. There's a bunch of build errors that need to be chased down. [14:54] Though, I should be able to do that some today. [14:54] Planning to spending a fun day with bileto [14:59] tedg, do you need help on those build issues? [15:01] seb128: nope [15:01] seb128: I don't think so, I think it's JFDI type things. [15:01] it should still work [15:01] tedg, k [15:01] andyrock, so just need to wake up Trevinho? ;-) [15:01] * seb128 sends some pizza to Trevinho [15:01] i'll schedule some time tomorrow to reviews a couple of Trevinho's MP === jhernandez is now known as jhernandez_ [15:15] andyrock, thanks [15:25] Laney, looking at: https://code.launchpad.net/~willcooke/ubuntu-themes/hidpiicons/+merge/305219 [15:26] I've fixed gtk-widgets-assets-radiance.css in both places [15:26] But I don't get what's wrong with ln 2218 & 2231 in Ambiance/gtk-3.20/gtk-widgets.css [15:26] oh, that didn't land? [15:27] not yet, need to fix some bugs [15:27] it's getting late, maybe going to be for next time [15:27] time->cycle [15:27] fine by me, but it's very very nearly ready [15:27] if that counts for anything [15:27] probably not [15:28] Laney, bug #1571729 on what arch did you try? it seems 32 bits specific [15:28] bug 1571729 in gnome-software (Ubuntu) "/usr/bin/gnome-software:11:look_at_pkg:load_apt_db:gs_plugin_refine:gs_plugin_loader_run_refine:gs_plugin_loader_run_results" [High,Incomplete] https://launchpad.net/bugs/1571729 [15:28] I also don't get what needs doing for "I also found a find and replace error that I made on a previous commit - could you look for "assets/scale.vertical-vertical-fill.png" and "assets/scale.vertical-vertical-fill-disabled.png" and fix those too please?" [15:28] seb128: definitely not 32 bit [15:29] willcooke: look for button-toolbar.png [15:29] willcooke: Look for those strings and fix the filenames [15:29] Laney, k, dunno if it's 32 bits but reports are only from armhf and i386 and it does it every time on i386 [15:30] I should get a valgrind [15:30] let me does that once my daily is downloaded, which is another 10 minutes [15:31] ah, line 2228 [15:32] maybe they moved if I merged it into trunk [15:34] willcooke, https://bugs.launchpad.net/mediaplayer-app/+bug/1626164 [15:34] Ubuntu bug 1626164 in mediaplayer-app "[MIR] mediaplayer-app" [Undecided,New] [15:34] thanks jhodapp [15:34] willcooke, np...one change was needed so far that I completed and documented in that MIR [15:37] willcooke, I would not ask them to hold on it, it just doesn't need to prioritized but if they have some extra review cycles... [15:37] undo [15:37] undo [15:37] lol [15:37] guess I can't delete that can I? [15:38] no [15:38] you can sometimes hide comments ;-) [15:55] ximion: I got a new machine with 32G of RAM ;-) [16:02] Laney: ...and that is another way to solve this problem :D [16:02] one I kind of like ^^ [16:02] did you ever try valgrinding the asgen? [16:02] now you could probably even extract the localization into memory :P [16:02] it dies for me [16:03] Laney, https://code.launchpad.net/~willcooke/ubuntu-themes/hidpiicons/+merge/306356 [16:03] yes, I did - but the GC makes valgrinding harder [16:03] lmdb cries [16:03] as far as I could see it tries to mmap with a huge size and valgrind needs to put that in ram, but can't [16:04] willcooke: merci [16:05] willcooke: you could have just pushed (with or without --overwrite), no need to make a new proposal [16:06] saves a bit of clicking anyway [16:07] although you need to comment in order to generate mail for the reviewer [16:08] urgh this locale synchronisation sucks [16:08] come on Jussi, fix your build system! [16:34] Laney, ah, oki. I just clicked the "resubmit proposal" button after I pushed the new stuff [16:35] you need that to change settings (e.g. add a prerequisite branch), but not to just add more commits [16:35] TYL :P [16:35] :)) [16:59] have a nice evening desktopers! [17:07] cya seb128 [18:34] going EOD - night all [22:07] Laney: I valgrinded that ages ago, but I think I simply went with a very small archive there and reduced the amount of stuff that gets mmapped