[06:35] <willcooke> morning all
[06:53] <jibel> Morning willcooke
[06:53] <willcooke> bonjour jibel
[06:53] <willcooke> ca va?
[06:53] <jibel> willcooke, ça va bien et toi?
[06:55] <willcooke> bien!
[07:00] <oSoMoN> good morning desktoppers
[07:01] <willcooke> hi oSoMoN!  Thanks for the screenshot
[07:01] <oSoMoN> hey willcooke! you're welcome
[07:02] <willcooke> oSoMoN, so far, so good :)
[07:03] <oSoMoN> good :)
[07:17] <duflu> Morning willcooke, jibel, oSoMoN
[07:17] <duflu> (Europe for now)
[07:17] <jibel> hi duflu
[07:20] <willcooke> hi duflu, good afternoon
[07:20] <willcooke> battery low, bbiab
[07:21] <didrocks> good morning
[07:22] <duflu> Hi didrocks
[07:29] <didrocks> hey duflu
[07:30] <oSoMoN> hey duflu, salut jibel & didrocks
[07:45] <didrocks> salut oSoMoN
[07:50] <jibel> Hello oSoMoN
[08:41] <seb128> good morning desktopers
[08:41] <didrocks> salut seb128
[08:42] <seb128> lut didrocks, en forme ?
[08:42] <didrocks> ça va, et toi ?
[08:48] <seb128> nickel
[08:55] <willcooke> seb128, you still OK to run the meeting today?
[08:55] <willcooke> I will send out the reminder
[08:56] <seb128> willcooke, hey, sure, thx for sending the reminder :)
[08:58] <Trevinho> Morning
[08:58] <seb128> hey trevinho, how are you?
[08:58] <seb128> what are you doing on european time? ;)
[08:59] <Trevinho> seb128: hey I'm good ;)
[08:59] <didrocks> morning willcooke, Trevinho
[08:59] <Trevinho> well, as the weekend I've been skiing I had to get up early and so I got used 😅
[09:00] <Trevinho> didrocks: hi, morning you too
[09:01] <Trevinho> seb128: ah the bileto with dbus test runner including Laney's change is ready for your final approval
[09:01] <seb128> trevinho, url?
[09:01] <seb128> trevinho, https://code.launchpad.net/~laney/dbus-test-runner/no-werror/+merge/352238 didn't get reviewed/approved, we need that before landing
[09:02] <Trevinho> seb128: https://bileto.ubuntu.com/#/ticket/3574
[09:02] <seb128> I understand the removed reference to Werror but it's not clear to me if the new dbus_test_task_prepare() symbol and the code changes are part of the "no Werror"
[09:03] <seb128> sorry, https://code.launchpad.net/~indicator-applet-developers/dbus-test-runner/no-werror/+merge/361756 now
[09:04] <Trevinho> seb128: I did review Laney's one on the fly of adapting it, no mayor change since that... but by reviewing I meant that too
[09:05] <seb128> well, you didn't comment, landing is going to fail if the MP is not approved
[09:05] <Trevinho> seb128: having an extra commit could be better though
[09:05] <seb128> also as said I don't understand if the code changes are part of that, it feels like they should be a separate commit/explained
[09:05] <seb128> let me comment on the mp saying that
[09:05] <Laney> i'm innocent
[09:05] <Trevinho> yes... I mean I just prepared the code...
[09:06] <Laney> stop pinging me about this old MP
[09:06] <Trevinho> Laney: never!
[09:06] <Trevinho> good morning
[09:06] <Trevinho> but no prescription exists here :-D
[09:06] <didrocks> Laney never looked that innocent, it's suspicious
[09:07] <seb128> hey Laney :)
[09:07] <Laney> MUHAHAH
[09:07] <Laney> what's up
[09:10] <Trevinho> you've to split that diff 😘
[09:11] <Laney> not going to do that
[09:11] <Laney> I don't even know what it is
[09:11] <Laney> delete it
[09:12] <Trevinho> :'(
[09:14] <Laney> I would at least remove/improve all those g_debug()
[09:14] <Laney> did I really write this?
[09:14] <Laney> very confusing
[09:16] <Trevinho> Laney: you were young...
[09:16] <seb128> Laney, trevinho, in we don't remember/understand the side changes let's drop those and just do the Werror thing?
[09:16] <Laney> that's what I jus said
[09:16] <Trevinho> I was about to say the same
[09:22] <Laney> :>
[09:23] <seb128> so we all agree, good :)
[09:45] <seb128> Trevinho, I can press the landing button once it's ready, just give me a ping
[09:45] <Trevinho> seb128: thanks, it's building right now
[10:09] <andyrock> morning all!
[10:12] <seb128> hey andyrock! how are you?
[10:13] <andyrock> hey seb128, in the office \o/
[10:14] <andyrock> came here in case I need a multi-head setup to reproduce the lockscreen issue on cosmic
[10:14] <andyrock> seb128: you?
[10:14] <seb128> oh, nice, enjoy the cookies :-)
[10:15] <seb128> I'm good, did some reviews/sponsoring this morning to start the day!
[10:16] <andyrock> I also came here for the free coffee 😂
[10:16] <willcooke> :D
[10:17] <Trevinho> seb128: https://bileto.ubuntu.com/#/ticket/3574 ready for your publish button press
[10:19] <seb128> trevinho, done
[10:33] <duflu> Trevinho, I'm noticing GC runs are still using 20-70% of my CPU during short profiling intervals. Do you think bumping the GC interval from 10s to 5m would hurt?
[10:34] <duflu> It should yield 30x lower CPU overhead assuming there's not much to collect
[10:34] <duflu> Correction: "20-70%" of gnome-shell's total usage, which isn't large
[10:35] <willcooke> lunch, l8r
[10:48] <Trevinho> duflu: mh... Maybe a bit less, but should not too much
[10:51] <duflu> Trevinho, I want at least one order of magnitude improvement and ideally two. So that means 100s - 1000s
[10:52] <duflu> But not today. I am done for today
[10:53] <duflu> So the long term power usage will be lower, AND it won't cloud performance profiles
[10:55] <duflu> Oh well. Night...
[12:49] <andyrock> I think I found the issue with the lockscreen
[12:49] <andyrock> \o/
[12:50] <Laney> :D
[13:06] <seb128> andyrock, well done!
[13:31] <Nafallo> o/
[13:31] <Nafallo> meeting?
[13:31] <Laney> 1 hour
[13:32] <Nafallo> hmmmm
[13:32] <Nafallo> yes.
[14:01] <Nafallo> hrmpf. my calendar on my phone set the meeting to 14:30. on the computer it's 15:30
[14:01] <Nafallo> how annoying...
[14:07] <seb128> Nafallo, Ubuntu on the computer?
[14:30] <seb128> it's meeting time!
[14:30] <seb128> #startmeeting Desktop Team Weekly Meeting 2019-01-15
[14:30] <meetingology> Meeting started Tue Jan 15 14:30:29 2019 UTC.  The chair is seb128. Information about MeetBot at http://wiki.ubuntu.com/meetingology.
[14:30] <meetingology> Available commands: action commands idea info link nick
[14:30] <Nafallo> seb128: ... do you even need to ask? ;-)
[14:30] <Nafallo> o/
[14:30] <seb128> Nafallo, it means Ubuntu 1 - 0 you-phone-OS
[14:31] <Nafallo> I blame Office 365 :-p
[14:31] <seb128> Roll call: andyrock, dgadomski, didrocks, duflu (out), jbicha, jamesh (out), jibel, kenvandine (out), laney, oSoMoN, seb128, tkamppeter, trevinho, robert_ancell (out)
[14:31] <didrocks> éhey
[14:31] <Laney> áhi
[14:31] <jbicha> hey
[14:31] <Trevinho> o/
[14:31] <oSoMoN> o/
[14:32] <andyrock> o/
[14:33] <seb128> sorry, was reading the late updates from the hub :)
[14:34] <seb128> k, so bugs reviews
[14:34] <seb128> 18.04.2 is getting close so now is time to focus on issues that need to land in that version
[14:34] <seb128> #topic rls bugs review
[14:34] <Nafallo> seb128: do we have a date yet? :-)
[14:34] <seb128> * disco, http://reqorts.qa.ubuntu.com/reports/rls-mgr/rls-dd-incoming-bug-tasks.html / http://reqorts.qa.ubuntu.com/reports/rls-mgr/rls-dd-tracking-bug-tasks.html
[14:35] <seb128> Nafallo, https://wiki.ubuntu.com/BionicBeaver/ReleaseSchedule
[14:35] <seb128> feb 7th according to that
[14:35] <Nafallo> thanks
[14:36] <seb128> the disco list has no incoming and the tracking list are either assigned or fix commited
[14:36] <seb128> * cosmic, http://reqorts.qa.ubuntu.com/reports/rls-mgr/rls-cc-incoming-bug-tasks.html / http://reqorts.qa.ubuntu.com/reports/rls-mgr/rls-cc-tracking-bug-tasks.html
[14:36] <seb128> no incoming
[14:37] <seb128> tracking seems on shape
[14:37] <seb128> * bionic
[14:37] <seb128> http://reqorts.qa.ubuntu.com/reports/rls-mgr/rls-bb-incoming-bug-tasks.html is empty
[14:37] <seb128> http://reqorts.qa.ubuntu.com/reports/rls-mgr/rls-bb-tracking-bug-tasks.html
[14:37] <seb128> bug #1745032 is unassigned, I'm going to take it
[14:38] <seb128> (it's an OEM request so I think it's fair it's targetted)
[14:38] <Trevinho> foundation?
[14:38] <seb128> Trevinho, you mean?
[14:38] <seb128> we look at the desktop section
[14:39] <Trevinho> I mean doesn't seem something related to our packages, more something lowlevel no?
[14:39] <seb128> upower is owned by us and there are gnome-control-center/gnome-shell changes
[14:39] <seb128> no, I think it's fine that desktop own this one
[14:39] <seb128> it's basically adding a new status to upower (which we own) and using that status in the GNOME UI
[14:39] <Trevinho> ah, ok... I saw now the comment
[14:40] <seb128> other one is bug #1811225 which I guess is for tjaalton
[14:40] <Trevinho> I can include it in the g-s landing I was preparing if you want
[14:40] <seb128> tjaalton, you aim at having that in 18.04.2?
[14:41] <seb128> Trevinho, yes please, also Daniel had some fixes he wanted included that he commented about on the hub weekly post, but I guess you are aware of those/are looking at them?
[14:42] <seb128> k, so I think that was it for the reviews
[14:42] <Trevinho> yep, not sure we wanted to have the landing with the XUbuntuCancel thing + more things.
[14:42] <seb128> I'm going to chase status update for some of the rls-bb-tracking bugs but after the meeting, I don't think we need to do that with everyone blocked
[14:42] <Trevinho> that was also targetted for .2
[14:42] <seb128> Trevinho, my gut feeling is that it's not important enough/too late for .2
[14:43] <seb128> we got 0 user reports about it
[14:43] <seb128> so not the most important thing probably
[14:43] <seb128> wdyt?
[14:43] <Trevinho> well it was bb tracking since ever xD, so you see why it wasn't higher prio for me too :D
[14:43] <Trevinho> but well, since it's there it's a bit annoying to rebase everytime
[14:43] <Trevinho> but I can do it if you prefer to keep it separated
[14:44] <seb128> right, well let's do a landing for .2 targetted fix
[14:44] <seb128> and then land that directly after
[14:44] <Trevinho> as per the g-s landing, I've asked again upstream a new release, but again... nothing.
[14:44] <seb128> :(
[14:44] <seb128> gnome-shell upstream is a bit of a frustation still :/
[14:44] <seb128> unsure how we can resolve that though
[14:44] <Trevinho> ok, I'll prepare a silo with everything then, then you'll reupload.
[14:45] <seb128> anyway, not a topic for that meeting, maybe one for fosdem over beer
[14:45] <seb128> thx
[14:45] <Trevinho> *much beer
[14:45] <tjaalton> seb128: yes
[14:45] <Laney> or never
[14:46] <seb128> anyway
[14:46] <seb128> #topic AOB
[14:46] <seb128> other topics?
[14:46] <seb128> I use that section to say it again, 18.04.2 is getting close, if you have fixes that need to be in there/you think should be in there, now is time to get them uploaded
[14:47] <didrocks> nothing for me
[14:47] <Laney> yeah, wanted to start thinking about updating to gnome 3.32 at some point
[14:48] <tkamppeter> The Bionic SRU bug 1804576 is stuck on openjdk-8, perhaps this should get an exception.
[14:48] <seb128> tkamppeter, is openjdk-8 creating problem for cups? or just for the test? (in which case we can probably convince the SRU team to unblock cups)
[14:49] <seb128> Laney, on 3.32 my opinion would be "those who are doing active work on a component and want to update it, feel free"
[14:50] <seb128> I don't think we need to fear gtk4 depends at this point, I doubt it's a think for 3.32 now
[14:50] <Laney> you mean having a random mix of versions?
[14:50] <seb128> I would stay away from updating things nobody is actively looking at until .90
[14:50] <seb128> well
[14:50] <seb128> I wouldn't bother updating e.g games
[14:51] <seb128> but if you/trevinho wants to jump on 3.31 for shell/nautilus/etc it sounds good to me
[14:51] <seb128> I'm happy to look at g-c-c/g-s-d (also maybe Robert is interested by that one as well since he has been quite active upstream recently)
[14:51] <seb128> well, just my 2 cents
[14:51] <Trevinho> not that I've plenty of time, but I can
[14:51] <tkamppeter> seb128, there is no complaint/bug report of someone having problems with openjdk and CUPS, it is just the test.
[14:52] <seb128> everyone know what they have on their plates, if you want to do 3.31 updates feel free
[14:52] <Trevinho> I'd give prio to the SRU first, then we see
[14:52] <seb128> just don't do mass updates to an intermediate version to not look at bugs/keep up with fixes and/or updates then
[14:52] <jbicha> we'll need to get libhandy MIR'd for at least gnome-control-center (it's a library from Purism for responsive UI)
[14:52] <seb128> tkamppeter, k, let me talk to the SRU team
[14:52] <seb128> jbicha, I though it was bundled and the copy used by default if the dep is not available?
[14:53] <seb128> which was the recommended way atm
[14:53] <jbicha> oh yeah, we can do that for 3.32
[14:53] <jbicha> whether that is recommended is controversial :)
[14:53] <seb128> my understanding from recent #gnome-hackers discussions was that it was the suggested approach atm
[14:53] <didrocks> I bet libhandy doesn't have a stable API right now, so sounds curious to use it externally
[14:53] <seb128> well, in any case I don't think that MIR blocks us
[14:56] <seb128> k
[14:56] <seb128> Laney, did you want more input on the topic/does that sound fine to you?
[14:56] <Laney> no, I was mainly looking for any unknown reason why not to do it
[14:56] <Laney> thx
[14:57] <seb128> np
[14:57] <seb128> other topic?
[14:58] <seb128> seems not
[14:58] <seb128> it's a wrap then!
[14:58] <seb128> thank everyone
[14:58] <seb128> #endmeeting
[14:58] <meetingology> Meeting ended Tue Jan 15 14:58:26 2019 UTC.
[14:58] <meetingology> Minutes:        http://ubottu.com/meetingology/logs/ubuntu-desktop/2019/ubuntu-desktop.2019-01-15-14.30.moin.txt
[14:58] <oSoMoN> thanks!
[14:58] <Laney> oh, we forgot the disco-proposed report
[14:59] <Laney> can we get rid of emacs off our list?
[15:01] <Nafallo> emacs the desktop package? *cries*
[15:01]  * Laney drops gedit
[15:02]  * jbicha drops glib
[15:02] <seb128> oh, ups
[15:02] <seb128> sorry about that!
[15:04] <seb128> I don't remember what is pulling emacs in
[15:04] <seb128> could have to do with tex
[15:04] <seb128> which is ours
[15:06] <Laney> https://paste.ubuntu.com/p/78CXKjsSWW/ would do it
[15:08] <seb128> ah :)
[15:08] <seb128> I though emacs-common was also one thing needed/pulled it in
[15:09] <seb128> willcooke, ^ do you have an opinion about dropping emacs for the supported desktop seed?
[15:10] <willcooke> I do
[15:10] <didrocks> "finally"
[15:10] <willcooke> :)
[15:10] <willcooke> It's a tricky one
[15:10] <willcooke> lemme ponder it for a bit
[15:10] <seb128> k
[15:11] <didrocks> (I guess he's joking, isn't he?)
[15:13] <willcooke> what's the package name for tex?
[15:14] <willcooke> or more specifically, what's the size impact of having emacs?
[15:14] <willcooke> I assume this isn't really a size issue though
[15:14] <andyrock> Trevinho: https://github.com/micheleg/dash-to-dock/pull/868 do you mind taking a look?
[15:14] <gitbot> micheleg issue (Pull request) 868 in dash-to-dock "theming: Ensure _trackingWindows contains valid windows" [Open]
[15:14] <Trevinho> k
[15:14] <andyrock> I you give a +1 I'll propose/push to ubuntu-dock too
[15:15] <andyrock> *if
[15:15] <andyrock> if you got cosmic you can try to reproduce the issue using firefox
[15:15] <seb128> andyrock, you finally found the problem then?
[15:16] <andyrock> seb128: yep, something that explains why trackingWindow contains invalid windows
[15:16] <seb128> willcooke, no, it's the supported seed, we don't ship it on the iso. It's just that it ends up on our list of owned component, so like when autopkgtests fail it's for us to resolve
[15:16] <seb128> andyrock, nice job!
[15:17] <andyrock> seb128: basically we populate it using a list of windows but we listen for added and removed events on another list
[15:17] <seb128> I see
[15:17] <andyrock> usually the two list contains the same window
[15:17] <seb128> and they happen to be similar most of the time so it usually works? ;)
[15:17] <jbicha> willcooke: no size issue. It's just whether Canonical wants emacs to have main support
[15:18] <andyrock> when dragging firefox tab arounds these two lists are not the same anymore
[15:18] <seb128> ah, nice way to trigger it :)
[15:18] <andyrock> I guess there are other ways to reproduce
[15:18] <andyrock> it's not always the case, but the fix should be the corrent one
[15:19] <andyrock> not a work-around
[15:19] <jbicha> GNOME 3.32 should be a pretty nice update: Terminal will finally offer a headerbar and the GNOME3 appmenu is gone (hamburger menus for everyone)
[15:21] <seb128> sounds like a bit boring if that's all there is to it :p
[15:27] <jbicha> lol
[15:32] <willcooke> seb128, ah I see.  Well yeah, I dont think it should be outs
[15:32] <willcooke> *ours
[15:33] <seb128> but do you think it should be in main/official supported by Canonical?
[15:33] <seb128> unsure who makes those calls
[15:34] <Laney> when we dropped evolution we asked support if any customers require it
[15:34] <Laney> they said no, and then I did it
[15:36] <seb128> willcooke, ^ can do you do that for emacs?
[15:36] <willcooke> good call Laney, I will do that
[15:36] <willcooke> yeah
[15:36] <willcooke> sure thing
[15:36] <seb128> thx
[15:36] <seb128> want a trello card for it?
[15:36] <Laney> might want to mention to Steve or someone as well in case they want to rescue it for some reason
[15:37] <Laney> thx
[15:37] <willcooke> yeah I will speak to Steve today too
[15:38] <willcooke> today/tonight/soon
[15:38] <willcooke> this week anyway
[15:42] <Laney> high five
[16:09] <andyrock> Trevinho: plase consider https://gitlab.gnome.org/GNOME/mutter/merge_requests/162 for the g-s update
[16:09] <gitbot> GNOME issue (Merge request) 162 in mutter "clutter/x11: Implement keycode remap to keysyms on virtual key devices" [1. Bug, 5. Input, Merged]
[16:09] <andyrock> it has been finally merged :)
[17:01] <Laney> spam128
[17:10] <jbicha> Trevinho: what new version of gnome-shell were you wanting?
[17:34] <Trevinho> jbicha: I want a 3.28.4
[17:35] <jbicha> then we'll probably need to do it ourselves
[17:35] <jbicha> Trevinho: do you have GNOME commit rights yet?
[17:36] <Trevinho> jbicha: I do, but I don't think Florian would be happy about
[17:36] <jbicha> did you ask him to do 3.28.4 or did you offer to do it? :)
[17:37] <Trevinho> nor I'd like to do it if maintainers don't want leave us the control
[17:38] <jbicha> are you interesting in doing the release if the maintainers don't object?
[17:47] <jbicha> https://gitlab.gnome.org/GNOME/gnome-shell/issues/910
[17:47] <gitbot> GNOME issue 910 in gnome-shell "3.28.4 release" [Opened]
[17:48] <jbicha> there's one more thing you'll need: someone with access to master.gnome.org to actually do the tarball upload (as mentioned at the end of https://wiki.gnome.org/MaintainersCorner/Releasing )
[20:56] <seb128> Laney, sorry, wrong time to subscribe to nautilus bugs... :)
[21:45] <Trevinho> jbicha: I've master.gnome.org access
[21:45] <Trevinho> but again..
[21:47] <jbicha> ok
[21:48] <Trevinho> jbicha: also florian will do it, but we've no timing for that, so better to go with a snapshot if we've the .2 freeze
[21:49] <jbicha> yes I see now (he replied on the gitlab issue and I think I can read between the lines)
[21:49] <jbicha> are you going to use gbp pq to cherry-pick all the commits or are you going to make a snapshot tarball?
[21:50] <Trevinho> I'd use a tarball...
[21:51] <Trevinho> not sure what's the best way for that given the fact we're using gbp, but for sure they should not be patches
[21:51] <Trevinho> or reviewing will be impossible
[21:51] <Trevinho> so i was thinking to just update the upstream/gnome-3.28 branch and use that
[21:53] <jbicha> ok
[21:53] <jbicha> I'm glad it uses meson since I think it's easier to create tarballs for meson
[21:56] <Trevinho> indeed
[21:56] <Trevinho> that would imply updating pristine-tar or we can just avoid it for this?
[21:57] <jbicha> unless you tell debian/gbp.conf otherwise, the pristine-tar branch is required for people to build your branch
[21:58] <jbicha> I've generally just done the gbp pq thing, but admittedly I haven't done an SRU quite like this one
[22:00] <jbicha> my closest was https://launchpad.net/ubuntu/+source/gnome-builder/3.30.1-6ubuntu1 with 30+ commits but it 1) got accepted just before release and 2) is a universe pkg
[23:02] <Trevinho> jbicha: would you mind to publish this https://bileto.ubuntu.com/#/ticket/3595 ?