[09:04] <Laney> howdy
[09:05] <seb128> hey Laney
[09:05] <seb128> good morning desktopers
[09:06] <Laney> hey seb128
[09:22] <darkxst> hey seb128
[09:22] <seb128> darkxst, hey
[09:23] <darkxst> could you possibly add something to my PPU/MOTU application?
[09:24] <seb128> darkxst, yeah, I received your email ... do you have a link to the what is in the Ubuntu GNOME package set?
[09:24] <darkxst> seb128, its everything seeded in the ubuntu gnome image, mostly
[09:25] <seb128> does that include stuff seeded in the Unity desktop as well?
[09:25] <darkxst> I don't know how to get a list though
[09:25] <seb128> Laney, ^?
[09:25] <darkxst> there would be some overlap
[09:25] <seb128> I'm fine giving you a +1 for MOTU, I share the same concerns Laney wrote on the wiki
[09:26] <seb128> nautilus 3.10 is another example
[09:26] <seb128> you asked for sponsoring bug you clearly didn't even try to test run under an Unity session/with the default theme
[09:27] <darkxst> seb128, I did test nautilus under ubuntu themes, but I don't normally run those so didnt notice the issues
[09:28] <Laney> Oh, there's no ubuntu gnome packageset
[09:28] <seb128> you didn't notice the white holes due to the round corners of the decorations?
[09:28] <seb128> that's pretty visible, even if you never run Unity/the default theme
[09:28] <Laney> laney@iota> edit-acl -P ubuntugnome -S trusty query                                                                                        ~
[09:28] <Laney> == All uploaders for package set 'ubuntugnome' in 'trusty' (owned by 'Ubuntu Technical Board') ==
[09:28] <darkxst> seb128, and to be fair, I do mostly contact you guys first for things that overlap
[09:28] <Laney> Archive Upload Rights for ubuntu-gnome-dev: archive 'primary', package set 'ubuntugnome' in trusty
[09:28] <Laney> laney@iota>                                                                                                                                ~
[09:29] <seb128> darkxst, right, but I don't know how much of that is because you need sponsoring...
[09:29] <darkxst> seb128, that is 1px in my VM ;(
[09:29] <Laney> I think I was thinking of desktop-extra
[09:30] <seb128> Laney, darkxst: hum, so what are we talking in that set request?
[09:31] <Laney> ubuntu gnome - ubuntu is what desktop-extra is, which is what I was considering
[09:32] <seb128> Laney, ok, let me look a desktop-extra, I'm trying to understand how much that includes Unity desktop components
[09:32] <darkxst> seb128, not much, if I send a request to you its due to the overlap
[09:35] <darkxst> Laney, going back a bit, why is there no ubuntu GNOME package-set?
[09:35] <Laney> I guess it hasn't been set up
[09:35] <seb128> darkxst, ok, that seems fine to me, I'm going to comment on the wiki in a bit
[09:35] <Laney> cjwatson has a script which maintains these
[09:35] <seb128> what would be included in a such set?
[09:35] <seb128> would that include everything on the GNOME image?
[09:36] <seb128> including e.g gtk and co?
[09:36] <Laney> see xubuntu's one
[09:36] <darkxst> seb128, yes, but I wouldnt touch gtk apart from trivial fixes
[09:37] <seb128> k
[09:38] <Laney> It'd probably discard ubuntu stuff I guess
[09:38] <Laney> darkxst: want to ask cjw to set that up?
[09:39] <Laney> then we can see what packages turn up in it; I actually think it'd be fine
[09:39] <darkxst> Laney, sure
[09:39] <Laney> https://bazaar.launchpad.net/~cjwatson/+junk/packageset/view/head:/packageset-report#L264
[09:39] <Laney> you'd get added to 271
[09:39] <Laney> which means that all stuff in ubuntu/kubuntu/edubuntu gets removed
[09:40] <Laney> if i'm reading it right
[09:42] <darkxst> Laney, yeh that is what the code says
[09:42] <Laney> nod
[09:42] <Laney> i'd be fine with that
[09:46] <darkxst> Laney, I'm not too fussed either way (we have lots in universe),  however it does seem odd that jbicha applied for Ubuntu GNOME packageset right after we became official and now apparently it doesnt exist
[09:47] <Laney> jbicha was in ubuntu-desktop and got desktop-extra created so that he could upload all ubuntu gnome stuff
[09:48] <darkxst> oh!
[09:49] <Laney> probably getting this fixed back then would have been sensible
[09:49] <darkxst> and now I can't even find him to give me an endorsement, given he sponsored > 50% of my packages
[09:53] <darkxst> Laney, seb128, regardless of packagesets etc. I am not going to step on your toes etc. I will either way contact you re overlap packages
[09:54] <darkxst> I has no idea epiphany was so popular outside the GNOME world]
[09:54] <Laney> it's more a matter of considering the impact of changes on everyone in the archive
[09:54] <Laney> to be honest ubuntu cocks that up a lot too
[09:55] <seb128> right, I don't think epiphany is "so popular", but still we should make sure things keep working
[09:58] <darkxst> Laney, I go well out of my way to make sure changes work for everyone
[09:58] <darkxst> but of course I am a dev not a designer
[09:59] <Laney> i've been impressed with your follow-up work, think I said as much
[09:59] <seb128> speaking of follow-up work, how is the nautilus 3.10 work going (fixing the few issues I pointed on that merge request)?
[10:01] <darkxst> seb128, corners are fixed, I can get buttons back to the right size by overriding padding (although that doesnt feel quite right to me)
[10:02] <seb128> do you know what adwaita is doing differently with the padding?
[10:07] <darkxst> seb128, not yet, I suspect the real issue here is that nautilus is not using a proper GtkHeaderBar yet
[10:07] <seb128> no, it's not
[10:08] <seb128> overriding the padding is fine with me (if it works) btw
[10:08] <darkxst> seb128, in the theme or nautilus itself?
[10:09] <seb128> whatever works ;-) nautilus is fine
[10:09] <seb128> you can maybe open an upstream bug about it and see what they think
[10:09] <seb128> nautilus bug that is
[10:09] <darkxst> I expect it will be ported to a proper header bar this cycle
[10:13] <seb128> that version is not going to be in Ubuntu this cycle though
[10:13] <seb128> they might want to fix the bug in 3.10 still
[10:16] <Trevinho> seb128: hey!
[10:16] <seb128> Trevinho, hey
[10:16] <Trevinho> seb128: any news on getting newer libcairo in distro?
[10:17] <seb128> Trevinho, no
[10:17]  * seb128 wonders wth is upstream doing
[10:17] <seb128> I've ,no hardware to test the hidpi stuff on either
[10:17] <Trevinho> seb128: mh... since they don't seem considering the case of doing releases... what about including a git revision? It's something I wouldn't do for a such big component, but if there are no known issues...
[10:18] <seb128> how do we know that there are "no known issues"?
[10:18] <Trevinho> seb128: me neither... but you know if you just see big things on normal screen is enough :D
[10:18] <Trevinho> (as soon as you override it with env vars)
[10:18] <seb128> lol, no, that would be buggy :p
[10:18] <Trevinho> ahah, sure
[10:18] <seb128> but thanks for the reminder
[10:18] <seb128> I'm going to ping upstream cairo about that again
[10:20] <Trevinho> as for unity, just having cairo_scale is mostly ok for painting our things, but that would cause everything to scale up considering apps..
[10:21] <Trevinho> seb128: thanks btw
[10:21] <seb128> Trevinho, yw
[10:22] <seb128> Trevinho, we have a desktop week in 10 days, I'm aiming at landing the new cairo by then,
[10:22] <Trevinho> seb128: ah, yeah I read that... cool
[10:59] <pitti> hey guys
[11:00] <pitti> so, for some weeks now the screen saver for my "martin" account is broken; it doesn't come up on ctrl+alt+l nor with the "lock" in the indicator nor on suspend; but it works for other users
[11:00] <pitti> gnome-screensaver is running
[11:00] <pitti> any idea how to debug this?
[11:00] <pitti> when I run it in the foreground, on ctrl+alt+l it says
[11:01] <pitti> [listener_lock_cb] gs-monitor.c:209 (12:00:40): Locking disabled by the administrator
[11:01] <pitti> but I don't see a setting for that in control-center
[11:01] <pitti> but the "Lock" section (lower half of "brightness and locks") is grayed out
[11:04] <pitti> can I somehow ask gsettings to only show me keys which changed from the schema defaults?
[11:04] <Laney> pitti: it's controlled by org.gnome.desktop.lockdown disable-lock-screen
[11:04] <pitti> org.gnome.desktop.lockdown disable-lock-screen true
[11:04] <Laney> that also greys out the 'lock' settings you're seeing
[11:04] <pitti> indeed, resetting that makes it work again
[11:04] <Laney> the question is how that got set to true ...
[11:05] <pitti> yeah
[11:05] <pitti> Laney: thanks; at least I can now travel again without leaving it unlocked all the time
[11:07] <Laney> http://162.213.35.4/search?weighted=1&q=disable-lock-screen
[11:09] <pitti> Laney: hm, that's still spinning for me
[11:09] <Laney> takes a while
[11:09] <Laney> moar caching
[11:09] <mlankhorst> ka-ching!
[11:09] <Laney> casper / ubiquity set it to true
[11:10] <Laney> maybe could happen if you ever ran ubiquity-dm?
[11:10] <pitti> Laney: well, who knows what I ran to break it
[11:10] <pitti> sounds unlikely, but not impossible
[11:10] <pitti> Laney: thanks for pointing out!
[11:10] <Laney> sure
[12:24] <Laney> sil2100: did you see my poke about grilo yesterday?
[12:26] <sil2100> Laney: hmm, hello! I think I might have missed it somehow - what was it about?
[12:27] <Laney> sil2100: I asked if the patch we have was forwarded
[12:27] <Laney> hi ;-)
[12:27] <sil2100> Laney: uuuu, give me a bit and I'll check, as it's been such a long time that I'm completely out-of-date ;)
[12:28] <Laney> okay, would be nice if you could do it if it isn't as we were in sync and this one looks upstreamable
[12:29] <sil2100> Sure, that makes sense indeed
[13:22]  * Sweetshark grumbles something about decision making gone bad.
[14:36] <Sweetshark> seb128: LibreOffice 4.2.0 for archive at http://people.canonical.com/~bjoern/trusty/ -- use it as needed with the poppler transition.
[14:37] <seb128> Sweetshark, great, thanks
[14:37] <seb128> Laney, ^ how does that play with the freeze?
[14:39] <Laney> seb128: it's affected
[14:39] <Laney> stuff will get stuck in proposed though so you don't have to stop uploading
[14:39] <Sweetshark> seb128: Im still building the last changes of it, not finished yet (anouther 3 hours). But the changes are really minimal, so should be fine.
[14:41] <seb128> Sweetshark, ok
[14:41] <seb128> Laney, right, thanks
[15:30] <desrt> seb128, Laney, attente, larsu, tkamppeter, mlankhorst, qengho, Sweetshark, desrt: meeting!
[15:30] <Sweetshark> o/
[15:30] <qengho> Hey hey!
[15:30] <Laney> hahaha
[15:30] <seb128> good
[15:30] <Laney> he was waiting for that
[15:30] <seb128> I don't have to lead
[15:30] <tkamppeter> hi
[15:30] <mlankhorst> hey
[15:30]  * seb128 goes back to reply to emails
[15:30] <qengho> desrt: You waited an entire nine seconds.
[15:31]  * desrt notes that when he starts the meeting, everyone is here right away
[15:31] <desrt> qengho: i'll try to do better next time :)
[15:31] <larsu> desrt: maybe you should run them from now on!
[15:31] <desrt> okay... now that i have you assembled
[15:31] <desrt> as my first order of business
[15:31] <seb128> larsu, that's what he just did
[15:31] <desrt> i pass the floor to seb :)
[15:31] <seb128> lol
[15:31] <larsu> heh
[15:31] <Sweetshark> desrt: I have a few meetings that you are invited to lead in my place ... ;)
[15:31] <seb128> desrt, you changed the order as well...
[15:32] <seb128> let's reverse that list and get started
[15:32] <seb128> desrt, you are up first ;-)
[15:32] <desrt> seb128: i'm more concerned about the possibility that maybe i forgot someone
[15:32] <larsu> seb128: ya. Clearly he's not capable for running the meeting yet
[15:32] <desrt> damnit
[15:32] <larsu> desrt: don't worry. You'll be ready when the time comes.
[15:32] <Laney> he's just doing that to go last
[15:32] <desrt> so i ended up merging another one of those monster patchsets
[15:32] <Laney> the cheek
[15:33] <desrt> the encoding issues of commandline arguments for glib
[15:33] <desrt> and the menu work for macos is now more or less done (for now)... so that was two major patchsets landed, i guess
[15:34] <desrt> we also now have GSimpleAction with default handlers for toggles and simple state-changing actions (ie: radios) which will save people from writing those trivial functions over and over again
[15:34] <larsu> desrt: any progress on the traditional menubar stuff? I could really use that for evince...
[15:34] <larsu> actually I can't, since we don't have new gtk
[15:34] <larsu> *cough
[15:34] <desrt> larsu: ya... it seems like mclasen might be starting to budge a bit on it
[15:34] <larsu> nice
[15:34] <desrt> i think the fact that i did my research and made sure that we will have a good case for all OSes is helping to prove the case
[15:34] <larsu> right
[15:34] <desrt> his main concern is that it's possibly a bit arbitrary
[15:34] <seb128> thanks for doing that btw ;-)
[15:35] <desrt> that we say "modern" vs. "traditonal" and maybe other people want something else elsewhere
[15:35] <larsu> that's a valid concern
[15:35] <desrt> but i really think it comes down to the two, more or less
[15:35] <larsu> I don't like the naming either
[15:35] <desrt> i wrote up my thoughts here: https://bugzilla.gnome.org/show_bug.cgi?id=722092#c12
[15:35] <ubot2`> Gnome bug 722092 in GtkApplication "Add GtkApplication resources support" [Normal,Unconfirmed]
[15:36] <desrt> anyway.... i'm currently designing my goptioncontext <-> gapplication friendship bridge
[15:36] <desrt> so the suffering can finally be over
[15:36] <desrt> i'm going to toss out the last set of patches i did on the topic
[15:36] <desrt> in all that encoding work i discovered that goptioncontext isn't awful
[15:36] <desrt> and i think we should save it and improve it
[15:37] <desrt> so i am no longer afraid to properly integrate it with gapplication
[15:37] <desrt> that's it for me, more or less
[15:37] <seb128> desrt, thanks
[15:37] <seb128> ok, now let's resume normal order :p
[15:38] <seb128> qengho, hey
[15:38] <qengho> yo.
[15:38] <qengho> * In progress: Preparing new Chromium v 32.0.1700.77 for release.
[15:38] <qengho> * In progress: More working Hi-DPI for on Cr+gtk.  80% done.  Looking into Aura work One Day.
[15:38] <qengho> * Next: Touch interface for Cr.
[15:38] <qengho> EOF
[15:39] <seb128> nice to see the hi-dpi work getting there
[15:39] <seb128> qengho, thanks
[15:39] <seb128> Sweetshark, hey
[15:40] <Sweetshark> - finished my pbuilder/jenkins rework, but still 'graced' with ccache missing cache all the time
[15:40] <Sweetshark> - some upstream QA mentoring
[15:40] <Sweetshark> - coordination upstream QA towards a more sane bug priotizing workflow
[15:40] <Sweetshark> - TDF BoD call and followup on some flamefesty decisions on TDF assets
[15:40] <Sweetshark> - usual TDF ESC call: http://nabble.documentfoundation.org/minutes-of-ESC-call-td4092648.html various tidbits
[15:40] <Sweetshark> - jumped in to create libabw repo on upstream gerrit for abiword import filters for LibreOffice
[15:40] <Sweetshark> - moved away some QA/infra ticket queues from upstream OTRS as that likely will be decommissioned
[15:40] <Sweetshark> - fixed fdo#71511 on upstream master which was an a11y regression introduced by a patch from bdrung that I upstreamed, also for review on -4-2 (its in the branch now and should be in trusty/4.2.1. https://bugs.freedesktop.org/show_bug.cgi?id=71511
[15:40] <ubot2`> Freedesktop bug 71511 in Writer "Writer no longer uses Text and Background Colours from Windows High-Contrast theme for displaying document" [Major,Verified: fixed]
[15:40] <Sweetshark> - some direction on the effort to give bibisect https://wiki.documentfoundation.org/QA/HowToBibisect an GUI for enduser bug triage
[15:40] <Sweetshark> - some concepts about LibreOffice without Java on LTS -- as of now, all suck.
[15:40] <Sweetshark> - finished the -l10n source pkg split off and pushed this to the prereleases PPA, no obvious bugs so far
[15:40] <Sweetshark> - thus we should now again have all l10ns in the PPA, which should spare me a few nagmails per week by $randomuser about it, and have one prereq for getting libreoffice rolling checked
[15:40] <Sweetshark> - prepared a 4.2.0~rc2 trusty/main (first new major, fingers crossed)
[15:40] <Sweetshark> EOF
[15:40] <Sweetshark> (yes, I cheated an took a look at my sent mail folder this time)
[15:41] <desrt>  - drank a lot of mate and fritz.  didn't sleep.
[15:41] <desrt> (busy week...)
[15:41] <Sweetshark> desrt: nah, thats a normal week, usually I spare you the details ;)
[15:42] <seb128> Sweetshark, did you get any feedback from rene on the l10N changes?
[15:42] <Sweetshark> seb128: nope
[15:42] <Sweetshark> seb128: well, rene wanted to have minimal tarballs (no duplication) as a prereq. so he wont use it for 4.2 anyway.
[15:43] <seb128> ok
[15:43] <Sweetshark> seb128: I guess we can work that out for 4.3 on debian
[15:43] <seb128> Sweetshark, I'm going to follow up on the java stuff after the meeting
[15:43] <seb128> Sweetshark, thanks
[15:43] <seb128> mlankhorst, hey
[15:43] <mlankhorst> Fixing drm kernel issues, frantically getting everything ready for merge window, keeping xorg 1.15 updated in the ppa. Testing mesa with dri3, last prerequisite outside of updated xorg/mesa in the archive.
[15:44] <mlankhorst> and libxcb update + dependencies
[15:44] <seb128> ok
[15:44] <seb128> what's the current status of xorg 1.15?
[15:45] <mlankhorst> waiting for fglrx, ready to go
[15:45] <mlankhorst> dri3 won't work for now :)
[15:45] <seb128> mlankhorst, thanks
[15:45] <seb128> Laney, hey
[15:46] <Laney> soz, someone came to the door
[15:46] <Laney> window cleaner ...
[15:46] <Laney> • cogl transition
[15:46] <Laney> • GNOME updates: d-conf glib
[15:46] <Laney> ∘ glib test failures: gather information, forward upstream, disable in Ubuntu (all new tests in this release which are extremely sensitive in our buildd/CI environment)
[15:46] <Laney> ∘ forward glib-networking test failure upstream; receive fix from danw & test it works, which it does!
[15:46] <Laney> • Work on webkitgtk 2.3.4, failures on i386 and ppc - testing fixes on porter box / de-virt PPA now
[15:46] <Laney> ∘ Notice webp transition & upload for that
[15:46] <Laney> ‣ Pillow (python-pil) autopkgtest fails due to a dubious assumption that webp images will be bit-for-bit identical across libwebp releases. Fix the test by generating the image before running the test.
[15:46] <Laney> • Alpha 2 wrangling: disable automatic builds, set up tracker, install freeze block, kick initial rebuilds. Most of the hard/time consuming work is being done by Riddell.
[15:46] <Laney> • system-settings autopilot tests - some minor improvements, get stressed about annoying failures (differences between running on desktop vs. phone, argh). Might have a lead on a workaround now. Need to fix an issue where starting a private bus means you have to mock ALL the dbus things (ofono tests fail). Will start it only when needed for now.
[15:46] <Laney> ✌
[15:48] <seb128> Laney, you should maybe mp your current fixes for system-settings/autopilot, let me know if you want me to take over/try to get the other issues resolved
[15:48] <Laney> I want to get it all passing really
[15:48] <Laney> then we can start from a clean state
[15:48] <Laney> it's all in that ap-fixes branch though
[15:49] <seb128> right, I'm just offering to share the annoyance to get there
[15:49] <Laney> sure
[15:49] <Laney> let me do this dbus thing and then I'll see what's left
[15:49] <seb128> k
[15:50] <seb128> Laney, thanks
[15:50] <seb128> tkamppeter, hey
[15:50] <tkamppeter> - cups-filters: Released 1.0.44 with support for PPD-less printing in gstopxl (PCL-XL filter), and automatic Poppler/Ghostscript selection in pdftoippprinter (PPD-less printing).
[15:50] <tkamppeter> - cups-filters, cups: Splitting of binary packages to allow small (mobile) printing stack with only basic filters for printing PPD-less on IPP printers with PDF, PostScript, PWG Raster, or PCL
[15:50] <tkamppeter> - Bugs.
[15:51] <seb128> tkamppeter, thanks
[15:51] <seb128> attente, hey
[15:51] <attente> debugged compiz and i-keyboard tests
[15:51] <attente> tried to debug Ambiance's missing menu separators, found the regression, but not a solution
[15:51] <attente> added global menu bar alt-mnemonics to the key grabber PPA (holding alt to reveal the menu bar still doesn't work though, and there's a bug with multi-monitor)
[15:51] <attente> EOF
[15:53] <seb128> attente, how is the compiz work going?
[15:53] <seb128> also what's the ambiance/menu issue?
[15:53] <attente> seb128, the MP just needs a review
[15:53] <seb128> good
[15:53] <attente> and menu separators are invisible under ambiance
[15:53] <seb128> is that a GTK 3.10 issue?
[15:54] <seb128> could be one for larsu? ;-)
[15:54] <attente> i think it's a theming issue
[15:54] <larsu> seb128: I've already talked to attente about it and he offered to look into it
[15:54] <attente> there's a commit in ubuntu-themes that when reverted fixes the problem
[15:54] <larsu> I can help if there are any problems, though
[15:54] <seb128> ok
[15:54] <seb128> what commit?
[15:54] <larsu> attente: which one?
[15:55] <attente> http://bazaar.launchpad.net/~ubuntu-art-pkg/ubuntu-themes/trunk/revision/315
[15:55] <attente> the WideSeparators line
[15:55] <larsu> bah, not that again
[15:56] <seb128> seems like larsu knows about that topic...
[15:56] <attente> if we remove it, the separators appear again, but the bug it corrects breaks again
[15:56] <seb128> hum, k
[15:56] <attente> it's unaffected in radiance though
[15:56] <seb128> no point discussing/debugging it during the meeting but might be a good after-meeting topic
[15:56] <attente> ok
[15:57] <seb128> attente, btw did you see that https://code.launchpad.net/~bfiller/ubuntu-keyboard/ubuntu-keyboard-active-language/+merge/201990 landed?
[15:57] <seb128> attente, which means we can do the settings side now
[15:58] <attente> seb128, oh, i hadn't. thanks!
[15:58] <seb128> yw!
[15:58] <seb128> attente, thanks
[15:58] <seb128> larsu, your turn
[15:58] <larsu> cool
[15:58] <larsu> I continued on evince but descoped it a bit due to taking too long (I initially wanted to port away from GtkAction completely)
[15:59] <larsu> I now have a version that exports a menubar natively
[15:59] <larsu> and am fighting with 3.10/master issues
[15:59] <larsu> both in evince and gtk
[15:59] <larsu> we really need desrt's set_accels_for_action backported I think :(
[15:59] <seb128> don't you dare asking for 3.12
[15:59] <larsu> in between a couple of small things popped up, like more gedit theming fixes
[16:00] <larsu> oh, and that indicator sound gsettings issue
[16:00] <desrt> larsu: hahahah
[16:00] <desrt> good luck backporting that :(
[16:00] <larsu> desrt: ya...
[16:00] <larsu> I really want to export the menu natively, thouh
[16:00] <larsu> but if that means we don't get multiple accels, that kind of sucks
[16:00] <desrt> you can still use gtkaction for your accels....
[16:00] <desrt> :/
[16:01] <larsu> bah
[16:01] <desrt> i wonder if we could convince Laney to accidentally upload the new gtk
[16:01] <larsu> then we can just not use those patches at all and use unity-gtk-module
[16:01] <larsu> which totally wasn't the point of this excercise...
[16:01] <larsu> desrt: seb128 might become a bit mad about that
[16:01] <desrt> i think we should give it a serious talk at the desktop weak, fwiw
[16:02] <seb128> who is being weak?
[16:02] <larsu> weak? srsly?
[16:02] <seb128> let's talk about it at the desktop strong yeah
[16:02] <desrt> *week.  sorry.
[16:02] <seb128> ;-)
[16:02] <larsu> seb128: LOL
[16:02] <desrt> trying to have too many conversations at once :)
[16:02] <Laney> haha
[16:02] <seb128> ok
[16:02] <seb128> larsu, thanks
[16:02] <Laney> let's just get seb drunk
[16:02] <desrt> "desktop strong"   /me has flashbacks to boston
[16:02] <seb128> so, my turn
[16:02] <seb128>  * some desktop updates (gimp, gnome-screenshot, goocanvas, glade, harfbuzz, e-d-s)
[16:02] <seb128>  * desktop bugs fixes (eog hanging on dialog close, g-s-d/fontconfig polling issues, nautilus sidebar status being wrong, accountsservice polling issue)
[16:02] <seb128>  * desktop bugs triage
[16:02] <seb128>  * started reviewing the ubuntu-system-settings current design/compared to the implementation to list things to check on/change
[16:02] <seb128>  * looked at the archive rebuild test results, fixed some builds
[16:03] <seb128>  * lot of random discussions and look at issues (like the dconf write on login)

