[00:56] <handsome_feng>  /set net_ping_timeout 0
[00:57] <handsome_feng> Sorry...
[06:12] <jibel> hi all
[06:37] <didrocks> good morning
[06:37] <jibel> salut didrocks
[06:40] <didrocks> salut jibel
[07:38] <duflu> Morning jibel and didrocks
[07:39]  * duflu is incredibly frustrated at replacing the same taps 3 times in 2 days and is glad to be sitting at a desk again
[07:43] <didrocks> hey duflu
[07:44] <oSoMoN> good morning desktoppers
[07:46] <duflu> Hi oSoMoN
[07:46] <oSoMoN> hey duflu
[07:47] <didrocks> hey oSoMoN
[07:47] <oSoMoN> salut diddledan
[07:47] <oSoMoN> darn stupid tab completion
[07:47] <oSoMoN> salut didrocks
[07:47] <oSoMoN> also, good morning diddledan :)
[07:49] <duflu> Now we need an 'oSoSiMiLaR'
[07:51] <oSoMoN> and a 'dufnotquitelu'
[08:01] <mwhudson> oSoMoN: would it inconvenience you if i uploaded cargo 0.39 to focal?
[08:01] <mwhudson> (and maybe the new rustc too although that's being awkward)
[08:07] <oSoMoN> mwhudson, that should be fine
[08:07] <oSoMoN> what's awkward about it?
[08:07] <mwhudson> oSoMoN: well, maybe i should say non-trivial
[08:08] <mwhudson> i did an upstream update in a lazy way and it fails to build
[08:08] <mwhudson> whereas cargo 0.39 was actually much easier than 0.37 -> 0.38
[08:16] <seb128> goooood morning desktopers
[08:17] <didrocks> hey seb128
[08:17] <seb128> lut didrocks, en forme aujourd'hui ?
[08:17] <didrocks> ça va, et toi ?
[08:17] <seb128> ça va bien!
[08:18] <duflu> Morning seb128
[08:21] <seb128> hey duflu
[08:21] <seb128> duflu, how are you?
[08:21] <seb128> duflu, sorry for not commenting on the IS trello card when the RT was sent
[08:21] <duflu> seb128, Going OK. No problem. How are you?
[08:22] <seb128> I'm good, I went to bed early yesterday, was good to have a longer night :)
[08:23] <seb128> duflu, I'm going to try to build a list of bugs that would be nice to fix tor the LTS, like papercut/polish kind of things, if you have some of those on your list or cross some when trying feel free to tag them/note them down and send them in my direction
[08:24] <seb128> then I'm going to try to argue at the product sprint that we need part of the cycle allocated to work on those
[08:28] <duflu> seb128, use rls-ff-incoming or something else?
[08:28] <seb128> something else, incoming are team reviewed in the perspective of being release blockers and then tracked
[08:29] <seb128> those would rather be a wishlist/papercut project
[08:29] <seb128> like things that would make a difference in polish level for the LTS but are not release critical
[08:29] <duflu> How about "bugs I can find in the first 5 seconds after logging in"
[08:30] <seb128> those are probably good candidate for polish fixing :)
[08:30] <duflu> seb128, I will use a tag of your choosing
[08:30] <seb128> duflu, desktop-lts-wishlist ?
[08:30] <duflu> Sure, whatever it is it only needs to be unique
[08:30] <seb128> k, let's use that then
[08:30] <seb128> thx :)
[08:32] <duflu> seb128, just remembered I had used 'visual-quality' for that for a few years. Already a long list
[08:33] <seb128> k, I will review that list as well
[08:33] <seb128> don't bother re-tagging those
[08:34] <seb128> wooot, that's quite a list indeed
[08:34] <duflu> Lots of Unity stuff in there so mostly ignorable
[08:36] <seb128> I will review it and tag some with the new tag
[08:38] <seb128> jamesh, tkamppeter, (Cc Laney FYI), rls bugs on discourse update reminder
[08:38] <seb128> jamesh, weekly summary also :)
[08:38] <jamesh> will do.
[08:39] <seb128> thx
[08:42] <duflu> seb128, https://bugs.launchpad.net/ubuntu/+bugs?field.tag=desktop-lts-wishlist
[08:42] <seb128> duflu, that looks like a nice list, thanks!
[09:00] <ricotz> godd morning desktopers!
[09:00] <oSoMoN> good morning ricotz
[09:01] <Laney> hi
[09:01] <ricotz> oSoMoN, hey, looks like one the few cycles where firefox doesn't require a unity patch update
[09:01] <ricotz> Laney, hey
[09:02] <ricotz> seb128, hi, is there further action required on https://bugs.launchpad.net/ubuntu/+source/vala/+bug/1803136 ?
[09:02] <ricotz> like reassigning to release-team?
[09:03] <ricotz> I am hoping the package won't be stuck in the queue for weeks
[09:07] <seb128> hey ricotz Laney, how are you?
[09:07] <seb128> ricotz, try pinging the SRU reviewer of the day? (shifts are listed on the wikipage)
[09:07] <seb128> lut oSoMoN, en forme ?
[09:11] <oSoMoN> hey Laney
[09:11] <oSoMoN> salut seb128, la forme, et toi?
[09:11] <oSoMoN> ricotz, that's very good news, more time for me to focus on backporting thunderbird 68 to stable releases :)
[09:12] <seb128> oSoMoN, ca va bien !
[09:12] <ricotz> seb128, thanks!
[09:13] <Wimpress> Morning desktoppers
[09:15] <seb128> hey Wimpress, how is u.k today?
[09:15] <Wimpress> Well, best described as grey. And cold.
[09:15] <Wimpress> How about you?
[09:17] <seb128> nice and sunny
[09:18] <oSoMoN> good morning Wimpress
[09:19] <didrocks> RAOF: hey, also if you have a minute to look at zsys on eoan (the fix is in -proposed in focal). Currently installing it will prevent you to log in on next reboot, so quite a high one :)
[09:19] <Laney> hi ricotz seb128 oSoMoN Wimpress
[09:19] <Laney> sunny and nice here
[09:20] <didrocks> hey Laney, Wimpress
[09:23] <Laney> \o didrocks o/
[09:25] <duflu> Morning ricotz, Wimpress and Laney
[09:25] <Laney> ahoy duflu!
[09:34] <clobrano> good morning all 0/
[09:35] <seb128> hey clobrano, how are you?
[09:35] <clobrano> hey seb128, I'm good thanks
[09:35] <seb128> clobrano, sorry I didn't really have time to investigate that deb upgrade issue
[09:35] <seb128> did you figure it out?
[09:35] <didrocks> hey clobrano
[09:36] <clobrano> hey didrocks :)
[09:36] <clobrano> seb128, kind of, but I was reviewing deb packages to test it locally
[09:37] <clobrano> basically, the PR to allow User Themes switch install gnome-shell in a yaru-gtk created folder
[09:38] <clobrano> I think I need to either change something in debian/gnome-shell.install or revert the change, installing gnome-shell again in /usr/share/gnome-shell and symlink it to /usr/share/themes
[09:44] <seb128> what's the issue? the file seemed to be on disk no?
[09:52] <seb128> or is update-alternative not liking the destination to be a symlink?
[09:52] <seb128> Laney, do you know if https://github.com/ubuntu/yaru/blob/master/debian/yaru-theme-gnome-shell.postinst#L7 would have an issue with the file being a symlink?
[09:52] <seb128> Laney, context is https://github.com/ubuntu/yaru/blob/master/debian/yaru-theme-gnome-shell.postinst#L7
[09:53] <seb128> update-alternatives: error: alternative path /usr/share/gnome-shell/theme/Yaru/gnome-shell.css doesn't exist
[09:53] <seb128> but the target should be there (it's provided by -gtk which is installed first)
[09:53] <seb128> didrocks, ^
[09:54] <Laney> don't think so
[09:54] <marcustomlinson> morning desktoppers
[09:54] <Laney> how do you reproduce this issue?
[09:55] <Laney> hey marcustomlinson
[09:55] <didrocks> I doubt update-alternatives have any issues with the file type as well
[09:55] <didrocks> hey marcustomlinson
[10:04] <duflu> Hi marcustomlinson
[10:33] <Laney> TFW you can't understand your own code
[10:33] <Laney> who wrote this and what was I thinking?
[12:26] <seb128> question of the day...when is the meeting? still in 2 hours from now? or is DST going to confuse again? ;-)
[12:27] <Laney> calendar says 2 hours
[12:27] <Laney> trust the calendar
[12:29] <Laney> although this one http://ubuntu-news.org/calendars/fridge says 18:30 WTF
[12:30] <seb128> :/
[12:30] <seb128> kenvandine and other USers, if it's in 2 hours it probably means shifted by one hour for you guys this week since you didn't have DST yet
[12:36] <kenvandine> It does say in 2 hours
[12:36] <Laney> seb128: dunno if you missed the message but how do you reproduce that yaru problem?
[12:37] <seb128> kenvandine, that's one hour off compared to your normal local time then right? anyway, as long as you are aware it's all good :)
[12:38] <seb128> Laney, I didn't try to reproduce yet, I just have the urls I shared earlier. but I think it's using this ppa https://launchpad.net/~communitheme/+archive/ubuntu/ppa and upgrading
[12:38] <seb128> Laney, let me try in a bionic chroot see if I hit the issue
[12:39] <Laney> ok cheers
[12:47] <diddledan> Morning, oSoMoN 😊 auto defeat ftw!
[12:48] <oSoMoN> :)
[12:52] <seb128> Laney, clobrano, I can't trigger the bug with dpkg, but I don't have the previous ppa version to try the update scenario
[12:52] <seb128> clobrano, Laney, in any case the -theme-gnome-shell should depends on -gtk if it symlinks to content from there
[12:53] <clobrano> seb128, sorry I missed the replies, reading now
[12:53] <seb128> that should also hep ensuring the content of -gtk is unpacked first
[12:53] <seb128> (or is Pre-Depends needed for that?)
[12:53] <Laney> nah, postinst -> depends
[12:55] <clobrano> seb128, as far as I understood, https://github.com/ubuntu/yaru/blob/master/debian/yaru-theme-gnome-shell.postinst#L7 triggers the error message, but I think the problem is before
[12:56] <seb128> clobrano, how before?
[12:56] <clobrano> meson build script installs gnome-shel under `/usr/share/themes/Yaru/gnome-shell`, but the folder `/usr/share/themes/Yaru` is created by yaru-gtk
[12:57] <clobrano> so if ones install gnome-shell first, or it only wants to install gnome-shell, that folder does not exists
[12:58] <seb128> right, which is why I said you need a Depends added to -theme-gnome-shell
[12:58] <clobrano> and if `/usr/share/themes/Yaru/gnome-shell` does not exist, nor its symlink under `/usr/share/gnome-shell` does
[12:58] <clobrano> right, but this means one cannot install Yaru gnome-shell without the gtk part, is that a problem?
[12:59] <seb128> well, they can't anyway
[12:59] <clobrano> why?
[12:59] <seb128> since you installed the actual shell css in a directory shipped by -gtk
[12:59] <seb128> and make the gnome-shell binary only ship a symlink
[13:00] <seb128> if you remove gtk then your shell css is a broken symlink no?
[13:00] <clobrano> oh yes, sure. That's why the other solution. Install gnome-shell under `/usr/share/gnome-shell` as we did before, and symlink into the gtk path
[13:01] <seb128> I don't understand enough of how the theme work / what you are doing to comment on that
[13:01] <clobrano> but that wouldn't work either... since at that point the would be the gtk folder that doesn't exist :(
[13:01] <seb128> e.g why do you have that new approach/need to symlink in between directories?
[13:02] <didrocks> I really don't think it's sane to ship the g-s css in the gtk directory
[13:02] <clobrano> that was to support User Themes gnome-shell extension
[13:02] <clobrano> didrocks, I see
[13:02] <seb128> right, which is where it's getting over my theme knowledge
[13:03] <seb128> like I don't know why technically that's the solution to that problem or if that's the right way to do it
[13:03] <clobrano> I read some people complaining that `/usr/share/gnome-shell` path is not the place, but I don't really know why
[13:04] <didrocks> it's clearly the place, you have /usr/share/gnome-shell/theme created upstream in the past
[13:04] <didrocks> it will fetch them there first
[13:04] <didrocks> and for themes, then, extensions needs to have a <theme>.css or something like that
[13:04] <didrocks> in the extension path
[13:04] <didrocks> (which is the weird part, but meh)
[13:05] <didrocks> actually, for the extension, it's the mode name
[13:05] <seb128> marcustomlinson, did you get any success with the libreoffice/focal autopkgtest issue? unsure how you ranked it on your priority list, it's blocking a stack of desktop components in focal-proposed atm, so would be nice to have it looked at in medium-to-high priority if possible
[13:05] <seb128> (unsure if the context was clear from my ping yesterday)
[13:05] <didrocks> hence the empty file we ship, like /usr/share/gnome-shell/extensions/ubuntu-dock@ubuntu.com/ubuntu.css to allow the theme to override it
[13:06] <clobrano> didrocks, what about shipping more than one default? Like the light and the dark variant? Both shall be installed in `/usr/share/gnome-shell`
[13:06] <clobrano> ?
[13:07] <didrocks> yeah, under /usr/share/gnome-shell/theme
[13:07] <didrocks> then, for switching them, this needs the extension though
[13:07] <marcustomlinson> seb128: will be fixed this week when I upload the new version, tomorrow or Thursday
[13:07] <seb128> marcustomlinson, excellent, thx
[13:08] <clobrano> didrocks, I see. I didn't try that first, because according to https://github.com/ubuntu/yaru/issues/1483 it seemed that, using /usr/share/gnome-shell, changing session one cannot use Yaru anymore
[13:09] <clobrano> but it would be a lot easier to install both themes under /usr/share/gnome-shell/ and not using any symlink
[13:10] <didrocks> just seeing the start of the discussion, I doubt the reporter has a deep understanding that there are 2 themes completely separated (gtk and shell)
[13:11] <clobrano> installing from source, it actually works with this configuration
[13:11] <clobrano> but it creates some issue with the debs
[13:11] <didrocks> yeah, I doubt though that once the assets (like imgs) are different, this will work with the alternative
[13:12] <didrocks> as you need an alternative on the directory symlink directly
[13:15] <clobrano> okay, I'll try with the old installation directory
[13:25] <clobrano> didrocks, an unrelated question, we still need the gtk-3.0 and gtk-3.20 folders?
[13:26] <didrocks> clobrano: that's more a question for seb128/Laney, I don't think we have apps built with pre-gtk3.20, but better to check with them
[13:26] <Laney> that's xenial basically
[13:26] <Laney> so if you have to work with xenial's gtk
[13:27] <Laney> (or older)
[13:27] <didrocks> so as we don't support it, I would say fine for cleaning it up
[13:27] <clobrano> Laney, but isn't yaru supported on >bionic?
[13:27] <didrocks> (we started pre-bionic, remember? ;))
[13:28] <clobrano> okay, I can use 3.0 only then, right?
[13:28] <didrocks> but the release is EOL for quite a long time :)
[13:28] <Laney> I dunno, any snap reasons?
[13:28] <clobrano> didrocks, yes sure, I was saying right now we support from bionic
[13:29] <didrocks> yeah, snaps, good point. It will be interesting to know if any are using an older gtk version
[13:29] <didrocks> (as we build the theme snap from the same source)
[13:29] <seb128> didn't jamesh spent weeks working on making the theme work on xenial's gtk for snap reasons?
[13:29] <seb128> kenvandine, ^
[13:29] <Laney> that'd be what a 3.0 is good for
[13:30] <kenvandine> seb128: yes
[13:30] <kenvandine> seb128: is there an issue?
[13:31] <Laney> just answering a question from Carlo
[13:31] <seb128> kenvandine, if I understood the discussion correctly, I think clobrano was wondering if they could drop the 3.20 folder/support now
[13:32] <kenvandine> yes, we need that for snaps on xenial
[13:32] <clobrano> seb128, exactly. This comes from a complain on yaru flatpak version and I just wanted to have a valid reply for keep/remove the folder
[13:32] <clobrano> kenvandine, perfect
[13:33] <seb128> kenvandine, but xenial users are on unity with ambiance so why do they need yaru?
[13:33] <Laney> current users running a snap with xenial's gtk in it
[13:33] <seb128> oh, that was it of course
[13:33] <seb128> thx Laney :)
[13:34] <kenvandine> yup
[13:34] <Laney> np
[13:34] <Laney> lunch, laterz
[13:34] <seb128> enjoy!
[13:34] <hellsworth> isn't it meeting time?
[13:34] <seb128> DST kicked in, it's in one hour
[13:34] <clobrano> alright, thanks all :)
[13:34] <seb128> well it did for UK/Europe
[13:34] <seb128> not US yet
[13:34] <seb128> always a fun time for calendars/meetings
[13:34] <hellsworth> oh that's right. stupid daylight savings :)
[13:35] <hellsworth> ok well good morning folks
[13:36] <didrocks> good morning hellsworth
[13:36] <didrocks> the calendar should be up to date though for meeting time, doesn't it translate it correctly?
[13:37] <hellsworth> yes it did but i didnt' look at the calendar
[13:37] <hellsworth> i was going off memory
[13:37] <didrocks> :)
[13:38] <hellsworth> that'll teach me :)
[13:41] <seb128> kenvandine, you should have a clicky url for the snapcraft PRs you are mentioning, I'm curious :)
[13:41] <seb128> kenvandine, also do you need help with the segfault issue?
[13:42] <seb128> jamesh, weekly summary post?
[13:42] <kenvandine> seb128: oh, i'll add them :)
[13:42] <jamesh> seb128: just finishing it up.  Thanks for the reminder
[13:42] <kenvandine> seb128: maybe, marcustomlinson ^^ want to get some help from seb128?
[13:42] <seb128> jamesh, thx, sorry for being naggy :)
[13:43] <kenvandine> jamesh: make sure you include any release bugs :)
[13:49] <marcustomlinson> seb128: let me at it for another day then I'll ping you if I'm jammed, thanks for offering
[13:49] <kenvandine> seb128: link added to the status report
[13:49] <seb128> marcustomlinson, np
[13:49] <seb128> kenvandine, thx
[13:49] <kenvandine> seb128: the snapcraft PR includes a link to a PR against gtk-common-themes
[13:50] <kenvandine> I think both look good, but wanted jamesh to look at them
[13:51] <seb128> right, nice numbers in the description, I like it :-)
[14:31] <seb128> Wimpress, team meeting?
[14:32] <seb128> k, I'm going to assume you don't have it yet in your calendar or got delayed and start it
[14:32] <seb128> #startmeeting Desktop Team Weekly Meeting - 2019-10-29
[14:32] <meetingology> Meeting started Tue Oct 29 14:32:51 2019 UTC.  The chair is seb128. Information about MeetBot at http://wiki.ubuntu.com/meetingology.
[14:32] <meetingology> Available commands: action commands idea info link nick
[14:33] <seb128> Roll call:  didrocks, duflu (out), hellsworth, jamesh (out), jibel, kenvandine, laney, marcustomlinson, oSoMoN, seb128 , tkamppeter, trevinho, robert_ancell (out)
[14:33] <oSoMoN> o/
[14:33] <hellsworth> 0/
[14:33] <marcustomlinson> \o
[14:33] <Trevinho> o/
[14:33] <kenvandine> seb128: I just invited Wimpress on the calendar event :)
[14:33] <seb128> kenvandine, that might be useful :)
[14:34] <seb128> k, half the team at least seems around let's get started
[14:34] <seb128> #topic rls-bb-bugs
[14:34] <seb128> http://reqorts.qa.ubuntu.com/reports/rls-mgr/rls-bb-incoming-bug-tasks.html
[14:34] <seb128> no desktop one
[14:34] <seb128> http://reqorts.qa.ubuntu.com/reports/rls-mgr/rls-bb-tracking-bug-tasks.html
[14:35] <seb128> that looks in shape, unassigned ones are fix commited
[14:35] <seb128> #topic rls-dd-bugs
[14:35] <seb128> http://reqorts.qa.ubuntu.com/reports/rls-mgr/rls-dd-incoming-bug-tasks.html
[14:35] <seb128> no desktop one
[14:35] <seb128> http://reqorts.qa.ubuntu.com/reports/rls-mgr/rls-dd-tracking-bug-tasks.html
[14:35] <seb128> no unassigned ones
[14:35] <seb128> #topic rls-ee-bugs
[14:36] <seb128> http://reqorts.qa.ubuntu.com/reports/rls-mgr/rls-ee-incoming-bug-tasks.html
[14:36] <seb128> still no desktop
[14:36] <seb128> bug #1848969 is border desktop but community side now so I don't think we need to handle it here
[14:37] <seb128> http://reqorts.qa.ubuntu.com/reports/rls-mgr/rls-ee-tracking-bug-tasks.html
[14:37] <seb128> bug #1845801
[14:37] <seb128> Laney commented on it that he couldn't reproduce
[14:37] <Laney> it's assigned
[14:38] <Laney> just not all of the tasks
[14:38] <seb128> do you know if Alberto noticed it was?
[14:38] <Laney> yes, as we talked on irc before
[14:38] <seb128> tseliot, ^ please confirm you saw the emails and just didn't /dev/null filter those :)
[14:38] <seb128> k
[14:38] <seb128> so I'm assigning to the other lines
[14:39] <Laney> I wouldn't usually just assign a bug to someone and expect them to notice that
[14:39] <seb128> ack
[14:39] <didrocks> as long as we don't know which component is impacted…
[14:39] <didrocks> Laney: you can with me, filter power ;)
[14:39] <seb128> bug #1847551
[14:39] <seb128> Trevinho, that's part of your pending SRU right?
[14:39] <Laney> yes
[14:39] <Laney> assign it
[14:40] <seb128> k
[14:40] <Trevinho> seb128: yes
[14:40] <Trevinho> already in queue
[14:40] <seb128> bug #1850052
[14:40] <didrocks> waiting in unapproved
[14:40] <seb128> didrocks, assigning that one to you
[14:41] <didrocks> doing, even if "fixed" and waiting from the SRU team to act on it (+ Laney to unblock focal, pretty please ;))
[14:41] <Laney> one thing at a time
[14:41] <seb128> I assigned the rygel one to me
[14:41] <seb128> and that's it
[14:42] <seb128> #topic rls-ff-bugs
[14:42] <seb128> http://reqorts.qa.ubuntu.com/reports/rls-mgr/rls-ff-incoming-bug-tasks.html
[14:42] <seb128> bug #1848766
[14:43] <seb128> it's assigned to xubuntu, the other lines seem buggy
[14:43] <seb128> but I've https://code.launchpad.net/~jbicha/libappindicator/drop-python-appindicator/+merge/335606 on my review queue which is related from our side of things
[14:43] <seb128> bug #1849773
[14:44] <seb128> it's an evince segfault on text selection on some specific documents
[14:44] <seb128> jibel could find only one private document example
[14:44] <jibel> it seems related to the font used in the doc
[14:44] <seb128> I think it's too specific to qualify as a rls bug, we should probably fix it but as normal business
[14:44] <jibel> +1
[14:44] <seb128> jibel, if you can add the font info to the bug that might be useful
[14:44] <tseliot> seb128, I got the bug mail, I remember Laney telling me about it too. I remember systemd complaining about things in the log. I haven't really got time to look into it. I am not sure if NVIDIA is the cause of the problem yet (it could just trigger it)
[14:45] <seb128> tseliot, k, thx
[14:45] <Wimpress> o/
[14:45] <seb128> unless someone objects I will notfixing the evince one
[14:45] <kenvandine> hey Wimpress!
[14:45] <Laney> can we also notfix the indicator-datetime thing pls
[14:45] <Laney> or else we will keep coming back to it
[14:46] <seb128> hey Wimpress
[14:46] <seb128> Laney, good point, done
[14:47] <seb128> bug #1848217	
[14:47] <seb128> that's fix commited, probably not rls material though
[14:47] <Laney> seems handled so I don't think it particularly matters either way
[14:47] <seb128> ah, it's in the installer context
[14:48] <seb128> so yeah, tag is fine, it's fix commited
[14:48] <seb128> right
[14:48] <seb128> http://reqorts.qa.ubuntu.com/reports/rls-mgr/rls-ff-tracking-bug-tasks.html
[14:48] <seb128> desktop clean
[14:48] <seb128> #topic update_excuses_by_team.html#desktop-packages
[14:49] <seb128> Laney, yours
[14:49] <seb128> (in the measure we are ready to look at it/should maybe wait for the initial sync churn to settle down)
[14:49] <Laney> forget it
[14:49] <Laney> it's ruined for this week at least
[14:49] <seb128> just libreoffice is obvious but marcus is on it
[14:49] <Laney> apart from some things like libreoffice which are known separately
[14:50] <seb128> thx Laney :)
[14:50] <seb128> #topic AOB
[14:50] <seb128> any other topic?
[14:51] <seb128> seems not, it's a wrap then
[14:51] <seb128> thanks team!
[14:51] <seb128> #endmeeting
[14:51] <meetingology> Meeting ended Tue Oct 29 14:51:55 2019 UTC.
[14:51] <meetingology> Minutes:        http://ubottu.com/meetingology/logs/ubuntu-desktop/2019/ubuntu-desktop.2019-10-29-14.32.moin.txt
[14:52] <kenvandine> thanks!
[14:52] <marcustomlinson> thanks
[14:52] <Trevinho> ta
[14:52] <Wimpress> seb128 kenvandine Thanks for running things. I'll be here on time next week now I have the calendar entry :-)
[14:52] <didrocks> thx!
[14:53] <seb128> Wimpress, no worry :)
[14:54] <kenvandine> Wimpress: let's hope that's the only think willcooke neglected to hand off :)
[15:17] <clobrano> didrocks, sorry to bother again :), but looking at user themes code, it seems to look for gnome-shell css installed under `/usr/share/themes/<theme>/gnome-shell` folder https://gitlab.gnome.org/GNOME/gnome-shell-extensions/blob/master/extensions/user-theme/extension.js#L42
[15:19] <didrocks> clobrano: interesting, this has changed as it as looking at the other places before
[15:19] <didrocks> I based the location on where the mode/theme for G-S was looking before we moving to an internal css in the compiled gressources
[15:19] <clobrano> didrocks, uhm let me check git history then
[15:19] <didrocks> so yeah, sounds like then moving the whole theme will be necessary. It means updating the Shell css
[15:20] <didrocks> clobrano: well, if upstream thinks now we should put them there, no need to dig more
[15:22] <clobrano> didrocks, yeah I guess
[15:22] <didrocks> clobrano: upstream disagrees with itself though: https://gitlab.gnome.org/GNOME/gnome-shell/blob/master/js/ui/main.js#L298
[15:22] <clobrano> so both gtk and gnome-shell goes into the same dir
[15:23] <didrocks> look here, in G-S, they are looking at the place we are using
[15:23] <didrocks> so I guess it's something for you to discuss with Trevinho, but the extension made by usptream and the G-S code should align at least
[15:24] <clobrano> eh, a bit messy indeed
[15:26] <didrocks> not that crazy… I was sure when I did the extension mode 2.5 years ago I didn't invent it from nothing ;)
[15:27] <clobrano> I'm sure you didn't :D
[15:27] <Trevinho> clobrano: probably upstream wants to keep both, like if the shell theme is the same of gtk then it goes with it otherwise it can use a local time
[15:27] <Trevinho> question of prioritizing one or the other
[15:27] <Trevinho> clobrano: I'd suggest you to ask in #gnome-shell to fmueller when he's around
[15:28] <Trevinho> or open an issue so we can discuss there the proper strategy
[15:32] <clobrano> Trevinho, yes, this could make sense
[16:07] <clobrano> Trevinho, didrocks, reply from #gnome-shell was that `/usr/share/gnome-shell/theme` is for session default and the other for 3rd party theme. Reconsidering the problem, we have Yaru(light) as default and Yaru-dark as selectable, so I can simply install the first under gnome-shell and the latter under themes
[16:07] <clobrano> as I was actually doing at the beginning
[16:08] <clobrano> to have yaru light available under gnome-session, the only option is the symlink
[16:23] <didrocks> yeah, it sounds weird to me, but ack
[16:39] <didrocks> Laney: I think you typoed the hint on https://bazaar.launchpad.net/~ubuntu-release/britney/hints-ubuntu/revision/4024: ss390x
[16:39] <Laney> k
[16:40] <Laney> merge proposals are accepted for reference for the future ;-)
[16:40] <didrocks> thx ;)
[17:30] <kenvandine> hellsworth: marcustomlinson found the crasher.  It's cairo 1.17.  Try downgrading it to 1.16
[17:33] <hellsworth> hmmmm
[17:34] <hellsworth> then it must be different from the librsvg issue of updating the build snap to librsvg-2.46
[17:35] <hellsworth> while the librsvg commit does change cairo versions, it updates librsvg to require 1.16.0 instead of cairo 1.15.12
[17:37] <hellsworth> still.. i'm build ing gnome-3-34-1804-sdk with cairo branch 1.16, rebuilt the platform snap, and rebuilt evince to test
[17:42] <kenvandine> hellsworth: i cherry-picked the fix into gnome-3-34-1804-sdk and pushed it to get a build in LP
[17:42] <hellsworth> oh nice!
[17:43] <hellsworth> can you launch a build? looks like the last lp build of the build snap was a week ago
[17:48] <kenvandine> waiting for the git mirror to sync
[18:04] <hellsworth> is there a way to tell the platform snap to use the gnome-3-34-1804-sdk that is installed locally rather than pulling from the snapstore?
[18:06] <marcustomlinson> hellsworth: doubtful, you could ask on #snapcraft
[18:08] <hellsworth> ah yes good idea
[18:13] <marcustomlinson> hellsworth: it's not that much work to just snapcraft push your local snap to edge
[18:13] <marcustomlinson> but I guess you're using edge at the moment as your release I guess
[18:13] <hellsworth> oh right i can do that from my lp build, i think
[18:13] <marcustomlinson> lots of guessing going on :P
[18:14] <marcustomlinson> hellsworth: doesn't your LP build push to edge already?
[18:15] <marcustomlinson> oh you mean you just need to trigger one
[18:15] <marcustomlinson> yeah that was why I suggested you have a personal one, for times like this where you want to bypass all the import waiting
[18:15] <hellsworth> i tend to just build locally because lp is confusing
[18:15] <hellsworth> yes you're right
[18:15] <hellsworth> and i think i have one
[18:15] <hellsworth> need to find it
[18:16] <marcustomlinson> that's fine, you can do: "snapcraft push <path to local snap>.snap --release edge"
[18:17] <marcustomlinson> hellsworth: ^
[18:17] <hellsworth> wat! i didn't know that
[18:17] <marcustomlinson> :)
[18:18] <hellsworth> i thought the only way to get to the store was to go through lp
[18:18] <marcustomlinson> hellsworth: for a snap to be seeded it needs to, but otherwise no. If I'm remembering correctly kenvandine?
[18:19] <kenvandine> right
[18:19] <kenvandine> there is a policy for seeded snaps
[18:19] <kenvandine> we also utilize LP for automated builds
[18:22] <hellsworth> well since my local build is still going, i just launched a new LP build on ~hellsworth/gnome-3-34-1804-sdk
[18:22] <hellsworth> and that should publish to the store
[18:23] <hellsworth> but my build will be finished first. oh well. lp can publish it for me.
[18:24] <kenvandine> hellsworth: is your snap built from the git mirror?
[18:24] <kenvandine> if so that mirror isn't updating
[18:25] <hellsworth> well my lp build builds from ~ubuntu-desktop/gnome-sdk/+git/gnome-sdk
[18:25] <marcustomlinson> hellsworth: what you've done with gnome-3-34-1804, do with gnome-3-34-1804-sdk
[18:25] <hellsworth> and doesn't that just point to the git repo
[18:25] <marcustomlinson> Source: https://gitlab.gnome.org/Community/Ubuntu/gnome-sdk.git gnome-3-34-1804-sdk
[18:26] <hellsworth> oh yeah marcustomlinson your'e right
[18:32] <hellsworth> isn't gnome-3-34-1804-sdk a seeded snap?
[18:32] <hellsworth> so i should go through lp for this snap to get in the store?
[18:33] <hellsworth> well i'll push it anyways. you wouldn't have told me to if i shouldnt' :)
[18:33] <hellsworth> sometimes i overanalyze things...
[18:36] <kenvandine> nope
[18:37] <hellsworth> out of curiosity, where is the list of seeded snaps?
[18:42] <hellsworth> ok updated build snap in edge. rebuilding the platform snap now.
[19:08] <Trevinho> clobrano: nice, I read on #g-s as well, so.. Yeah somewhat similar to what I was guessing, but nice that we've a definition now
[19:14] <marcustomlinson> hellsworth: if you have time, you think you could give this suggestion a try today? https://gitlab.freedesktop.org/cairo/cairo/issues/382#note_278108
[19:16] <marcustomlinson> kenvandine: got a reply on that bug that looks promising ^
[19:18] <kenvandine> yeah, a build of gnome-3-34-1804-sdk with cairo 1.17 plus that patch shouldn't be too hard
[19:18] <kenvandine> or even just update the cairo part to use the git branch in that PR
[19:19] <hellsworth> well but how do we do that in the build snap? can i have the cairo portion in the build snap checkout a merge request?
[19:19] <marcustomlinson> hellsworth: https://gitlab.freedesktop.org/psychon/cairo/tree/invalid-free-crash
[19:19] <hellsworth> yeah ok i can use this persons branch
[19:24] <marcustomlinson> kenvandine: all 5 of my test apps are working now, I've promoted 3-32 build and platform snaps to stable
[19:25] <marcustomlinson> you can rebuild drawing and let that guy know the good news on forum.snapcraft.io :)
[19:25] <hellsworth> rebuilting gnome-3-34-1804-sdk with the invalid-free-crash branch of ciaro now
[19:25] <marcustomlinson> hellsworth: thanks!
[19:28] <hellsworth> i also had already built the build snap with cairo branch 1.16, pushed it to edge, rebuilt the gnome-3-34-1804 platform snap, pushed it to edge, moved it to stable and am rebuilding evince
[19:47] <hellsworth> evince still crashes for me when i have the build snap using cairo source-branch: 1.16. evince started ok, i went to open a pdf and when i selected a pdf and clicked open, i got a segfault
[19:48] <hellsworth> https://paste.ubuntu.com/p/43yg8JPWHT/
[19:48] <hellsworth> my build of the buildsnap with the invalid-free-crash branch is still going
[19:48] <marcustomlinson> hellsworth: you connected to the right platform snap?
[19:49] <marcustomlinson> You’ll need to connect to a platform snap that is also built from the new build snap
[19:51] <hellsworth> yep and i did that
[19:51] <marcustomlinson> hellsworth: also, the 1.16 branch may be broken as it’s WIP, I meant use the 1.16.0 tag
[19:51] <hellsworth> ah ok
[19:52] <marcustomlinson> The branch I believe has some 1.16.1 work in it
[19:52] <hellsworth> maybe that's the problem then.
[19:53] <marcustomlinson> hellsworth: but good to know that 1.16.1 is broken too. Could you leave a comment on that bug about that
[19:53] <hellsworth> i need to run in a little bit to pick up my daughter from daycare (closing early today because of snow) but i should at least be able to launch a build of the platform snap with the invalid-free-crash build snap first
[20:01] <marcustomlinson> Thanks hellsworth, appreciate it!
[20:05] <hellsworth> my pleasure :)
[20:19] <hellsworth> for some reason, my laptop can't build any snaps: https://paste.ubuntu.com/p/yRdDRvWJw3/
[20:19] <hellsworth> does anyone know how to fix this?
[20:19] <hellsworth> there is no /var/lib/dpkg/lock*
[20:20] <hellsworth> i can do other things like apt update (which wouldn't work if there was already a lock in place)
[20:20] <hellsworth> and my snapcraft version is the stable one (not one of my local builds)
[20:21] <marcustomlinson> hellsworth: that error is coming from the multipass vm not your host
[20:21] <hellsworth> hmm ok maybe i'll reinstall multipass
[20:22] <marcustomlinson> hellsworth: you could try ‘multipass delete snapcraft-evince’
[20:22] <marcustomlinson> Then ‘multipass purge’
[20:22] <hellsworth> ok i will try that
[20:25] <hellsworth> yep that worked!
[20:25] <hellsworth> thanks marcustomlinson
[20:25] <marcustomlinson> np, yeah those VMs can sometimes get into a funky state
[20:25] <hellsworth> ok i need to run and finish up the invalid-free-crash testing later tonight
[20:26] <kenvandine> later
[22:51] <ricotz> kenvandine, hi, https://launchpad.net/~ubuntu-desktop/+snap/gnome-calculator-master -- is this actually using vala 0.40.8 to build gnome-calculator from latest git master? :(