[01:44] I guess my laptop had a brief moment where it broke the laws of physics and what today's radio could do by having a brief moment where it exceeded 5Gbps. === cpaelzer_ is now known as cpaelzer [06:50] good morning desktoppers [06:52] Morning oSoMoN [06:56] hey duflu === pstolowski|afk is now known as pstolowski [07:19] good morning [07:28] salut didrocks [07:28] hey oSoMoN [07:39] lut didrocks oSoMoN [07:39] hey duflu [07:39] how are you today? [07:40] Hi seb128. Going well. You? [07:40] salut seb128 [07:40] duflu, I'm good! [07:41] could have slept a bit longer, 6:30am :/ [07:41] That's not great [07:41] well at least I had emails/backlog done and baby ready to go by 8am [07:42] hey seb128 [07:42] lut didrocks [07:51] morning all 0/ [07:52] hey clobrano! :) [07:53] feeling better? No secondary effect from your back surgery? [07:54] hey didrocks, still full of painkillers :D but I should be fine [07:54] sounds like everything went fine, great! [07:55] morning [07:58] Morning willcooke [07:58] :) [07:58] Morning Class7 [07:58] Argh [07:58] Morning clobrano [07:58] hi duflu [08:03] greetings [08:05] hey willcooke, Laney [08:06] clobrano: on my question for the MP, master will release a snap for bionic, so it will end up in bionic as well [08:06] clobrano: but is this variable read by the bionic version of the dock? [08:07] damn it, I can't find an actual bug number for the virtualbox issue. Anyone got any clues? (tjaalton perhaps?) [08:08] hey willcooke, Laney, how is your side of the channel today? [08:08] hey seb128, quite sunny today \o/ [08:08] The omnipresent grey clouds of Brexit are on the horizon though [08:08] oh, I made myself sad. [08:09] willcooke: bug 1796056 [08:09] bug 1796056 in xorg-server (Ubuntu) "Xorg crashed with SIGABRT in glamor_egl_init()" [Medium,Confirmed] https://launchpad.net/bugs/1796056 [08:09] which I can't repro anymore [08:09] tjaalton, ah, I found that one, but I didnt think it was the right thing. Since, yeah, it doesnt crash now , but the display is all messed up still [08:09] should I log a new bug for that one? [08:10] bug #1792932 was the previous week one [08:10] bug 1792932 in xorg-server (Ubuntu Cosmic) "Cosmic Desktop fails to boot in vbox: Xorg assert failure: Xorg: ../../../../dix/privates.c:384: dixRegisterPrivateKey: Assertion `!global_keys[type].created' failed." [High,Fix released] https://launchpad.net/bugs/1792932 [08:10] willcooke: install updates and check again [08:10] with latest kernel vboxvideo.ko is loaded before X is starte [08:10] d [08:12] hey didrocks seb128 [08:13] tjaalton, do you know what changed? is that a fix or luck? [08:13] tjaalton, well this is for the live cd - so I should try with a new ISO right? The one I tried from yesterday morning was still b0rked [08:14] seb128: I don't, dozens of updates via 4.18.x [08:15] willcooke: ok, so it's not the same then, I was testing with an installed system which this bug was about (regression of the xserver update) [08:15] didrocks: that's correct, unfortunately. I am not aware of any way to limit the scope of the variable to a specific dock version [08:15] tjaalton, ok, I will log a new one [08:15] thanks [08:16] the pending ISO works for me in vbox [08:18] clobrano: well, we already changed the panel as well, I don't think changing the dock color in bionic is a biggy, it will match as well the panel that way, wdyt? [08:19] Laney, super! Downloading and testing.... [08:21] didrocks: I agree. If we ship this in both, cosmic will have the same transparency for panel and dock, while in bionic the dock will be more transparent. Which is way better that having the dock darker like it is now in cosmic with master [08:23] clobrano: ok, let's do this then :) [08:23] didrocks: I'll update the PR title [08:23] thx! let me merge it then [08:24] Laney, you don't see this? https://imgur.com/a/rkTId4S [08:24] no [08:25] Laney, you're running vbox on Cosmic I assume? (I'm running it on Bionic) [08:25] clobrano: thanks a lot :) [08:25] that's correct [08:25] didrocks: yw [08:26] jibel, can you reproduce this on Bionic running virtualbox, installing cosmic in to a VM: https://imgur.com/a/rkTId4S [08:26] willcooke: is it 100% of the time for you? [08:26] Laney, yeah [08:26] still? [08:26] ho hum [08:26] let me try again [08:26] yeah, that's with the ISO from this morning [08:27] there's a kernel in *proposed*, dunno if that is what tjaalton was trying with [08:27] I installed on a bionic host with an older image from last week and had no such thing [08:27] tjaalton, did you say you were running Vbox from upstream? [08:27] though it did suffer from the old bug which also required nomodeset.. [08:28] no, stock distro [08:28] once the system is done upgrading I'll try with a current image [08:28] tjaalton, thx! [08:29] willcooke: go to the terminal and check 'dmesg|grep vboxvideo' [08:29] check the timestamp [08:29] compare to /var/log/Xorg.0.log [08:31] tjaalton, switching vts gets restores the screen to normal. Is that going to have messed the logs up? [08:32] no [08:33] xorg log: https://paste.ubuntu.com/p/kgYWct2QP2/ [08:33] dmesg: https://paste.ubuntu.com/p/fbXBC64yHz/ [08:33] [ 14.762240] vboxvideo: module is from the staging directory, the quality is unknown, you have been warned. [08:33] [ 14.762271] vboxvideo: module verification failed: signature and/or required key missing - tainting kernel [08:33] [ 14.774141] [drm] VRAM 01800000 [08:33] [ 14.789234] [TTM] Zone kernel: Available graphics memory: 743060 kiB [08:33] [ 14.789235] [TTM] Initializing pool allocator [08:33] [ 14.789238] [TTM] Initializing DMA pool allocator [08:33] [ 14.860361] fbcon: vboxdrmfb (fb0) is primary device [08:33] [ 14.860441] Console: switching to colour frame buffer device 100x37 [08:33] [ 14.860446] vboxvideo 0000:00:02.0: fb0: vboxdrmfb frame buffer device [08:33] [ 14.860458] [drm] Initialized vboxvideo 1.0.0 20130823 for 0000:00:02.0 on minor 0 [08:33] vs [08:33] [ 14.592] [08:34] X.Org X Server 1.20.1 [08:34] so unlucky :P [08:34] So looks like xorg is starting too soon again? [08:34] yep [08:34] could this have anything to do with Plymouth? [08:34] maybe [08:35] tjaalton, shall I log a new bug still? [08:35] yep [08:35] let's use that for discussing with foundations if there's something to be done [08:36] tjaalton, should I put it against xorg for now? [08:36] that's fine [08:36] thanks tjaalton [08:38] clobrano: hum, the snaprevs update failures is back for the last few days, I've reasked the snap store team about this: https://forum.snapcraft.io/t/snaprevs-update-failed/7106/11 [08:39] didrocks: yes, also mads was unable to test some changes for this [08:40] clobrano: actually, I think the snaps are still published, if you follow the pattern, you should get the correct channel [08:42] Trevinho, Laney, hey, is one of you working on getting the gnome-shell .1 update in cosmic? [08:45] * didrocks wonders if https://gitlab.gnome.org/GNOME/gdm/commit/a3904bf5f9e6fe6bc3bb2ad9c856cf1361b8194d is maybe related to the gdm issue I'm seeing [08:46] I don't use autologin, but this code is "on_start_user_session", which is when I start having issues [08:50] seb128: "is" no, it only came out last night. "will you?" yes [08:50] jbicha (and Laney), Since last year mozjs has been built with --disable-optimization because "Copy these build flags from Fedora". Any idea why? [08:50] I need to communicate in a way that comes accross better :/ [08:51] Laney, thx, that's what I meant to ask [08:51] Or rather "--disable-optimize" [08:51] Laney, I didn't look at timing of the tarballs, just got reminded because translations are borked in .0 and then I saw that .1 was on version ;) [08:52] good that it's on time for cosmic! [08:52] annoying that gitlab has the same hidden "patch view" feature than github, without any UI to access it [08:53] didrocks, I found it via the GUI [08:53] oh? [08:53] where is it, when you are on the commit view? [08:53] ohhhhhh [08:53] in options [08:53] options -> plain diff [08:53] would need to remember this [08:54] didrocks, I meant in a merge request -- the cloud icon [08:54] ah, but this is the .diff, not .patch [08:54] didrocks, cloud icon -> Email patches [08:54] ok, so "email patch" in options [08:54] Does not "Email" but "Makes email patches" [08:54] yeah, cloud icon -> weird choice for putting this here [08:54] duflu: I hoped that Fedora knew what they were doing, but now that you mention it, that sounds like a flag we don't need [08:54] didrocks, you can just add the .patch or .diff to the url no? [08:55] seb128: right, this is why I called it "hidden" :) [08:55] jbicha, I only found it because I noticed the debug info we publish doesn't work either. So will try building both alternatives [08:55] so basically, from the UI, options or cloud icons [08:55] thanks duflu [08:56] duflu: it's also not set at https://gitlab.gnome.org/GNOME/jhbuild/blob/master/modulesets/gnome-suites-core-deps-latest.modules#L1651-1655 [08:56] Well, maybe the tests fail. We shall see [08:58] seb128: np, I was concerned that you were nagging me about an update within 1 hour of beginning the next day after it came out but I shouldn't have been, sorry for coming across grumpy [08:58] np! [08:58] duflu: https://salsa.debian.org/mozilla-team/firefox/blob/release/master/debian/rules#L90-92 seems reasonable [08:59] what does that disable-optimize flag do? [08:59] didrocks: oh, ok [08:59] I can't tell yet. I was only looking for usable debug symbols [08:59] mozjs60 is clearly built with -O [09:00] and -g [09:00] duflu: I wonder what --disable-strip does [09:00] ok, trying again gdm, then with the patch, getting some debug logs and let's see [09:01] It is presently building with -O2 -O3 -fomit-frame-pointer with optimization enabled. [09:01] if I don't come back, it's because of the wormhole of this 100% CPU spinning [09:01] I should check the defaults again [09:02] it would certainly not be unheard of for -O3 to break stuff [09:05] lintian seems to be happy with optimization [09:05] Hmm [09:06] no luck with the autologin patch in master :/ [09:07] at least, I should have some debug logs now [09:10] jbicha, Laney, a quick test reveals: enable-optimize works but doesn't seem to offer measurable improvements. debug fails to run because: [09:10] Assertion failure: isDebugBuild, at /home/dan/src/mozjs60/mozjs60-60.2.3/js/src/vm/Initialization.cpp:74 [09:17] Ugh. That just means you can't have debug unless gjs is built the same way [09:22] didrocks: if you're wanting to do a last minute osinfo-db upload, I think we should finalize the 18.10 xml (remove prerelease & set the URLs) & create a 19.04 xml [09:23] we might need to distro-patch that since upstream seems to like test data for metadata changes like that but those iso's don't exist yet! [09:24] jbicha: I think we should focus on fixing the bug first [09:24] so, let's see teuf's review [09:24] then, we can see if we distro-patch or not [09:25] I was only commenting since you were talking about doing an upload :) [09:25] upstream is happy to cut a release once teuf has reviewed it [09:26] jbicha: yeah, I don't really care about the pre-release state or such. I'm mostly caring of being able to have VMs that can be installed :) [09:26] (and also my gdm issue, which is hard to pinpoint :p) [09:27] didrocks: btw, the Debian maintainer doesn't need a release tag to do his uploads, see comment 17 on Debian bug 908973 [09:27] Debian bug 908973 in src:osinfo-db "osinfo-db: New upstream release 201809020" [Wishlist,Fixed] http://bugs.debian.org/908973 [09:27] jbicha: right, but upstream wants to cut a release for us, I won't prevent them from doing it :) [09:27] when pre-release is set, 18.10 won't show up in the Download an OS feature in GNOME Boxes [09:27] it doesn't care whether the date is future! [09:27] I never had that feature working btw [09:28] it should work in 18.10 [09:28] it downloads to ~/Downloads/ [09:31] * didrocks tries with another gdm revert [09:35] nope :/ [09:36] didrocks, git bisect? ;) [09:36] seb128: that's basically what I'm doing, but not every commits builds… [09:36] issue with not having a mainline [09:37] I'm unsure what's happening, but a side effect is already ureadahead going crazy [09:37] like printing [09:37] oct. 09 11:33:12 casanier ureadahead[320]: ureadahead:: Chemin relatif ignoré [09:37] oct. 09 11:33:12 casanier ureadahead[320]: ureadahead:sys: Chemin relatif ignoré [09:37] oct. 09 11:33:12 casanier ureadahead[320]: ureadahead:class: Chemin relatif ignoré [09:37] oct. 09 11:33:12 casanier ureadahead[320]: ureadahead:dmi: Chemin relatif ignoré [09:37] in loop [09:37] (tried on multiple boots, and only boots having the broken gdm triggers this) [09:42] willcooke: now I installed on a vbox, and after reboot gdm fails, no x log [09:42] needs to be restarted [09:44] just the first time though, probably raced against vboxvideo still [09:44] tjaalton, that could be a known issue, Do you get a flashing cursor and no gdm? [09:45] yep [09:45] tjaalton, could it be this? https://gitlab.gnome.org/GNOME/gdm/issues/428 [09:45] GNOME issue 428 in gdm "Ubuntu 18.10 boots to black screen with flashing cursor, no gdm. Switching to tty2 and back to 1 fixes it." [Opened] [09:45] it remained dead [09:49] is anyone planning g-c-c changes/fixes before cosmic now? [09:49] andyrock, ^ you maybe? [09:49] (trying to figure out if I need a no change rebuild for translations or wait for a legit upload) [09:50] I'm working on some g-c-c crashes right now [09:50] but that would take time [09:50] *could [09:50] tjaalton, sounds like a different problem, I will try the daily on a physical machine [09:50] seb128: ^^^ [09:51] andyrock, k, let's see if you have something by tomorrow [09:51] if not I do a no change upload [09:51] kk [09:54] found the issue! [09:54] after an epic bisect on all complicated commits and so on… [09:55] the issue is "simply" triggered by https://gitlab.gnome.org/GNOME/gdm/commit/5cd78602d3d4c8355869151875fc317e8bcd5f08 [09:55] (I have a dual intel/nvidia card) [09:55] I wonder if anyone tries to blacklist his card if they get the same issue… [09:57] willcooke: adding vboxvideo to initrd should fix all races.. [09:57] seems to load here at 1.2s and not 6.5s [09:57] tjaalton, did you ask kernel/foundations if they want to do that? [09:57] no [09:57] why not? [09:57] if that's the suggested way out [09:57] just found out [09:58] I though we already circled around that a week ago during the meeting [09:58] you said the loading time was because the driver was missing from the initrd [09:58] it wasn't there before [09:58] in bionic [09:59] willcooke, I've your cosmic/pending iso video corruption happening on a xenial/virtualbox VM booting the iso [09:59] tjaalton, right, doesn't hurt to ask if they are wanting to consider adding it to it though, if you think that would be the right thing to do [10:00] tjaalton, there is still a bug on the xorg side though, but seems like that one is harder to get fixed? [10:00] yeah I'd say very little chance at least to get it fixed this week [10:01] willcooke, https://pasteboard.co/HHDoqeG.png [10:04] seb128: I don't remember, do we force Xorg for our gdm session? [10:04] we don't use WaylandEnable=false because this disables the wayland options for users [10:05] but I don't remember anymore if we did anything special for gdm [10:05] no [10:05] doing that would make gdm not list wayland sessions [10:05] ah, you said that [10:05] yep :) [10:05] no, we just use plain default wayland [10:05] I wonder if we added anything else [10:06] ok [10:06] no [10:06] would be great if someone can try to blacklist their card [10:06] and see if the issue is only nvidia or as soon as you blacklist a card [10:06] tjaalton, willcooke, I replied to that email asking for the initrd/vboxvideo [10:07] didrocks, how do you blacklist a card? [10:07] I'm in middle of reviewing a stack of translations settings in launchpad but I can try to have a go later [10:08] seb128: modify /lib/udev/rules.d/61-gdm.rules and add something like DRIVER=="", RUN+="/usr/lib/gdm3/gdm-disable-wayland" [10:08] didrocks, is that gdm-disable-wayland command working on an already loaded greeter? would going to a vt and doing that by hand trigger the bug? [10:09] seb128: I'm unsure how this is ran, by gdm for sure, but as a subprocess it seems? [10:09] meanwhile, I'm updating the bug and will ping Jonas [10:09] looks like an udev rule no? [10:09] it writes a configuration to /run [10:09] with WaylandEnable=false [10:10] ah, so you mean, if I set WaylandEnable=false, I should trigger the same issue? [10:10] worth trying [10:10] yep [10:10] let me attach my logs first to the bugs [10:10] so that I don't loose them [10:10] seb128: yep [10:10] I wonder if it's not related to the ICC profile [10:11] I'm on nvidia btw, that udev rule fires for me properly [10:11] shrug, if I know who enabled that launchpad translations setting for all projects :/ [10:11] taking hours to review the stack :( [10:12] seb128: :( [10:12] :/ [10:12] thanks seb128 [10:12] no API? [10:13] Laney: do you use an ICC profile? [10:13] not knowingly [10:13] yeah, I bet something like "fallback to Xorg -> ICC profile loaded -> can't load it because on user's home" [10:13] ricotz, for the firefox-next xenial build failures, I think you'll need to patch python/mozbuild/mozbuild/action/check_binary.py to remove the checks on libstdc++, like https://bazaar.launchpad.net/~mozillateam/firefox/firefox-beta.trusty/revision/1243 [10:13] but the whole is world readable though [10:13] didrocks, could be, but I start by checking manually if the imports where outdated or not which is manual work [10:13] (as the directory) [10:13] seb128: :( [10:14] seb128: btw, could you import the polari .pot now? I reverted gnome-recipes to not use langpacks for now since its .pot generation is broken [10:14] I don't think we're going to end up doing gnome-contacts 3.30 this cycle [10:15] jbicha, done [10:15] it's late to be changing icon names [10:15] you could revert that part in the packaging [10:15] I mean it's probably late for a serie update [10:15] but the icon issue is easy to workaround [10:15] ok, trying with WaylandEnable=False [10:15] ricotz, have you tried backporting nodejs 8.11 to trusty and encountered issues, or is it just that you haven't tried yet? [10:21] WaylandEnable=false triggers it as well, so it's really my machine + Xorg for gdm [10:21] disabling the color profile hasn't done anything though [10:21] oSoMoN, I haven't tried yet, but I am currently looking at its builddeps [10:25] this is going to pull in a lot of build deps that aren't in trusty :/ [10:26] jbicha, grilo-plugins has no translations in launchpad/doesn't use dh_translations, can you fix it in Debian so we can sync the update? [10:27] didrocks, :( [10:27] didrocks, at least it removes the question of racy behaviour [10:27] if it's in the static config it's not the dynamic change [10:27] * duflu attempts to cook Indian [10:27] seb128: right [10:27] seb128: quite blocked now though, let's see on #gdm [10:27] right [10:28] seb128: grilo-plugins is split in Ubuntu because of main/universe issues [10:28] jbicha, ah right, well if you still want to look at fixing it/not having that delta... ;) [10:28] I can have a look later otherwise, still going through those components, that's tedious :/ [10:29] it was a bit difficult to explain to the Debian maintainer the justification for the split [10:30] seb128: hey... So yeah, once we've a final review. Also I wanted to backport the fixed for the me leak to bionic... I started this way yesterday, then... The other Issues come up. [10:30] hey Trevinho [10:31] Trevinho, cosmic is a priority over bionic for the next week, please focus full energy on cosmic [10:31] bionic can come in a week when cosmic is frozen/ready to get out [10:32] seb128: found the problem for https://errors.ubuntu.com/problem/2c64a180c193cbafd37c76a0a6a4885e5322ba64 so you can get a proper upload \o/ [10:32] Ok. Fair enough. [10:32] andyrock, great! [10:32] Trevinho, thx [10:36] * andyrock is wondering if what we do today should go in today bullet list or in the one of next week [10:51] today = next week [10:52] we wrap the summaries on monday evening [10:52] so it's tuesday to monday activity [10:58] k, on that note, lunch! [11:03] didrocks: any clue why we're still hitting https://errors.ubuntu.com/problem/1d505b2589761bfc2d44875a226ee3d3623abd3c === pstolowski is now known as pstolowski|lunch [11:49] Trevinho: can you check gnome-shell from lp git pls? [11:49] search cancellation stuff needed some updating, want to know it's ok [11:59] Laney: ok, after lunch [12:00] grazie [12:06] andyrock, was moving https://trello.com/c/OZkeMW3b/181-cancelling-snapd-authorization-triggers-error-notification to the proposed column an error and you meant done? [12:07] seb128: it's done [12:07] robert updated it [12:07] *uploaded [12:07] ah yeah [12:07] yes done! [12:07] fixed [12:07] andyrock, right, I just got an email "Andrea Azzarone moved the card Cancelling snapd authorization triggers error notification to Proposed on Ubuntu Desktop 18.10 cycle" [12:07] thx [12:08] :) [12:08] seb128: so I got a fix for https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1796872 [12:08] Ubuntu bug 1796872 in gnome-control-center (Ubuntu) "/usr/bin/gnome-control-center:11:g_type_check_instance_cast:whoopsie_properties_changed:ffi_call_unix64:ffi_call:g_cclosure_marshal_generic" [High,In progress] [12:08] this is ubuntu specific [12:08] I'm preparing a MR againts our git [12:08] +1 [12:08] let me know when you have it ready, I'm happy to sponsor [12:08] it should be quite small [12:12] andyrock, the ibus fix you did in master applies to stable? should we cherry pick it? [12:12] I think we can wait until 3.30.1 is released [12:13] *3.30.2 [12:13] I think we should cherry-pick the one in errors.ubuntu.com [12:14] k, wfm [12:14] seb128: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1796855 and the one i'm doing now [12:14] Ubuntu bug 1796855 in gnome-control-center (Ubuntu) "/usr/bin/gnome-control-center:double free or corruption (fasttop)" [High,In progress] [12:15] it's different from the one you just mentioned a few minutes ago right? === pstolowski|lunch is now known as pstolowski [12:28] yep, 1796855 applies upstream, 1796872 it's just in ubuntu [12:28] seb128: do you want me to proper an upload or just a MP for 1796872 [12:28] *preper [12:29] *prepare :) [12:29] 1796855 is easy to reproduce, 1796872 is not that likely to happen [12:30] andyrock, well, let's batch the fixes you get today and do an upload later/tomorrow? [12:40] seb128: kk === hyperair is now known as Guest50288 [13:10] seb128: https://code.launchpad.net/~azzar1/ubuntu/+source/gnome-control-center/+git/gnome-control-center/+merge/356324 [13:10] this is just for one crash [13:11] k [13:19] Trevinho: https://gitlab.gnome.org/GNOME/gnome-shell/commit/b719744e75e56502cf0340066f9311fdcc755628 [13:19] Trevinho: sorry, didn't see your ping. I'm unsure, is the SRU completely deployed? [13:19] this could also be related to the "--replace" issue [13:19] this has just been commited [13:20] Trevinho: look at the package version, there is very few reports with latest version (which is weird as well) [13:30] hey there, meeting time but not quite, willcooke"s machine has just frozen and he's trying to reboot [13:30] we wait a few min for him and start without him if reboot fails [13:31] * didrocks wonders if I should try the gdm patch meanwhile :) [13:32] haha [13:33] wb willcooke! [13:34] hey! [13:34] sorry everyone [13:34] bear with me [13:34] * didrocks is bearing :p [13:34] #startmeeting Desktop Team Weekly Meeting - 2018-10-09 [13:34] Meeting started Tue Oct 9 13:34:58 2018 UTC. The chair is willcooke. Information about MeetBot at http://wiki.ubuntu.com/meetingology. [13:34] 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/3VYBPFaR/ubuntu-desktop-1810-cycle | Amaterasu watches over you benevolently | Desktop Team Weekly Meeting - 2018-10-09 | Current topic: [13:35] Roll call: andyrock, dgadomski, didrocks, duflu (out), jbicha, jamesh (out), jibel, heber, kenvandine (hols), laney, oSoMoN, seb128, tkamppeter, trevinho, robert_ancell (out), tjaalton, tseliot [13:35] hey o/ [13:36] hey ho [13:36] o/ [13:36] oh, Till is out too [13:36] o/ [13:36] o/ [13:36] While we wait for everyone to arrive, some notes... [13:36] o/ [13:37] If you have things to raise, they should have been in your meeting notes. If you forgot, or find something to talk about now, if it can wait to after the meeting, please do that, otherwise there will be AOB at the end [13:37] Second thing - release is just over a week away - so naturally Cosmic is the focus. We still have quite a few issues getting it to boot and start correctly. [13:38] I'm going to skip Bionic again this week so we focus only on Cosmic [13:38] Please have a look through the notes and if you can help with sponsoring or reviews, please dive in [13:38] Notes are here: https://discourse.ubuntu.com/t/monday-8th-october-2018/8221/5 [13:39] ok, so I don't see anything in the notes for people with questions, so lets get stuck in to rls bugs [13:39] 1st up is: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1796822 [13:39] Ubuntu bug 1796822 in xorg-server (Ubuntu) "Desktop live cd boots corrupted screen in Virtualbox on Bionic" [Critical,Confirmed] [13:40] This is where you get a messed up screen when booting on Virtualbox. [13:40] We have threads open with tjaalton and foundations about this one, and I think it's a release blocker [13:40] so I vote to accept it, but then it's not really in our team to fix it. [13:41] I'm talking to the right people, so I think its under control [13:41] https://bugs.launchpad.net/ubuntu/+source/cups-pk-helper/+bug/1290533 [13:41] Ubuntu bug 1290533 in cups-pk-helper (Ubuntu) "cups-pk-helper-mechanism crashed with signal 5 in g_variant_new_va()" [High,Confirmed] [13:41]