[00:06] robert_ancell: yes, I'll do that [00:07] robert_ancell: can you please add a Trello card for me? I'm afk right now === cpaelzer__ is now known as cpaelzer [06:05] good morning [06:08] Hi didrocks [06:09] hey duflu [06:59] good morning desktoppers [07:00] Hi oSoMoN === pstolowski|afk is now known as pstolowski [07:10] hi duflu [07:11] hey again desktopers [07:13] Hi seb128 [07:14] hey oSoMoN, seb128 [07:15] hey duflu didrocks oSoMoN [07:16] salut didrocks, seb128 [07:16] Morning o/ [07:16] morning Wimpress [07:19] Morning Wimpress [07:21] hey Wimpress [07:26] hey Wimpress [07:40] good morning! [07:40] hey marcustomlinson [07:41] morning marcustomlinson [07:41] hey didrocks and oSoMoN, how are you? [07:41] I'm ok, thanks, yourself? [07:42] yeah pretty good [07:42] Hi there marcustomlinson [07:42] hey duflu [07:42] hey marcustomlinson [07:43] how goes it seb128 and duflu? [07:43] good, I need to try to stop being distracted by bugs triaging and wanting to SRU more fixes to the LTS though :) [07:43] marcustomlinson, tired and aching. I am assuming that's temporary. You, marcustomlinson? [07:43] I saw an evince bugs about annotations and now I'm going over the topic and triaging issues downstream and upstream :p [07:44] duflu: that sucks... I jut recovered from a sore back recently, was torture [07:45] So sad though, I hurt it... getting up from my chair wrong... 🤦🏻‍♂️ [07:46] 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] seb128: sounds like you need a long weekend to reboot ;) [07:47] :) [07:49] 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] seb128, thanks! I'll try the mail-list! [07:50] np! [07:50] moin [07:50] morning willcooke [07:50] how goes marcustomlinson [07:50] ?> [07:50] good thanks! Yourself? [07:51] Not too bad thanks [07:52] hey willcooke [07:52] hi didrocks [07:53] hey willcooke [07:54] morning oSoMoN [07:54] duflu, thanks for pitching in on: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1831514 [07:54] Launchpad bug 1798790 in gdm3 (Ubuntu Eoan) "duplicate for #1831514 Ubuntu login screen never appears when using the Nvidia driver (and setting WaylandEnable=false fixes it)" [High,In progress] [07:54] is there something we should rollback to stop people hitting that, or is it fairly low impact? [07:55] I know Laney is working on the fix upstream, but is there something worth doing in the meantime? [07:55] willcooke, I've been handholding that bug for a long time now. The workaround listed in the title is my only suggestion [07:56] Morning willcooke [07:56] afternoon :) [07:56] I would assume it's not blowing up for everyone with an nv card, or we would have heard more about it [07:57] 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] got it, thanks duflu [07:57] willcooke, I think Laney said a "race"? If so then it would come and go [07:57] ahhh, that sounds likely [07:59] 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] So more in reality [07:59] I got pinged by someone last night who was affected when the latest g-s and g-s-c landed. [08:01] they had to hold back the packages or get black screen [08:02] 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] 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] peace [08:04] Hi Laney [08:04] it's to do with how long the wayland attempt takes to fail, yes [08:04] hey duflu [08:06] morning Laney [08:12] morning Laney [08:12] moin didrocks oSoMoN, how's it going? [08:13] night was short so feeling a bit tired, but good otherwise [08:13] :( [08:13] hope nothing too bad [08:15] hey Laney [08:16] 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] that report the reported said he has constant failure to login, post reboots and post reinstall [08:16] it seems different from the race to me [08:17] morning Laney [08:17] 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] we should at least get a journal log [08:18] Yes, that might help. Otherwise just treat it as a separate bug after the big one is fixed [08:19] 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] Laney, nah, just went to bed late and got up too early, that's it, no sick kids or anything like that [08:19] But there's no evidence yet that it's wrong [08:20] duflu, I'm concerned that we overlook a regression but flagging it as "it's is old issue" [08:20] but oh well [08:20] we have 3 reported regresssions for sure which are new segfault/errors, so maybe that's just one of those [08:20] the SRU is blocked meanwhile [08:21] seb128, OK no problem. If they are assigned to gdm3 and tagged 'nvidia' they also won't get lost. === ecloud is now known as ecloud_wfh [08:32] 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] that's low priority and "free to grab" for those who want to do some of them (I will pick a few) [08:33] just pinging you as a FYI, help is welcome but I'm not assigning/forcing those on anyone [08:33] thx [08:33] ack [08:36] Laney: I'm ok (in meeting, sorry). Seems the zfs list made it to phoronix again [08:37] you celebrity [08:38] positive echo there? [08:40] they found the todo board on github and wrote a bit around that [08:41] * Laney goes to figure out charm relations [08:42] now you can deploy the cloud worker, and it sets up some of the units [08:42] needs to connect to rabbitmq now [08:48] * seb128 changing location, brb [11:59] 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] seb128: that was ~ppa1, correct? ~ppa2 passed [12:04] (and is the one corresponding to the NEW queue) [12:04] didrocks, https://launchpadlibrarian.net/426755593/buildlog_ubuntu-eoan-amd64.grubzfs-testsuite_0.1~ppa1_BUILDING.txt.gz [12:04] so yes [12:05] seb128: yeah, already handled, but thanks for the ping :) [12:05] yw === cpaelzer__ is now known as cpaelzer [13:52] I have prepared a debdiff for the Bionic SRU for bug 1763520, could someone sponsor the upload? Thanks. [13:52] bug 1763520 in gtk+3.0 (Ubuntu Bionic) "after upgrade to bionic, printing fails without explanation / logs / debuggability" [High,In progress] https://launchpad.net/bugs/1763520 [14:00] tkamppeter, you should subscribe ubuntu-sponsors [14:01] (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] 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] tkamppeter, as said it's fine to ask here, but best to also subscribe sponsors [14:09] some of us do use the sponsoring queue as a reminder as well [14:10] OK. [14:12] mvo: seb128: bionic currently uses core (and snapd from within), is it ready to switch to core18+snapd snaps? [14:15] xnox: yes, with 2.39 we should be good to move to the snapd snap [14:26] 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] 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] didrocks: it's a git-dpm branch [14:26] not gbp [14:26] ah, that explains [14:26] yup :) [14:27] cyphermox: ok, thx! I will refresh with this :) [14:27] 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] nice! I'll see how to refresh/add patches. I hope the mapages are good enough :) [14:27] 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] oh boy [14:28] no, they aren't great tbh [14:28] cyphermox: jibel and I are adding zfs linux support [14:28] spoiler alert on doc quality :) [14:28] so, this shouldn't impact too much your merge [14:28] isn't there already some zfs support in grub? [14:28] cyphermox: not really for multi-systems, also no snapshot/clone supports and so on [14:29] ok [14:29] well, in short: [14:30] git-dpm checkout-patched; ; git add ; git commit ; git-dpm update-patches [14:30] if you need to modify patches, or put it somewhere other than the end; you can 'git rebase -i upstream' [14:30] cyphermox: wonderful, that will help. Thanks again :) [14:31] you really shouldn't change any patch unless you're in 'git-dpm checkout-patched' (a branch starting with patched-) [14:31] that is, if you care about committing and merging without a universe of conflicts [14:31] got it. Will take care of this [14:31] 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] cyphermox: sure [14:33] 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] yeah, a little bit like gbp pq with the additional branch, so not that different :) [14:52] 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:52] bug 1820259 in update-notifier (Ubuntu Bionic) "[FFe] Add a indicator to show the status of Livepatch" [Undecided,Fix committed] https://launchpad.net/bugs/1820259 [14:53] yes sure, is tomorrow ok though? [14:54] Laney, yes, no problem [14:54] thx! [14:55] basically for me: if you install it on a clean system and don't set up livepatch, do you get no indicator? [14:55] same for if you turn it on and then later disable [14:58] yes and yes [14:58] it hides as soon as the service is disabled [14:58] can double check though ;-) [14:59] 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] seb128, I've just this moment installed a fresh 18.04 on my test laptop for this :) [14:59] willcooke, woot, thx [15:27] seb128, Laney done. All looks good to me now [15:27] Bug updated [15:27] The UX is good now, I like [16:03] willcooke, thx for testing! === pstolowski is now known as pstolowski|afk [17:25] night all [18:45] good night