[09:05] <dgadomski> hey cyphermox, do you know if fix for bug #1749289 is going to be backported to xenial?
[09:48] <xnox> dgadomski, the verification you did of the bionic image, would appear to be incomplete for me.
[09:49] <xnox> dgadomski, before choosing to reboot the second time, did you enable proposed and upgrade all packages from proposed?
[09:49] <xnox> dgadomski, cause the new ubiquity with fixes is only in bionic-proposed, and not bionic-updates yet
[09:49] <dgadomski> xnox: nope, oem configuration seemed not to work at all for me for bionic (unlike xenial)
[09:49] <dgadomski> I've reported a separate bug about it
[09:49] <xnox> dgadomski, with alternate installer, you should be booting with apt-setup/proposed=true kernel cmdline option
[09:50] <xnox> dgadomski, i am talking about the separate bug you filed
[09:50] <xnox> dgadomski, can you please attach all of /var/log/installer logs from the https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1789920 case?
[09:51] <dgadomski> xnox: ack, will try that
[09:54] <xnox> dgadomski, https://wiki.ubuntu.com/Testing/EnableProposed#line-95 same applies to alternate installer
[11:39] <didrocks> bdmurray: hey! So my theory for the apport regression is in https://code.launchpad.net/~didrocks/apport/handle-older-reports/+merge/354692. If you +1 on it, I'll upload to cosmic and reupload a bionic version
[12:54] <rbasak> tsimonq2: why did you sync mysql-5.7?
[12:55] <rbasak> tsimonq2: AFAICT it's now stuck due to https://bugs.launchpad.net/ubuntu/+source/mecab/+bug/1781529
[13:04] <psusi> pitti: gnome-disks is failing to unmount for me.  It seems it has a race condition where it issues the unmount command to udisks, then looks to see if there are still any mount points left and tries to unmount them.  The property hasn't updated yet so it tries to unmount the same location a second time, which fails.
[13:04] <psusi> pitti: is there a proper dbus way if you expect a property to change, to make sure you wait for it to do so?
[13:18] <psusi> hrm... I found udisks_client_settle(), but it didn't seem to help...
[14:02] <michael-vb> Hello there.  I have been seeing a minor quirk in the 18.04 dash/dock, where the icon for VirtualBox is not shown correctly until the screen locks and unlocks.  VirtualBox is an X11 application and I am running a Wayland session.  Who should I poke?
[14:51] <cpaelzer> cjwatson: hi, since you do 99+% of openssh changes I wanted to ask if bug 1790963 is on your radar?
[14:54] <cjwatson> cpaelzer: not really.  maybe it should be taken upstream
[14:54] <cpaelzer> only affecting RSA certs I'm not even sure enough to triage the severity
[14:54] <cpaelzer> cjwatson: I had the impression that "Scott Emmons" that updated the bug might be upstream - is that a name known to you?
[14:55] <cjwatson> this sounds churlish, but I'm afraid I find Ubuntu openssh bugs increasingly hard to follow since there's always a support firewall that gets there before me
[14:55] <cjwatson> not AFAIK; don't know where you got that idea
[14:55] <cpaelzer> misinterpretation in between his lines :-)
[14:56] <cjwatson> since it's affecting other distributions, I think it'll probably just be a matter of cherry-picking an upstream fix eventually
[14:58] <cjwatson> hm, though on reading more it sounds like we need to backport a correction to the server-advertised key types list?
[15:00] <cjwatson> have you checked whether the people reporting this have modified PubkeyAcceptedKeyTypes/HostbasedAcceptedKeyTypes in their sshd_config?
[15:01] <cjwatson> or indeed in the ssh client config
[15:01] <cpaelzer> cjwatson: no I have not
[15:01] <cjwatson> worth checking both ends
[15:02] <cpaelzer> I just have seen a few updates on the bug and desperately tried to reach someone with more experience on the matter => you :-)
[15:03] <cpaelzer> I could tomorrow try a debian/ubuntu container test with differen setups to confirm the issue for us
[15:03] <cpaelzer> since Debian is on 7.8 already that should be easy
[15:13] <tsimonq2> rbasak: Ah, sorry :/ want me to revert the dep?
[15:15] <rbasak> tsimonq2: yes please. I don't think the MIR will land any time soon. The security team have a rather large backlog of MIR reviews I believe, and mecab isn't a high priority.
[15:17] <tsimonq2> rbasak: ack, will do this afternoon US time.
[15:17] <rbasak> Thanks!
[15:17] <tsimonq2> Thanks for letting me know.
[15:38] <Skuggen> tsimonq2: I'll prepare an upload for it once we've finalized a fix for #1791010
[15:38] <Skuggen> 5.7, I mean
[16:14] <tsimonq2> Skuggen: ack, I'll be happy to sponsor if you can't upload.
[16:15] <Skuggen> Great, thanks!
[16:16] <Skuggen> I've started making a ppu application, but need some sponsors for that too :P
[19:06] <slangasek> kees, stgraber: TB meeting?