[05:03] <jibel> morning
[05:04] <tsimonq2> o/ jibel
[05:11] <jibel> hey tsimonq2
[05:25] <duflu> Morning jibel, tsimonq2
[05:26] <tsimonq2> o/ duflu
[05:27] <duflu> \o
[06:18] <oSoMoN> good morning desktoppers
[06:25] <tsimonq2> o/ oSoMoN
[06:31] <oSoMoN> hey tsimonq2 , congrats on the MOTU promotion!
[06:35] <ricotz> oSoMoN, hey, there is an updated wip-5.4 branch
[06:39] <oSoMoN> hey ricotz, thanks, taking a look now
[06:42] <tsimonq2> oSoMoN: Thanks :D
[06:51] <oSoMoN> ricotz, lgtm
[06:53] <ricotz> oSoMoN, pushed :)
[07:03] <seb128> good mroning desktopers
[07:08] <duflu> Morning seb128
[07:08] <seb128> hey duflu, how are you?
[07:08] <duflu> seb128, not too bad. You?
[07:08] <jamesh> hi seb128, duflu
[07:08] <seb128> duflu, I'm good thanks
[07:08] <duflu> Afternoon jamesh
[07:09] <jamesh> just had my new laptop delivered
[07:09] <duflu> woo
[07:09] <seb128> duflu, I just saw that you moved https://trello.com/c/3tMZbqwd/39-support-for-accelerated-video-playback-on-intel-in-totem-and-mpv to blocked, what is it blocked on? (would be nice to add the reason in a comment when something is blocked)
[07:09] <seb128> jamesh, which one did you get?
[07:09] <duflu> seb128, comment is already there :)
[07:09] <duflu> Same as last time
[07:10] <duflu> Also mentioned in status reports for a few weeks
[07:10] <jamesh> seb128: ThinkPad X1
[07:10] <seb128> duflu, oh, right, I didn't really understand this bug, that's about the ubuntu-restricted-addons changes?
[07:11] <seb128> having gstreamer1.0-vaapi added?
[07:11] <duflu> seb128, yes it's about finishing the OOTB experience
[07:11] <seb128> duflu, k, sorry about that, the patch name is "debdiff including lubuntu changes"
[07:12] <seb128> so I assumed it was something for lubuntu when I read it a few weeks ago
[07:12] <duflu> seb128, yeah it didn't help that the patch changed
[07:12] <duflu> Bryan asked me today if I could sponsor it :)
[07:12] <seb128> haha
[07:12] <seb128> I'm not familiar with that package
[07:13] <seb128> do we need the depends in main or partner?
[07:13] <duflu> ??
[07:17] <amano> Wow. JAdahl just pushed builtin screencasting and remote desktop support to Mutter. From what I can see it is VNC only and disabled by default: https://bugzilla.gnome.org/show_bug.cgi?id=784199
[07:18] <duflu> I'm not familiar... has development pace been this rapid always or did it pick up recently?
[07:18] <amano> Considering the state of Remmina it is probably nice to have and probably stable by the time Ubuntu 18.04 arrive
[07:19] <amano> .... arrives.
[07:22] <amano> duflu, the example app for it is https://github.com/jadahl/gnome-remote-desktop. The initial commit was at the end of 2015.
[07:44] <amano> Interesting background information here: https://ctrl.blog/entry/wayland-gnome-remote-desktop
[07:46] <seb128> duflu, btw https://didrocks.fr/2017/08/18/ubuntu-gnome-shell-in-artful-day-5/ has a section about the launcher button being at the bottom
[07:46] <seb128> "For instance, the application picker button is kept at the bottom and not moved at the top of the dock. Indeed, the application picker button isn’t the BFB from the Unity world launching our “dash”"
[07:47] <duflu> seb128, that's fine. Reject the bug if you want
[07:47] <duflu> It's not important
[07:50] <seb128> I'm not going to close it since I'm not sure I agree with having it at the bottom
[07:50] <seb128> we need designers :-)
[07:54] <duflu> I have more challenging issues today like finding out why Totel needs 50% of its CPU time spent software filling pixels
[07:54] <duflu> Totem too
[07:56] <duflu> seb128, anyone, did you notice Alt+drag for moving windows doesn't work? Is that just in Wayland?
[07:56] <seb128> just in wayland
[07:56] <seb128> and yes, I keep hitting it and I find it frustrating
[07:56] <duflu> Cool, got a bug?
[07:57] <tjaalton> ctrl-win-arrow shortcuts don't work either
[07:58] <duflu> tjaalton, Aren't they less traditional and more Unity-only?
[07:58] <tjaalton> duflu: they worked at some point
[07:58] <seb128> duflu, no I don't, I should probably look for/open one
[07:58]  * duflu files another bug
[07:59] <tjaalton> btw, I added some xwayland backports to xserver, brings wacom support etc
[08:00] <duflu> tjaalton, Cool! I was wondering why Wacom support went backwards
[08:00] <tjaalton> I haven't tested any of it myself since my wacom is hidden in a moving box somewhere
[08:04] <seb128> Trevinho, good morning?
[08:04] <duflu> seb128, https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1713650
[08:05] <Trevinho> hi seb128
[08:05] <Trevinho> morning
[08:05] <seb128> duflu, thanks
[08:05] <seb128> hey Trevinho :-)
[08:05] <seb128> so you are up, just hidding from us :p
[08:06] <Trevinho> seb128: yeah, I'm "a bear" in the morning.... I don't speak much even in real life :-D
[08:06] <seb128> hehe
[08:06] <seb128> Trevinho, anyway, I'm teasing you but I actually had a question
[08:06] <davmor2> Morning all
[08:07] <seb128> Trevinho, what's the status of the landing of the indicators build fixes for gcc7?
[08:07] <duflu> Morning davmor2, bear-Trevinho
[08:07] <seb128> hey davmor2
[08:08] <Trevinho> seb128: eh, I put that in hold as I had to finish the mutter and indicator extension work
[08:08] <Trevinho> seb128: however, the indicators are ready to land in theory
[08:08] <seb128> Trevinho, the ind... right, exactly
[08:08] <seb128> can we just do another landing for those?
[08:09] <seb128> we have other fixes/changes we can maybe land
[08:09] <Trevinho> seb128: waht needs love is unity/nux which fails in other archs because of libsigc++...
[08:09] <seb128> and I wanted to add a tweak for langpacks
[08:09] <Trevinho> seb128: ok, let me split the bileto
[08:09] <seb128> Trevinho, well, don't bother
[08:09] <seb128> Trevinho, just drop indicators from yours
[08:09] <Trevinho> seb128: I asked for a porter box for such archs...
[08:10] <duflu> seb128, worse for native Wayland apps: They have no title bar to drag either. You need to Alt+Space to get to the move option
[08:10] <Trevinho> seb128: ok, as you wish I can do mine in a sec
[08:10] <Trevinho> seb128: or steal indicators from https://bileto.ubuntu.com/#/ticket/2892
[08:11] <Trevinho> seb128: just let me know how to proceed
[08:12] <seb128> Trevinho, as said I want maybe to include some extra changes to the indicator
[08:12] <seb128> let me get my change up for review
[08:12] <seb128> Trevinho, what do you think about landing https://code.launchpad.net/~dobey/indicator-sound/drop-greeeter/+merge/320858 ?
[08:13] <seb128> well we don't need the change so maybe we should just land things that are useful
[08:18] <Trevinho> seb128: oh, that's seem ok for me
[08:49] <seb128> Trevinho, https://code.launchpad.net/~seb128/indicator-power/use-universe-translations/+merge/329797 and https://code.launchpad.net/~seb128/indicator-sound/use-universe-translations/+merge/329798 if you to add those and move to another silo?
[08:50] <Trevinho> seb128: ok, I'll do it in 5
[08:50] <seb128> Trevinho, thanks
[08:54] <mpt> andyrock, it is already the case that with the checkbox checked, a Livepatch update might not install immediately — because you might not be connected to the Internet when the update is published. Taking a few seconds to sign in is just another possible reason for delay.
[08:55] <Laney> /o\
[08:55] <Laney> hey we missed this channel's 10th birthday
[08:55] <Laney> 29/08 09:55:15 -!- Channel #ubuntu-desktop created Sun Nov 26 06:42:54 2006
[08:57] <andyrock> mpt: I've a branch with the behaviour you wanted, but it feels broken to me
[08:57] <andyrock> I'll push in a ppa
[08:58] <tsimonq2> Laney: gosh darnit
[08:58] <andyrock> mpt: would be easier for me with a spinner and binding the checkbox to the daemon status
[08:59] <mpt> andyrock, when you turn on a backup service for the first time, it’s plausibly interesting to see the setup status, because the first backup will start as soon as the setup is complete. But with Livepatch the first update might not happen until hours/days later, so there’s nothing interesting to wait for. “Enabled” is not a thing that is relevant to users.
[08:59] <mpt> And nor is “daemon status”.
[08:59] <andyrock> kk
[09:00] <andyrock> mpt: another problem is what should happens when you click multiple times on it
[09:00] <mpt> I appreciate that this does make multiple clicks a bit harder — you might have to turn off the daemon as soon as you’ve finished turning it on, or vice versa
[09:02] <andyrock> this is going to break your system if you do multiple clicking
[09:02] <mpt> Why would it break your system?
[09:02] <andyrock> well if it takes 1 min to enable the system and you queue 10 enable/disable commands
[09:02] <andyrock> or more
[09:03] <andyrock> you'll have in background software-properties-dbus for 10/15 minutes
[09:03] <andyrock> cancelling it's not an option
[09:03] <mpt> Then … implement it as a state rather than as a queue of commands
[09:04] <andyrock> mpt: it's not a queue
[09:04] <mpt> Good!
[09:04] <andyrock> right now: click->enable/disable
[09:05] <andyrock> I can use an idle but that does not guarantee that the requests will overlap
[09:06] <andyrock> *will not
[09:07] <mpt> andyrock, imagine the case where I click the checkbox three times: check, uncheck, check. After the first check, you tell the daemon to start up. When it tells you that it’s running, then you look at the current state of the checkbox. Is it checked? Yes. Is the daemon running? Yes. So you don’t need to do anything further.
[09:07] <Laney> seb128: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1713391 <- did you work out it was in the patch or is it an upstream bug?
[09:07] <Trevinho> seb128: https://bileto.ubuntu.com/#/ticket/2928
[09:07] <Trevinho> nope... I missed your PRs :D
[09:07] <Laney> marcoooooooooo
[09:07] <Trevinho> laneeyyyyyyyyyyyyy
[09:10] <andyrock> mmm mpt that makes sense
[09:11] <seb128> Laney, it's in the patch, I talked to desrt a bit and she said she still planned to land that change in git this cycle but she was in a German class and couldn't look more at the time
[09:12] <Laney> sure
[09:12] <Laney> did she say she would fix that bug or?
[09:12] <Laney> otherwise I would ping muktupav_els :-)
[09:13] <seb128> she didn't
[09:13] <seb128> but I expected she would
[09:13] <seb128> could be wishful thinking from my part though :-)
[09:13] <Laney> heh
[09:14] <Laney> muktupavels: ^- interested in bug #1713391 ? it's in the per-session override patch
[09:21] <muktupavels> Laney: I am interested that per-desktop overrides are merged upstream. Not so much in bugs, but I will look at that bug.
[09:23] <Laney> muktupavels: you might be interested in not introducing bugs if it's merged maybe :P
[09:26] <muktupavels> Laney: patches are more or less from desrt and I already fixed few problems in them. :P
[09:26] <Laney> :-)
[09:27] <Laney> thanks for looking
[09:27] <muktupavels>  I will look at that bug :)
[09:32] <seb128> thanks
[09:48] <seb128> bah, I just let my laptop unlock in a public place while going to the toilet
[09:49] <seb128> ctrl-alt-L -> go reflex and the keybinding stopped working :-/
[09:49] <seb128> I need to get used to super-L
[09:50] <muktupavels> glib-compile-schemas are used without --strict, right?
[09:50] <seb128> muktupavels, correct
[09:51] <muktupavels> Ok, then I will update patch.
[09:51] <seb128> should we use --strict?
[09:51] <seb128> in any case if it double free without it that's still a bug
[09:51] <muktupavels> No.
[09:52] <muktupavels> I will update patch
[09:52] <seb128> thanks
[09:55]  * Laney changed the keybinding back to c-a-l
[10:05] <muktupavels> seb128, Laney: patch updated and attached to upstream bug.
[10:05] <seb128> muktupavels, thanks!
[10:07] <Laney> oh for g_auto
[10:12] <muktupavels> seb128:
[10:12] <muktupavels> Gtk/IMModule does not look like valid key!
[10:14] <Laney> they probably want to put that in overrides :/
[10:14] <flexiondotorg> Morning desktopers
[10:16] <flexiondotorg> Laney seb128 Trevinho I was at the Fit and Finish sprint with did_rocks and Will last week.
[10:16] <flexiondotorg> I was working on GTK theme fixes.
[10:16] <Trevinho> flexiondotorg: yeah.... :)
[10:16] <seb128>  hey flexiondotorg, how was that?
[10:16] <flexiondotorg> I have a whole heap of stuff, that Will has approved :-)
[10:16] <seb128> muktupavels, Laney, yeah, that override seems buggy indeed
[10:16] <flexiondotorg> seb128 Was very productive.
[10:16] <seb128> great
[10:17] <flexiondotorg> But I have some questions about how best to proceed.
[10:17] <flexiondotorg> I need to rebase on a recently released ubuntu-themes.
[10:17] <flexiondotorg> The notebook refactor is massive ~1500 added ~1000 removed.
[10:18] <flexiondotorg> Then I have some much smaller discrete improvements.
[10:18] <flexiondotorg> Should I submit the Notebook refactor as a standalone merge proposal.
[10:19] <flexiondotorg> And when that change is merged released, submit a new merge proposal for the other odds and ends where each commit is a discrete change?
[10:19] <flexiondotorg> Or just create one merge proposal where notebook refactor is the first commit with the discrete changes each in a commit there after?
[10:20] <flexiondotorg> I can do the builds in Bileto, but I'll need someone to Approve the merge proposal(s).
[10:20] <flexiondotorg> Last week did_rocks Approved my Notebook refactor merge proposal, but that now need rebasing.
[10:20] <Laney> approved as in he did a code review?
[10:20] <Laney> or the design?
[10:21] <flexiondotorg> Will approved the design and didrocks did a light touch code review.
[10:21] <Laney> I think you should propose merge proposals, the smaller the better
[10:22] <Laney> You can set a prerequisite for the later ones on top of the refactor if you need to
[10:22] <Laney> Trevinh_o is probably going to be the one reviewing those
[10:22] <Trevinho> flexiondotorg: I can look at them too
[10:22] <Laney> oho
[10:22] <flexiondotorg> Cool.
[10:22] <flexiondotorg> I'll start with a rebase of the Notebook refactor and then stack the other changes on that then.
[10:23] <Laney> If they don't touch the same lines then they don't need to be stacked
[10:23] <flexiondotorg> OK.
[10:23] <Trevinho> flexiondotorg: mind that there's a bileto branch that I wanted to merge asap
[10:23] <flexiondotorg> Trevinho I think we did that as the sprint.
[10:23] <flexiondotorg> *at
[10:24] <flexiondotorg> Which is why I need to rebase.
[10:24] <Trevinho> flexiondotorg: k
[10:25] <flexiondotorg> https://bileto.ubuntu.com/#/ticket/2848#audit_log
[10:25] <flexiondotorg> Actually.
[10:25] <flexiondotorg> did_rock tried to publish but it failed with Bad Merges.
[10:26] <flexiondotorg> Trevinho ^
[10:26] <flexiondotorg> I'm planning on working on the theme updates in the evenings this week. I don't have time during day.
[10:31] <Trevinho> flexiondotorg: yeah, use the bileto branch in the mean time as base
[10:32] <Trevinho> flexiondotorg: the reason was that https://code.launchpad.net/~3v1n0/ubuntu-themes/better-destructive-action/+merge/329392 was not reviewed
[10:32] <Trevinho> which I asked to do :)
[10:33] <Trevinho> ah, he actually did it
[10:33] <Trevinho> flexiondotorg: I'll fix that later, anyway the bileto branch can be your base
[10:33] <andyrock> mpt: ok almost done
[10:33] <flexiondotorg> Trevinho OK, so the slipped through the net sorry.
[10:33] <flexiondotorg> I reviewed it. All good. I have now approve powers.
[10:34] <flexiondotorg> *no
[10:34] <andyrock> just one more thing: what about a generic error? e.g. network timeout, random error somewhere in the system
[10:34] <Trevinho> flexiondotorg: ok, waiting for a fix c-lobrano fix too, at this point, it shouldn't bother you much if you use the branch as prereq
[10:34] <flexiondotorg> OK, I've not used Bileto as a base before. How do I do that?
[10:38] <mpt> andyrock, I guess that needs a standalone error dialog, since software-properties-gtk might not even be open when the error occurs
[10:39] <andyrock> kk can you provide me the text?
[10:39] <andyrock> mpt: ^^^
[10:43] <mpt> andyrock, how about:
[10:43] <mpt> primary text: Sorry, there’s been a problem in setting up Canonical Livepatch.
[10:43] <mpt> secondary text:  The error was: “%s”
[10:43] <mpt> buttons: Settings… Ignore
[10:44] <tjaalton> FYI, I'm about to move the apport script/links from xdiagnose to xserver-xorg, so that the dependency on xdiagnose can be dropped
[10:44] <tjaalton> I think it has served it's purpose by now
[10:46] <c-lobrano> Trevinho, flexiondotorg: fix for LP 1700100 has all the needed files now :)
[10:46] <andyrock> mpt: can we avoid the secondary text? because it's not easy to get one from canonical-livepatch
[10:47] <andyrock> if it's important I'll fix this
[10:47] <flexiondotorg> c-lobrano Thanks!
[10:47] <mpt> andyrock, hmm, well, it’s hard for a user to fix an error if they don’t know what it is
[10:48] <flexiondotorg> Trevinho If you kick of Bileto I can test from the PPA later.
[10:48] <c-lobrano> ;)
[10:51] <Trevinho> flexiondotorg: cool
[10:52] <Trevinho> thanks a lot c-lobrano
[11:07] <oSoMoN> chrisccoulson, hey, there's a chromium update ready for publication at https://launchpad.net/~canonical-chromium-builds/+archive/ubuntu/stage/+packages
[11:47] <chrisccoulson> oSoMoN, oh, yay
[11:47] <chrisccoulson> thanks
[11:56] <seb128> shrug
[11:56] <seb128> indicator-session landing failed because...
[11:57] <seb128> xnox, could you please stop touching desktop packages if you don't intend to respect the vcs or commit your changes?
[11:59] <xnox> seb128, sure. it would have been useful if desktop team moved indicators-* off url-launcher before feature freeze and enabled landing qt transition earlier instead on the 11th hour post feature freeze
[11:59] <xnox> seb128, feel free to revert/override my uploads as qt transition is done.
[12:00] <seb128> xnox, right, maybe I would have had some cycles for that if I was not busy redoing work and fixing the stuff you did without carring
[12:00] <xnox> yeah, i did mass upload of a few things to chop ubuntu-ui-toolkit which was blocking qt migration in bulk before hoping on a plane.
[12:05] <Beret> xnox, are you the one we can blame for breaking dpi scaling? :)
[12:05] <Beret> seb128, smack him!
[12:05] <xnox> Beret, in what toolkits? unity8 / qtubuntu?
[12:06] <seb128> Beret, GNOME?
[12:06] <Beret> xnox, I was referring to artful (gshell/wayland)
[12:06] <seb128> we changed desktop
[12:06] <Beret> yeah
[12:06] <seb128> Trevinho is working on fixing that
[12:06] <xnox> Beret, sorry did not touch stuff that affects gshell/wayland.
[12:06] <Beret> dang
[12:06] <Beret> seb128, then I decline my offer to hold xnox for you while you punch him in nyc
[12:06] <seb128> lol
[12:07] <xnox> Beret, you seem to make an assumption, that such actions would be considered as punishment by me...
[12:07] <xnox> anyway, offtopic
[12:08] <xnox> seb128, is unity-scopes-api a unity7 or unity8 thing? and does it still need to support clicks, or is that an acceptable degradation?
[12:09] <xnox> seb128, can you fix these to not depend on url-dispatcher?
[12:09] <xnox> $ reverse-depends --list src:url-dispatcher
[12:09] <xnox> indicator-datetime
[12:09] <xnox> indicator-network
[12:09] <xnox> indicator-power
[12:09] <xnox> indicator-sound
[12:09] <xnox> unity-greeter-session-broadcast
[12:10] <xnox> or is unity-scopes-api both?
[12:12] <seb128> xnox, unity8
[12:12] <seb128> I don't have slots to fix those
[12:12] <seb128> but we can add it to the our backlog
[12:13] <jbicha> Beret: I think I'm to blame for dpi scaling by uploading gnome-settings-daemon 3.25.91
[12:13] <Beret> jbicha, we forgive you
[12:13] <Beret> whois jbicha
[12:13]  * Beret hands himself a /
[12:13] <Beret> I must be seriously lagged
[12:14] <Beret> that's the third time I've done that this morning
[12:14] <Beret> I heard fractional dpi scaling was coming at some point too
[12:15] <jbicha> Beret: I think it will be fixed once we get mutter 3.25 but it's blocked because gjs/mozjs52 on armhf doesn't work
[12:16] <jbicha> there's an experimental gsettings for fractional scaling with mutter 3.25.91
[12:16] <Beret> neat
[12:17] <Beret> atm I get around it by specifying my own scaling settings for chrome and spotify
[12:17] <Beret> and letting wayland do the default 2:1
[12:17] <Beret> but smaller title bars would be welcome
[12:17] <Beret> or I guess it's mutter doing it
[12:19] <jbicha> Beret: if you like testing beta stuff, you can use the GNOME3 Staging PPA and set something like
[12:19] <jbicha> gsettings set org.gnome.mutter experimental-features "['scale-monitor-framebuffer']"
[13:18] <gQuigs> anyone mind sponsoring the discussed restricted-extras changes - https://bugs.launchpad.net/ubuntu/+source/ubuntu-restricted-addons/+bug/1709166, please?
[14:20] <oSoMoN> seb128, chrisccoulson : have you seen my e-mail about building chromium dev on trusty and C++14 support?
[14:21] <oSoMoN> does backporting clang 4.0 to trusty sound feasible/desirable, and if so who would take care of it?
[14:21] <seb128> oSoMoN, I didn't, when/where did you send it?
[14:22] <oSoMoN> seb128, to you and chris_ccoulson last Friday
[14:23] <seb128> oSoMoN, sorry but I don't have it, what was the title?
[14:24] <kenvandine> Laney, what's the status of the gnome-software UI for connecting interfaces?
[14:25]  * seb128 wonders why kenvandine is asking about that
[14:25] <kenvandine> seb128, i have a confined snap for gnome-system-monitor which requires interfaces that aren't auto connected :)
[14:25] <seb128> kenvandine, I doubt it's close from being ready to land, and shouldb't be much useful to us anyway since what we want is rather to autoconnect no?
[14:26] <seb128> ah, good luck with that
[14:26] <seb128> why aren't they autoconnected?
[14:26] <kenvandine> it works well though... as long as you make the connections :)
[14:26] <kenvandine> system-observe, hardware-observe, process-control
[14:26] <seb128> they should allow to autoconnect those
[14:26] <kenvandine> g-s-m won't run without those....
[14:26] <oSoMoN> seb128, "C++14 in chromium and trusty support"
[14:26] <kenvandine> they aren't
[14:27] <seb128> what's the point of having a system monitor without those?
[14:27] <kenvandine> indeed
[14:27] <seb128> kenvandine, right, that's why I say we should ask for them to be
[14:27] <seb128> isn't that up to the store team
[14:27] <seb128> to add them to the manifest?
[14:27] <kenvandine> oh... you can ask for them for a specific snap?
[14:27] <seb128> I don't know
[14:28] <kenvandine> :)
[14:28] <seb128> I assume you could
[14:28] <kenvandine> jdstrand, ^^ do you know?
[14:28] <oSoMoN> seb128, just re-sent
[14:28] <andyrock> seb128: I'm taking a look into indicator-datetime
[14:28] <seb128> andyrock, what about it?
[14:28] <andyrock> the building failure
[14:28] <seb128> oSoMoN, I received it this time, thanks
[14:28] <andyrock> seb128: looks like a crash in the tests
[14:29] <seb128> andyrock, k, good, thanks
[14:29] <jdstrand> kenvandine: what's the specific question?
[14:29] <kenvandine> jdstrand, to recap, can we get a specific snap allowed to auto connect to some interfaces?
[14:29] <kenvandine> gnome-system-monitor won't work without system-observe, hardware-observe, process-control
[14:29] <jdstrand> kenvandine: yes... but we've talked about that in general before. what specifically are you wanting?
[14:30] <jdstrand> is this about gnome-24?
[14:30] <kenvandine> jdstrand, no
[14:30] <kenvandine> gnome-system-monitor won't work without system-observe, hardware-observe, process-control
[14:31] <kenvandine> jdstrand, that's another can of worms that i need to get back to :)
[14:31] <jdstrand> kenvandine: ok, so you follow the same process: https://forum.snapcraft.io/t/process-for-reviewing-aliases-auto-connections-and-track-requests/455
[14:31] <kenvandine> cool
[14:31] <jdstrand> kenvandine: this time it won't be contentious
[14:31] <kenvandine> :-D
[14:31] <jdstrand> cause this is all standard stuff
[14:31] <kenvandine> great
[14:31] <kenvandine> it's in the review queue now :)
[14:31] <jdstrand> also, wrt gnome-24, it looks like there is an open question for you guys
[14:32] <kenvandine> i'll triple check each interface that's needed to make sure i'm not asking for more than i need
[14:32] <jdstrand> kenvandine: yes, I'll be going through the queue today
[14:32] <kenvandine> jdstrand, yeah, some of which i'm not sure how to answer really
[14:32] <seb128> jdstrand, I don't understand the question
[14:32] <jdstrand> kenvandine: so I'll get the dbus bit done (assuming it is needed), and then there will be the voting process for the others and I'll issue a snap declaration when the vote is tallied
[14:32] <kenvandine> iirc the issue comes down to the fact that our platform snap is really built for ubuntu, not for any base snap
[14:33] <seb128> the solution was to change the name it seems
[14:33] <kenvandine> dbus is needed for all the gnome apps, the gapplication registration stuff
[14:33] <seb128> changing the name sure, why not
[14:33] <seb128> it's not like it fixes any of the concerns though
[14:33] <seb128> or of the potential problems
[14:33] <jdstrand> kenvandine, seb128: I'd rather not be the middle person again. Please talk to niemeyer in #snappy. I'm happy to watch and participate as needed
[14:33] <kenvandine> jdstrand, yeah... understood
[14:34] <seb128> jdstrand, no worry, I'm not interested in continuing that discussion either, you are the one that mentioned it
[14:35] <jdstrand> seb128: well, today things are blocked. niemeyer tried to come up with a procedure that will help guide people today while the proper solution is implemented. that involves a rename. if you don't rename, nothing will move forward in the short term
[14:35] <kenvandine> seb128, well we should respond in some fashion :)
[14:35] <jdstrand> seb128: so I mentioned it here
[14:35] <seb128> k, well if kenvandine  wants to reply no objection from me
[14:36] <kenvandine> i will later today
[14:36] <seb128> that rename is just stupid nitpicking on details
[14:36] <kenvandine> i need to re-read all that, those brain cells have been recycled :)
[14:36] <seb128> while ignoring all the fundamental problems they argued existed
[14:36]  * jdstrand resists being the middle man
[14:36] <seb128> :-)
[14:36] <kenvandine> seb128, i know how you feel... better for me to respond then :)
[14:36] <kenvandine> less friction :-p
[14:37] <seb128> well I'm not going to reply anyway don't worry
[14:37] <GunnarHj> seb128: Hi! We have a loose end wrt default IM framework for CJKV languages.
[14:37] <GunnarHj> https://trello.com/c/NteXn9nA/161-gnome-and-fcitx
[14:37] <GunnarHj> Has a decision (implicitly?) been made to switch to IBus for 17.10?
[14:37] <seb128> it just feels like he's arguing on a non sense rename now to not say that what we were arguing for was fine
[14:38] <seb128> hey GunnarHj, well GNOME integrates with ibus only so I guess it has been decided implicitly by not having anyone coming with a solution working for fcitx
[14:41] <jbicha> GunnarHj: I thought I heard that fcitx doesn't work with Wayland any way?
[14:41] <jbicha> similar problem as onboard
[14:42] <GunnarHj> seb128, jbicha: Well, deeming from the short list discussion, happyaron seems to think that it would be preferable to keep Fcitx. But whichever route we take, there are a couple of small things, such as which packages to seed, to handle. (I heard about the Wayland issue too.)
[14:45] <GunnarHj> seb128: But if the decision is IBus, I thought I'd have a look at the details with the seed and possibly im-config/language-selector.
[14:46] <seb128> GunnarHj, well, if somebody wants to propose a solution for fcitx it's fine, but that didn't happen, so I think we need to go with ibus?
[14:47] <GunnarHj> seb128, jbicha: That's my understanding too.
[14:49] <GunnarHj> seb128, jbicha: I'll get back to you with a related seed MP.
[14:49] <seb128> GunnarHj, thanks
[14:50] <seb128> jbicha, did you see reports about g-c-c 3.25 segfaulting (maybe 3.24) did as well on the hotspot screen? (in libnm)
[14:50] <jbicha> GunnarHj: fcitx was briefly discussed in #gnome-hackers last week with the conclusion that the only reason ibus integration was so good was because GNOME picked just 1 IM framework to support
[14:50] <seb128> typical GNOME comment
[14:51] <seb128> they don't even understand what the problem is/what the people who ask for the other framework want
[14:51] <jbicha> GunnarHj: it feels to me like it's appropriate for fcitx to drop to universe since it's just not something we can support as well now?
[14:52] <jbicha> seb128: g-c-c 3.25.91 still has lots of crashes, some fixes in git master though I haven't tried to cherrypick yet
[14:53] <seb128> jbicha, that one is in libnm and I tried from trunk
[14:53] <jbicha> we'll need to figure out what package should install the connectivity snippet, I thought we might discuss that in the meeting
[14:56] <GunnarHj> jbicha: As regards Fcitx in main: I would vote for keeping it for now. My understanding is that there is a plan to fix a solution for 18.04, and I have a feeling that many Fcitx users will keep using it one way or another. (Also, all the flavors still have Fcitx as default for CJKV, but that fact is irrelevant for main, of course.)
[14:56] <jbicha> wifi hotspot works here without crashing with 3.25.91 from gnome3-staging ppa
[14:57] <seb128> jbicha, if you change panels from wifi to bluetooth/background and back to wifi
[14:58] <jbicha> it's not crashing for me now, but yes there are some crashes when changing panels with 3.25.91
[14:58] <jbicha> I was impressed by how much nicer 3.25.91 was than 3.25.90 though
[15:02] <seb128> how nicer?
[15:02] <seb128> I didn't see a real difference
[15:02] <seb128> but I guess I don't look much a spacing and alignments tweaks
[15:03] <jbicha> the big wi-fi icon on the Network page is gone and horizontal resizing works a lot better now
[15:30] <seb128> ok, it's meeting time
[15:30] <seb128> #startmeeting Desktop Team 2017-08-29
[15:30] <meetingology> Meeting started Tue Aug 29 15:30:40 2017 UTC.  The chair is seb128. Information about MeetBot at http://wiki.ubuntu.com/meetingology.
[15:30] <meetingology> Available commands: action commands idea info link nick
[15:30] <jbicha> o/
[15:30] <seb128> Roll call: andyrock, dgadomski, didrocks (out), duflu (out), jbicha, jamesh (out), jibel/heber (out), kenvandine, laney, oSoMoN, seb128, tkamppeter, trevinho, robert_ancell (out)
[15:30] <andyrock> hey
[15:30] <kenvandine> o/
[15:30] <oSoMoN> 🐵/
[15:31] <heber> o/
[15:31] <Laney> moin
[15:31] <seb128> ok, quite some people around, let's get started :-)
[15:31] <seb128> #topic andyrock
[15:31] <seb128> andyrock, hey
[15:31] <andyrock> # Proposed branches for artful and xenial for canonical-livepatch, update-manager, update-notifier
[15:32] <andyrock> # Working on sofware-properties (right now the error dialog)
[15:32] <andyrock> # Help debugging a lockscreen issue (sometimes the text-entry field does not appera)
[15:32] <andyrock> # Fixing a build issue with date-time
[15:32] <andyrock> *date-time indicator
[15:32] <andyrock> #eow
[15:33] <seb128> thanks andyrock
[15:33] <seb128> #topic dgadomski
[15:33] <seb128> dgadomski, hey
[15:33] <dgadomski> hey
[15:33] <dgadomski> * verified fix to bug #1702529
[15:33] <dgadomski> * still discussing options for disabling WiFi Direct capabilities for iwlwifi devices (to conform to some Cisco hw settings related to WFD)
[15:33] <dgadomski> * back to examining python performance regression (bug #1638695)
[15:33] <dgadomski> eof
[15:34] <tseliot> Laney: hey, have you had the chance to review my patch?
[15:34] <seb128> thanks dgadomski
[15:34] <seb128> #topic duflu
[15:34] <Laney> tseliot: no sorry (plus I thought upstream was doing it) (also, let's wait until after the meeting)
[15:34] <seb128> * Totem:
[15:34] <seb128>   - Unexpectedly lost a day trying to fix random totem build failures: https://bugzilla.gnome.org/show_bug.cgi?id=786248
[15:34] <seb128>   - Making great progress profiling totem, but its hotspots vary between different video files and between X vs Wayland.
[15:34] <seb128>   - Now focusing on Totem on Wayland where it spends 50% of its CPU rendering GTK/widgets (even in fullscreen where no widgets are visible).
[15:34] <seb128> * Gnome Shell:
[15:34] <seb128>   - Lost a day testing Gnome Shell 3.25/3.26 and comparing app performance. While performance is good, the improvements don't seem to affect totem's own clutter performance problems. I had hoped they were related...
[15:34] <seb128>   - Lost another day chasing down broken colours in Gnome Shell 3.25/3.26 affecting totem and some other apps; https://bugzilla.gnome.org/show_bug.cgi?id=786786
[15:34] <seb128>     . Now fixed, which is good since that pre-emptively unblocks the move to Gnome 3.26
[15:34] <seb128> * Bluez:
[15:34] <seb128>   - Released: https://launchpad.net/ubuntu/+source/bluez/5.46-0ubuntu2
[15:35] <seb128> * PulseAudio:
[15:35] <seb128>   - Almost released?: https://launchpad.net/ubuntu/+source/pulseaudio/1:8.0-0ubuntu3.4
[15:35] <seb128> * Video acceleration:
[15:35] <seb128>   - Public announcement about out-of-box support is still blocked awaiting: https://bugs.launchpad.net/ubuntu/+source/ubuntu-restricted-addons/+bug/1709166
[15:35] <seb128> * Awaiting sponsorship:
[15:35] <seb128>   - https://bugs.launchpad.net/ubuntu/+source/ubuntu-restricted-addons/+bug/1709166  (FFE now?)
[15:35] <seb128>   - https://launchpad.net/ubuntu/+source/pulseaudio/1:8.0-0ubuntu3.4
[15:35] <seb128> * Daily bug management across gnome-shell, gdm, ubuntu-themes, bluez, pulseaudio and mir.
[15:35] <seb128>  
[15:35] <seb128> if somebody knows about ubuntu-restricted-addons and want to review/sponsor that one ^
[15:36] <seb128> ok, I hope it's done copying
[15:36] <seb128> let's move on
[15:36] <seb128> #topic jbicha
[15:36] <seb128> jbicha, hey
[15:36] <jbicha> • split packages for better behavior with GNOME Software (gedit-plugins, eog-plugins, evolution)
[15:36] <jbicha> • fixed libxcursor packaging regression
[15:36] <jbicha> • Lots of GNOME 3.25.91 work for Feature Freeze
[15:36] <jbicha> • Filed some late MIRs for GNOME apps LP: #1713171 LP: #1713176
[15:36] <jbicha> • GTK 3.22.19 with cherry-picked regression fix LP: #1712701
[15:36] <jbicha> • Uploaded james_h's Captive Portal work, uploaded the -ubuntu connectivity package
[15:36] <jbicha> • Became a Debian Developer
[15:36] <jbicha> eof
[15:37] <seb128> congrats on becoming a Debian Developer!
[15:37] <kenvandine> jbicha, congrats!
[15:37] <seb128> and nice work on the MIRs/FFe/updates
[15:37] <seb128> thanks jbicha
[15:37] <seb128> #topic jamesh
[15:38] <seb128> snapd: Initial polkit patch was accepted to master.  I've put together
[15:38] <seb128> two more PRs that build on top of it that are listed on the review
[15:38] <seb128> sprint.  When running snapd with these patches, I was able to install
[15:38] <seb128> snaps via gnome-software without providing Ubuntu One credentials.
[15:38] <seb128> snapd-glib: wrote a small pull request to handle the
[15:38] <seb128> X-Allow-Interaction header added by one of the new snapd PRs.
[15:38] <seb128> fonts for snaps: created a PR to add empty directories to the core
[15:38] <seb128> snap as mount points for system fonts.
[15:38] <seb128> gnome-control-center: started looking at hooking whoopsie up to the
[15:38] <seb128> privacy control panel using the existing UI for ABRT
[15:38] <seb128>  
[15:38] <seb128> #topic jibel/heber
[15:38] <heber> hey! QA updates:
[15:38] <heber> * In depth, manual review of the installer (live session, oem configuration, disk partitioning, …)
[15:38] <heber> * Tested wayland session by default (new installation and upgrade from Zesty)
[15:38] <heber> * Fixed update-manager on wayland in Artful and SRU to Zesty
[15:38] <heber> * Fixed Ubiquity OEM mode in Artful
[15:38] <heber> * Dealing with failing upgrade tests in QA lab
[15:38] <heber> * Performed SRU verification of gnome-software, appstream-glib, gnome-logs, update-notifier, update-manager
[15:39] <heber> * Fix cleaning up functions for VMs in utah and upgrade jobs.
[15:39] <heber> * Analyze/fix failing jobs for Artful in MaaS.
[15:39] <heber> * Identify/Automate default apps tests.
[15:39] <heber> EOF
[15:39] <seb128> heber, hey, and thanks
[15:39] <seb128> #topic kenvandine
[15:39] <seb128> kenvandine, hey
[15:39] <kenvandine> * Built a classic snap for gnome-system-monitor, which I just got working with strict confinement but requires manually
[15:39] <kenvandine>  connecting some interfaces.  This is awaiting review in the store now.
[15:39] <kenvandine>   - I need to create a forum thread to request it be auto-connected to some interfaces
[15:39] <kenvandine> * Built confined eog snap, mostly works and published to edge channel.  Thumbnails aren't working, which I think I've traced down to mimetype query fails.  Looking into a way to fix that.
[15:39] <kenvandine> * Did some testing of theme fixes, thanks Trevinho!  I think I still owe a review on one of them, I'll double check.
[15:39] <kenvandine> eof
[15:40] <kenvandine> that first point was i started with a working classic snap for g-s-m :)
[15:40] <kenvandine> now it's confined
[15:40] <kenvandine> or i first created it as a classic :)
[15:41] <seb128> kenvandine, done?
[15:41] <kenvandine> yup
[15:41] <seb128> thanks kenvandine!
[15:41] <seb128> #topic laney
[15:41] <seb128> Laney, hey
[15:42] <Laney> HI
[15:42] <Laney> • short week, public holiday monday
[15:42] <Laney> • fixed some gnome-software bugs, uploaded the latest release, got it into artful
[15:42] <Laney> • some testing of NM connectivity checker, found/backported a curl patch to fix some things there
[15:42] <Laney> • some mozjs52/armhf debugging / investigating with upstream
[15:42] <Laney> • console-setup: a bit more work on the patch, that got uploaded
[15:42] <Laney> • autopkgtest:
[15:42] <Laney> ∘ bump the inotify limit for lxd/lxc workers
[15:42] <Laney> ∘ look at why zesty is erroring when collecting data for the web UI - problem with the swift servers, reported to IS
[15:42] <Laney> ∘ possibly something going on with building new images, investigating that with slangasek atm
[15:42] <Laney> • poking at stuff in proposed to get it to migrate
[15:42] <Laney> • start looking at XDG_DATA_DIRS problems in wayland (Xsession.d stuff), probably need a couple of snippets there
[15:42] <Laney> 💨
[15:43] <seb128> Laney, some of the snappy team people are working on the XDG_DATA_DIRS, you should maybe comment if you want to change the outcome before commit
[15:43] <seb128> thanks Laney
[15:43] <Laney> it's not just for snap
[15:43] <Laney> like the /usr/share/$DESKTOP_SESSION thing
[15:43] <seb128> ah, right, sorry
[15:43] <seb128> yeah, we have a trello card about that, maybe add yourself to it :-)
[15:43] <kenvandine> also sound themes are broken
[15:43] <Laney> I assigned myself to the bug
[15:43] <seb128> thanks Laney
[15:44] <Laney> np
[15:44] <seb128> kenvandine, report a bug if there isn't one
[15:44] <seb128> #topic oSoMoN
[15:44] <seb128> oSoMoN, hey
[15:44] <kenvandine> there is
[15:44] <oSoMoN> hey team
[15:44] <oSoMoN> • Updated chromium stable to 60.0.3112.113, ready for publication in staging PPA.
[15:44] <oSoMoN> • Updated chromium beta to 61.0.3163.59, now building for all supported series with is_component_build=false and is_official_build=true.
[15:44] <oSoMoN> • Updated chromium dev to 62.0.3192.0 and spent a fair amount of time and energy to get it to build on trusty, unsuccessfully. Started conversation to decide the way forward to continue supporting trusty with newer chromium releases.
[15:44] <oSoMoN> • Investigated libreoffice 5.4 autopkgtest failures on non x86-64, tracked down to architecture-dependent file that was being installed by an arch-indep package (bug #1712873), fix will go into 5.4.1, to be released this week.
[15:44] <oSoMoN> • Investigating libreoffice 5.4.0 snap issues (bug #1713730 and bug #1713742)
[15:44] <oSoMoN> • That's all folks 🐰
[15:45] <seb128> thanks oSoMoN, good work
[15:45] <seb128> do you know how libreoffice migrated out of proposed with the test issue?
[15:45] <seb128> did somebody forced it through?
[15:45] <oSoMoN> I assumed you did :)
[15:46] <seb128> no I didn't, I guess somebody wanted to force poppler in or something
[15:46] <seb128> anyway good for us :-)
[15:46] <jbicha> webkit2gtk will require a newer gcc to build on xenial (for the 2.20 cycle I believe) so I'm interested to see what happens with trusty
[15:46] <seb128> thanks
[15:46] <seb128> #topic seb128
[15:46] <seb128> * one vac day
[15:46] <seb128> * reported some upstream bugs
[15:46] <seb128> * started changing indicators to use langpacks again from universe
[15:46] <seb128> * debugged/fixed g-s-d notifications not displaying translated
[15:46] <seb128> * debugged a g-c-c segfault
[15:46] <seb128> * investigated reports about glib-compile-schemas issues, figured out a testcase/got a valgrind log of an error
[15:46] <seb128> * triaged recent launchpad reports and some of the nautilus backlog

