[01:34] <JanC> seems like upgrades to 16.04 don't install the breeze theme for LibreOffice?
[05:03] <hikiko> Hi
[05:44] <pitti> Good morning
[06:40]  * ricotz welcomes yakkety
[06:41] <pitti> my dictionary fails on that -- I suppose that's just some made-up and phonetically nice word, yes?
[06:41] <pitti> a yak alliteration
[06:41] <ricotz> haven't investigated it yet ;)
[06:41] <flocculant> pitti: "just catching up on everything...nothing important "
[06:42] <pitti> flocculant: that's what "yakkety" means?
[06:42] <flocculant> and some really old song that infinity remembers :p
[06:42] <flocculant> yup
[06:42]  * pitti still votes for rolling in between LTSes :)
[06:42] <ricotz> ah, so still a placeholder?
[06:43] <flocculant> I said it to tsimon in xubuntu-offtopic when I failed to come up with a yy name for me to use :)
[06:43] <pitti> no, that adjective is settled -- https://launchpad.net/ubuntu/yakkety
[06:43] <flocculant> ricotz: yea :)
[06:43] <ricotz> pitti, I see
[06:43] <flocculant> pitti: LOL
[06:44] <ricotz> "Yakkety yakkety yakkety yakkety yakkety yakkety yakkety yakkety yak. Naturally 🙂"
[06:44] <ricotz> by quoting http://www.markshuttleworth.com/archives/1496
[06:44]  * flocculant is prescient ... "<flocculant> it's still on the w spec for someone to copy to the yakkity yak one" from weeks ago :p
[06:45] <pitti> we all pretty much agreed on the yak :)
[06:45] <pitti> but I suppose there's no adjective sufficiently close to shaving that starts with y :)
[06:46] <ricotz> heh
[07:49]  * Sweet5hark takes out the papers and the trash!
[07:56] <seb128> good morning desktopers
[07:56] <seb128> hey Sweet5hark
[07:56] <pitti> bonjour seb128 ! wie gehts/
[07:56] <seb128> salut pitti! sehr gut, danke! und dir?
[07:57] <pitti> seb128: prima, danke!
[07:57]  * pitti feels very yakkety
[07:57] <seb128> was a name announced?
[07:57] <pitti> seb128: yes, although a lot less funny post than usual: http://www.markshuttleworth.com/archives/1496
[07:58] <seb128> lol
[07:58] <seb128> no fun, infity/the guys at the office had it right :p
[07:58] <seb128> it's not usual that Mark picks something suggested by others!
[07:58] <Sweet5hark> https://www.youtube.com/watch?v=E6-2eXjx-h0 looping here
[07:59] <pitti> seb128: I guess the yak was pretty much without alternative anyway
[07:59] <seb128> yeah, but "yakkety" could have been changed ;-)
[07:59]  * seb128 is facing the dilemna about what to do with his laptop
[07:59] <seb128> I guess I'm going to stick to the LTS until .1
[08:00] <seb128> or at least a bit to get some SRUs going
[08:00] <pitti> VMs FTW!
[08:02] <willcooke> morning seb128 pitti
[08:02] <pitti> hey willcooke
[08:02] <larsu> morning! Congrats on the release!
[08:02] <pitti> hey larsu, thanks!
[08:02] <seb128> hey willcooke, had a good trip back yesterday?
[08:02] <seb128> hey larsu, thanks!
[08:03] <larsu> also, yakkety yak is a *perfect* ubuntu name
[08:03] <seb128> pitti, right, but you don't end up using VMs much, you just spawn them for quick testing
[08:03] <seb128> ;-)
[08:03] <willcooke> seb128, met an old school friend after the office, so didnt get home till late
[08:03] <seb128> pitti, I can as well build/test apps on xenial and downgrade back then
[08:03] <pitti> seb128: yeah, but that seems alright for you for doing yakkety stuff until .1?
[08:03] <Sweet5hark> FWIW, me does all testing on VMs (and building on pbuilders) ... -- currently having 11 VMs (sized for LibreOffice) which brings the 512GB SDD to its limits sometimes ...
[08:03] <seb128> willcooke, oh ok, nice, at least you celebrated xenial :-)
[08:04] <willcooke> seb128, :)
[08:04] <larsu> Sweet5hark: I hope some of those are nested... :P
[08:04] <larsu> that's where the fun comes in
[08:04] <seb128> pitti, I usually don't even bother doing VM, I do my merges on n-1 and test there and then downgrade, at least for GNOME apps and such, like if it's the same upstream version and just merges not a lot can go wrong
[08:05] <pitti> n-1?
[08:05]  * flexiondotorg fears the Yak shaving jokes.
[08:05] <willcooke> morning Sweet5hark larsu
[08:05] <willcooke> flexiondotorg, :)  I can't work out if that's real or epic troll
[08:05] <flexiondotorg> willcooke, I hope a troll.
[08:05] <flexiondotorg> Youthful Yucatan anyone?
[08:06] <flexiondotorg> Has the advantage it's a squirrel, so no artwork changes.
[08:06] <willcooke> :D
[08:06] <flexiondotorg> And no last minute scramble with the design team ;-)
[08:07] <seb128> pitti, yak-1 = xenial :p
[08:07] <Sweet5hark> larsu: precise64, trusty64, vivid64, wily64, xenial64, ooo33, aoo411, debian, snappy, vagrant_default..., allsnaps. I guess some could be cleaned up by now ...
[08:08]  * larsu is impressed
[08:08] <flexiondotorg> willcooke, not a troll. Syncs have started to yakkety.
[08:09]  * Sweet5hark needs to add yakety yak to technical.dic. Totally a technical term right now.
[08:10] <ara> willcooke, seb128: hello!
[08:10] <ara> willcooke, seb128: did we remove browsing files using BT in xenial on purpose?
[08:10] <seb128> hey ara
[08:11] <seb128> ara, removed from where compared to what?
[08:12] <ara> seb128, if you open set up a mobile device over BT, you no longer have the option to browse the files in the phone
[08:12] <ara> seb128, you are able to send or receive files, but not browse the contents
[08:13] <seb128> ara, was that working and in what ubuntu version? 14.04? 15.10?
[08:14] <seb128> ara, and what were you using to browse them, nautilus?
[08:14] <seb128> ara, please provide some details
[08:14] <ara> seb128, 14.04 for sure, no sure about wily sorry
[08:14] <ara> seb128, using the indicator
[08:14] <seb128> the indicator is only a menu
[08:14] <seb128> it never provided some "browsing UI"
[08:15] <seb128> so I guess it was calling from some external program
[08:19] <ara> hey chih
[08:19] <seb128> hey chih
[08:19] <ara> seb128, chih is the one reporting this issue, he will be able to give you more details
[08:19] <chih> hello seb128
[08:19] <seb128> ara, thanks
[08:19] <seb128> chih, what did you use to browse those shares with? nautilus
[08:19] <seb128> is that using obex?
[08:20] <chih> seb128, using obex is fine. it is through gui tool that has issues
[08:20] <seb128> what gui?
[08:20] <chih> seb128, bluetooth-setting?
[08:21] <seb128> bluetooth-setting is not a thing
[08:21] <seb128> we don't have such codebase/app/project
[08:21] <seb128> nor ever did
[08:21] <chih> seb128, right. need to be more precise. hold on.
[08:21] <seb128> can you just describe/screenshot/screencast what you did on 14.04?
[08:23] <seb128> did you use to browse your phone with nautilus over obex?
[08:23] <seb128> is that what this is about?
[08:23] <chih> seb128, unity-control-center bluetooth
[08:23] <seb128> that's the config panel
[08:23] <seb128> it allows to pair device
[08:23] <seb128> it never had a file browser included
[08:24] <chih> seb128, we used another pc to file browsing
[08:24] <seb128> ok, that's getting nowhere
[08:25] <seb128> please provide a screencast of what you are doing on the old Ubuntu
[08:25] <seb128> or tell me what application is used for browsing
[08:25] <chih> seb128, sure. we should have prepared for this
[08:25] <seb128> or is the app that secret that nobody wants to share its name? ;-)
[08:25] <chih> seb128, let us find it out for you.
[08:25] <seb128> thanks
[08:25] <chih> seb128, sure
[08:26] <seb128> chih, ara, I expect you are using nautilus and being bitten by http://www.hadess.net/2011/11/obexftp-in-gnome-non-update.html / https://bugzilla.gnome.org/show_bug.cgi?id=745621
[08:26] <ubot5`> Gnome bug 745621 in [obsolete] obexftp backend "remove obsolete obexftp code" [Normal,Resolved: fixed]
[08:27] <chih> seb128, need to go attend a call now. i am having another team member check with you on this issue.
[08:28] <seb128> k
[08:30] <kristinchuang> seb128: ping
[08:30] <seb128> lol
[08:30] <seb128> hey kristinchuang ;-)
[08:31] <kristinchuang> seb128: hello :)
[08:31] <kristinchuang> seb128: I'm here to provide some info on debugging the BT browsing function :)
[08:32] <seb128> kristinchuang, can you screenshot/screencast what you used to do which worked? or give me the name of the application doing the browsing (is that nautilus?)
[08:34] <kristinchuang> seb128: do you mean the application that's supposed to be doing the actual browsing (i.e. showing all the files to be browsed)? Yes that's nautilus
[08:34] <seb128> k
[08:34] <seb128> thanks, that's all I wanted
[08:34] <kristinchuang> seb128: but I haven't been able to reach the step where nautilus is launched though
[08:34] <seb128> kristinchuang, so I think your issue is https://git.gnome.org/browse/gvfs/commit/?id=606ef241fb8677528bd5d5526854658f0f298a2c
[08:34] <seb128> see http://www.hadess.net/2011/11/obexftp-in-gnome-non-update.html
[08:35] <seb128> and https://bugzilla.gnome.org/show_bug.cgi?id=757901
[08:35] <ubot5`> Gnome bug 757901 in [obsolete] obexftp backend "Resurrect obexftp backend" [Normal,New]
[08:35] <seb128> basically that feature was buggy and non maintained and didn't work with bluez5
[08:35] <seb128> so they removed it
[08:44] <kristinchuang> seb128: I see......thanks! Let me go get engineers involved first and get back to you later :D
[08:44] <seb128> kristinchuang, yw!
[08:44] <seb128> kristinchuang, sorry but it's not going to be an easy fix
[08:50] <kristinchuang> seb128: :D oops so this means that there's no confirmed schedule for the resurrection yet right?
[08:51] <seb128> kristinchuang, correct, nobody seems to work on it
[08:51] <seb128> there is a patch on the bug I pointed out
[08:51] <seb128> but it got one review and has been sitting there since
[08:53] <kristinchuang> seb128: ok got it. Thanks for the info!
[08:53] <seb128> yw!
[08:55] <Laney> meow
[08:55]  * Laney is running yakkety
[08:55] <Laney> it's reaalllly stable
[08:55] <willcooke> :D
[08:57] <pitti> hey Laney
[08:57] <Laney> hey pitti!
[08:57] <pitti> Laney: ooh, any kool new features yet? :-)
[08:58] <Laney> shiny png transition to get your teeth into :P
[08:59] <pitti> Laney: oh, that actually has new packages already?
[08:59]  * pitti had assumed it would need a new toolchain first
[08:59] <Laney> https://launchpad.net/ubuntu/yakkety/+queue?queue_state=1&queue_text=
[08:59] <Laney> soon
[09:00] <pitti> then I guess I'll do my traditional debhelper merge today :)
[09:01] <Laney> yeah, you can put stuff in the queue
[09:01] <pitti> Laney: but still working on charming up lxd workers, so that we can move armhf to scalingstack
[09:01] <Laney> w00t
[09:01] <pitti> finally, some actual development after this crazy week :)
[09:01] <pitti> Laney: put more eggs into that brittle basket :-P
[09:02] <seb128> hey Laney
[09:02] <seb128> Laney is the opposite of me :p
[09:03]  * seb128 sticks to the LTS and intend to SRU strongly in the next weeks
[09:03] <seb128> no yak to shave here!
[09:04] <seb128> willcooke, btw any though as what as a team we should focus on in the next weeks? unsure if we should have a team focus or just let people go crazy on what they prefer doing ;-)
[09:04] <seb128> Laney, where did you guys go to eat btw?
[09:06] <Laney> seb128: the diner place
[09:06] <willcooke> seb128, not sure I follow you.  Sprint next week where I we can discuss goals etc - or do you mean something else?
[09:06] <Laney> pitti: charming> where's juju involved in that part?
[09:07] <Laney> using juju to manage lxd?
[09:07] <pitti> Laney: we need autopkgtest-cloud-worker to be able to start workers with an lxd configuration
[09:07] <seb128> Laney, the one place where you can get dinner in London? ;-)
[09:07]  * seb128 hides
[09:07] <Laney> one n!
[09:07] <pitti> Laney: hand it a list of "architecture IP #workers"
[09:07] <Laney> the place up the road
[09:07] <Laney> where we got a free meal
[09:08] <seb128> oh, I see!
[09:08] <seb128> fancy
[09:08] <seb128> :-)
[09:08] <Laney> I had an "american breakfast"
[09:08] <Laney> was good
[09:08] <seb128> was the free meal coupon still valid?
[09:08] <pitti> Laney: and it sets up the correspondig remotes, uses a different worker.conf, and call lxd on these remotes instead of ssh/nova
[09:08] <seb128> oh
[09:08] <seb128> that one
[09:08] <seb128> gotcha
[09:08] <pitti> Laney: I also want to create a separate machine/service for the lxd controllers; the nova autopkgtest-worker service/machine is loaded enough already
[09:08] <pitti> (controller, just one for now)
[09:09] <seb128> willcooke, no, I was just wondering how we put the balance between LTS work/stabilization/SRU and new yakky crazyness, but I guess that's a good topic for next week
[09:09] <pitti> Laney, seb128: you guys are back home now?
[09:09] <seb128> pitti, I am
[09:09] <Laney> pitti: ah right, I just thought you would teach the existing one how to do lxd too
[09:09] <seb128> was only in London for one day
[09:09] <Laney> pitti: nope, but I'm going to head back in the day today
[09:09] <pitti> Laney: yeah, it's the same charm, but it needed some extension for all this
[09:09] <pitti> Laney: just boring plumbing for the most part, but it needed to be done :)
[09:11]  * pitti still needs some time to train his fingers to write juju-1 instead of juju, argh
[09:11] <Laney> hehe
[09:11] <Laney> alias juju=juju-1 :P
[09:11] <willcooke> seb128, gotya.  There are a couple of clear issues in X that need sorting around g-s and the missing menus issue which we should get on, but I think we can afford a day of playing :)
[09:12] <seb128> yeah
[09:12] <seb128> well, playing is fine
[09:12] <seb128> I guess people who update still have the LTS in a vm and can work on SRUs there
[09:12] <Laney> that stuff is going to be fixable in both
[09:14] <seb128> yeah, it's just that we have a big stack of things worth SRUing and probably more are going to be reported
[09:14] <willcooke> I think over the next, say, 6 weeks, we'll spot the really common issues
[09:14] <seb128> maybe se should a sub/virtualteam focussed on .1
[09:15] <seb128> we did that after some previous LTSes (precise(iirc?) had a formal virtual team with explicit goal to work on .1)
[09:15] <seb128> +get
[09:15] <willcooke> and get people from kernel, etc etc as part of that team?
[09:15] <seb128> yes, we have 1/2 person of each team, kernel/foundation/desktop/qa
[09:16] <seb128> had*
[09:17] <willcooke> davmor2, jibel - how would you guys be fixed for some additional 16.04 QA over the next couple of months?
[09:17] <willcooke> and then maybe CC cyphermox and/or xnox? ^
[09:17] <willcooke> or pitti?
[09:17]  * willcooke volunteers all the people 
[09:18] <seb128> :-)
[09:18] <willcooke> I'll speak to Steve of course
[09:18] <seb128> yeah, let's see, I don't know if that's compatible with the objective/focus for next cycle
[09:18] <seb128> e.g if we can manage to officially redirect that bunch of people to the .1
[09:18] <seb128> but it would be nice if we could :-)
[09:18] <willcooke> worth exploring for sure
[09:19] <willcooke> I think NM will need some love
[09:19] <seb128> for sure
[09:19] <willcooke> xorg / fglrx
[09:19] <willcooke> ubiquity
[09:19] <willcooke> snapd
[09:19] <willcooke> ;)
[09:19] <seb128> :-)
[09:20] <willcooke> maybe bluez?  Seems ok so far, but OEM might want some work of theirs SRUing?
[09:23] <seb128> yeah, let's see what's the feedback/reports in the next weeks or so
[09:24] <willcooke> sounds like a good plan
[09:31] <davmor2> willcooke: No but what I would suggest is we start 16.04.1 testing earlier maybe instead
[09:37] <willcooke> :)
[10:09] <davmor2> willcooke: so I think that cyphermox and co are well aware of the issues as they currently stand, But I would suggest that a month before 16.04.1 we start looking at it weekly till the end and ensure the issue that currently stand are resolved and that no new ones have arrived but maybe discuss a time frame around that when he is online, Also I would assume by then the majority of the user issue would be
[10:09] <davmor2> resolved by your team for any major niggles in the system itself that none of us have happen to trip over
[10:11] <davmor2> willcooke: also jibel is off today and might have a differing opinion so maybe re-discuss on Monday
[10:11] <willcooke> thanks davmor2
[10:46]  * willcooke begins backing up
[11:05] <andyrock> good morning all
[11:05] <willcooke> hey andyrock
[11:30] <seb128> hey andyrock, how are you?
[13:01] <andyrock> seb128: lunch time with Trevinho
[13:01] <andyrock> XD
[13:01] <seb128> andyrock, Trevinho, are you guys taking the day to enjoy Prague?
[13:01] <seb128> have fun there!
[13:01] <andyrock> Just a little bit
[13:02] <andyrock> :)
[13:02] <andyrock> I worked this morning during the travel Marco swapped the day
[13:03] <seb128> k
[13:03] <seb128> say hey to Trevinho ;-)
[13:06] <seb128> willcooke, Laney, attente, reading the g+ post from hughsie about the number of users hiting their firmware server since yesterday, did we talk to them/ask if them if they are fine having our user hammering their resources?
[13:06] <seb128> he doesn't complain about it in the post/sounds positive about it but I wonder if that might become an issue as more users upgrade
[13:18] <attente> seb128: maybe canonical can offer resources for that?
[13:18] <attente> it would be a nice gesture
[13:19] <seb128> attente, is that a "no" then? e.g we didn't discuss the topic at all with them?
[13:19] <seb128> or you don't know
[13:19] <seb128> ?
[13:19] <seb128> but yeah, offer resources
[13:19] <attente> seb128: that's a no, i didn't even anticipate that problem :)
[13:19] <seb128> or have our own server
[13:19] <desrt> good morning ubuntu
[13:19] <desrt> how's the hangover? :)
[13:20] <seb128> I don't know how comfortable we have having all our desktop install "dialing" into a third party infra daily
[13:20] <seb128> we are*
[13:20] <desrt> seb128: based on the 'enthusiastic' response we've received every time we try anything of the sort, i'm going to go with 'not' :)
[13:21] <seb128> hey desrt! doing good, back to business, some crazy distroer even dealing with yaks ;-)
[13:21] <seb128> desrt, yeah, me too...
[13:22]  * desrt eats a chocolatine with powdered sugar on top
[13:22]  * desrt is conflicted
[13:22] <seb128> that sounds wrong
[13:23] <seb128> shound be icing
[13:23] <seb128> should
[13:23] <desrt> i already told the guy at the counter that he's lucky that no french person is in here
[13:23] <seb128> lol
[13:39] <pitti> hey desrt!
[13:39] <desrt> hello pitti :)
[13:39] <desrt> i'm coming to visit your country soon
[13:40]  * desrt will spend 2 hours there on sunday :)
[13:40] <pitti> desrt: that stretches the meaning of "visit" quite a bit :)
[13:41] <desrt> i also have a short vacation there during may :p
[13:42] <desrt> pitti: what are you up to lately?
[13:42] <pitti> desrt: fun with the release up to last night, and opening yakkety right now :)
[13:43] <desrt> oh seriously
[13:43] <desrt> we actually called it that?
[13:43] <pitti> desrt: apparently so
[13:43] <pitti> yodelling yak would have been fun :)
[13:43] <desrt> awesome.  just awesome.
[13:44] <seb128> desrt, https://launchpad.net/ubuntu/yakkety
[13:44] <desrt> finally a release name that i can get behind!
[13:45] <seb128> pitti, desrt, google insist on it being written "yakety", did we typo that?
[13:45] <desrt> ya.  i was noticing that and wondering if this is part of mark's plan to convince the word to spell this word differently
[13:46] <desrt> i'm sure the spelling was carefully considered and that there is a good reason for it..... but what? :)
[13:46] <pitti> seb128: dictionary wise neither is a real word :)
[13:47] <desrt> maybe it's to avoid infringing copyright on the song title :p
[13:47] <desrt> ...or to make it easier to search for *our* yakkety yak
[13:47] <desrt> but mostly i just see a million google results pages "...did you mean 'yakety'?"
[13:48] <seb128> pitti, well, http://www.oxforddictionaries.com/definition/english/yak has "yackety-yak"
[13:48] <desrt> we're already 3rd hit on yakkety, so i guess this will go fairly well, in fact
[13:48] <seb128> :-)
[13:48]  * desrt is particularly enjoying her morning caffeine buzz today
[13:49] <desrt> i wonder if these people are on to something with the sugar on the chocolatines
[13:50] <seb128> are you sure it was sugar? :p
[13:50] <desrt> lol
[14:09]  * qengho afk lunch
[14:29]  * Sweet5hark feels sorry for the folks watching the social media accounts for this company: http://yakketyyakllc.com/social-media-marketing/ 
[14:31] <ogra_> the company might like us now though :)
[14:31] <ogra_> free ads ! :)
[15:06] <attente> seb128: hughsie said that the fwupd servers are at 3% load, but if it ever gets really bad, he would update the cache time and ask us to cherry pick that
[15:06] <seb128> attente, ok, willcooke emailed him as well
[15:08] <willcooke> he just replied, it's not a problem.  But we should get our own servers up I think.  We can start that next week
[15:08] <seb128> yes
[15:25] <seb128> dpm, pitti, what is defining what goes in -gnome langpacks?
[15:25] <seb128> http://launchpadlibrarian.net/249587950/ubuntu-xenial-translations.tar.gz has evolution-3.18.po
[15:25] <seb128> but they are missing from the langpacks in xenial
[15:25] <seb128> well the .mo are
[15:28] <pitti> seb128: http://bazaar.launchpad.net/~ubuntu-langpack/langpack-o-matic/main/view/head:/lib/pkg_classify.py, but that's fairly unrelated
[15:28] <pitti> as that just decides between -gnome and main
[15:28] <pitti> if it's missing entirely, there's a different problem
[15:28] <seb128> seems to be
[15:29] <pitti> WARNING: unknown translation domain: evolution-3.18
[15:29] <pitti> hm, missing from mapping.txt?
[15:29] <seb128> http://packages.ubuntu.com/search?searchon=contents&keywords=evolution-3.18.mo&mode=filename&suite=xenial&arch=any
[15:29] <seb128> weird
[15:29] <pitti> seb128: if you have it downloaded already, mind checking?
[15:29] <seb128> 3 langpacks have one
[15:30] <pitti> seb128: I guess those are obsolete ones which fell under the 5% treshold
[15:30] <seb128> likely
[15:30] <pitti> langpack@snakefruit:/srv/language-packs.ubuntu.com/xenial$ find -name evolution-3.18*
[15:30] <pitti> -> nothing
[15:30] <seb128> let me check for the mapping.txt
[15:31] <pitti> e-d-s-3.18 seems fine
[15:31] <pitti> seb128: or it's another bug with multiple domains from one package (sil2100 fixed that some weeks ago, but perhaps not completely)
[15:31] <seb128> did we rebuild xenial langpacks with that fix applied?
[15:32] <pitti> yes
[15:32] <sil2100> hmm
[15:35] <seb128> pitti, the mapping has
[15:35] <seb128> evolution evolution-3.18
[15:35] <seb128> evolution-data-server evolution-data-server-3.18
[15:35] <seb128> evolution-indicator evolution-indicator
[15:35] <pitti> ok, that looks fine
[15:36] <pitti> but sorry, no steam today any more to debug this still, and need to run in about 10 minutes anyway
[15:36] <pitti> bug report appreciated
[15:37] <seb128> pitti, we have bug #1545212 opened on february
[15:37] <seb128> shrug, I reassigned back then but forgot to follow up
[15:37] <pitti> ah, thanks
[15:40] <seb128> np, thanks for the replies
[15:40] <xclaesse> wow, totem 3.18 is a MASSIVE perf regression o_O
[15:40] <xclaesse> it can't even play a 640x480 mp4 smoothly anymore
[15:40] <xclaesse> on my older laptop connected on my tv
[15:41] <xclaesse> with gst-play and vlc the video play fine
[15:41] <seb128> xclaesse, :-(
[15:41] <xclaesse> but with totem I get like 10fps, it's impossible to watch
[15:41] <seb128> xclaesse, does it work better if you use the old totem version?
[15:41] <xclaesse> on my newer x230 laptop totem runs fine though
[15:42] <seb128> could also be something in gstreamer stack that changelog
[15:42] <xclaesse> seb128, was working just fine on 14.04
[15:42] <seb128> gst-play and totem might use different pipelines/elements
[15:42] <xclaesse> I suspect clutter/cogl, tbh, but with no proof atm
[15:43] <seb128> pitti, where did you see that "WARNING: unknown translation domain: evolution-3.18" warning?
[15:43] <seb128> xclaesse, could be yes
[16:01] <Laney> Well, yes, it was known that firmware updates are going to use the LVFS. That's a goal of the service.
[16:02]  * seb128 googles LVFS and finds "Linux Vendor Firmware Service"
[16:03] <Laney> It's the work that superm1 was enabling
[16:03] <seb128> just curious but is it owned by hughsie himself?
[16:03] <seb128> or on some fdo or such infra?
[16:04] <Laney> I think it's on a RedHat machine, but you could go ask him
[16:04]  * superm1 pokes in
[16:04] <superm1> openshift IIRC
[16:04]  * seb128 googles openshift as well :p
[16:04] <seb128> oh, a RH thing
[16:05] <superm1> when i talked to hughsie, he was confident he could handle the load from this getting into distros
[16:05] <superm1> but willing to expand out to a mirroring system if need be
[16:05] <seb128> well anyway, I've no clue if we are fine using that or if we want our how mirror/server, willcooke is going to investigate
[16:07] <Laney> Call it the Ubuntu Firmware Service while you're at it
[16:07] <superm1> something that could be explored is just mirroring metadata (and metadata signature) somewhere else ubuntuey and still pulling firmware from his service instead
[16:07] <seb128> Laney, :-p
[16:07] <seb128> I've a feeling you don't like the idea how having a mirror
[16:09] <superm1> the metadata and firmware can realistically be hosted in separate places.  authenticity is verified for them separately on each of them
[16:10] <seb128> yeah, unsure if that's needed
[16:11] <seb128> it just feels suboptimal to rely on an external service we have no garantee about
[16:12] <jcastro> anyone have a link to the server side component he's using?
[16:13] <seb128> jcastro, https://github.com/hughsie/lvfs-website I guess
[16:15] <superm1> Yeah that's his site.
[16:22] <seb128> Laney, are you back home btw? had a good train back?
[16:33] <Laney> seb128: yeah, train was mostly non eventful
[16:33] <Laney> I found a cool turkish place quite near to st pancras and had some lunch there
[16:33] <Laney> börek
[16:40] <seb128> that looks good
[16:40]  * seb128 starts being hundry and wouldn't say no to some börek
[16:46]  * desrt looks that up
[16:46] <desrt> mmm.  now i'm hungry too.  thanks :p
[17:16] <Laney> after I wrote that I found the second half of my börek in my bag and ate it
[17:16] <Laney> :D
[17:26] <seb128> have a good w.e everyone, see you on sunday!
[17:48] <dobey> hrmm, i wonder why sometimes my volume control keybindings just stop working
[17:48] <dobey> so weird
[17:49] <JanC> I wonder why gnome-terminal breaks dead keys in xenial (also weird)
[17:51] <JanC> breaks dead keys & compose
[17:59] <qengho> JanC: My compose works in gnome-terminal, FWIW.
[18:03] <JanC> hm
[18:04] <JanC> qengho: do you have customized compose keys (in ~/.XCompose)?
[18:07] <qengho> JanC: No.
[18:30] <JanC> roxterm doesn't have the bug, so seems like it's in gnome-terminal and not libvte
[19:53] <qengho> JanC: Compare your environments between terminal emulators too. Is LANG the same?
[20:16] <JanC> $LANG shouldn't influence keyboard layout
[21:03] <qengho> JanC: Yes, but (I think) LANG should influence what compose mappings are loaded.
[21:04] <JanC> it really shouldn't  :)
[21:05] <JanC> $LANG seems to be the same everywhere though
[21:07] <qengho> Ooh, that's the encoding, not the locale. Sorry, JanC.
[22:09] <JanC> hm, nautilus has the same problem
[22:13] <JanC> so, seems like the bug is related to the xim input module