[02:45] Trevinho, hi(?), it seems you landed on the wrong page/date: https://discourse.ubuntu.com/t/desktop-team-updates-monday-17th-february-2020/14395/14 === popey8 is now known as popey [07:09] good morning [07:10] salut didrocks [07:10] good morning desktoppers [07:12] bonjour à tous [07:13] didrocks, if I read it well, the zsys MIR has been approved [07:13] \o/ [07:14] jibel: yes! It seems to be the case, both on the bug and trello card! [07:14] hey oSoMoN [07:16] i didn't look at the card [07:17] Laney, are you looking at the build failure of desktop images of focal? [07:17] I reported bug 1864608 to track it [07:17] bug 1864608 in livecd-rootfs (Ubuntu) "Focal desktop images fail to build with: error: cannot validate seed: cannot use snap XXX base "core18" is missing " [Critical,Confirmed] https://launchpad.net/bugs/1864608 [07:26] salut jibel [07:26] Morning oSoMoN, jibel and anyone I missed [07:26] hey duflu [07:29] hey duflu [08:08] goood morning desktopers [08:09] Hi seb128 [08:09] hey duflu, how are you today? [08:09] seb128, headache but not too bad. You? [08:10] duflu, the day is only starting here but I'm good so far :) [08:10] didrocks, congrats on getting the zsys MIR finally approved :) [08:12] seb128: yeah! Now, we can do a final round of testing before releasing what we have and wire up with the installer [08:30] Morning o/ [08:32] Morning Wimpress [08:34] good morning Wimpress [08:40] hey Wimpress, how are you? [08:42] Wimpress, I think you forgot the monday rls-bugs discourse topic? [08:44] Laney, jamesh, tkamppeter, weekly summary reminder [08:44] kenvandine, oh, and you [08:55] salut seb128 [08:55] good morning Wimpress [08:56] oSoMoN, salut, comment ça va aujourd'hui ? [08:56] seb128, nuit agitée pour cause de bébé malade, mais sinon ça va [08:56] oSoMoN, :-(, bon courage, en espérant que ça aille mieux ce matin! [08:57] ça va déjà un peu mieux, merci [08:57] c'est déjà ça [08:58] Morning seb128. I'll post the rls-bugs shortly. [08:58] morning duflu didrocks oSoMoN jibel seb128 and Wimpress [08:58] :) [08:58] Wimpress, thanks [08:59] hey marcustomlinson, how are you today? [08:59] seb128: bleh :P [08:59] hey marcustomlinson [08:59] nah, alright thanks, yourself? [08:59] marcustomlinson, I'm good thanks, could have used more sleep but that's often the case right? :) [08:59] gonna miss you guys next week :/ [08:59] we are going to miss you as well! [08:59] Morning marcustomlinson [09:02] moin [09:02] hey Laney [09:02] seb128: AH thanks I started writing that yesterday but got distracted by uploading gnome stuff and forgot to do it [09:02] you summary police [09:02] Morning Laney [09:02] do you like go and tick off the list or something? [09:02] hey Laney [09:02] :p [09:02] do it for the rls bugs too? [09:02] see backlog :) [09:03] but yeah, for people not updating, good point [09:03] I think the rls thing doesn't work great atm, that's on my list of topic to discuss next week [09:04] well if everybody ignores something then yes by definition it's not working [09:04] would be the same for team updates if nobody did that [09:05] jibel: today's image built [09:06] hey Laney [09:07] Laney, thanks [09:07] moin marcustomlinson duflu and didrocks too [09:08] is there a know issue with snapd.seeded.service failing to start on focal and blocking default.target? [09:08] not known by me at least [09:10] brb, changing location [09:41] seb128: I think I've found a relatively clean way of doing these snap transitions in update-manager now [09:41] marcustomlinson, ah, nice! [09:42] duflu: indeed I did, thanks :P [09:42] (I think I just needed to sleep on it) [09:43] hey Trevinho, how are you? [09:43] hi seb128 all good :) [09:43] yourself? [09:43] marcustomlinson, glad that you got unblocked, I hadn't forgotton you but the morning tend to be busy [09:44] Trevinho, I'm good! [09:45] seb128: np! thanks for the shoulder to cry on last night [09:45] I'll shout if I get stuck again [09:46] Morning Trevinho ;) [09:46] hi duflu [10:09] kenvandine, the gnome-clocks-master snap fails to build because it wants glib 2.58 and the one it gets (from the platform?) is too old [10:16] ricotz, hey, is there any chance you could look at the indicator-keyboard build issue? I reported https://gitlab.gnome.org/GNOME/pango/issues/456 to pango upstream but got no reply, but we will need to get it rebuilt with the new gnome-desktop soname now so I wonder if there is any easy change we can do on the indicator side to restore build [10:16] GNOME issue 456 in pango "Gir error, symbol PangoFc could not be found" [Opened] [10:21] seb128, this pango issue looks the same as https://gitlab.gnome.org/GNOME/pango/issues/458 [10:21] GNOME issue 458 in pango "Gir: no type defined for hb_feature_t" [Opened] [10:28] ricotz, ah, thanks ... so we need harfbuz and pango updates in Debian/Ubuntu then I guess? [10:31] seb128, no, the easiest is to add some metadata for PangoFT2-1.0 to indicator-keyboard [10:31] nonetheless those gir deps need to be fixed in pango upstream [10:32] I will try to take a look later [10:39] ricotz, thx [11:00] seb128, I have a build of clocks that uses the new build snap, just waiting for the gnome-3-34 extension to land [11:02] seb128, weekly summary done. [12:07] seb128, it is a pango meson bug [12:08] seb128, https://paste.debian.net/plain/1132106 [12:09] so the generated PangoFc-1.0.gir is not fully correct [12:27] seb128, https://gitlab.gnome.org/GNOME/pango/-/commit/63c3eb8b7aa6ee9397c1d89a232514583f464fb5 [13:13] tracker's crashing on current isos :'( [13:14] https://bugs.launchpad.net/ubuntu/+source/tracker-miners/+bug/1864153 [13:14] Error: ubuntu bug 1864153 not found [13:25] on focal in general, not only the iso [13:25] I got this crash after this morning's update [13:25] believable [13:30] didrocks, https://bugs.launchpad.net/bugs/1864651 [13:30] Ubuntu bug 1864651 in snapd (Ubuntu) "snap.seeded.service never finishes loading and blocked multi-user.target" [Undecided,New] [14:02] ricotz, thanks! [14:22] tkamppeter, unsure if you noticed but Locutusofborg fixed your sane-backends build, see https://launchpad.net/ubuntu/+source/sane-backends/1.0.29-0ubuntu5 [14:23] jamesh, kenvandine, weekly status update? [14:25] seb128: sorry... I could have sworn I did that on friday! [14:25] maybe I posted it to the wrong week :) [14:26] good morning desktopers [14:26] good morning hellsworth [14:26] hi oSoMoN ! [14:27] hey Heather! how are you? [14:27] hi seb128 , i'm pretty good. you? [14:27] jibel, you should probably flag that issue to the snapd team if that hasn't been done yet [14:27] hellsworth, I'm great, thanks! :) [14:27] hey hellsworth [14:28] hellsworth: so did a simple rebuild of lo for arm64 do the trick? [14:28] it was still going when i stopped working yesterday so lemme go check [14:30] k, it's meeting time [14:31] #startmeeting Desktop Team Weekly Meeting - 2020-02-25 [14:31] Meeting started Tue Feb 25 14:31:00 2020 UTC. The chair is seb128. Information about MeetBot at http://wiki.ubuntu.com/meetingology. [14:31] Available commands: action commands idea info link nick === meetingology changed the topic of #ubuntu-desktop to: Home of the Desktop Team, https://wiki.ubuntu.com/DesktopTeam | For help or questions, try #ubuntu | Work (read-only for non-developers): https://trello.com/b/mxaCZTVc | GNOME 3.36 work claiming / tracking: https://trello.com/b/z29JJK3q/gnome-336 | Desktop Team Weekly Meeting - 2020-02-25 | Current topic: [14:31] Roll call: didrocks (out), duflu (out), hellsworth, jamesh (out), jibel, kenvandine, Laney, marcustomlinson, oSoMoN, seb128 , tkamppeter, trevinho, robert_ancell (out) [14:31] o/ [14:31] \o [14:31] \o [14:32] oSoMoN, don't move so far to the right! [14:32] k, let's get started [14:32] #topic rls-bb-bugs === meetingology changed the topic of #ubuntu-desktop to: Home of the Desktop Team, https://wiki.ubuntu.com/DesktopTeam | For help or questions, try #ubuntu | Work (read-only for non-developers): https://trello.com/b/mxaCZTVc | GNOME 3.36 work claiming / tracking: https://trello.com/b/z29JJK3q/gnome-336 | Desktop Team Weekly Meeting - 2020-02-25 | Current topic: rls-bb-bugs [14:33] o/ [14:33] http://reqorts.qa.ubuntu.com/reports/rls-mgr/rls-bb-incoming-bug-tasks.html [14:33] no desktop item [14:34] http://reqorts.qa.ubuntu.com/reports/rls-mgr/rls-bb-tracking-bug-tasks.html [14:34] nothing interesting there, either old/incomplete bugs or the nm ones we still didn't sort out (probably going to be easier to do in Frankfurt now) [14:34] #topic rls-ee-bugs === meetingology changed the topic of #ubuntu-desktop to: Home of the Desktop Team, https://wiki.ubuntu.com/DesktopTeam | For help or questions, try #ubuntu | Work (read-only for non-developers): https://trello.com/b/mxaCZTVc | GNOME 3.36 work claiming / tracking: https://trello.com/b/z29JJK3q/gnome-336 | Desktop Team Weekly Meeting - 2020-02-25 | Current topic: rls-ee-bugs [14:35] http://reqorts.qa.ubuntu.com/reports/rls-mgr/rls-ee-incoming-bug-tasks.html [14:35] nothing for desktop [14:35] http://reqorts.qa.ubuntu.com/reports/rls-mgr/rls-ee-tracking-bug-tasks.html [14:35] nothing interested there [14:35] #topic rls-ff-bugs === meetingology changed the topic of #ubuntu-desktop to: Home of the Desktop Team, https://wiki.ubuntu.com/DesktopTeam | For help or questions, try #ubuntu | Work (read-only for non-developers): https://trello.com/b/mxaCZTVc | GNOME 3.36 work claiming / tracking: https://trello.com/b/z29JJK3q/gnome-336 | Desktop Team Weekly Meeting - 2020-02-25 | Current topic: rls-ff-bugs [14:35] http://reqorts.qa.ubuntu.com/reports/rls-mgr/rls-ff-incoming-bug-tasks.html [14:36] https://bugs.launchpad.net/ubuntu/+source/gnome-calculator/+bug/1797734 [14:36] Ubuntu bug 1797734 in gnome-calculator (Ubuntu) "slow calculator startup" [High,Confirmed] [14:36] I need to talk to duflu about champagne use... [14:36] kenvandine, I guess just an untag for that one? [14:36] yeah [14:36] agreed [14:36] not as important if it's no longer seeded [14:37] bug #1864127 [14:37] bug 1864127 in chromium-browser (Ubuntu) "apparmor denies ~/snap/chromium/ writes" [Undecided,New] https://launchpad.net/bugs/1864127 [14:37] I need to look into that one [14:37] I don't think there is enough data to convince me to rls track for now [14:38] oSoMoN, should we just assign to you for investigation and revisit next week once you looked? [14:38] from a very cursory look, it sounds like a problem of the snap refreshing while running [14:39] seb128, I don't think assigning is even needed, I have the tab open and I'll request more info [14:39] right [14:39] ack [14:40] bug #1864260 [14:40] bug 1864260 in mozjs60 (Ubuntu) "TEST-UNEXPECTED-FAIL" [Undecided,New] https://launchpad.net/bugs/1864260 [14:40] looks like that was fixed, https://bugs.launchpad.net/ubuntu/+source/mozjs60/60.8.0-2ubuntu4 [14:40] Ubuntu bug 60 in Baz (deprecated) "buildcfg should be runnable from anywhere" [Wishlist,Won't fix] [14:40] (not that I mind being assigned, but it might give a false impression that I'm acknowledging the bug before even being convinced that it's an actual problem) [14:40] I'm closing it [14:40] oSoMoN, right [14:41] bug #1864274 [14:41] bug 1864274 in firefox (Ubuntu) "crunchy pixels" [Undecided,New] https://launchpad.net/bugs/1864274 [14:41] I will ask for details on this one [14:42] or I could do it, but thanks for the offer :) [14:42] accept then? [14:43] Laney, I'm a bit lost of what to do from the champagne to be honest, I don't think the intend there was to raise it as a rls bug ... so yeah, I probably say rls-not-fixing? [14:44] hopefully we can have a proper cross team discussion about those next week [14:44] Laney, also it just reminded me I forgot to review/comment on your email draft, sorry about that! [14:44] so -1 from me for that one/ rls-ff-notfixing [14:44] other opinions? [14:45] it is sort of the intent but you've argued against that multiple times now so I don't think you are minded to accept it being done this way [14:45] maybe you want to take over proposing a process from me [14:46] can we just evealuate it after the reporter provides more details/video? [14:46] let's discuss later (probably next week?) [14:46] sgtm [14:46] good topic for the sprint [14:47] I've asked for details [14:47] right [14:47] i saw that [14:47] let's move on [14:47] I personally think it's fine to assign to someone and let them close it if necessary [14:47] that's a valid outcome [14:47] I agree [14:47] i agree with Laney [14:47] so assign & untag? [14:48] or tag not-fixing? [14:48] assign & untag [14:48] or just assign [14:48] if we 'just assign' it's stay on the list and we see it again next week [14:49] but you ask the assignee to do simething with it before then [14:49] whether tag or close or w/e [14:49] if we leave it tagged we can keep track of the status of all champagne bugs as they are being worked [14:49] dunno [14:49] right [14:49] also, i'm the new kid so this is my naive perspective :) [14:49] we are not likely to solve that today, let's ignore the issue for another week I say [14:49] i'd say assign and leave tagged [14:50] let's do that for this week [14:50] * Laney shrugs [14:50] Laney, don't shrug too much, I think I'm just being lost on what the process should be for case that need info [14:51] or maybe it's obvious and no-enough-info -> not ready to be rls accept -> notfixing [14:51] we should have champagne with our champagne discussion next week 🎉 [14:51] +1 [14:51] anyway I don't want to make everyone waste time because I'm confused [14:51] i think you're not the only one that's confused about how this tag should be used seb128 [14:52] yeah, definitely not the only one [14:52] so it's not wasting time to discuss it but we can better discuss it in person next week [14:52] right [14:52] that's an agreement [14:52] moving on from that discussion until next week then! [14:52] better ignore my proposed email then [14:52] bug #1864577 [14:52] bug 1864577 in gnome-control-center (Ubuntu Focal) "Ubuntu logo is not displayed in the 'About' Pane" [Undecided,Confirmed] https://launchpad.net/bugs/1864577 [14:53] it's minor but I think it's a regression [14:53] i think we should fix it [14:53] I would tend to vote +1 [14:53] +1 [14:53] definately +1 [14:53] kenvandine, assigned to Robert is fine? [14:53] looks like low hanging fruit [14:53] yes [14:53] thx [14:55] http://reqorts.qa.ubuntu.com/reports/rls-mgr/rls-ff-tracking-bug-tasks.html [14:56] k, nothing interesting there, the exif one is to close, nm is known, and the last one we discussed [14:56] #topic update_excuses_by_team.html#desktop-packages === meetingology changed the topic of #ubuntu-desktop to: Home of the Desktop Team, https://wiki.ubuntu.com/DesktopTeam | For help or questions, try #ubuntu | Work (read-only for non-developers): https://trello.com/b/mxaCZTVc | GNOME 3.36 work claiming / tracking: https://trello.com/b/z29JJK3q/gnome-336 | Desktop Team Weekly Meeting - 2020-02-25 | Current topic: update_excuses_by_team.html#desktop-packages [14:56] https://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses_by_team.html#desktop-packages [14:57] Laney, do you want to do it or should I keep that for now since I'm still active on dealing with issue for the time being? [14:57] you can [14:57] k [14:57] sooo [14:57] long list of things blocked on icu [14:58] + now poppler and gnome-desktop transitions started [14:58] icu was a dependency on many of these yesterday and was triggering a LO test that was failing because of a copy timeout in the build runner [14:58] tjaalton, are you looking at the xorg-server issues? [14:58] * Trevinho wonders if icu would change also mozjs tests... [14:58] (not for this though) [14:58] bubblewrap/libcap is being handled, there a mp upstream now [14:59] laney has increased the copy time and that improved things but the LO arm64 test was failing in a way that a retrigger has fixed for other tests so it has been retriggered and everyone cross your fingers [14:59] Trevinho, https://bugs.launchpad.net/ubuntu/+source/mozjs60/60.8.0-2ubuntu4 was a simple fix needed for mozjs60, dunno for 68 [14:59] Ubuntu bug 60 in Baz (deprecated) "buildcfg should be runnable from anywhere" [Wishlist,Won't fix] [14:59] its weird that this list in update_excuses doesn't say that they depend on icu anymore.. [14:59] hellsworth, http://autopkgtest.ubuntu.com/packages/libr/libreoffice/focal/arm64 has failed retries from today ... [15:00] ok we've that already [15:00] yeah, I think the fact they stated what they were blocked on was a new improvement [15:00] unsure what happened/if they rolled back or if it broke for some reason [15:00] I will investigagte, it was useful info [15:00] anyway [15:01] out of those issues, we are good [15:01] seb128: right and the last failure that ran for 12h is what i'm looking at. that uicheck test has failed in other tests if you scroll down - glib and python - in both cases a rerun fixed it. [15:02] we really need an owner for gscan2pdf/arm, so please take the card if you want to volunteer [15:02] otherwise we will probably assign someone this week [15:02] it's block xorg-server and now the sane-backends update [15:03] and that's it for proposed migration [15:03] #topic AOB === meetingology changed the topic of #ubuntu-desktop to: Home of the Desktop Team, https://wiki.ubuntu.com/DesktopTeam | For help or questions, try #ubuntu | Work (read-only for non-developers): https://trello.com/b/mxaCZTVc | GNOME 3.36 work claiming / tracking: https://trello.com/b/z29JJK3q/gnome-336 | Desktop Team Weekly Meeting - 2020-02-25 | Current topic: AOB [15:03] a remainer that ff is this week [15:03] yes [15:03] Laney, go! [15:03] Trevinho: do you want to describe the gjs bug situation? [15:03] yeah [15:04] (while you do that, I state again that we could use help on GNOME updates) [15:04] so... gjs moved to use mozjs68, gnome-shell depends on latest gjs so we had to upgrade the whole stack. Now, gjs proved to be a bit unstable while doing garbage-collection [15:04] so we may have a bit more crashes... [15:05] now, there's a WIP mr that aims to improve the situation and we included in debian [15:05] but still there are reports of crashes, so updating to .35 would imply a more unstable desktop till we don't fix gjs [15:05] seb128: yes? [15:05] https://gitlab.gnome.org/GNOME/gjs/issues/301 [15:05] now... What to do? wait for the fix to land before going .35 or not? [15:05] GNOME issue 301 in gjs "Various GNOME Shell crashes during GC, mozjs68 regression" [1. Bug, 1. Crash, Opened] [15:05] thanks L [15:06] when do you think the fix will land? [15:06] personally, from random usage I didn't see many issues, but.... [15:06] hellsworth: no clear idea, probably we may have to get the hands dirty to get a proper fix as upstream has not found a final solution yet [15:06] to help* [15:07] imho, i would take the safer route and wait to include .35 until the fix lands, while also trying to get it landed. [15:07] Laney, Trevinho, what's your gut feeling? [15:07] and by i, i mean you :) [15:07] as said, we included https://gitlab.gnome.org/GNOME/gjs/-/merge_requests/396 but not complete yet [15:08] can we update gnome-shell without updating gjs? [15:08] hellsworth: yeah, well... we should go past FF; so... better people to know it. [15:08] seb128: we *may*. [15:08] I should have added 'easily' [15:08] yeah, it's quite easy in fact [15:09] I would either do that [15:09] we may have two choices, go with gjs 1.93.. smth, I mean the one before mozjs68 [15:09] *OR* just cherry-pick the required change that the shell depends on [15:09] * Trevinho blames himself for it xD [15:09] or update including mozjs68 and use a block-proposed to stop it migrating until it gets more testing/a proper fix [15:10] so using mozjs60 is still possible for a bit, but I *WON't*m suggest it for the lts, as we'd loose all the point-releases support. [15:10] plus ability of cherry-picking changes from upstream [15:10] right, I wouldn't suggest that enough [15:11] but we need to get gnome-shell some testing [15:11] so if it's easy I would do a first landing with mozjs60 [15:11] and then go for 68 and block that in proposed [15:11] enough->either [15:11] other opinions? [15:11] ok, so let me try if we can just get the gjs patch out with the current gjs we've in ubuntu, and then we can try to move to the latest [15:12] it should be simple enough [15:12] k, that has my vote as step1 then [15:12] probably ok, but testing random combinations of stuff isn't great as a rule [15:13] right [15:13] Laney: isn't a random combination in this case, because the fact is that the only reason why new gjs is needed, is because a JS definition, nothing else [15:13] we should move to the new version whenever possible [15:13] but move on as soon as possible is indeed better. [15:13] but meanwhile there is value getting some testing of the new serie [15:13] it is random, because gnome doesn't expect you to use parts of their old release and parts of the new one [15:13] seeing new feature, potential UI/behaviour changes etc [15:13] but being gjs just an interpreter, and being js always the same lang, there should not be any problem [15:14] k [15:14] your call [15:14] given I'm the one who bumped that requirement upstream, I can define it not random :) [15:14] I think getting the update based on 68 blocked in proposed should be fine as well [15:14] :-) [15:14] Laney, Trevinho, you got what you wanted from the discussion for now? [15:15] sure [15:15] but as you guys prefer, I mean, I'm ok with leaving a crashing desktop xD, but then I don't want to hear anybody at FRA blaming for it [15:15] we can do it [15:15] no guarantees though, that's likely to be a pretty untested combination [15:15] I would advice against having an update with a known crasher landing in focal proper [15:15] like nothing says you don't require some other fix in the new gjs for new shell [15:16] for the reason you just stated [15:16] but it might or even is likely to be ok [15:16] right [15:17] Laney: unless I missed something, no... Or we can actually use the *expected* version as I said, so 1.63.2 (mozjs60 based) [15:17] well let's block in propose and do a round of in team testing first [15:17] that wouldn't be random, but the one upstream requires [15:17] so, as you guys prefer. But just a patch could be enough imho. [15:18] Trevinho, you are the mainainer (upstream & downstream), do what you believe is the best :) [15:18] k, enough on that for now, we can keep discussing after the meeting if needed [15:18] any other topic? [15:18] I do another round of reminders [15:18] - we could use extra hands for GNOME updates [15:19] - ff is thursday, land your features! [15:19] - Signup at https://trello.com/b/z29JJK3q/gnome-336 for GNOME packaging :) [15:20] - https://people.canonical.com/~platform/desktop/desktop-packages.html to see what's missing [15:20] lets wrap on that note then! [15:20] thx for the urls Trevinho :) [15:20] #endmeeting === meetingology changed the topic of #ubuntu-desktop to: Home of the Desktop Team, https://wiki.ubuntu.com/DesktopTeam | For help or questions, try #ubuntu | Work (read-only for non-developers): https://trello.com/b/mxaCZTVc | GNOME 3.36 work claiming / tracking: https://trello.com/b/z29JJK3q/gnome-336 [15:20] Meeting ended Tue Feb 25 15:20:56 2020 UTC. [15:20] Minutes: http://ubottu.com/meetingology/logs/ubuntu-desktop/2020/ubuntu-desktop.2020-02-25-14.31.moin.txt [15:22] seb128: could you look into libgusb update or should I? Given that it helps with libfprint (not sure the changes you had to do for testing was caused by that) [15:23] Trevinho, I can have a look [15:23] you are busy enough [15:23] Trevinho, also please look at your query, unsure what's going on without IRC client :) [15:26] seb128: just too many notifications everywhere... And now, signal! :( [15:27] oSoMoN: fyi, I commented on https://launchpad.net/bugs/1864127 [15:27] Ubuntu bug 1864127 in chromium-browser (Ubuntu) "apparmor denies ~/snap/chromium/ writes" [Undecided,New] [15:28] during MIR meeting -> doko | apparently, desktop just asking kernel for a take over on -devel ;p [15:28] seb128: do you know what this is about? I’m out of context [15:28] didrocks, I would guess https://bugs.launchpad.net/ubuntu/+source/alsa-ucm-conf/+bug/1862776 [15:28] Ubuntu bug 1862776 in alsa-ucm-conf (Ubuntu) "[MIR] alsa-ucm-conf & alsa-topology-conf (b-d of alsa-lib)" [High,New] [15:29] didrocks, which would be funny seeing that doko opened the bug and he's the one who assigned to Kernel Packages [15:29] yeah, I’m requested to review it now [15:29] apparently [15:30] didrocks, I guess that's what you get for trying to be nice and help other teams, I should have let it to be completed by the kernel team [15:30] I don’t have slots for doing it before next week though [15:34] didrocks, yeah, no hurry, but also feel free to bounce back from taking it, it's not a desktop item, it's a hwe one [15:34] didrocks, oem teams want those to support new hardware [15:34] I guess I can have a look, but not timely for FF [15:38] jdstrand, ack, thanks! that's my suspicion too [15:40] bah [15:43] e-d-s fails to build with [15:43] 'dh_girepository: Could not find ICalGLib-3.0.typelib dependency' [15:44] ricotz, ^ any idea about that one? ;) [15:45] seb128: do you have the new libical-dev? [15:45] there was something like that that I fixed a couple of weeks ago [15:46] * ricotz suspects a broken ical install too [15:47] Laney, oh, the update is blocked in proposed [15:47] thx for pointing that out [15:47] yeah, icu :( [16:23] seb128: Hi, u there ? === alan_g_ is now known as alan_g [17:16] seb128: I have made few unity merges here. Can you review ? [17:19] seb128: https://bugs.launchpad.net/ubuntu/+source/unity-settings-daemon/+bug/1863584 [17:19] Ubuntu bug 1863584 in unity-settings-daemon (Ubuntu) "Drop gnombg for background drawing" [Undecided,Confirmed]