[04:48] <didrocks> good morning
[04:51] <jibel> salut didrocks
[04:52] <didrocks> salut jibel
[05:12] <duflu> Morning didrocks and jibel
[05:40] <didrocks> good morning duflu
[06:27] <oSoMoN> good morning desktoppers
[06:36] <duflu> Morning oSoMoN
[08:01] <marcustomlinson> morning all
[08:03] <Laney> yo de yo
[08:03] <didrocks> hey marcustomlinson, Laney
[08:03] <Trevinho> morning folks
[08:04] <didrocks> and a Trevinho
[08:04] <Trevinho> hi didrocks
[08:06] <Laney> hi Dan Rock and Mark Trevor
[08:07] <Trevinho> duflu: hey still here?
[08:07] <duflu> Morning marcustomlinson, Laney and Trevinho...
[08:07] <duflu> yes?
[08:08] <Laney> hello Dieter der Vogel
[08:09] <Trevinho> night duflu!
[08:09] <duflu> Trevinho, not yet. Only 4pm
[08:10] <Trevinho> So, as per the vmwgfx regression, as I was telling seb in one of my machine I was affected by that although not sure i did a bionic dist-upgrade, but more i upgraded to cosmic few days after release but and then to disco, but iirc this happened when switching to disco.
[08:11] <marcustomlinson> Who's Euan Lone talking to?
[08:11] <Trevinho> in that machine, what I've isn't anything crashing, more not showing things but the buffer per se is there.
[08:11] <Trevinho> so something lower level
[08:12] <Laney> yo Marcello Tonioli
[08:13] <Trevinho> duflu: as for https://gitlab.gnome.org/GNOME/mutter/merge_requests/613 I expect upstream prefers always to keep crashes around more than avoiding them, when the solution isn't the final one.
[08:13] <Trevinho> but if can replicate that?
[08:14] <duflu> Trevinho, I closed that and am working on an alternative. But I also explained why I disagree with crashing in this case
[08:14] <Trevinho> the only case I might think could be an issue is the case where a window isn't added to the window group actor (and thus not destroyed) or not deleted from the windows list when syncing the stack.
[08:14] <Trevinho> duflu: I know, but I expect that while we might use it as distro-patch I don't see that being accepted considering the upstream modus operandi
[08:15] <duflu> That's fine. It's not a critical issue and I will work toward whatever upstream prefer
[08:15] <Trevinho> for sure that foreach covers the case where windows aren't in the window group, and I should have done that before, so that's not wrong.
[08:16] <duflu> I agree it is correct. I was saying it's just not the only fix we should have
[08:16] <duflu> Trevinho, can you propose that fix too?
[08:16] <Trevinho> I also expect not to do much, in my tests I never got there with a populated list
[08:16] <Trevinho> k
[08:17] <duflu> Because yours might fix the root cause, but doesn't prevent regressions. Mine (and v2 of mine) also prevents regressions so we don't see it again.
[08:17] <duflu> We shall see how upstream feels about them
[08:17] <Trevinho> but I expect that in the sync case we're forgetting some window... Following the over-complicated logic, I can't find the issue easily, but maybe I'm missing the point where we remove the window from the list, but we never add it back to the windows list... nor destroy it (or that's not either destroyed ever)
[08:18]  * duflu nods
[08:18] <Laney> you should probably be talking in #gnome-shell ...
[08:18] <Trevinho> right :)
[08:33] <oSoMoN> Laney, didrocks: are you familiar with the image build infrastructure? I'm looking at bug #1832656, trying to understand why that build failed to contact the snap store while installing the updated chromium-browser
[08:34] <oSoMoN> I suppose the build environment has restricted network access
[08:34] <didrocks> oSoMoN: the image build has restricted network access, but can contact the snapstore
[08:35] <didrocks> I didn't look at the bug yet, but FYI, it happens that there are glimps sometimes and the image fail to build due to network issue on the snapstore
[08:35] <didrocks> (so, if it's a one time build failure, ignore it)
[08:35] <didrocks> ah, but you are doing this when installing the deb
[08:36] <didrocks> oSoMoN: did the previous build used the same deb: https://launchpad.net/~ubuntu-cdimage/+livefs/ubuntu/eoan/ubuntukylin/ ?
[08:36] <didrocks> (yesterday, there was a store/network outage during image build)
[08:36] <oSoMoN> didrocks, no, the previous successful build used the old deb that doesn't install the snap
[08:37] <didrocks> yeah, that's what I see
[08:37] <didrocks> so, the debs are installed in a chroot
[08:37] <didrocks> which copies resolv.conf and such
[08:37] <didrocks> I'm unsure though that it has all the settings for the snap store there
[08:37] <Laney> It'll be because of network access, indeed
[08:37] <didrocks> (like snapd isn't running for instance)
[08:38] <Laney> in livecd-rootfs we pass SNAPPY_STORE_NO_CDN for example, that's probably important in this area
[08:38] <didrocks> yeah, so this env variable is certainly not in the chroot ^
[08:38] <Laney> I would guess that this is reproducible if you make a pkg in a PPA that has Build-Depends: chromium-browser
[08:39] <oSoMoN> interesting, I'll test that
[08:39] <Laney> nice that you don't have to build the browser to iterate on fixes
[08:40] <Laney> did Stéphane avoid this for lxd by switching the seeds?
[08:40] <Laney> that might be more correct btw
[08:41] <oSoMoN> yeah, certainly, but it would be good to figure out the problem anyway
[08:41] <oSoMoN> I don'
[08:41] <Laney> it'll be hard to do the environment variable for only image builds
[08:41] <oSoMoN> I don't know what Stéphane did, will ask him
[08:46] <Laney> https://paste.ubuntu.com/p/PyKKVNpnPm/
[08:46] <Laney> can anyone explain this? :(
[08:46] <Laney> there clearly is a WantedBy there
[08:47] <didrocks> Laney: missing reload <unit>?
[08:48] <Laney> I tried a systemctl daemon-reload
[08:49] <didrocks> yeah, so not that…
[08:49] <Laney> /o\
[08:49] <Laney> bah
[08:49] <Laney> it's to do with that drop-in file
[08:50] <Laney> if I remove it, it works again
[08:56] <oSoMoN> Laney, your guess seems correct, a PPA build cannot contact the snap store: https://launchpad.net/~osomon/+archive/ubuntu/foobar-test-chromium-browser-builddepends/+build/16944565
[08:58] <Laney> oSoMoN: cool, so you can't really (easily) have such packages in build-depends
[08:59] <Laney> unless they do something like "if [ -e /CurrentlyBuilding ]; then export SNAPPY_STORE_NO_CDN=1; fi
[08:59] <oSoMoN> I guess in the case of chromium-browser that's not really a problem, who would want to build-depend on a browser anyway? but that means that seeds need to be updated to install the snap
[08:59] <Laney> (package builds set that, not actually 100% sure if image ones do)
[09:00] <Laney> s/set that/create that file/
[09:00] <Laney> would be interesting to me to know if that env var does make it work
[09:02] <oSoMoN> this comment suggests that seeds were updated when lxd was transitioned to snap: https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/1788040/comments/12
[09:36]  * Laney cries
[09:36] <Laney> what ever is wrong with this
[09:44] <didrocks> 380 zfs tests for grub menu generation!
[14:00] <ovrh> Hey everyone, I think I messed up my video drivers again and I can't figure out how to get it back to work. I installed slimbook (from the ppa) and powertop this morning to try and see if I could get longer battery life for my laptop (which I didn't), but now that I connected it back to power and my second monitor, it absolutely fails to recognize it
[14:00] <ovrh> I removed slimbook and powertop already
[14:02] <ovrh> But still, every time I was attaching the hdmi cable, the whole laptop would freeze slow and nothing else would happen. So I fired up nvidia-settings, switched the setting to the nvidia card from in there, and restarted, but still nothing
[14:02] <ovrh> The laptop doesn't seem to freeze anymore when I plug in the monitor with the hdmi, but it doesn't appear to recognize it at all. Went in "Displays" but there's nothing there
[14:03] <ovrh> Any idea what else could be messed up?
[14:11] <tkamppeter> kenvandine, Laney, seb128, sorry, it looked for me that cyphermox has done it, I have even seen a fixed nm.py script what was missing.
[14:13] <tkamppeter> It was this one giving me the confidence: https://git.launchpad.net/network-manager/commit/?h=gir-nm&id=6fb84a283f0587a894c00dcf9f13f3c35744a5d3
[14:13] <kenvandine> tkamppeter: yeah, cyphermox said he things it's hanging in a callback
[14:13] <kenvandine> after his port
[14:14] <kenvandine> tkamppeter: we need this fixed asap
[14:15] <kenvandine> s/things/thinks :)
[14:19] <tkamppeter> kenvandine, I will look into it, but I probably also do not have more GLib/gir knowledge than cyphermox.
[14:21] <kenvandine> tkamppeter: poke around and find people to ask.  Maybe Laney might be able to give you some hints after you do some debugging
[14:29] <tkamppeter> kenvandine, I will look into what comes out in the logs and then ask.
[14:39] <Laney> yeah (although I'm off tomorrow and Monday)
[15:38] <kenvandine> oSoMoN: i moved the USN refresh card for chromium to done based on the date the latest revision was published
[15:38] <kenvandine> we now have an empty list
[15:38] <kenvandine> which won't last for long :)
[15:39] <oSoMoN> kenvandine, thanks, and sorry for not doing it myself. I have multiple builds of the various branches of chromium snap going, and each single build takes a long time to complete, so it's hard to tell for sure when the refresh is actually done
[15:39] <oSoMoN> but at least it's being actively handled :)
[15:39] <kenvandine> no worries
[15:39] <kenvandine> :)
[15:40] <kenvandine> the list is much more for mine since i have so many to juggle
[15:40] <kenvandine> i'm just glad mine build quicker :)
[16:16] <tkamppeter> cyphermox, hi
[16:17] <tkamppeter> cyphermox, do you have any log from the failed nm.py after the port to gir1.2-nm-1.0?
[16:18] <cyphermox> no
[16:18] <cyphermox> it's trivial to test though, you can just run it via autopkgtest -U -s . -- qemu <whatever VM>
[16:19] <tkamppeter> cyphermox, so this is what you did and where you observed the error?
[16:19] <cyphermox> there is no error, it just hangs and eventually autopkgtest times out
[16:20] <tkamppeter> cyphermox, OK.
[16:24] <tkamppeter> cyphermox, thank you, I will try it.