[01:01] <jbicha> robert_ancell: hi, in case you didn't hear, I guess they want you to upload your ubuntu-welcome app soon :)
[01:07] <duflu> jbicha, thanks for the suspend-on-power fix BTW
[01:08] <jbicha> duflu: maybe we'll bring it back next year :)
[01:08] <duflu> jbicha, if it's configurable, sure. :)
[01:08] <duflu> AFAIK it's not yet user-configurable for the login screen
[01:09] <jbicha> right
[06:34] <oSoMoN> good morning desktoppers
[06:37] <jibel> Salut oSoMoN
[06:38] <oSoMoN> salut jibel
[07:11] <didrocks> good morning
[07:13] <oSoMoN> bonjour didrocks
[07:14] <didrocks> salut oSoMoN
[07:15] <seb128> salut didrocks oSoMoN
[07:15] <oSoMoN> salut seb128
[07:15] <jibel> Bonjour didrocks seb128 and all
[07:15] <seb128> lut jibel
[07:15] <seb128> good morning desktopers
[07:16] <didrocks> salut seb128, jibel !
[07:37] <seb128> andyrock, hey
[07:37] <seb128> andyrock, I'm backporting your udisks segfault fix to bionic, just as a fyi
[07:38] <andyrock> hey hey
[07:38] <andyrock> thx!
[07:40] <duflu> Morning oSoMoN, jibel, didrocks, seb128, andyrock
[07:40] <seb128> hey duflu
[07:40] <didrocks> hey duflu!
[08:00] <willcooke> morning
[08:00] <duflu> Morning willcooke
[08:00] <willcooke> duflu, koza - are you doing the BT meeting today?
[08:01] <duflu> The BT meeting moved again. Depends if koza wants it
[08:01] <duflu> Or seb
[08:01] <willcooke> Lovely timezones
[08:01] <willcooke> Seb is out this morning for a little while
[08:01] <willcooke> I have nothing
[08:02] <duflu> Alright. In that case I am putting the camera away. FYI willcooke, koza
[08:02] <duflu> & jibel ^
[08:02] <willcooke> duflu, ack.
[08:02]  * willcooke looks like crap anyway
[08:02] <Laney> moin
[08:02] <duflu> Morning Laney
[08:03] <willcooke> The kids have given me some illness
[08:03] <willcooke> hi Laney
[08:03] <duflu> Well, their immune systems get a good education
[08:03] <duflu> at least
[08:05] <didrocks> hey willcooke, Laney
[08:05] <didrocks> willcooke: I guess we can make a club of "be sick, thanks to the kids" this week :)
[08:06] <willcooke> :DD
[08:06] <didrocks> at least, you know how to do it, being sick during work days
[08:06] <didrocks> for me, that was during extended week-end
[08:06] <didrocks> less attractive :p
[08:06]  * didrocks needs to plan better next time
[08:07] <willcooke> urg, that's the worst
[08:07] <willcooke> actually, being sick on holiday is the worst
[08:08] <didrocks> I guess I had my share of that since December. I should ask for reimbursement to "life"! :)
[08:12] <Laney> /o\
[09:10] <seb128> back
[09:10] <willcooke> morning seb128
[09:10] <seb128> hey willcooke, how are you today?
[09:10] <willcooke> got a bit of a cold from the kids
[09:11] <willcooke> One of thm was up a lot last night coughing
[09:11] <willcooke> so tired as well
[09:11] <willcooke> yay :)
[09:11] <didrocks> wb seb128
[09:11] <seb128> thx
[09:12] <seb128> willcooke, welcome to the club!
[09:12] <willcooke> ha
[09:27] <ali1234> i think there is a problem with the fontconfig cache on the live images
[09:28] <willcooke> Hi ali1234, is that a new problem?  In the last few days?
[09:28] <ali1234> no
[09:28] <ali1234> it's been around for a long time
[09:28] <ali1234> it just took a long time to track it down
[09:28] <willcooke> How is it manifesting itself?
[09:29] <ali1234> basically, the files in /var/cache/fontconfig are not accepted, so the font cache gets rebuilt in ~/.cache/fontconfig for every installed font
[09:29] <willcooke> ah.  jibel - that could be a candidate for slow start up?
[09:29] <ali1234> this takes like a minute or more and delays getting to the live desktop or installer
[09:29] <ali1234> right, it's the slow startup
[09:29] <seb128> good finding if that's the issue!
[09:30] <willcooke> looks like we owe you some beers ali1234
[09:30] <ali1234> if you update a font package it rebuilds the font cache and then the problem goes away
[09:30] <seb128> so it's only the cache included on the iso?
[09:30] <ali1234> yes
[09:30] <seb128> do you know what it doesn't like about it?
[09:30] <ali1234> a little bit
[09:30] <ali1234> at xubuntu, we thought the problem was caused by bluez and we have a bug tracking that
[09:31] <seb128> that would be weird
[09:31] <ali1234> last night i figured out bluez was a red herring: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1754836
[09:31] <ubot5`> Ubuntu bug 1754836 in bluez (Ubuntu) "Xubuntu: ERROR:dbus.proxies:Introspect error on org.bluez:/org/bluez: dbus.exceptions.DBusException: org.freedesktop.DBus.Error.TimedOut: Failed to activate service 'org.bluez': timed out (service_start_timeout=25000ms)" [Critical,Confirmed]
[09:31] <ali1234> see my comments at the bottom of that
[09:32] <ali1234> i dont know whether to change that bug or make a new one, if a new one i don't know what to open it against :)
[09:32] <ali1234> all the info is there though
[09:33] <ali1234> one interesting thing is that ubuntu seems to rebuild the font cache during the installer so it is only affected in the live image. however, xubuntu does not so it happens again on the user's first login to the installed system
[09:33] <jibel> willcooke, could be but the bootchart should have shown IO generated by the creation of the cache.
[09:34] <willcooke> jibel, sounds like it could well be a culprit, so interesting that the boot chart doesnt show it.
[09:34] <jibel> unless it stops too early
[09:34] <willcooke> oh, yeah
[09:34] <ali1234> it definitely gets rebuilt - just check ~/.cache/fontconfig. it should be empty except for maybe 1 file for the firefox emoji font
[09:35] <didrocks> /var/lib/dpkg/info/fontconfig.postinst looks correct at first look
[09:35] <didrocks> in the "trigger" case
[09:35] <seb128> well there are caches in the system location
[09:35] <seb128> but they are invalid
[09:35] <didrocks> we should look for "fc-cache failed" in iso build logs
[09:36] <seb128> where is the iso build log? ;)
[09:36] <didrocks> in case the invalid caches are from a fc-cache error
[09:36] <didrocks> this is why I didn't put a link, I don't know :p
[09:36] <seb128> Laney, ^ help? :)
[09:36] <seb128> or maybe jibel knows
[09:36] <ali1234> if anyone knows the structure of the cache files, i did a binary diff between working/non-working
[09:36] <ali1234> details on the bug
[09:37] <didrocks> the best case would be fc-cache generating that errors with the logs in /var/log/fontconfig.log
[09:37] <seb128> it's over my understand of fontconfig details
[09:37] <didrocks> if it only generates invalid caches and don't error out… urgh, harder to understand
[09:37] <jibel> seb128, https://people.canonical.com/~ubuntu-archive/cd-build-logs/ubuntu/bionic
[09:37] <seb128> jibel, thx
[09:37] <jibel> then look at the build id in the first lines of the log
[09:38] <jibel> https://launchpad.net/~ubuntu-cdimage/+livefs/ubuntu/bionic/ubuntu/+build/128542 in this case
[09:38] <didrocks> no fc-cache error line :/
[09:38] <seb128> nothing useful in that log
[09:38] <seb128> Setting up fontconfig (2.12.6-0ubuntu1) ...
[09:38] <seb128> Regenerating fonts cache... done.
[09:38] <didrocks> so the trigger happily passed
[09:38] <seb128> Processing triggers for fontconfig (2.12.6-0ubuntu1) ...
[09:39] <seb128> yeah
[09:39] <seb128> well not a surprise if a cache file is generated
[09:39] <didrocks> and nothing below…
[09:39] <didrocks> yeah
[09:39] <jibel> Setting up fontconfig (2.12.6-0ubuntu1) ...
[09:39] <jibel> Regenerating fonts cache... done.
[09:39] <jibel> yeah :)
[09:39] <didrocks> /var/log/fontconfig.log ?
[09:39] <didrocks> is that purged from the iso? (I don't have one handy
[09:39] <didrocks> )
[09:39] <didrocks> in case that can help
[09:40] <didrocks> as we run fc-cache in verbose mode and redirect to it…
[09:40] <jibel> didrocks, i'll have a look i'm testing beta2
[09:40]  * didrocks crosses fingers log will help
[09:42] <willcooke> Debian are fingering Noto as the problem, is that right?
[09:42] <ali1234> no
[09:42] <ali1234> Noto is really slow to generate because it is huge
[09:42] <ali1234> but the issue is it shouldn't be getting generated because the cache is supposed to already be there
[09:44] <willcooke> ahhhh
[09:47] <ali1234> https://cgit.freedesktop.org/fontconfig/tree/src/fccache.c#n996 is the list of reasns why fontconfig will reject a cache file
[09:48] <ali1234> the ifdef jumps out at me as something which could be represented by that mystery field
[09:50] <jibel> hm, latest iso doesn't boot if I go directly to the live session from syslinux
[09:52] <Laney> seb128: I got as far as noticing gsd-xsettings is slow when doing some fontconfig thing, this sounds further along than I got
[09:52] <Laney> or what did you want my help with?
[09:52] <seb128> Laney, getting the url of the iso build log, but jibel had it
[09:53] <Laney> ok
[09:53] <Laney> https://launchpad.net/~ubuntu-cdimage/+livefs/ubuntu/bionic/ubuntu/ this is a good index
[09:53] <seb128> thx
[09:58] <jibel> didrocks, http://paste.ubuntu.com/p/7YxNf7MsvY/ and it says existing cache is valid
[10:00] <seb128> it might be worth sending an email to the upstream fontconfig list with the cache bin diff
[10:00] <seb128> they might be helpful
[10:00] <seb128> ali1234, would you like to do that?
[10:01] <didrocks> jibel: :/
[10:01] <jibel> ali1234, do you know which job trigger fc-cache on log in?
[10:04] <jibel> one day I'll dd an iso to my hard drive :/
[10:11] <Laney> The GLib update doesn't look that interesting
[10:11] <jibel> interesting finding
[10:11] <Laney> gtk+3.0, probably is ok
[10:11] <LocutusOfBorg> seb128, not major update, minor debian revision
[10:11] <LocutusOfBorg> Laney, if you want, just ack and I'll upload in a ppa
[10:12] <seb128_> right, the glib change seems a bit late in the cycle
[10:12] <LocutusOfBorg> I don't want to mess up with your iso generations or similar
[10:12] <didrocks> seb128_: good catch!
[10:13] <jibel> seb128_, do you know what triggers fc-cache on log in?
[10:13] <seb128_> no
[10:13] <jibel> I cannot find anything
[10:13] <seb128_> likely fontconfig which when being used validates the cache
[10:13] <seb128_> so apps themself
[10:13] <Laney> it breaks stuff too https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=894763
[10:13] <ubot5`> Debian bug 894763 in libglib2.0-0 "libglib2.0-0: symbol lookup error: /usr/lib/arm-linux-gnueabihf/libgobject-2.0.so.0: undefined symbol: g_date_copy" [Grave,Open]
[10:13] <Laney> jibel: gsd-xsettings does something with fontconfig
[10:14] <Laney> and that is part of the startup
[10:15] <Laney> LocutusOfBorg: you can upload to the queue, it'll probably get accepted after the beta
[10:15] <seb128_> bbiab, need to change location
[10:15] <Laney> and please make sure to do your changes in bzr too if you don't mind
[10:16] <Laney> might want to check if jbicha_ hasn't started this work too, would be annoying to duplicate
[10:16] <LocutusOfBorg> ok nice
[10:17] <LocutusOfBorg> I think he is *happy* to stop merging it :)
[10:18] <Laney> ok, if you know that based on some evidence
[10:18] <LocutusOfBorg> last time he asked me to do the merge :)
[10:19] <LocutusOfBorg> I did a gtk2 and he asked me to also merge gtk3
[10:19] <LocutusOfBorg> and after that also glib2 :)
[10:19] <Laney> he asked you to merge this glib upload?
[10:20] <LocutusOfBorg> nope
[10:20] <LocutusOfBorg> I'm talking about previous uploads
[10:20] <Laney> ok
[10:20] <LocutusOfBorg> done gtk3 in queue
[10:30]  * duflu closes eyes and logs off before finding any more mutter issues
[10:48] <seb128> k, back at my desk/online
[10:48] <seb128> didrocks, ali1234, sorry, had to drop from IRC for a bit, was there anything else said on the topic meanwhile?
[10:49] <ali1234> i read that bug report. seems to exactly describe what i am seeing
[10:49] <seb128> yeah, what I though as well from your binary diff/explanations
[10:49] <didrocks> seb128: nothing more, no
[10:50] <seb128> ali1234, do you want to provide some details on that upstream report or should I?
[10:50] <Laney> jibel attached the log that was asked for
[10:51] <ali1234> ah FC_DEBUG=16... i think i tried every other possible number :)
[10:52] <seb128> ah, nice
[10:55] <ali1234> ah i think i understand this now from that log - "cache checksum 1522818676.601423551 dir checksum 1522818676.0"
[10:56] <ali1234> so it is actually the font directory that has had the timestamp changed by going through squashfs
[10:59] <ali1234> and that's why the mystery field changes to zero
[10:59] <seb128> right
[11:00] <seb128> didrocks, do you want that as a launchpad bug report or just IRC ping?
[11:00] <seb128> $ dpkg-deb -c libsysmetrics-dev_1.0.3_i386.deb | grep pc
[11:00] <seb128> -rw-r--r-- root/root       258 2018-04-03 09:51 ./usr/lib/i686-linux-gnu/pkgconfig/sysmetrics.pc
[11:00] <seb128> didrocks, the arch triplet is i386-linux-gnu no i686
[11:00] <seb128> it makes ubuntu-welcome fail to build on i386 since it doesn't find the .pc
[11:02] <Laney> that looks like DEB_HOST_GNU_TYPE or something was used instead of DEB_HOST_MULTARCH
[11:02] <didrocks> seb128: let me just fix it, no need for paperwork
[11:02] <didrocks> yes
[11:02] <didrocks> fixing right away
[11:02] <seb128> didrocks, thx
[11:02] <Laney> with right spelling of multiarch
[11:02] <seb128> :)
[11:03] <didrocks> nw! thanks for pointing it!
[11:03] <didrocks> Laney: :)
[11:10] <didrocks> seb128: fixed, built, tested and uploaded. You can take and build latest from github if you want to take that one instead of copying on your system :)
[11:15] <seb128> didrocks, thx, the build is from a ppa so I'm just going to wait for it to be in the archive and retry
[11:15] <seb128> my bionic system is amd64 :p
[11:16] <didrocks> argh, I needed to keep one GNU style for build dir due to dh_golang…
[11:16] <didrocks> oh, true, you reinstalled :)
[11:18] <Laney> seb's specialist dual boot system
[11:19] <seb128> :)
[11:35] <didrocks> ok, the ppa ran worked this time (to avoid an useless upload), pushing
[11:35] <seb128> didrocks, :)
[11:36] <seb128> didrocks, thanks for fixing!
[11:36] <didrocks> so yeah, I used the GNU type due to dh_golang and didn't think about build dir being different than install dir (don't understand exactly why)
[11:36] <didrocks> yw!
[11:36] <didrocks> the 2 tools, being debian specific, should use the same triplet format IMHO
[11:37] <seb128> yeah, I don't know either
[11:37] <didrocks> Travis is having large roundtrip anyway to start a build, so I was able to slip that in between 2 builds :)
[11:40] <willcooke> Is there a good LP bug for the fontconfig issue?  I'd like to tag it rls-bb-incoming at least.  I can open a new one based on the upstream one if needed
[11:40] <ali1234> i don't know of any others
[11:41] <seb128> ali1234, the bluez one was about bluez or really about the slow boot/fontconfig?
[11:41] <seb128> in which case we just need to rename it
[11:41] <didrocks> seems the timeout on bluez is due to slow boot
[11:41] <seb128> willcooke, we had one about slow boot on our side already which we can maybe use?
[11:41] <ali1234> i opened it when we thought the slow boot was caused by bluez
[11:41] <ali1234> there is https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1749546
[11:41] <ubot5`> Ubuntu bug 1749546 in casper (Ubuntu) "Booting a live session is slow " [Undecided,New]
[11:42] <seb128> reusing that seems fine to me
[11:42] <willcooke> ah nice, let's reuse that one
[11:42] <willcooke> ta
[11:42] <seb128> willcooke, thx
[11:42] <willcooke> I'll update etc
[11:42] <didrocks> it's great to have at least an idea where this may be coming from :)
[11:42] <jibel> willcooke, I'll reassign to fontconfig
[11:42] <willcooke> jibel, I'm doing that now
[11:43] <Laney> I'm already assigned to it, it's fine
[11:43] <Laney> but if you want ...
[11:43] <willcooke> :)
[11:43] <jibel> you can remove casper
[11:44] <Laney> oh you probably don't mean #1750846
[11:45] <jibel> no it's different
[11:46] <Laney> is it though
[11:46] <ali1234> i have a feeling that the fontconfig thing may cause a knock-on effect where other stuff times out
[11:46] <ali1234> especially dbus - hence the bluez thing as well
[11:46] <willcooke> +1
[11:46] <ali1234> i have no evidence for this though
[11:47] <willcooke> sounds plausible
[11:47] <seb128> one easy way to figure out, fix the fontconfig issue and see if that resolves the other ones :)
[11:47] <willcooke> :)
[11:47] <willcooke> anyone want to own this one?
[11:47] <willcooke> Would like to see if we can get it fixed for beta
[11:47] <seb128> do you know where is the team mapping list?
[11:47] <willcooke> try at least
[11:48] <seb128> I wonder who owns fontconfig
[11:48] <Laney> be calm
[11:48] <Laney> I've been assigned to the bug I just referenced for some time, I'm working on it
[11:48] <seb128> wfm, thanks Laney!
[11:49] <Laney> I found out last night / this morning that gsd-xsettings was blocking the start up in fontconfig stuff
[11:49] <willcooke> thanks Laney
[11:49] <Laney> so ali1234 coming in with more analysis is good timing
[11:49] <seb128> Laney, well it was just that if the issues turns out to be in fontconfig and that foundations own that then we might want to bounce to them at this point
[11:50] <seb128> but your call at the end
[11:50] <willcooke> j_bicha was the last one to touch it ;))
[11:51] <Laney> as for who owns the package, look at the subscribers
[11:51] <Laney> mapping is generated from that
[11:51] <seb128> desktop-packages and foundations-bugs are subscribed
[11:51] <seb128> so we both own it? :)
[11:51] <Laney> seems so
[11:51] <Laney> quick, press the unsubscribe button
[11:52] <seb128> I was going to say :p
[11:52] <didrocks> ahah, first one unsubribing wins :)
[11:55]  * willcooke <- sandwich 
[11:56] <seb128> willcooke, enjoy!
[11:56]  * seb128 just had some takeway pasta, that was good
[12:54] <Laney> can't think of a better way to fix that fontconfig thing than ignoring the nanoseconds if it's 0
[12:54] <Laney> ali1234: got any ideas?
[12:55] <Laney> I tried a patch to do that, which works
[12:55] <Laney> boot speed still isn't exactly amazing though
[12:56] <Laney> ubuntu@ubuntu:~$ systemd-analyze
[12:56] <Laney> Startup finished in 24.412s (kernel) + 1min 23.971s (userspace) = 1min 48.384s
[12:56] <Laney> graphical.target reached after 28.680s in userspace
[12:57] <Laney> however it does fix the gsd problems
[13:04] <Laney> hmm that second try was way better, weird
[13:05] <Laney> ubuntu@ubuntu:~$ systemd-analyze
[13:05] <Laney> Startup finished in 12.572s (kernel) + 23.512s (userspace) = 36.084s
[13:05] <Laney> graphical.target reached after 23.473s in userspace
[13:55] <oSoMoN> willcooke, seb128: libreoffice 6.0.3 will be out this week (currently in RC2, for which we have a snap in the candidate channel btw), and we have 6.0.2 in bionic today. How do you feel about pushing the update (supposedly bug fixes only, I will double-check that)? Or better to SRU after release?
[13:55] <willcooke> hum
[13:56] <willcooke> I dont suppose we've really given .2 a proper shakedown since not that many people are using it.
[13:56] <willcooke> So shipping .3 isn't a massive problem
[13:57] <willcooke> What do we do with, say, Firefox in this situation chrisccoulson?  ^
[13:57] <seb128> oSoMoN, I would push it to bionic, we can keep it in proposed for a while and decide to turn it into a SRU from there if we prefer
[13:57] <jbicha> we're still ~3 weeks from release, we still do bug fix updates :)
[13:59] <chrisccoulson> willcooke, I normally just upload it and somebody approves it - it's usually already in the security pocket for other releases by the time I do that though
[14:00] <seb128> chrisccoulson, hey again, did you see my questions about those translations earlier? ;)
[14:00] <chrisccoulson> seb128, yeah. The answer is yes
[14:00] <seb128> jbicha, btw bug #1759538 has been ack-ed so you can make g-s recommends it with the next upload
[14:00] <ubot5`> bug 1759538 in bolt (Ubuntu) "[ffe] Install bolt by default for thunderbolt devices support" [Medium,Triaged] https://launchpad.net/bugs/1759538
[14:00] <seb128> chrisccoulson, thx
[14:01] <oSoMoN> good, so I'll double-check the upstream changelog and diff to make sure they didn't sneak new features in, and will coordinate with ricotz to prepare a 6.0.3 upload
[14:02] <seb128> thx, let me know if/when you need sponsoring
[14:03] <oSoMoN> that'll most likely be early next week
[14:06] <seb128> k
[14:07] <Laney> looks like ipv6 came back, brb!
[14:07] <Laney> feels modern
[14:08] <seb128> is there a way to make softwares not removable in gnome-software?
[14:08] <seb128> bug #1756788 seems annoying
[14:08] <ubot5`> bug 1756788 in gnome-session (Ubuntu) "Removing "Startup Applications" in "Ubuntu Software" makes the system unable to launch GDM" [Undecided,New] https://launchpad.net/bugs/1756788
[14:08] <seb128> I guess it removes gnome-session, DOH
[14:08] <Laney> yes, you can make it compulsory-for-desktop or whatever the thing is
[14:09] <seb128> k, thx
[14:12]  * ricotz wonders what openjdk-11 packages versioned as 10~46-4ubuntu1 are about
[14:13] <ricotz> hey desktopers
[14:17] <seb128> hey ricotz
[14:17] <Laney> moin ricotz
[14:18] <Laney> don't think the desktop team particularly knows about java, better to ask the uploader?
[14:18] <seb128> +1
[14:18] <ricotz> seb128, Laney, hi
[14:19] <ricotz> I guess the uploader already removed the source packages from the archive again
[14:19] <ricotz> so hard to tell where it came from, I assume d_oko did
[14:20] <Laney> https://launchpad.net/ubuntu/+source/openjdk-lts/10~46-4ubuntu1
[14:20] <seb128> jbicha, thx :)
[14:21] <ricotz> Laney, oohh
[14:21] <ali1234> Laney: i don't know, but can't you fix the squashfs, rather than patching fontconfig?
[14:21] <ricotz> Laney, aptitude failed to show me the changelog
[14:23] <Laney> ali1234: how?
[14:24] <ali1234> well the most obvious way would be to build it on a filesystem that doesn't have nanos, so that the cache remains valid after being copied through squashfs
[14:25] <ali1234> manually stripping the nanos from /usr/share/fonts (recursive) before generating the cache would also work
[14:26] <ricotz> chrisccoulson, hi, are you going to upload tb 52.7.3?
[14:26] <ali1234> i suppose that would mess with the deb file timestamps
[14:27] <ricotz> chrisccoulson, ah sorry, I thought they tagged it
[14:28] <Laney> not sure LP people would be happy with that, and I'd rather a more generic solution anyway
[14:28] <Laney> so either make fontconfig tolerate this situation or change squashfs
[14:30] <ali1234> the way i see it, the timestamps are going to be truncated at some point. so you'd just be making it happen earlier
[14:30] <ali1234> it wouldn't change the effective timestamp on any files managed by packages
[14:32] <ali1234> but i have no idea how the image builders work
[14:34] <jbicha> ricotz: did you want to try adding/moving the Thunderbird app icons LP: #1682455 ?
[14:34] <ubot5`> Launchpad bug 1682455 in thunderbird (Ubuntu) "thunderbird not available in GNOME Software" [Medium,Triaged] https://launchpad.net/bugs/1682455
[14:39] <ricotz> jbicha, tweaking the stable packages is more a thing for chris
[14:39] <ricotz> jbicha, did you find a way to confirm that this works properly with the ff60 betas?
[14:40] <jbicha> ask Lan_ey but I don't think appstream data from PPAs is usable in the GNOME Software app yet
[14:41] <jbicha> so the only way I know to know for sure is to upload to bionic and see
[14:50] <ricotz> jbicha, I could take a look if chris would push his packaging changes
[14:50] <ricotz> should be similar to the firefox-esr changes I made
[14:52] <jbicha> thanks
[14:52] <ricotz> jbicha, e.g. https://paste.debian.net/plain/1018499
[14:59] <jbicha> ricotz: maybe you could talk Mozilla into providing an ESR snap so you don't have to maintain that PPA :)
[15:02] <ricotz> jbicha, I am not sure that people wanting firefox-esr are using snaps
[15:04] <jbicha> it might not be a bad choice compared to a PPA
[15:05] <jbicha> I'm just guessing, but I think we'll be hesitant to allow firefox-esr in to the Ubuntu archives
[16:34]  * Laney waves from the train
[16:34] <Laney> new 4g wifi thing works well!
[16:42] <xnox> Laney, cool! =)
[16:42]  * Laney high fives xnox 
[16:43] <Laney> I should probably turn some things off so I don't burn through all the data tho
[16:44]  * Laney ticks "restrict background data usage"
[16:46] <xnox> Laney, i wonder if unattended-upgrades respects the "restrict background data usage" is that an Gnome-shell thing, or a Network Manager thing?
[16:52] <Laney> xnox: It sets metered on the dbus interface I think, and GNetworkMonitor exposes that (g_network_monitor_get_network_metered())
[16:52] <Laney> so it probably doesn't unless it uses one of those APIs
[16:53] <xnox> Laney, session or system bus?
[16:53] <Laney> NM is on the system bus
[16:54] <Laney> do something like busctl --system introspect org.freedesktop.NetworkManager /org/freedesktop/NetworkManager
[16:56] <Laney> although for me that is currently 4 which is apparently GUESS_NO
[17:19] <Laney> ok now it's 1 after reconneccting
[17:32] <Laney> xnox: https://paste.ubuntu.com/p/KBH6G3ZBGf/
[17:33] <Laney> I think android and ios have a thing to set that automatically on tethering btw
[17:42] <Laney> goodnight from newark northgate
[17:49] <willcooke> night all