[05:49] <duflu> jamesh, was there a logical reason for changing the default branch on https://git.launchpad.net/~ubuntu-audio-dev/pulseaudio ?
[05:51] <duflu> Hmm, can't be. It changed to "master" which doesn't exist. And so the web interface showed the latest branch instead. Now changed back to "ubuntu"
[06:05] <jamesh> duflu: I'm not sure how to change the default branch, so it if was something I did it was unintentional
[06:05] <duflu> jamesh, no, looks like a launchpad bug/change
[06:05] <duflu> The default branch reverted to "master" which does not exist so confuses the web interface
[06:06] <jibel> Good morning
[06:06] <duflu> Morning jibel
[06:08] <jibel> Hey duflu
[06:18] <didrocks> good morning
[06:18] <jamesh> hi didrocks, jibel
[06:19] <jibel> Hi jamesh and didrocks
[06:27] <didrocks> hey jamesh, salut jibel
[06:33] <jibel> duflu, I reverted the title of bug 1792932 , it's more discoverable for user of cosmic on vbox. Also even if the assertion is the same it may just be a symptom of different root causes.
[06:35] <duflu> jibel, I think assertion failures in general indicate a bug. Even if you arrive at the failure by different means it's a nice clear-cut way to identify the bug by the assertion so should be considered the same bug. The only definite fix for assertion failures is to modify the code so the assertion no longer exists, or never fails
[06:36] <duflu> But I don't think it's helpful for xenial users etc to say "cosmic" or "vbox"
[06:37] <duflu> I've said enough on that now and won't change it again
[07:40] <Nafallo> hmm I see loop devices in Other Locations on nautilus=1:3.26.3-0ubuntu4. known regression?
[07:41] <Nafallo> on bionic
[07:41] <didrocks> I didn't hear about it
[07:41] <didrocks> maybe check with andyrock once he's around, he worked on the lib to hide them
[07:42] <Nafallo> all of them are lxd. no others.
[07:42] <didrocks> ah, could be that we only have hidden the snaps, but I don't think it would be a regression then
[07:42] <didrocks> maybe lxd changed?
[07:42] <didrocks> worth checking with them :)
[07:42] <Nafallo> oh, sorry. lxd snaps...
[07:43] <didrocks> yeah, could be a regression in the lxd snaps maybe, talk to stgraber
[07:45] <oSoMoN> good morning desktoppers
[07:49] <willcooke> good morning
[07:50] <willcooke> Happy October
[07:50] <didrocks> salut oSoMoN, hey willcooke
[07:50] <didrocks> happy october indeed
[07:50] <oSoMoN> morning willcooke, didrocks
[07:51] <oSoMoN> goodbye September
[07:55] <willcooke> Woah, suddenly I've got tab completion inside gmail.
[07:55] <willcooke> It offers to finish my sentences for me, and it's pretty good
[07:57] <oSoMoN> not good enough until it learns to write your e-mails entirely for you
[07:57] <willcooke> :)
[07:58] <jibel> if it could work for me and pay my taxes it'd be perfect
[07:59] <oSoMoN> duflu, welcome back
[08:00] <duflu> Morning oSoMoN, thanks
[08:00] <willcooke> jibel, out source yourself
[08:00] <duflu> Morning didrocks, Nafallo, willcooke
[08:00] <Nafallo> hey duflu :-)
[08:00] <willcooke> https://www.bbc.co.uk/news/technology-21043693
[08:01] <Laney> hai
[08:03] <duflu> 'lo
[08:16] <oSoMoN> is https://discourse.ubuntu.com/t/high-power-consumption/8191 something we are aware of?
[08:18] <jibel> I saw it but it's too vague
[08:19] <seb128> good morning desktopers
[08:19] <oSoMoN> salut seb128, ça va?
[08:19] <seb128> lut oSoMoN, ouais, et toi ?
[08:20] <oSoMoN> très bien! les vacances étaient bien?
[08:20] <seb128> coming back from holidays and realizing you forgot the power block from your laptop and don't have a spare one
[08:20] <seb128> #fail
[08:20] <seb128> nickel !
[08:20] <oSoMoN> perfect excuse for an extra week of holidays to go fetch it
[08:23] <Laney> hey seb128
[08:23] <Laney> feeling relaxed?
[08:23] <seb128> oSoMoN, I should :)
[08:23] <seb128> Laney, yes, very much!
[08:23] <seb128> I wonder if I can find a latitude power block in town
[08:24] <seb128> I moved my disk to an old laptop but that's slow and noisy :/
[08:24] <seb128> even slower than my personal old laptop :p
[08:24] <Nafallo> seb128: eeepc? ;-)
[08:25] <seb128> what is eeepc?
[08:25] <seb128> ah, I guess a type of netbook/slow laptop?
[08:25] <Nafallo> first netbooks. 2008 ;-)
[08:26] <Nafallo> underclocked celeron @ 630MHz, 4GB DDR, 4GB internal USB stick, 7" screen. something like that.
[08:26] <Nafallo> actually. probably not 4GB memory :-P
[08:26] <Laney> I had one of those
[08:26] <Laney> seb128: where is it? at the holiday place?
[08:27] <seb128> no, at my place in France
[08:27] <willcooke> seb128, just buy a new laptop.
[08:27] <seb128> I could have it send by post, it's going to take a few days though
[08:27] <seb128> willcooke, I plan to do that, but I probably want a Dell one so need to web order and it's going to take a bit
[08:27] <willcooke> :)
[08:27] <seb128> meanwhile I would like a machine I can use to work :)
[08:28] <willcooke> pfft
[08:28] <Laney> that's what the cloud is for!
[08:28] <seb128> or you say it's fine I don't work until new laptop arrive?
[08:28]  * seb128 goes to the swimming pool
[08:28] <willcooke> :D
[08:28] <Nafallo> 512MB memory, not 4GB :-P
[08:28] <Nafallo> and DDR2
[08:30] <willcooke> kenvandine, jibel:  WOAH!!!! I connected to the Windows PC via VNC, started an Ubuntu machine in Hyper-V, copied a load of text to the clipboard and then pasted in to an email on this machine!
[08:31] <jibel> seb128, or buy a generic power supply with interchangeable connectors and power. hopefully one will be compatible.
[08:31] <willcooke> Ubuntu -> Hyper V -> Windows -> VNC -> Ubuntu
[08:31] <jibel> willcooke, I'm happy that makes you happy :D
[08:31] <willcooke> ha, thanks
[08:31] <Nafallo> seb128: I suppose laptop-ng will be changed with USB-C then ;-)
[08:31] <Nafallo> charged
[08:33] <Trevinho> hi all, and welcome back seb128 :)
[08:33] <seb128> good morning Trevinho!
[08:33] <oSoMoN> morning Trevinho
[08:35] <duflu> Morning Trevinho
[08:46] <willcooke> duflu, jibel thanks for replying to that post that oSoMoN linked to
[08:46] <willcooke> thanks for pointing it out oSoMoN
[08:47] <duflu> willcooke, no worries. ~ubuntu-power-consumption is a lonely place these days but mostly because it's much better than it used to be
[08:47] <duflu> Without the tilde
[08:56] <duflu> willcooke, I wonder... is Tuesday morning still OK for Australia to submit reports? Same as before. That's bascially "Monday night"
[08:57] <duflu> I guess the answer is yes unless you're collating them at 2am-ish
[08:59] <willcooke> duflu, yeah that's totally fine
[09:01] <willcooke> I dont intend on collating anything, the hub posts should be just that
[09:02] <willcooke> so as long as there is something for you to read before the meeting so that you can either raise questions on the hub or however we do it
[09:02] <duflu> I know, but that's the verb which came to mind
[09:02] <willcooke> that will work
[09:02] <willcooke> :)
[09:03] <duflu> I think that will be true either way. We will have all Tuesday to read it
[09:04] <willcooke> ya
[09:04] <willcooke> kenvandine, seb128 - is this blocked until the other MIR review goes through?
[09:04] <willcooke> https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal/+bug/1749672
[09:06] <seb128> duflu, that requirement was more for europeans to write the summary on their monday, so robert_ancell has a chance to read them before the meeting (since he's usually off by the time europe starts on tuesday)
[09:06] <duflu> Yes, he is very close to the international date line. Relatively
[09:06] <seb128> willcooke, yes
[09:29] <seb128> oSoMoN, I'm reading the irclog from past week, what happened to "  - prepared and tested 62.0.2 update in a PPA, waiting for feedback from Chris before I upload to cosmic, and I will then proceed to prepare the updates for bionic, xenial and trusty"?
[09:29] <seb128> still waiting on chrisccoulson?
[09:51] <seb128> Laney, are the gstreamer point updates somewhat on your todo?
[09:51] <Laney> somewhere yes
[09:53] <seb128> good, thx
[09:57] <seb128> k, I'm almost done with IRC backlog from past week :)
[09:58] <seb128> didrocks, hey, I see Till mentioned vpn issue past week, which is resolved by a n-m-applet revert (https://gitlab.gnome.org/GNOME/network-manager-applet/issues/20) could you have a look at backporting the change in cosmic? (sorry that you got your name on that one from the update :p)
[09:58] <gitbot> GNOME issue 20 in network-manager-applet "Cannot import VPN configuration from standard ovpn files" [Closed]
[10:08] <oSoMoN> asking meld to diff two 70k lines build logs: not a good idea
[10:09] <seb128> hehe
[10:11] <seb128> you usually want to sed replace some of things in build log as well, like builddir, to simplify the diff
[10:18] <Laney> didrocks: ignore that, I started preparing on friday (for debian, then we'll can merge, you can handle that part if you want) (seb128)
[10:25] <Laney> bubblewrap needs promoting now plz
[10:28] <seb128> Laney, didrocks, having it through Debian is fine, but what I care about is having it in cosmic before we release, unsure if we plan to remerge n-m-applet at this point so please one of you get it by the way you prefer (merge/cherry pick/...)
[10:29] <Laney> yes seb
[10:29] <seb128> thx
[10:29] <Laney> I would have done the merge but since you pinged I offered it up
[10:29]  * Laney knows how this works
[10:29] <seb128> I'm sure Didier is happy to let you handle it :)
[10:29] <seb128> thx Laney
[10:30] <Laney> it's not hard to ask
[10:32] <seb128> Laney, blubblewrap is pulled it by gnome-desktop3 now right?
[10:32] <Laney> yes
[10:32] <seb128> yes, looks like it
[10:32] <Laney> see excuses
[10:32] <seb128> I got confused by the changelog summary
[10:32] <seb128> you kept the items in the "remaining changes" section
[10:32] <seb128> and then listed them as dropped bellow
[10:32] <seb128> now makes sense :)
[10:34] <seb128> bah
[10:35] <seb128> Laney, I did promote it but noticed after that the bug was not "fix commited"
[10:35] <seb128> I hope I don't get dok_oked over it :p
[10:36] <Laney> thx
[10:37] <Laney> I think we said at that meeting that we didn't have to go back to the mir team in this situation
[10:37] <Laney> but the status might have been wrong since the updates happened before that
[10:37]  * Laney shrugs, we'll see
[10:41] <seb128> jbicha, woff2 promoted as well while I was at doing those
[10:42]  * didrocks is happy to let Laney handling it, ofc :)
[10:42] <Laney> thx & morning
[10:48] <didrocks> morning Laney ;)
[10:51] <didrocks> willcooke: hey, have you seen https://github.com/ubuntu/yaru/issues/676#issuecomment-425258757? (got pinged because of the new uploads without those changes)
[10:51] <gitbot> ubuntu issue 676 in yaru "Ubiquity improvements" [Design, Discussion, Enhancement, Open]
[10:52] <willcooke> didrocks, what's the ask?  To re-do the sceenshots in the insatller?
[10:53] <didrocks> willcooke: "I had to change the folder structure a bit, but you can grab the images and CSS from there."
[10:53] <didrocks> from what I read
[10:53] <didrocks> I'm trying to convince him to do some launchpad bzr MP so that it's easiest for you to review
[10:53] <willcooke> didrocks, I still dont follow, what are they asking to be done?
[10:54] <willcooke> New CSS in the installer?
[10:54] <willcooke> Ohhh
[10:54] <willcooke> I thought that link was a picture, it's interactive
[10:54] <didrocks> yep
[10:55] <willcooke> Well, I can test it here, but feels a bit too risky for me now
[10:55] <didrocks> I'll let you answer on the MP
[10:55] <willcooke> 2 weeks before release, and maaaybe the installer will break
[10:55] <willcooke> ack
[10:55] <willcooke> on github right?
[10:55] <didrocks> trying to teach him launchpad, I'll let you know
[10:56] <willcooke> oki, well I can reply on the github issue if needed. But I won't just yet otherwise they won't try LP
[10:56] <willcooke> FTR - happy to merge these right at the start of next cycle, but IMO it's too late this cycle and too risky
[11:08] <didrocks> willcooke: here you go: https://code.launchpad.net/~madsrh/ubiquity-slideshow-ubuntu/Yaru-CSS/+merge/355913
[11:10] <andyrock> Trevinho: do you mind cherry-picking https://gitlab.gnome.org/GNOME/gnome-shell/commit/7ea034c7190d2bd13a0b3ab863df0d6700a1732e and https://gitlab.gnome.org/GNOME/gnome-shell/commit/11fb91f60f17f6013e40992563936ac0a98262cb in gnome 3.28 branch ?
[11:19] <Trevinho> andyrock: join gnome-shell, garnacho said there might be some fallout
[11:19] <Trevinho> so you might talk better than me there
[11:22] <willcooke> thanks didrocks
[11:31] <GunnarHj> Hey Laney, can you please look at the FFe request at bug #1791367?
[11:32] <Laney> I try not to look at 100% of the desktop issues, so I'd prefer if you ask in #ubuntu-release initially please
[11:34] <GunnarHj> Laney: Ok, will do.
[11:35] <Laney> thanks!
[11:53] <Nafallo> didrocks: it's loops where the backend file has been removed.
[11:54] <Nafallo> didrocks: so something didn't tore down the loop device before snap removed the file. I suppose I should talk to someone else now? :-)
[11:55] <didrocks> Nafallo: no, I would still check with Stéphane
[11:55] <didrocks> as the loop was created by lxd
[11:57] <Nafallo> didrocks: the snap loops are created by lxd?
[11:58] <Nafallo> bah. I had to reboot, and of course the issue disappeared...
[11:58] <didrocks> Nafallo: wait, you told the loop devices were the ones created by lxd?
[11:58] <didrocks> now, you think it's the one created by snapd?
[11:59] <Nafallo> didrocks: no, that it was the lxd snap loops...
[11:59] <didrocks> Nafallo: talk to Stéphane, really, to see if this is the one created by lxd itself or the snap
[11:59] <Nafallo> it's not related to lxd more than that being the snap that got refreshed...
[11:59] <didrocks> he would know better than a man in the middle :p
[12:00] <didrocks> if you are sure it's a snapd issue, please check #snappy
[12:00] <Nafallo> yeah. will do :-)
[12:04] <popey> willcooke: added a couple of handy links to your post :)
[12:04] <willcooke> popey, ah!!! Nice one, thank you.  I will copy that for next time
[12:08] <willcooke> I like seeing the posts on there already.  Good plan team
[12:31] <k_alam> Hi, which branch is for merge proposals in ubuntu-themes ? https://code.launchpad.net/ubuntu/+source/ubuntu-themes/+git
[12:32] <k_alam> ubuntu/devel ?
[12:33] <didrocks> k_alam: you sure rather use this branch: https://code.launchpad.net/ubuntu-themes (lp:ubuntu-themes) as the target
[12:33] <didrocks> the others are some autogenerated by launchpad
[12:33] <didrocks> (if you are talking about the theme pre-cosmic)
[12:34] <k_alam> So , using bzr ?
[12:35] <didrocks> yes, it seems they are using bzr by default
[12:35] <didrocks> this is for ambiance/radiance
[12:36] <k_alam> Ah. Right. Thanks. :)
[12:37] <didrocks> yw ;)
[12:38] <Laney> just found a "This is a temporary workaround" patch in gnome-shell that is approaching its first birthday 🎂
[12:38] <Laney> guess that is young in the grand scheme 😉
[12:39] <didrocks> Laney: what was it? The extension one?
[12:40] <Laney> workaround_crasher_fractional_scaling.patch
[12:40] <didrocks> interesting
[13:36] <Trevinho> when someone has time.. https://code.launchpad.net/~3v1n0/ubuntu/+source/gnome-calculator/+git/gnome-calculator/+merge/355919
[13:36] <Trevinho> Laney: yeah, actually I think it's not either needed anymore with current theming, but not sure... andy did it, but I never have been able to reproduce it
[13:53] <Trevinho> sil2100: hey, could you check the discussion at https://code.launchpad.net/~3v1n0/ubuntu/+source/gnome-calculator/+git/gnome-calculator/+merge/354330 and see if you're ok with that?
[14:35] <sil2100> Trevinho: let me take a look at it in a minute
[14:41] <seb128> Trevinho, Laney, does https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1795230 ring any bell to you? (a bit difficult to know what's going on without debug info, I commented asking for details)
[14:43] <Laney> not really
[14:44] <seb128> k, thx anyway
[14:44] <Laney> a better bt would help for sureu
[14:44] <Laney> -u
[14:45] <seb128> right
[14:48] <k_alam> Hi, I have couple of merge proposals, please review
[14:48] <k_alam> 1. https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1773045
[14:48] <k_alam> 2. https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/1795145
[14:48] <k_alam> 3. https://bugs.launchpad.net/ubuntu/+source/telepathy-mission-control-5/+bug/1795412
[14:49] <k_alam> 4. https://bugs.launchpad.net/ubuntu/+source/telepathy-mission-control-5/+bug/1708375
[14:49] <k_alam> 5. FTBFS: indicator-sound: https://code.launchpad.net/~khurshid-alam/indicator-sound/gicon-fix
[14:49] <k_alam> It only fixes the regression in glib, but not other errors, Trevinho please take a look...
[14:49] <k_alam> 6. [FFE] https://bugs.launchpad.net/ubuntu/+source/unity-control-center/+bug/1741027
[14:49] <k_alam> not really ffe, because ui for sharing panel has been landed in bionic. but anyway...
[14:50] <seb128> k_alam, hey, I'm not sure that spamming the channel this way is the best way to get your review
[14:50] <seb128> reviews
[14:50] <seb128> try maybe emailing the ubuntu-desktop@ list? Also we stopped maintaining the unity component so maybe you should land those without seaking for us to approve first
[14:51] <jbicha> seb128: do we still use that email list? we talked about just using the Community site
[14:53] <seb128> jbicha, you unsubscribe I guess :p
[14:53] <seb128> the git merge request emails go there and I approve them daily
[14:53] <k_alam> seb128: sorry about that, but nobody reviews them and I was asked to ping on #ubuntu-desktop
[14:53] <seb128> so we sort of use it for workflow (automated) messages
[14:53] <seb128> not for discussion
[14:54] <seb128> unsubscribed*
[14:54] <didrocks> especially spamming the channel for already merged MP
[14:54] <jbicha> k_alam: maybe you could ask bigon to review the telepathy-mission-control change for Debian (and the minimal Ubuntu diff)
[14:54] <didrocks> (like the ubuntu-themes one)
[14:55] <jbicha> I guess I'll take the ubuntu-settings one
[14:56] <seb128> thx
[14:56] <k_alam> didrocks: I see it merged...Thanks
[14:56] <didrocks> yeah, and please assign the team rather than individuals
[14:57] <didrocks> like themes was for me, ubuntu-settings seems to be directly assigned to (?reasons?) Laney
[14:57] <didrocks> k_alam: jbicha: please don't turn the background plugin for all in ubuntu
[14:57] <didrocks> only do it in the unity session
[14:57] <didrocks> we don't need/want that in all session inheriting "ubuntu"
[14:59] <jbicha> ok
[14:59] <k_alam> didrocks: So it stays as turned off for Ubuntu, or should I remove it , as g-s-d doesn't use that any more
[14:59] <jbicha> how do you guys handle accepting git merge proposals?
[15:00] <seb128> you mean?
[15:00] <seb128> launchpad has an UI similar to the one it has for bzr ones
[15:00] <didrocks> k_alam: keep it off, I didn't look at g-s-d code to ensure it's not used anywhere or that there is no side-effect in other pieces
[15:00] <jbicha> yeah, GNOME itself doesn't use the active keys in g-s-d any more, we just kept those because unity-settings-daemon hadn't adapted to that yet
[15:00] <seb128> you can change the status and it auto mark as merged if you merge/push
[15:00] <didrocks> k_alam: so, better to only turn it on back in unity for cosmic
[15:01] <k_alam> didrocks: All right.
[15:01] <k_alam> jbicha: Can  I ask xnox about mission-control ?
[15:01]  * didrocks would prefer this kind of "cleaning" at the start of the cycle than after FF, maybe just trying to be too conservative… :)
[15:01] <jbicha> k_alam: bigon is sort of the Debian maintainer :)
[15:08] <seb128> k_alam, I pinged j_dstrand on https://bugs.launchpad.net/ubuntu/+source/telepathy-mission-control-5/+bug/1708375 and he suggested changes
[15:09] <didrocks> jbicha: have you merged ubuntu-settings?
[15:10] <jbicha> yes
[15:10] <didrocks> ah, it seems you changed in the commit itself directly
[15:10] <didrocks> ok, was expecting k_alam to do it or a message in the MP :)
[15:11] <jbicha> I figured it wasn't worth the back-and-forth since we already discussed it here
[15:11] <didrocks> yeah, you could have move with all others "Unity" properties though
[15:11] <didrocks> as I tried to organize the file for readibility…
[15:11] <k_alam> seb128: Yes,  I am updating the patch. Thanks.
[15:12] <didrocks> jbicha: also, the default in org.gnome.settings-daemon.plugins.gschema.xml is true, no?
[15:12] <didrocks> so basically, the override is wrong
[15:12] <didrocks> you need to set it "false" for :ubuntu and reset it true to :Unity
[15:13] <didrocks> jbicha: want me to fix it?
[15:13] <jbicha> just a moment
[15:14] <jbicha> the default is whatever we want it to be since those keys are part of g-s-d's revert-gsettings-removals.patch
[15:15] <didrocks> as you wish, one way or the other, just ensure that default for ubuntu session is false
[15:15] <didrocks> which isn't the case with your last commit
[15:15] <didrocks> I don't have opinion, if g-s-d will have an upload with default set to false, that's fine by me
[15:15] <jbicha> I mean I'm confident that g-s-d doesn't pay any attention to that key
[15:16] <didrocks> not related to the discussion, we decided to go on the safe path for this cycle, and ensure the key is false
[15:17] <jbicha> ok
[15:17] <didrocks> thx
[15:23] <jbicha> grr, oops
[16:23] <xnox> willcooke, the new desktop theme is way too consistent
[16:23] <andyrock> what is gnome-get-source.mk useful fore?
[16:23] <andyrock> *for
[16:24] <xnox> it is nice, but i am taste-less person and would rather just smear orange all over the place, and then complain about orange smeared all over the place
[16:30] <jbicha> andyrock: we're eventually getting rid of it in favor of just using uscan with debian/watch
[16:31] <andyrock> jbicha: that's to say that if I find a package that still uses it I can remove it?
[16:31] <jbicha> as long as the package still builds
[16:32] <andyrock> kk thanks
[16:33] <jbicha> evolution currently uses a variable set in that file, but most packages don't
[16:35] <jbicha> one reason we had it was to fulfil the get-orig-source requirement but that was dropped in Debian Policy 4.1.4
[16:52] <andyrock> thanks for the info!
[17:44] <willcooke> gnight all