[15:46] <seb128> #topic tkamppeter
[15:47] <seb128> tkamppeter, hey
[15:47] <tkamppeter> - cups-filters: Added PCLm support from the GSoC student project. Now we have full support for driverless printing with all known standards, especially also on Mopria and Wi-Fi Direct printers. Also improved the handling of reolutions reported by driverless printing, especially to work around firmware bugs. Released cups-filters 1.17.2.
[15:47] <tkamppeter> - CUPS: Reported 2 crash bugs upstream which caused around 20 reports each on errors.ubuntu.com. These bugs got fixed upstream then. Backported the patch to the Debian package of CUPS and synced the package (with additional bug fixes) to Ubuntu.
[15:47] <tkamppeter> - Google Summer of Code 2017: The coding period ended today and the student had to make a final web presentation of their work. Reviewed the presentations of the 7 OpenPrinting students. They will all pass the final evaluation and we will soon work on the upstream integration of the projects (PCLm support I have already integrated, see above).
[15:47] <tkamppeter> - Bugs.
[15:47] <seb128> thanks tkamppeter
[15:47] <seb128> #topic trevinho
[15:47] <seb128> Trevinho, hey
[15:48] <seb128> maaarcccoooo
[15:48] <tkamppeter> seb128, sorry, I meant 20 crash reports/day each.
[15:49] <seb128> tkamppeter, no worry, good work in any case :-)
[15:49] <seb128> no Trevinho I guess
[15:49] <seb128> #topic robert_ancell
[15:49] <seb128> - gnome-software 3.20.5-0ubuntu0.16.04.6 and 3.22.7-0ubuntu3.17.04.7 SRUs uploaded.
[15:49] <seb128> - snapd-glib 1.17 released with fixes for threaded apps
[15:49] <seb128> #topic AOB
[15:49] <seb128> did I forget anyone? any other topic?
[15:50] <jbicha> I have some AOB
[15:50] <jbicha> gnome-control-center 3.25.91 blocked on rebasing network-proxy and dock-settings patches
[15:50] <jbicha> GNOME Shell is held up by mozjs52 being broken on armhf
[15:50] <jbicha> One temporary workaround would be to remove gjs 1.49 (and a few rebuilds) from -proposed since gnome-shell 3.25.91 still works with gjs 1.48/mozjs38
[15:51] <seb128> one topic at time
[15:51] <seb128> is the rebasing difficult?
[15:51] <seb128> I can help and look at rebasing the dock settings tomorrow
[15:51] <Trevinho> seb128: sorry, I missed my moment...
[15:51] <jbicha> I looked at rebasing the network-proxy patch but what I came up with crashed :|
[15:51] <Trevinho> Working in mutter, fixing issues with small text in fractional scaling and wallpaper issues
[15:52] <seb128> Trevinho, wait, I come back to your after the aob
[15:52] <Trevinho> ah ok
[15:52] <seb128> jbicha, your patch is in the branch you pushed?
[15:52] <jbicha> not yet but I'll go ahead and push there after meeting
[15:52] <seb128> thanks
[15:52] <seb128> I can help with that tomorrow
[15:52] <seb128> about gjs I didn't try to follow muhc
[15:53] <seb128> Laney do you understand the situations and our options?
[15:53] <seb128> if so does what jbicha suggested makes sense to you?
[15:53] <jbicha> GNOME bug is at https://bugzilla.gnome.org/786578 if you want to read up later
[15:54] <seb128> k
[15:54] <Laney> it's probably ok for now but I think it should be fixed before the release
[15:54] <Laney> we can't be blocked on an old mozjs
[15:54] <seb128> right
[15:54] <seb128> well let me know if you need an archive admin
[15:54] <Laney> yes
[15:54] <seb128> I'm happy to enter commands as needed
[15:54] <Laney> jbicha will presumably tell you what to delete
[15:55] <seb128> k
[15:55] <jbicha> ok
[15:55] <seb128> that seems on track then
[15:55] <seb128> jbicha, did you want to discuss the connectivity changes as well?
[15:55] <jbicha> What should pull in the connectivity package? LP: #997200
[15:55] <Laney> seed it?
[15:55] <jbicha> I am proposing we add it to the desktop-common seed
[15:55] <jbicha> as a Depends
[15:56] <seb128> why depends and not recommends?
[15:56] <jbicha> it provides the URL that is needed for gnome-control-center's Privacy settings to work
[15:56] <seb128> (unsure why I ask since I don't have a strong opinion either way)
[15:56] <seb128> k
[15:56] <Laney> wait
[15:56] <Laney> work in what way?
[15:56]  * seb128 waits
[15:57] <jbicha> it can be disabled with a simple 2-line /etc file if someone doesn't run gnome-control-center
[15:57] <jbicha> Captive Portal needs a URL to work so I think if there is no URL configured, g-c-c will lie and say it's turned on?
[15:58] <Laney> umm
[15:58] <Laney> I think g-c-c should rather hide the row in that case
[15:58] <jbicha> why would we want someone to not have the URL pre-configured?
[15:59] <Laney> it sounds like your rationale is to work around a bug in the control-center
[15:59] <jbicha> we could make a separate package with that 2-line snippet to disable if that would make people feel better
[16:00] <jbicha> is desktop-common the right place for at least a recommends?
[16:01] <Laney> probably the same place network-manager is seeded
[16:02] <seb128> wfm
[16:03] <jbicha> I think NM is seeded individually in all the desktop flavors
[16:04] <jbicha> lubuntu-next briefly switched to some other networking stack this cycle but it broke so they are back on NM
[16:05] <jbicha> the snippet doesn't hurt anything if NM isn't installed
[16:05] <seb128> I don't have any opinion either way
[16:05] <seb128> maybe you and Laney decide after the meeting
[16:05] <seb128> I don't think we need to discuss it more in the meeting?
[16:05] <jbicha> ok, we can talk more later
[16:05] <seb128> thanks
[16:05] <seb128> any other topic?
[16:05] <jbicha> how about dropping onboard from the default install?
[16:06] <seb128> +1
[16:06] <seb128> it doesn't work with wayland
[16:06] <seb128> maybe we get it back next cycle
[16:07] <jbicha> and my final AOB is just pinging about our outstanding MIRs
[16:07] <seb128> it's a bit tricky to get mir reviuew cycle; I will see if I can buy somebody some beers to help
[16:08] <seb128> thanks again for filling those!
[16:08] <jbicha> ok, that's it for me, thanks for your patience
[16:08] <Trevinho> seb128: can I go now?
[16:08] <seb128> np, thanks for pushing us forward
[16:08] <seb128> #topic Trevinho
[16:08] <seb128> Trevinho, yes
[16:08] <Trevinho> · Mutter for fractional scaling: fixed wallpaper positioning, and text rendering
[16:08] <Trevinho>                                  working in some issues with offscreen animations
[16:08] <Trevinho> · Some debugging for indicators support in gnome shell, discussions about tray
[16:08] <Trevinho> · Worked in some changes for appindicator GS extension
[16:08] <Trevinho> · Theme fixes for destructive action in ambiance/radiance
[16:08] <Trevinho> · Review of theme changes and landed them
[16:08] <Trevinho> · Tests for $other_project
[16:09] <Trevinho> :motor_scooter:
[16:09] <Trevinho> and sorry for missing the moment :)
[16:09] <seb128> thanks Trevinho
[16:09] <seb128> no worry
[16:09] <seb128> is transmission supposed to work with the appindicator extension?
[16:09] <seb128> seems not here when I tried
[16:09] <jbicha> Trevinho: why is fractional scaling hidden behind an experimental gsettings value?
[16:09] <Trevinho> seb128: yep, once you enable the setting
[16:09] <Trevinho> jbicha: cause there are some issues we're still fixing
[16:10] <seb128> I tried to enable the setting, going to try again later
[16:10] <seb128> thanks Trevinho
[16:10] <Trevinho> jbicha: such as gnome shell thing being blurry as not properly rendered
[16:10] <seb128> and I think on that note it's a wrap
[16:10] <seb128> thanks everyone
[16:10] <seb128> #endmeeting
[16:10] <meetingology> Meeting ended Tue Aug 29 16:10:19 2017 UTC.
[16:10] <meetingology> Minutes:        http://ubottu.com/meetingology/logs/ubuntu-desktop/2017/ubuntu-desktop.2017-08-29-15.30.moin.txt
[16:10] <jbicha> Trevinho: do you know how likely it is for that to be enabled by default for 3.26? if not, does it make sense for Ubuntu 17.10 to enable it?
[16:10] <Trevinho> we can backport the fixes if we want and enable it later
[16:10] <Trevinho> jbicha: we wanted to, but I've been a little slow in some things as I had other things to cover too....
[16:11] <Trevinho> so, we can try to backport the changes in case
[16:11] <Trevinho> and not enabling by default, but enabling it early next cycle
[16:11] <jbicha> ok
[16:11] <Trevinho> even before moving to the final gnome version we want for the LTS
[16:12] <Trevinho> cool
[16:14] <jbicha> seb128: removal list: gjs, gnome-sushi, gnome-weather
[16:21] <Laney> jbicha: ok, I just removed config-connectivity-{debian,ubuntu} and the row is hidden as I would expect
[16:21] <Laney> so imho seed it alongside network-manager and let each flavour decide if they want it
[16:21] <Laney> in checking that I noticed that we seed nm-gnome; is that right or should it be nm?
[16:25] <seb128> jbicha, k
[16:26] <jbicha> I'll do some more checking on nm-gnome; Debian & Ubuntu GNOME still pulls it in but maybe g-c-c doesn't need it any more
[16:28] <jbicha> that's interesting that Ubuntu Desktop only ends up recommending NM, Ubuntu GNOME had a Depends on NM
[16:58] <jbicha> oh, g-c-c depends on nm-gnome which depends on nm
[17:09] <jbicha> seb128: g-c-c 3.25 still has a few places it tries to run nm-connection-editor
[17:10] <jbicha> we could still change the seed from nm-gnome to nm and just let g-c-c take care of its dependency
[18:16] <dobey> seb128, Trevinho: you can land that if you want i guess, but i would expect that stuff to drop into universe for 17.10, and then out of archive by 18.04
[18:46] <amano> Cairo 1.15.8 is out with emoji support. Maybe something to consider. The last missing part would be a color emoji font. Low hanging fruit?
[18:47] <jbicha> amano: we also need an unreleased fontconfig
[18:48] <jbicha> but the 2 parts you mentioned aren't "low hanging fruit"
[18:48] <jbicha> cairo 1.15 is the dev branch and would definitely need a Feature Freeze Exception
[18:49] <jbicha> *it would need a FFe if we were going to consider it
[18:50] <jbicha> it's a good goal for 18.04
[18:50] <amano> Np ;)
[19:42] <seb128> jbicha, I'm not sure to understand your comment from earlier, you consider nm-connection-editor as deprecated?
[19:44] <jbicha> seb128: g-c-c still needs nm-connection-editor which is provided by nm-gnome
[19:44] <seb128> ok
[20:34] <ahasenack> hi guys, I was looking at https://bugs.launchpad.net/ubuntu/+source/nmap/+bug/1713274
[20:35] <ahasenack> basically the desktop file for zenmap calls su-to-root, which is in the menu package, but there is no dependency on said package
[20:35] <ahasenack> I was just wondering if there are other implications in installing the "menu" package in a desktop nowadays
[20:35] <ahasenack> considering gnome-shell specifically, in artful
[20:46]  * ahasenack finds the big list at https://bugs.launchpad.net/ubuntu/+source/nmap/+bug/1713311