[00:06] <kenvandine> robert_ancell: yes, I'll do that
[00:07] <kenvandine> robert_ancell: can you please add a Trello card for me?  I'm afk right now
[06:05] <didrocks> good morning
[06:08] <duflu> Hi didrocks
[06:09] <didrocks> hey duflu
[06:59] <oSoMoN> good morning desktoppers
[07:00] <duflu> Hi oSoMoN
[07:10] <oSoMoN> hi duflu
[07:11] <seb128> hey again desktopers
[07:13] <duflu> Hi seb128
[07:14] <didrocks> hey oSoMoN, seb128
[07:15] <seb128> hey duflu didrocks oSoMoN
[07:16] <oSoMoN> salut didrocks, seb128
[07:16] <Wimpress> Morning o/
[07:16] <oSoMoN> morning Wimpress
[07:19] <duflu> Morning Wimpress
[07:21] <didrocks> hey Wimpress
[07:26] <seb128> hey Wimpress
[07:40] <marcustomlinson> good morning!
[07:40] <didrocks> hey marcustomlinson
[07:41] <oSoMoN> morning marcustomlinson
[07:41] <marcustomlinson> hey didrocks and oSoMoN, how are you?
[07:41] <didrocks> I'm ok, thanks, yourself?
[07:42] <marcustomlinson> yeah pretty good
[07:42] <duflu> Hi there marcustomlinson
[07:42] <marcustomlinson> hey duflu
[07:42] <seb128> hey marcustomlinson
[07:43] <marcustomlinson> how goes it seb128 and duflu?
[07:43] <seb128> good, I need to try to stop being distracted by bugs triaging and wanting to SRU more fixes to the LTS though :)
[07:43] <duflu> marcustomlinson, tired and aching. I am assuming that's temporary. You, marcustomlinson?
[07:43] <seb128> I saw an evince bugs about annotations and now I'm going over the topic and triaging issues downstream and upstream :p
[07:44] <marcustomlinson> duflu: that sucks... I jut recovered from a sore back recently, was torture
[07:45] <marcustomlinson> So sad though, I hurt it... getting up from my chair wrong... 🤦🏻‍♂️
[07:46] <jerbob92> Hi! Due to recent problems with a Intel microcode update which broke booting completely, I'd like to suggest to add dis_ucode_ldr (disable loading of microcode) to boot options in recovery mode. Where should I add such suggestions?
[07:47] <marcustomlinson> seb128: sounds like you need a long weekend to reboot ;)
[07:47] <seb128> :)
[07:49] <seb128> jerbob92, hey, that's not rather a desktop topic, on IRC I would suggest #ubuntu-devel. You can file a wishlist on launchpad and for discussion I would recommend https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel
[07:50] <jerbob92> seb128, thanks! I'll try the mail-list!
[07:50] <seb128> np!
[07:50] <willcooke> moin
[07:50] <marcustomlinson> morning willcooke
[07:50] <willcooke> how goes marcustomlinson
[07:50] <willcooke> ?>
[07:50] <marcustomlinson> good thanks! Yourself?
[07:51] <willcooke> Not too bad thanks
[07:52] <didrocks> hey willcooke
[07:52] <willcooke> hi didrocks
[07:53] <oSoMoN> hey willcooke
[07:54] <willcooke> morning oSoMoN
[07:54] <willcooke> duflu, thanks for pitching in on:  https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1831514
[07:54] <willcooke> is there something we should rollback to stop people hitting that, or is it fairly low impact?
[07:55] <willcooke> I know Laney is working on the fix upstream, but is there something worth doing in the meantime?
[07:55] <duflu> willcooke, I've been handholding that bug for a long time now. The workaround listed in the title is my only suggestion
[07:56] <duflu> Morning willcooke
[07:56] <willcooke> afternoon :)
[07:56] <willcooke> I would assume it's not blowing up for everyone with an nv card, or we would have heard more about it
[07:57] <duflu> willcooke, it was not anything new so I would not worry about whatever caused one or two people to only see it recently. Many people have been seeing it for a long time
[07:57] <willcooke> got it, thanks duflu
[07:57] <duflu> willcooke, I think Laney said a "race"? If so then it would come and go
[07:57] <willcooke> ahhh, that sounds likely
[07:59] <duflu> I think I saw it once or twice last week, but otherwise I do not see it. Meanwhile there are 58 people "affected" by the bug
[07:59] <duflu> So more in reality
[07:59] <popey_> I got pinged by someone last night who was affected when the latest g-s and g-s-c landed.
[08:01] <popey_> they had to hold back the packages or get black screen
[08:02] <duflu> In that case it would be a side-effect. The new packages are not faulty, but some slowdown (or speedup?) somewhere could make the same old bug more easily reproducible
[08:02] <duflu> The only condition is that we ask all users to try the workaround. If the workaround doesn't help them then they need to log a separate bug
[08:03] <Laney> peace
[08:04] <duflu> Hi Laney
[08:04] <Laney> it's to do with how long the wayland attempt takes to fail, yes
[08:04] <Laney> hey duflu
[08:06] <didrocks> morning Laney
[08:12] <oSoMoN> morning Laney
[08:12] <Laney> moin didrocks oSoMoN, how's it going?
[08:13] <oSoMoN> night was short so feeling a bit tired, but good otherwise
[08:13] <Laney> :(
[08:13] <Laney> hope nothing too bad
[08:15] <seb128> hey Laney
[08:16] <seb128> duflu, there you are assuming that their issue is the same one, but I don't think that has been backed up by fact, from what we know it could also be that gnome-shell segfault for them (we had a few segfault regression reported)
[08:16] <seb128> that report the reported said he has constant failure to login, post reboots and post reinstall
[08:16] <seb128> it seems different from the race to me
[08:17] <marcustomlinson> morning Laney
[08:17] <duflu> seb128, there may be other causes of the Wayland probe crashing on Nvidia, but I am not sure it's helpful to assume that's more likely. I'm also not sure we get crash reports for that -- maybe gdm catches them
[08:18] <seb128> we should at least get a journal log
[08:18] <duflu> Yes, that might help. Otherwise just treat it as a separate bug after the big one is fixed
[08:19] <duflu> I think being wrong about a duplicate status is better organisation than never linking bugs at all. They are more likely to linger forever if not linked
[08:19] <oSoMoN> Laney, nah, just went to bed late and got up too early, that's it, no sick kids or anything like that
[08:19] <duflu> But there's no evidence yet that it's wrong
[08:20] <seb128> duflu, I'm concerned that we overlook a regression but flagging it as "it's is old issue"
[08:20] <seb128> but oh well
[08:20] <seb128> we have 3 reported regresssions for sure which are new segfault/errors, so maybe that's just one of those
[08:20] <seb128> the SRU is blocked meanwhile
[08:21] <duflu> seb128, OK no problem. If they are assigned to gdm3 and tagged 'nvidia' they also won't get lost.
[08:32] <seb128> Laney, oSoMoN, others, I've added https://trello.com/c/2aTq2RXr/167-gnome-stable-updates-srued-to-bionic to the june backlog where I listed some GNOME updates that look like that would be usefil to SRU to bionic
[08:33] <seb128> that's low priority and "free to grab" for those who want to do some of them (I will pick a few)
[08:33] <seb128> just pinging you as a FYI, help is welcome but I'm not assigning/forcing those on anyone
[08:33] <Laney> thx
[08:33] <oSoMoN> ack
[08:36] <didrocks> Laney: I'm ok (in meeting, sorry). Seems the zfs list made it to phoronix again
[08:37] <Laney> you celebrity
[08:38] <seb128> positive echo there?
[08:40] <Laney> they found the todo board on github and wrote a bit around that
[08:41]  * Laney goes to figure out charm relations
[08:42] <Laney> now you can deploy the cloud worker, and it sets up some of the units
[08:42] <Laney> needs to connect to rabbitmq now
[08:48]  * seb128 changing location, brb
[11:59] <seb128> didrocks, I guess you got the email, but in case not the desktop list moderation queue had emails about grubzfs-testsuite failing to build in the canary ppa
[12:04] <didrocks> seb128: that was ~ppa1, correct? ~ppa2 passed
[12:04] <didrocks> (and is the one corresponding to the NEW queue)
[12:04] <seb128> didrocks, https://launchpadlibrarian.net/426755593/buildlog_ubuntu-eoan-amd64.grubzfs-testsuite_0.1~ppa1_BUILDING.txt.gz
[12:04] <seb128> so yes
[12:05] <didrocks> seb128: yeah, already handled, but thanks for the ping :)
[12:05] <seb128> yw
[13:52] <tkamppeter> I have prepared a debdiff for the Bionic SRU for bug 1763520, could someone sponsor the upload? Thanks.
[14:00] <seb128> tkamppeter, you should subscribe ubuntu-sponsors
[14:01] <seb128> (it's fine to ask on the channel as well, I might have a look at some point if no-one else does it before)
[14:09] <tkamppeter> seb128, I have subscribed ubuntu-sponsors now, but I asked in the channel first in the hope to get it done with higher priority and not in the long line of non-Canonical contributors.
[14:09] <seb128> tkamppeter, as said it's fine to ask here, but best to also subscribe sponsors
[14:09] <seb128> some of us do use the sponsoring queue as a reminder as well
[14:10] <tkamppeter> OK.
[14:12] <xnox> mvo:  seb128: bionic currently uses core (and snapd from within), is it ready to switch to core18+snapd snaps?
[14:15] <mvo> xnox: yes, with 2.39 we should be good to move to the snapd snap
[14:26] <didrocks> cyphermox: hey, small question on the grub launchpad branch. I did branch ubuntu, upstream, pristine-tar. However gbp builpackage --git-ignore-branch (as I'm on the ubuntu branch) tells me "gbp:error: upstream/2.02+dfsg1 is not a valid treeish". And indeed, this tag doesn't exist, how do you build it?
[14:26] <didrocks> cyphermox: related to this, gbp pq rebase/import fails on the first patches with index errors. I wonder if there is something special when you work on those branches?
[14:26] <cyphermox> didrocks: it's a git-dpm branch
[14:26] <cyphermox> not gbp
[14:26] <didrocks> ah, that explains
[14:26] <cyphermox> yup :)
[14:27] <didrocks> cyphermox: ok, thx! I will refresh with this :)
[14:27] <cyphermox> so to build, you may need to run git-dpm prepare (if you don't already have downloaded the tarball before), and then you could just debuild I guess
[14:27] <didrocks> nice! I'll see how to refresh/add patches. I hope the mapages are good enough :)
[14:27] <cyphermox> didrocks: what are you trying to do? I have blocked time to do the grub merge and a few changes in SB now
[14:27] <cyphermox> oh boy
[14:28] <cyphermox> no, they aren't great tbh
[14:28] <didrocks> cyphermox: jibel and I are adding zfs linux support
[14:28] <didrocks> spoiler alert on doc quality :)
[14:28] <didrocks> so, this shouldn't impact too much your merge
[14:28] <cyphermox> isn't there already some zfs support in grub?
[14:28] <didrocks> cyphermox: not really for multi-systems, also no snapshot/clone supports and so on
[14:29] <cyphermox> ok
[14:29] <cyphermox> well, in short:
[14:30] <cyphermox> git-dpm checkout-patched; <do your changes>; git add <whatever you changed>; git commit <and add Patch-Name: below your description, see the other patches>; git-dpm update-patches
[14:30] <cyphermox> if you need to modify patches, or put it somewhere other than the end; you can 'git rebase -i upstream'
[14:30] <didrocks> cyphermox: wonderful, that will help. Thanks again :)
[14:31] <cyphermox> you really shouldn't change any patch unless you're in 'git-dpm checkout-patched' (a branch starting with patched-)
[14:31] <cyphermox> that is, if you care about committing and merging without a universe of conflicts
[14:31] <didrocks> got it. Will take care of this
[14:31] <cyphermox> if you run into trouble, I'm happy to do the git-dpm bits, just give me a patch and I'll figure it out ;)
[14:33] <didrocks> cyphermox: sure
[14:33] <cyphermox> essentially the end result is if you're in a patched- branch, then you have a nice git tree with everything being commits, first upstream code and then any debian/ubuntu changes
[14:33] <didrocks> yeah, a little bit like gbp pq with the additional branch, so not that different :)
[14:52] <seb128> willcooke, Laney, could you give another round of testing to update-notifier in bionic-proposed (and bug #1820259), I've updated it with a fix to hide the icon when livepatch is not in use, things seem to work fine form my testing but since you found issues in the previous round I would appreciate if you could poke again
[14:53] <Laney> yes sure, is tomorrow ok though?
[14:54] <seb128> Laney, yes, no problem
[14:54] <seb128> thx!
[14:55] <Laney> basically for me: if you install it on a clean system and don't set up livepatch, do you get no indicator?
[14:55] <Laney> same for if you turn it on and then later disable
[14:58] <seb128> yes and yes
[14:58] <seb128> it hides as soon as the service is disabled
[14:58] <Laney> can double check though ;-)
[14:59] <seb128> it probably doesn't require you guys to try it, but it doesn't hurt to have another look, you did find a problem in the previous round :)
[14:59] <willcooke> seb128, I've just this moment installed a fresh 18.04 on my test laptop for this :)
[14:59] <seb128> willcooke, woot, thx
[15:27] <willcooke> seb128, Laney done.  All looks good to me now
[15:27] <willcooke> Bug updated
[15:27] <willcooke> The UX is good now, I like
[16:03] <seb128> willcooke, thx for testing!
[17:25] <willcooke> night all
[18:45] <oSoMoN> good night