[16:03] <Laney> oh yeah i didn't look at the rebuild yet
[16:03] <Laney> got the link handy?
[16:04] <Laney> http://people.ubuntuwire.org/~wgrant/rebuild-ftbfs-test/test-rebuild-20140108-trusty.html
[16:04] <desrt> seb128: what do you think should be the recommended punishment for when we find people writing to dconf at login?
[16:04] <seb128> http://people.ubuntuwire.org/~wgrant/rebuild-ftbfs-test/test-rebuild-20140108-trusty.html
[16:04] <seb128> Laney, bah :p
[16:04] <seb128> desrt, ice cream?
[16:04] <Laney> they have to fill out a spreadsheet for every commit from now on

[16:04] <seb128> (when they fix it, which larsu did ;-)
[16:04] <desrt> i mean... clearly these rules are not having an effect... we need mandatory minimum sentences...
[16:04] <desrt> i hear those always prevent crimes
[16:05] <larsu> desrt: it'd be nice if we had some kind of test for that
[16:05] <larsu> in my case, a seemingly harmless commit did the damage
[16:05] <seb128> yeah, right
[16:05] <desrt> larsu: i asked for one a very long time ago from the QA guys
[16:05] <desrt> who said they would do it
[16:05] <desrt> not sure what became of that
[16:05] <larsu> right. I don't think it's reasonable to manually test that all the time
[16:06] <larsu> and as we saw, people (aka "me") forget
[16:06] <seb128> desrt, so many priority changes recently (especially with touch), I guess that got dropped on the way
[16:07] <seb128> ok, on that note
[16:07] <seb128> is there any question/comment?
[16:08] <seb128> seems not, that's a wrap then
[16:08] <seb128> thanks everyone!
[16:09] <Laney> cheers
[16:10] <desrt> okay everyone
[16:10] <desrt> i declare this meeting to be over
[16:10] <desrt> seb128: thanks for your help this week with chairing the meeting
[16:11] <seb128> desrt, yw ;-) (thanks for getting everyone around, that worked well, nobody was late missing)
[16:13] <ochosi> larsu: quick question, is there an eta for robert_ancell's indicator-power-patch (unity-control-center2) so i can rebase my branch on it?
[16:16] <attente> ChrisTownsend, hi
[16:16] <ChrisTownsend> attente: Hey, what's up?
[16:17] <attente> ChrisTownsend, just wondering if you had time to help review https://code.launchpad.net/~attente/compiz/plugin-actions/+merge/200307
[16:17] <ChrisTownsend> attente: Oh, ok, that's ready again.  Sure, I'll review it soon.
[16:17] <ChrisTownsend> attente: Thanks for reminding me:)
[16:18] <larsu> ochosi: I approved it, right? It should have been merged already
[16:18] <attente> ChrisTownsend, thanks
[16:18] <ochosi> larsu: approved but not merged as far as i can see
[16:19] <larsu> ochosi: we're talking about this one, right? https://code.launchpad.net/~robert-ancell/indicator-power/unity-control-center2/+merge/201130
[16:19] <larsu> I wonder what happened, I remember approving it after we talked about this last time
[16:19] <ochosi> larsu: yeah, that one
[16:19] <ochosi> i don't see it in https://code.launchpad.net/~indicator-applet-developers/indicator-power/trunk.14.04
[16:20] <larsu> right, let me try again
[16:20] <ochosi> ok :)
[16:21]  * larsu keeps the tab open this time to check up on it
[16:22] <ochosi> hehe
[16:48] <larsu> ochosi: it's merged
[16:49] <ochosi> larsu: thanks, will ping you again once my branch is rebased
[17:19] <Laney> oops
[17:19] <Laney> almost made the u-s-s tests flaky
[17:21] <seb128> keyword "almost" ;-)
[17:23] <Laney> dragging causes a flick which meant that sometimes the pointer would miss the thing it tried to click on
[17:38] <brainwash> larsu: hey, so xubuntu 14.04 palns to ship a wrapper for the gtk3 indicators, everything seems to work fine so far, but the sound indicator tends to not load its panel icon (basically it stays invisible). actions like volume change or mute do not restore the icon, only killing the sound indicator service does eventually. any ideas how to debug this race condition?
[17:45] <ochosi> larsu: ok, rebased the patch and resubmitted the merge-proposal
[17:46] <ali1234> brainwash: i bet that is related to the xfdesktop wrong-theme bug and the gtk stock icons problems
[17:47] <ali1234> remember what happened when i tried to use a stock icon in the indicator, and that stock icon wasn't available?
[17:47] <brainwash> but it happens randomly
[17:47] <ali1234> so does the xfdesktop problem
[17:47] <brainwash> and other indicator don't seem to be affected
[17:47] <brainwash> xfdesktop only on session start
[17:48] <ali1234> sound ndicator is only affected on session start too
[17:49] <brainwash> did you try to kill the sound indicator service to force the invisible icon?
[17:49] <ali1234> yes
[17:49] <brainwash> and it never happened?
[17:49] <ali1234> no
[17:49] <ali1234> it only ever happens at session startup for me
[17:51] <brainwash> wait, but a volume change or mute do not restore the icon
[17:51] <brainwash> or does that not matter
[17:54] <brainwash> ali1234: I was able to force the missing icon
[17:54] <brainwash> mid session
[17:55] <attente> Trevinho, not really sure what we should call that method tbh...
[17:55] <Trevinho> attente: mh
[17:55] <attente> Trevinho, maybe something like getNonOptionActions?
[17:56] <Trevinho> Well, I mostly was concerned by the class Class thing...
[17:56] <brainwash> ali1234: killed the service like 20 times and it failed 3 times
[17:56] <attente> Trevinho, oh. that's what's done in CompOption
[17:56] <attente> Trevinho, i thought it'd be more convenient to use the same convention
[17:56] <Trevinho> mh, ok... yeah, I wondered it was inheredited from it..
[17:58] <attente> Trevinho, it's also a non-const reference returned there, but i can fix both in the MP
[18:07] <attente> Trevinho, what about Container?
[18:07] <Trevinho> attente: yeah, better...
[18:07] <attente> ok, i'll update it
[18:11] <attente> (just the CompAction::Class, i'm not changing the CompOption::Class name)
[18:17] <Laney> yay
[18:17] <Laney> all the AP tests pass on the phone!
[18:18] <seb128> Laney, \o/
[18:19] <Laney> doesn't mean they will work for anyone else
[18:19] <Laney> I know how this stuff goes :P
[18:21] <seb128> hehe
[18:22] <seb128> yeah, they fail under a french locale to start
[18:23] <didrocks> TheMuso: hey, FYI, we had to revert at-spi2-core (more info on the ubuntu-phone ML) to get back to a nice state. We can chat at the sprint I guess
[18:24] <Laney> I get a UnicodeDecodeError traceback under fr_FR.UTF-8
[18:24] <Laney> ho hum
[18:26] <seb128> Laney, https://code.launchpad.net/~vrruiz/ubuntu-system-settings/autopilot/+merge/192869/comments/454716
[18:27] <seb128> Laney, I didn't block the merge on that to be fixed because it already took way to land to get that stuff to land (there was like a week delay between review comments and fixes)
[18:27] <Laney> did you see the same python error?
[18:31] <seb128> Laney, no, I get 4 errors
[18:31] <seb128>   File "/usr/lib/python2.7/dist-packages/ubuntu_system_settings/tests/__init__.py", line 117, in assert_space_item
[18:31] <seb128>     self.assertThat(len(values), GreaterThan(1))
[18:31] <seb128>   File "/usr/lib/python2.7/dist-packages/testtools/testcase.py", line 412, in assertThat
[18:31] <seb128>     raise MismatchError(matchee, matcher, mismatch, verbose)
[18:31] <seb128> MismatchError: 1 is not < 1
[18:32] <Laney> ah I just ran test_about
[18:32] <seb128> Laney, that's because the value there is coming from the split which is buggy with the french spaces
[18:32] <seb128> Laney, that's in test_about afaik
[18:33] <Laney> shrug
[18:33] <Laney> can look at that another time
[18:33] <Laney> PS4 time now ;-)
[18:33] <seb128> yeah, don't bother about it
[18:33] <seb128> Laney, have fun!
[18:33] <Laney> thanks, see you!
[19:46]  * Sweetshark realizes he will have 4 hours of conference calls in the next 7 days (so far).
[19:46] <Sweetshark> *urgh*
[19:58] <Sweetshark> seb128: the 4.2.0~rc2/trusty build finished and succeeded.
[20:06] <robert_ancell> jasoncwarner, did your graphics issues get resolved?
[20:08] <Sweetshark> oh, Linus flamed us on slashdot yesterday?
[20:08]  * Sweetshark grabs popcorn.
[20:09] <robert_ancell> larsu, thanks for the indicator merge
[20:10] <robert_ancell> larsu, who's managing the other indicators?
[20:11] <jasoncwarner> robert_ancell it appears to have. I did another update and it went away. I still have n-m crashes, but seem to be unrelated.
[20:11] <jasoncwarner> Sweetshark: link?
[20:16] <jasoncwarner> Sweetshark: nm, found it
[21:21] <robert_ancell> tedg, are you still looking after indicators?
[21:22] <tedg> robert_ancell, Sure
[21:22] <tedg> What's up?
[21:23] <robert_ancell> tedg, can you get some momentum on https://code.launchpad.net/~robert-ancell/indicator-bluetooth/unity-control-center2/+merge/201118, https://code.launchpad.net/~robert-ancell/indicator-session/unity-control-center2/+merge/201131, https://code.launchpad.net/~robert-ancell/indicator-sound/unity-control-center2/+merge/201132
[21:23] <robert_ancell> would like to land these so we can switch on unity-control-center by default
[21:24] <tedg> Ah, okay.
[21:24] <tedg> What's happening with like XFCE?
[21:24] <tedg> Shouldn't we be doing it by env var instead of whether it's in the path?
[21:25] <robert_ancell> tedg, we can check if XDG_CURRENT_DESKTOP is Unity as well if you'd like
[21:25] <tedg> robert_ancell, That makes sense to me, you?
[21:26] <robert_ancell> tedg, sure, I'll update those MPs
[21:26] <tedg> Cool, thanks!
[21:28] <ali1234> Xfce currently has an upstart session, but the indicators get started by XDG
[21:28] <ali1234> we are looking to add support for the new launching style to lightdm-gtk-greeter too
[21:29] <ali1234> Xubuntu also probably wants to use some bits from u-c-c, since we have the same problems with g-c-c that you do
[21:33] <TheMuso> didrocks: I won't be there. seb128 asked me to update it...
[21:34] <ali1234> regarding XDG vs upstart, i think upstart is preferable since XDG seems to have no mechanism for restarting the indicators if they crash
[21:34] <ali1234> i assume upstart can do this
[21:34] <TheMuso> ...and there is no need for at-spi to be on touch atm...
[21:35] <robert_ancell> tedg, on indicators and u-c-c. Do you want to move the date time panel from indicator-datetime into u-c-c?
[21:35] <tedg> robert_ancell, I don't see any reason to leave it in g-c-c, charles?
[21:36] <ali1234> relevant: bug 1074314
[21:36] <ubot2`> Launchpad bug 1074314 in indicator-datetime (Ubuntu) "indicator-datetime configuration panel only works in Unity session" [Undecided,Confirmed] https://launchpad.net/bugs/1074314
[21:36] <charles> they share a small amount of formatting code from utils.c, so it's a little ugly to duplicate that I guess
[21:36] <charles> but that's minor
[21:37] <robert_ancell> there's no need to move it unless it makes life easier
[21:37] <charles> Other than the code duplication, which is minor, I don't mind either way
[21:38] <tedg> I think long term it does as we'll want indicator-datetime to be more touch focused.  Short term I don't think it makes a huge difference.
[21:38] <tedg> It'll shrink the build-deps for indicator-datetime
[21:38] <charles> One thing, I have a pretty large MP for datetime coming, so if we act on 1074314 I'd prefer we do it after that goes through
[21:39] <charles> hm, that's related, but not exactly the same. robert_ancell, is there a ticket already for separating out the panel code?
[21:39] <robert_ancell> charles, no ticket
[21:40] <charles> k
[21:40] <robert_ancell> charles, we would need to wait until after the u-c-c migration occurs because it would drop support for g-c-c
[21:41] <charles> robert_ancell: that sounds good. At that point let's move it over
[21:41] <charles> I don't have strong feelings on this either way but ted's point about reducing i-datetime's deps makes sense
[21:47] <robert_ancell> I'll open a bug
[21:49] <robert_ancell> charles, bug 1271339
[21:49] <ubot2`> Launchpad bug 1271339 in Indicator Date and Time "Move panel to unity-control-center" [Wishlist,Triaged] https://launchpad.net/bugs/1271339
[21:53] <robert_ancell> tedg, those MPs are updated now
[21:56] <robert_ancell> darkxst, regarding lp:~darkxst/gnome-control-center/vanilla - you can own that branch now since I'm not going to do anymore g-c-c updates. Once we do the switch to u-c-c by default you should be able to upload those changes
[22:01] <darkxst> robert_ancell, ok
[22:18] <robert_ancell> tedg, is there a plan to migrate indicator-datetime to geoclue 2.0?
[22:18] <tedg> robert_ancell, No plan, is that a trusty thing?
[22:18] <robert_ancell> tedg, I just noticed the new version is there in the archive, just wondering if we'll update to it
[22:19] <tedg> Hmm, I'd need to update ubuntu-geoip as well.
[22:19] <robert_ancell> the indicator is the only thing pulling it in
[22:19] <robert_ancell> yes
[22:19] <tedg> I have nothing against it, but I doubt I'll have time before feature freeze.
[22:19] <robert_ancell> I'll file a bug :)
[22:21] <darkxst> I don't think that will be to easy, geoclue-2.0 does not support custom backends
[22:21] <tedg> Ha, awesome!