[06:19] <jibel> Good morning
[06:20] <dupondje> Wohooo :) firefox update fixed crashing web.whatsapp! Great
[06:24] <seb128> good morning desktopers
[06:30] <duflu> Morning jibel, seb128
[06:30] <seb128> hey duflu, how are you?
[06:31] <jibel> Hi duflu and seb128
[06:31] <duflu> seb128, getting closer to normal, which is an improvement. You?
[06:31] <seb128> lut jibel
[06:32] <seb128> duflu, I'm ok, a bit tired, baby was stomach sick yesterday evening and part of the night
[06:35] <seb128> good morning didrocks
[06:35] <didrocks> hey seb128
[06:35] <duflu> o/   didrocks   \o
[06:36] <didrocks> gnome-shell gdm is still spiking at 100%
[06:36] <didrocks> can't type, nothing :/
[06:36] <duflu> Hmm
[06:36] <didrocks> hey duflu
[06:36] <seb128> when did that start?
[06:37] <didrocks> yesterday
[06:37] <seb128> does it go away? or how do you manage to log in?
[06:37] <duflu> I will return to profiling gnome-shell soon. Maybe I can figure out how to run the login screen from git?
[06:37] <seb128> Trevinho can help you with that
[06:37] <didrocks> wait, can't type
[06:37] <didrocks> trying to paste something
[06:37] <seb128> stop doing IRC from gdm :p
[06:38] <didrocks> http://paste.ubuntu.com/p/q6wwXqKbmG/
[06:38] <didrocks> no
[06:38] <didrocks> the issue is that gnome shell gdm is fine
[06:38] <didrocks> then you login
[06:38] <didrocks> yuor sessino starts
[06:38] <didrocks> and here, gdm gnome-shell goes crazy
[06:38] <didrocks> but if you kill it
[06:38] <didrocks> after a 3rd attempt, your session vanishes
[06:38] <seb128> weird
[06:39] <seb128> the new gdm is supposed to kill the greeter session after you log in
[06:39] <duflu> Yeah the login screen is killed on VT switching now so it's a bit less reliable at staying up than it used to be
[06:39] <seb128> what packages did you get updated yesterdya?
[06:39] <didrocks> seb128: it's definitively running here
[06:39] <duflu> Sometimes you VT switch and everything freezes
[06:39] <didrocks> I noticed it yesterday morning, so it means updates on Friday
[06:40] <didrocks> wait, really slow, I can't type for 20s every 10s
[06:40] <seb128> what packages did you get updated on friday?
[06:40] <seb128> looks like the new gdm landed
[06:40] <didrocks> I meant, on Monday, trying to gather the list
[06:40] <seb128> maybe try to downgrade that?
[06:40] <didrocks> http://paste.ubuntu.com/p/QTzwBd3bd7/
[06:41] <didrocks> yeah, gdm is in the list
[06:41] <seb128> yeah, gdm is in that list
[06:41] <didrocks> doing that
[06:41] <seb128> good
[06:41] <didrocks> unsure how I will do
[06:41] <didrocks> or maybe reboot, tty…
[06:41] <didrocks> as gdm is always around
[06:42] <seb128> Switching to a vt should stop the greeter session
[06:43] <seb128> I can get you the wget & dpkg -i command to copy/paste if that helps
[06:43] <seb128> bah, let's wait for him to be back
[06:46] <didrocks> indeed, reverting gdm works
[06:46] <didrocks> at least, I can type now :p
[06:46] <oSoMoN> good morning desktoppers
[06:47] <didrocks> seb128: switching to a vt kept the 100% CPU spike for gdm gnome-shell process
[06:47] <didrocks> hey oSoMoN
[06:47] <oSoMoN> salut didrocks
[06:51] <seb128> didrocks, good! please open a bug upstream, they have been responsive to reports recently
[06:51] <seb128> lut oSoMoN, en forme ?
[06:53] <oSoMoN> seb128, oui, et toi?
[06:55] <duflu> Hi oSoMoN
[06:55] <duflu> seb128, yeah I get the impression we were using 3.30 daily before upstream
[06:56] <duflu> So they have been slow to notice the regressions in gdm this cycle
[06:56] <seb128> oSoMoN, okish, kid was sick yesterday evening/in the night (stomach/vomited), let's see if that was only his stomach not agreeing with diner or a proper stomach bug (if it is, I hope I manage to avoid it this time)
[06:57] <oSoMoN> hey duflu
[06:57] <oSoMoN> seb128, good luck with that, stay away from real-life bugs!
[06:57] <seb128> duflu, right, same problem as always, they don't have a big userbase so we are usually the first to throw the code to enough users to see the issues reported
[06:58] <seb128> oSoMoN, thx, trying!
[07:17] <jibel> tkamppeter_, did you talk to upstream about bug 1789184 ? It makes no sense to me to not release it in Cosmic until Cosmic is release.
[07:18] <jibel> Also it's on the ISO and cannot be fixed by an SRU after the release
[07:18] <didrocks> seb128: will do in a bit ;)
[07:19] <didrocks> am I really the one one experiecing it in a up to date cosmic ?
[07:19] <didrocks> (with Xorg, our default, ofc)
[07:33] <didrocks> seb128: FYI: https://gitlab.gnome.org/GNOME/gdm/issues/429
[07:33] <gitbot> GNOME issue 429 in gdm "Regression in 3.30.1 (from 3.30.0): gnome-shell process in gdm is spiking at 100% once logged in" [Opened]
[07:44] <willcooke> morning all.  No water and no internet this morning.
[07:45] <willcooke> Internet fixed at least.  Turned if off and back on again.
[07:46] <popey> A future in IT Support awaits you willcooke
[07:47] <didrocks> hey willcooke
[07:48] <duflu> Morning willcooke, popey
[07:48] <popey> Morning!
[07:48] <duflu> ish
[07:48] <oSoMoN> hello IT^Wwillcooke
[07:48] <willcooke> :)
[07:51] <seb128> didrocks, thx
[07:52] <seb128> hey willcooke popey
[07:52] <seb128> didrocks, no cpu/gdm issue here, willcooke had some problems getting the greeter to display until he switched vt but that sounds different
[07:55] <didrocks> yeah, it sounds quite different
[07:55]  * didrocks opens the FFe for gsconnect new snapshot
[08:01] <Laney> sup
[08:02] <didrocks> hep Laney
[08:03] <Laney> hap hoooo
[08:06] <duflu> hip Laney
[08:07] <oSoMoN> hop hop hop
[08:07] <willcooke> RAOF, hihi!  This colord log spam... every time I resume the machine its adding a hundred lines or so of SNMP "stuff" to the logs.  Google suggests that colord has a dep on SNMP libs - that can't be right can it?!  Is there anything we can do to stop the log spamming?
[08:07]  * duflu forgot he was also annoyed by that
[08:10] <jibel> I've a ghost auth dialog on the screen, annoying
[08:11] <didrocks> seb128: FYI, I repinged k_envandine on the hub this time about the snap icon not matching Suru team (the team feels that despite opening topics on the snapcraft forum, they aren't really supported on that one)
[08:11] <didrocks> something to track IMHO before release
[08:11] <didrocks> (don't know if we open a bug and where for this, as it's a snap and pings on the forum doesn't seem to work well…)
[08:14] <RAOF> <freenode_wil "RAOF, hihi!  This colord log spa"> Hm. I see that too. I'll try disabling colord-sane and see if that silences it.
[08:14] <willcooke> RAOF, thanks!
[08:14] <willcooke> damn it, now I can't get cosmic to fail any more
[08:14] <willcooke> gdm works every time
[08:15] <duflu> willcooke, I wonder if you still had 3.29 installed and/or hadn't rebooted with 3.30 when logging that bug?
[08:17] <willcooke> duflu, it's possible I guess, but I've certainly rebooted that machine a lot of times
[08:17] <willcooke> I think I will reinstall again
[09:09] <seb128> didrocks, k, I would say that snap/suru icon is not trivial to solve and a low priority item at this point, sorry for the sure team if they feel like ignored but not much we can dp
[09:09] <seb128> do
[09:10] <seb128> we have more important problem with fontconfig cache version/startup time and theming still not working for most apps
[09:10] <seb128> and portals to land
[09:11] <didrocks> seb128: well, we can at least answer there are some investigation on it before they ping 4 times and wait for an additional 10 days
[09:11] <seb128> shrug
[09:11] <didrocks> telling there are also other things we manage
[09:11] <seb128> they are not center of the world, we have ten of thousands of bugs sitting without reply for years
[09:11] <seb128> sorry, didn't mean it to be worded that strongly
[09:11] <didrocks> yeah, but they are contributors, who devoted a lot of time for our default look
[09:11] <seb128> but yeah, welcome to reality, we are busy and they issue is a low priority one
[09:12] <seb128> I appreciate that
[09:12] <seb128> but there is only so much we can do
[09:12] <seb128> we struggle with release blockers issues atm
[09:12] <didrocks> but if not answering in 20 days and 4 pings is ok, that's fine, unsure why I try to mitigate and help there
[09:12] <didrocks> anyway, "not my pb", topic closed
[09:12] <seb128> noted
[09:12] <seb128> thanks for caring and raised it though
[09:13] <willcooke> I'll ask Ken to give them a general update on what's going on.  It's fair that we at least ack their request, even if the answer is "sorry, cant help right now"
[09:13] <didrocks> doesn't seem I should have raised it, but meh
[09:13] <willcooke> tjaalton, thanks for the xorg upload.
[09:14] <willcooke> didrocks, it's good that you raised it, thank you.  The solution is simply better communication.  That doesnt need to take us long to do, just need to do it.
[09:15] <willcooke> (easier said than done though :) )
[09:15] <didrocks> that was all that I was asking for, but it seems not widely shared, anyway…
[09:15] <seb128> I also think we need to somewhat set up expectations
[09:15] <seb128> it's not realistic that people expect us to be responsive on everything
[09:15] <seb128> I don't even manage to get people from our team to reply to me on trello cards pings or bugs assigned :p
[09:15] <willcooke> :D
[09:16] <didrocks> depending on who… I don't think it's a healthy state though that you don't get answer
[09:17] <seb128> right
[09:17] <seb128> I'm just saying, that icon issue is minor
[09:18] <seb128> they shouldn't expect us to be top responsive to every single of their minor issues, we do what we can but we are busy
[09:18] <willcooke> Ken has an email which lays out exactly what they're working on and the state.  That probably has enough info in to show why things are not P1 on his list.  I'll speak to him later about posting that on the hub or something.
[09:19] <willcooke> If we share that info then people can see what's in front of them in the queue
[09:19] <didrocks> +1
[09:19] <willcooke> that will show what seb128 says about it being fairly minor in comparison with the bigger fish.
[09:19] <willcooke> Give a sense of scale
[09:20] <willcooke> scale
[09:20] <willcooke> fish
[09:20] <willcooke> geddit
[09:42] <willcooke> Fresh install of Cosmic from last nights ISO boots to GDM first time.
[09:42] <willcooke> grrr
[09:42] <willcooke> maybe its fixed
[09:42] <willcooke> darn races
[09:46] <seb128> Laney, thx for doing that n-m update, I had it on my todo backlog but was struggling to get to it, nice to see it didn't miss cosmic :)
[09:47] <seb128> also nice to see that version lists items from the unapproved queue, I forgot it was doing that and even indicating them with a (Q) :)
[09:54] <Laney> seb128: nm, it fixes the crash that w_illcooke and I and probably others were having (silently, since it doesn't cause apport errors at all for some reason)
[09:54] <seb128> nice!
[09:54] <seb128> did you manage to reproduce?
[09:54] <Laney> yeah on the other laptop too
[09:54] <seb128> well I guess I could try myself to sig11 it
[09:55] <seb128> I'm curious of why is apport not triggering
[09:55] <Laney> right maybe try to kill -SEGV it, see if that doesn't apport either
[09:55] <Laney> the systemd unit has the hardening stuff enabled
[09:55] <Laney> that would be my first suspicion as a cause
[09:55] <Laney> who did the Q thing? you?
[09:55] <Laney> nice feature :>
[09:56] <seb128> I think it was robert a while ago
[09:56] <seb128> indeed :)
[10:14] <Laney> seb128: can you help with gjs/s390x removals in a bit please? https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/1794721
[10:14] <Laney> we should get the new one in sooner rather than later imho
[10:15] <Laney> going to upload ostree to get it off that list first though
[10:17] <willcooke> ok, new install of cosmic from yesterday, added proposed, rebooted - the gdm problem is back
[10:18] <duflu> :(
[10:18]  * duflu -> dinner
[10:20] <seb128> Laney, yeah, I saw your comment on the hub but wanted to check rdepends etc before doing anything and day went by before I had time to look at it again
[10:20] <seb128> willcooke, :/
[10:21] <Laney> ok well I'll upload it, you do whatever checking you want whenever you can
[10:21] <Laney> I just want a yes in principle so it doesn't end up not happening
[10:21] <seb128> k, I'm having a look in a bit
[10:22] <seb128> it's fine, +1 from me
[10:22] <seb128> well I mean deleting gjs on s390x is +1
[10:23] <seb128> I don't know enough about that late mozjs version change to have an opinion on that, out that it feels late so yeah if we do it the sooner the better
[10:23] <Laney> can't not be done really, security thangs and all
[10:25] <seb128> k, so let's do it! :)
[10:26]  * Laney roars
[10:30] <willcooke> Laney, oh noez:
[10:30] <willcooke> Oct  3 11:25:23 test-Inspiron-3137 dbus-daemon[868]: [session uid=123 pid=868] Successfully activated service 'org.freedesktop.portal.IBus'
[10:30] <willcooke> Oct  3 11:25:23 test-Inspiron-3137 kernel: [    9.303956] show_signal_msg: 28 callbacks suppressed
[10:30] <willcooke> Oct  3 11:25:23 test-Inspiron-3137 kernel: [    9.303959] NetworkManager[484]: segfault at 18 ip 00007f39b9dd72d9 sp 00007ffed7021000 error 4 in libc-2.28.so[7f39b9d65000+171000]
[10:30] <willcooke> Oct  3 11:25:23 test-Inspiron-3137 kernel: [    9.303968] Code: e9 57 fb ff ff 48 89 5c 24 30 49 39 f7 74 5a 49 8b 71 28 4c 89 48 20 48 89 70 28 49 89 41 28 48 8b 70 28 48 89 46 20 4c 89 ce <48> 8b 7e 18 e9 1a f7 ff ff 48 81 7c 24 28 ff 03 00 00 48 8b 5c 24
[10:31] <willcooke> oh
[10:31] <willcooke> did you new version hit proposed yet?
[10:31] <Laney> no
[10:31] <willcooke> k, ignore
[10:31] <willcooke> sorry
[10:31] <Laney> heh
[10:36] <seb128> jibel, https://trello.com/c/NO4od6Pv/44-optimise-gnome-software-startup-time is one of the card we failed to triage/move in Brussel because you were at another meeting and the rest of the team didn't know what to do with it, can you update as fit?
[10:36] <seb128> jibel, oh, and https://trello.com/c/P0QWFNyr/28-add-snap-support-to-autopkgtest is probably for next cycle now?
[10:38] <RAOF> willcooke: So, `chmod -x /usr/lib/x86_64-linux-gnu/colord-sane` removes the SNMP spam (and partially replaces it with “can't spawn colord-sane” spam, but that's somewhat expected)
[10:39] <willcooke> RAOF, ah, interesting
[10:39] <willcooke> I would test, but machine is in a special state right now
[10:39] <willcooke> RAOF, is that something which can be fixed in the packaging, or is it a hack?
[10:40] <RAOF> That's a hack. Although it was possible in the past to disable colord-sane via configuration file.
[10:40] <RAOF> But what this suggests is that libsane is spewing SNMP errors during probing.
[10:41] <willcooke> what is it using SNMP for?  Finding network scanners or something?
[10:41]  * willcooke thought he'd seen the last of MIB files about 10 years ago
[10:41] <RAOF> Presumably?
[10:42] <RAOF> Because madness it's also possible that it's not libsane, but a sane plugin that's doing the SNMP.
[10:42] <willcooke> Should I go and bother sane maintainers?
[10:42] <RAOF> I think that'd be a reasonable port of call.
[10:42] <willcooke> ack, thx
[10:44] <RAOF> sane does not exactly have the best reputation here; colord-sane is a separate binary because when the main colord daemon linked to sane directly various sane plugins would leak fds until colord crashed (because of Ubuntu hardening; on Debian it would just consume 100% CPU)
[10:46] <seb128> willcooke, I'm cleaning up our current board by moving cards to the next cycle one now
[10:47] <seb128> so we can focus on the direct line to getting 18.10 out
[10:47] <willcooke> seb128, ace, thanks
[10:47] <seb128> most of the work which isn't targetted to get 18.10 out in shape can be postponed at this point imho
[10:47] <seb128> np!
[10:47] <willcooke> +1
[10:50] <seb128> didrocks, jibel, do you consider https://trello.com/c/mAIfBwox/225-new-installer-investigations as being the initial investigation/to be closed before the planning sprint/this cycle? or a card to carry over for next cycle?
[10:54] <xnox> Laney, seb128: +2 on purging gjs from s390x. it has been escalated multiple times to IBM that it is in a poor state, and out of scope.
[10:54] <Laney> escalated by who?
[10:55] <Laney> not sure why they are bothered either way
[10:55] <xnox> Laney, we sent requests to IBM toolchain team about, via our current engagement.
[10:55] <xnox> Laney, i think the reply was "is it used by nodejs?"
[10:55] <Laney> oh, then not sure why *you* were bothered :P
[10:56] <Laney> seems mozilla don't test spidermonkey on s390x though ;-)
[10:56] <xnox> another ibm wanted to run firefox =) and i'm like.... yo.... talked to your mates.... or better don't do it....
[10:57] <seb128> Laney, I still didn't look at it, but did you check if there as simple as removing gjs or if there are other packages using it to delete as well?
[10:57] <Laney> I put a list on the bug
[10:58] <Laney> it could be wrong in some way though, hopefully britney will give a more definitive one
[10:59] <seb128> k
[10:59] <seb128> thx
[11:24] <xnox> Laney, seed-webkit2 ?
[11:24] <xnox> nevermind, that one never built
[11:27] <Laney> probably easier to see what proposed-migration says
[12:14] <didrocks> seb128: yes, this is basically the "goal to deliver a slidedeck for Will to present at the planning sprint"
[12:15] <didrocks> (we still need to finish the time estimation as the plan changed)
[12:16] <seb128> didrocks, k, what I though, I kept it on the trello from this cycle, thx!
[12:16] <didrocks> and deeper investigation in curtin and so on while we are at it
[12:16] <didrocks> yw
[13:03] <jbicha> seb128: kenvandine: Security grudgingly approved bug 1750069 for cosmic only
[13:06] <kenvandine> jbicha: thx
[13:07] <seb128> jbicha, thx, launchpad do send emails, no need to proxy bugs comments on IRC though :)
[13:07] <seb128> (I saw it/mentioned it earlier)
[13:09] <jbicha> do we want it as a depends or recommends from ubuntu-desktop once MIR is fully approved?
[13:09] <seb128> that needs a ffe btw
[13:10] <seb128> recommends should be good enough?
[13:10] <seb128> you don't have to use snaps/flatpaks on Ubuntu
[13:11] <jbicha> ok
[13:11] <kenvandine> yeah
[13:12] <kenvandine> I'll file a ffe for it today
[13:12]  * bcurtiswx waves and goes back into hibernation
[13:12] <kenvandine> hey bcurtiswx
[13:12] <bcurtiswx> hope ya'll are doing OK, it's been too long
[13:21] <willcooke> tkamppeter_, hi! Did anything change in xenial re: the printing stack?
[13:44] <seb128> k, I tried to cherry pick a gtk commit as a patch using gbp pq rebase/git cherry-pick -x <id>/gbp pq export --no-patch-numbers
[13:44] <seb128> that's a fail
[13:44] <seb128> well the patch is there but it did a stack of random formatting changes to other patches :/
[13:44] <seb128> how do I undo those?
[13:45] <Laney> like updating the indexes?
[13:45] <seb128> like removing "-# Patches not in Debian" from debian/patches/series
[13:46] <Laney> yeah, topic is gbp pq's way of doing that
[13:46] <Laney> if you do git add -p you can just add the bits you care about to the commit
[13:47] <seb128> and then how can I tell it to discard the other ones from the "staging"?
[13:47] <Laney> after committing, git reset --hard
[13:47] <seb128> thx
[13:50] <seb128> is there a command that auto-magically take the changelog diff to suggest a git commit msg?
[13:52] <Laney> debcommit
[13:52] <seb128> ah, thx
[13:52] <Laney> -e to edit it
[13:52] <seb128> same as with bzr :p
[13:52] <Laney> yep it works with most vcs
[14:10] <seb128> is git tag signing really bringing value?
[14:11]  * seb128 finds those annoying, get prompted more than I would like when doing updates
[14:11] <seb128> (unsure why the agent doesn't catch those sometme for me also)
[14:15] <Laney> I like that we have an indication that you can trust in git that the tag corresponds to the archive's upload
[14:15]  * Laney is building a new desktop iso now so people can test if the xorg-server fix worked
[14:16] <seb128> \o/
[14:16] <seb128> I'm unsure to understand how the signing provide more trust
[14:16] <seb128> you need to be able to commit to tag right?
[14:16] <seb128> what sort of errors/attack does it prevent to sign?
[14:18] <Laney> wherever you get the tag from you know it is good
[14:20] <seb128> k, I need to read about this
[14:21] <Laney> it means you don't have to trust the place you are getting the commits from
[14:22] <seb128> I've a feel of why it's useful for but not really a concrete one, it still looks like to me it that it protects from temperring with a tag but if someone gets access to vcs with the intend to screw things in there I feel like we have other problems
[14:22] <seb128> well, we don't sign commits though
[14:22] <seb128> so nothing tells me than the content staged since the previous upload didn't get screwed
[14:23] <Laney> indeed, that's the uploader's review
[14:23] <Laney> that is what you are signing
[14:23] <seb128> I see
[14:23] <seb128> thx
[14:25] <seb128> gnome-control-center$ git checkout pristine-tar
[14:25] <seb128> error: pathspec 'pristine-tar' did not match any file(s) known to git.
[14:25] <seb128> :(
[14:25] <seb128> git grrr :)
[14:25]  * seb128 googles on what he did wrong this time
[14:25] <seb128> I guess I need to -b pristine-tar pristine-tar right?
[14:26] <seb128> sometime that seems to be implicit/work out of the box and sometime not
[14:26] <seb128> -b pristine-tar origin/pristine-tar
[14:26] <seb128> I mean
[14:27] <Laney> if you use gbp clone it sets that up for you
[14:27] <seb128> ah, I probably used git in that case
[14:27] <seb128> I just want to fix/update the pristine-tar from debian :/
[14:28] <seb128> my local copy is 1 commit ahead 4 behind from the remote one, I probably did something wrong
[14:28] <seb128> $ git pull salsa pristine-tar
[14:28] <seb128> Depuis https://salsa.debian.org/gnome-team/gnome-control-center
[14:28] <seb128>  * branch            pristine-tar -> FETCH_HEAD
[14:28] <seb128> warning: Cannot merge binary files: gnome-control-center_3.30.0.orig.tar.xz.delta (HEAD vs. 24ecec67bc2fe60204daefdbfe6fd276250f5632)
[14:28] <seb128> shrug
[14:28] <seb128> or maybe that's not me, I'm not the one that did 3.30 :p
[14:31] <seb128> sorry team, but I'm going to let that in a buggy state for now I think
[14:31] <seb128> I've a long todo still for this week and it's over my git foo to sort that out
[14:32] <Laney> fixed
[14:34] <seb128> how did you do it?
[14:34] <Laney> in salsa/pristine-tar, I did "git merge -s ours lp/pristine-tar"
[14:34] <Laney> then pushed to lp and salsa
[14:35] <seb128> is that a case where it diverged because people did the same update on both side in an independent way?
[14:35] <seb128> upstream/latest has a similar issue I guess
[14:36] <seb128> though a git pull leads to a merge in that case
[14:36] <seb128> unsure if that's the right thing to do though?
[14:36] <Laney> yes, see ee7d28708 and 6c73a4253
[14:36] <seb128> k, makes sense
[14:37] <Laney> this won't happen once we unleash The Plan
[14:40] <willcooke> thanks for the fix zyga
[14:40] <zyga> willcooke: I'm sorry for missing this in the first place!
[14:40] <zyga> happy I could help though
[14:40] <willcooke> zyga, nw!
[14:40] <zyga> I was worried this is some deeper kernel voodoo
[14:41] <seb128> Laney, what about upstream/latest, should I commit the merge than a git pull gives me?
[14:42] <Laney> I would rather merge the ubuntu one into salsa/upstream/latest and then push that to lp and salsa
[14:42] <Laney> well, I don't know what result that merge is giving you
[14:43] <Laney> something like "git checkout -b salsa-upstream-latest salsa/upstream/latest && git merge origin/upstream/latest"
[14:43] <Laney> then check "git diff salsa/upstream/latest" to make sure it is empty and push to salsa and origin
[14:44] <Laney> I assume "salsa" refers to salsa and "origin" to launchpad, adjust if that is not true
[14:45] <seb128> it does
[14:45] <seb128> thx
[14:46] <seb128> that git diff is empty
[14:46] <seb128> thx
[14:47] <Laney> hopefully stop having to do this weird stuff soon
[14:47] <seb128> yes
[14:47]  * Laney needs to send ze email
[14:52] <seb128> k, did it
[14:52] <seb128> I hope I didn't screw something up again
[14:53] <Laney> looks good here
[14:54] <seb128> great, thx :)
[14:54] <Laney> don't forget upstream/3.30.1
[14:57] <seb128> bah
[14:59] <seb128> of course clicking "merge" in the salsa web UI doesn't get those
[14:59] <seb128> needs to add the remote from andy to my vcs now I guess to fetch the tag and push it
[14:59] <seb128> done
[14:59] <Laney> ♥
[15:12] <andyrock> seb128: thanks for the reviews <3
[15:13] <seb128> andyrock, yw!
[15:18] <didrocks> do-release-upgrade -d doesn't work from bionic
[15:18] <didrocks> telling not running latest supported version (which is false)
[15:19] <didrocks> let me ask bdmurray on -devel
[15:20] <jbicha> didrocks: did you tell it to notify you of any Ubuntu version, not just LTS?
[15:20] <didrocks> jbicha: I just run it manually with -d ^
[15:20] <jbicha> right but that will pull from http://changelogs.ubuntu.com/meta-release-lts-development
[15:20] <didrocks> I wasn't expecting that setting to have an impact there
[15:20] <didrocks> but it seems it does, indeed
[15:20] <didrocks> thanks jbicha
[15:20] <jbicha> but you need http://changelogs.ubuntu.com/meta-release-development
[15:23] <didrocks> ah, and I do have the appstream failure now
[15:27] <seb128> Laney, btw gjs/s390x list of binaries removed
[15:28] <Laney> thx!
[15:28]  * Laney whips the release team
[15:39] <jbicha> seb128: could you remove mozjs60 too if you didn't already?
[15:39] <jbicha> on s390x
[15:40] <seb128> what's the rational?
[15:40] <jbicha> the same reason. mozjs60 fails so many tests on s390x that we don't think mozjs60 runs on that arch. It's the reason we're removing gjs/s390x
[15:41] <jbicha> Debian bug 909536
[15:43] <jbicha> it's blocking mozjs60 60.2.1-1 in -proposed since the earlier upload ignored those test failures
[15:48] <seb128> k
[15:49] <Laney> there's a new iso btw
[15:49] <seb128> oh, nice, thanks Laney!
[15:49] <Laney> in case virtualbox friends want to test virtualbox things
[15:49] <seb128> jibel might
[15:49] <didrocks> Trevinho: is there anyway to tell G-S to reload remotely?
[15:52] <seb128> jbicha, done
[15:52] <jibel> Laney, what's new in this image?
[15:53] <Laney>  xorg that is supposed to fix the things
[15:54] <jibel> k
[15:54] <jibel> i'll try it
[15:55] <Laney> 😚
[15:57] <didrocks> Trevinho: it seems that one idea would be to run on the eval dbus call: eval("Meta.restart(_('Restarting…'))")
[15:57] <willcooke> Trevinho, thanks for looking at that u/s gdm issue
[15:57] <willcooke> Laney, I'll download and try
[15:57] <didrocks> (need to check for wayland compositor first though)
[16:15] <willcooke> jibel, Laney: First attempt, corrupted display, switching tty and back fixed it.  Attempt #2: I get a log in prompt.
[16:15] <willcooke> a gdm prompt I should say
[16:16] <willcooke> it's better, but not sure if it's quite right yet
[16:16] <willcooke> attempt 3, gdm again
[16:16] <willcooke> oh
[16:16] <willcooke> ignore #2 and #3
[16:16] <willcooke> the ISO had popped out
[16:17] <Laney> you should probably tell tjaalton and/or Trevinho
[16:17] <willcooke> Laney, ack
[16:18] <Laney> :>
[16:19] <willcooke> tjaalton, https://imgur.com/a/oxOHdyu
[16:19] <willcooke> jibel, Trevinho ^
[16:28] <willcooke> FWIW, nomodeset still fixes it
[17:16] <Trevinho> mhmhmh
[18:35] <willcooke> Hm, new ISO Ubiquity seems very crashy
[18:36] <willcooke> Suddenly seeing this: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1676647
[18:38] <sarnold> Found label 'Ubuntu-Studio 17.04 _Zesty Zapus_ - Beta amd64 (20170321)'
[18:39] <willcooke> thats the bug it told me had already been reported, I dont believe it any more :)
[18:39] <willcooke> this is a network manager / Ubiquity thing
[18:39] <sarnold> yeah :) I'm willing to say you found a new one :) hehe
[18:39] <willcooke> :D
[18:44] <xnox> a zapus appears in your path
[18:46] <willcooke> New bug for tomorrow
[18:46] <willcooke> Bug #1795955
[18:49] <tjaalton> willcooke: restart virtualbox.. helped on windows. i had the same with bionic guest
[18:49] <sarnold> I love how systemd shoves its inane chatter in the middle of the kernel inspecting ACPI tables.. somehow I doubt it's started CUPS before node 0 is brought up..
[18:51] <sarnold> is this syslog like seven or eight boots that happened all at the same "time" and thus have had their log entries intermixed?
[18:51] <willcooke> tjaalton, testing
[18:52] <willcooke> sarnold, it's a live session if that makes any difference
[18:53] <willcooke> tjaalton, oh, are you talking about the corrupted graphics, or this ubiquity thing?
[18:56] <willcooke> I restarted virtual box and the graphics corruption is still there.
[18:57] <willcooke> The ubiquiuty issue is on real hardware
[18:57] <tjaalton> willcooke: corruption
[18:59] <Laney> willcooke: Oct  3 18:38:06 ubuntu NetworkManager[1076]: malloc(): corrupted unsorted chunks 3
[18:59] <Laney> that's probably the same ol NM bug
[18:59] <Laney> goodnight!
[19:03] <willcooke> hi Laney, bye Laney
[19:03] <willcooke> tjaalton, yeah, didnt help
[19:04] <willcooke> imma try and reboot
[19:11] <willcooke> same
[19:11] <willcooke> right, I give up for tonigth
[19:11] <willcooke> try again tomorrow
[19:11] <willcooke> night all
[21:48] <jbicha> seb128: don't work too late, but if you're around, I see that the Trello 1904-cycle card doesn't look like it's under the Ubuntu Desktop team