[08:49] <seb128> good morning desktopers
[08:49] <ali1234> morning
[08:51] <seb128> hey ali1234, how are you?
[08:51] <ali1234> fine thanks :)
[08:51] <seb128> ali1234, well done one fixing that lightdm bug, I need to restart with the update to see if it works for me as well ;-)
[08:52] <ali1234> turns out it was timing related after all... timing of finalize() anyway
[08:52] <ali1234> i'm just waiting for my xfwm4 patches to be accepted, then we have completely seamless backgrounds from login to logout on xubuntu
[09:03] <Laney> hey
[09:03] <Sweetshark> Moin!
[09:11] <seb128> hey Laney Sweetshark
[09:13] <Laney> hey seb128 Sweetshark
[09:13] <Laney> how's it going?
[09:15] <seb128> good! you?
[09:16] <Laney> pretty decent thanks
[09:50] <seb128> larsu, do you know in which case GtkTreeView uses a GtkAdjustment for vertical scrolling or not?
[09:50] <larsu> seb128: I'm not sure. I assume when the minimum sizes of the columns exceed the width of the tree view?
[09:53] <seb128> larsu, is that dynamic?
[09:53] <seb128> larsu, I'm trying to make sense of https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1024590
[09:53] <ubot2> Launchpad bug 1024590 in update-manager (Ubuntu Saucy) "update-manager crashed with AttributeError in _on_download_changed(): 'NoneType' object has no attribute 'get_value'" [Medium,Confirmed]
[09:54] <seb128> that code does
[09:54] <seb128>             adj = self.get_vadjustment()
[09:54] <seb128>             is_scrolled_down = (adj.get_value() + adj.get_page_size() ==
[09:54] <seb128>                                 adj.get_upper())
[09:54] <larsu> seb128: it is dynamic, but you can fix it by setting GtkTreeViewColumn::fixed-width
[09:54] <seb128> but sometime vadjustment is null
[09:54] <larsu> oh
[09:55] <seb128> I'm pondering just putting a "if adj is not None" in there
[09:56] <seb128> I don't know that code, but it's topping e.u.c for ages and mvo/glatzor don't seem to have time for that nowadays
[09:56] <larsu> vadjustment can definitely be NULL
[09:56] <larsu> according to the docs
[09:56] <seb128> right
[09:56] <seb128> if there is no adjustement in use
[09:56] <mvo> seb128: actualy I probably would have done exactly this
[09:56] <seb128> that is_scrolled_down seems a bit weird to me
[09:57] <larsu> why does this code need to know whether it's scrolled down?
[09:57] <seb128> mvo, ok, sending a mp your way then
[09:57] <seb128> larsu, http://paste.ubuntu.com/6513667/
[09:58] <seb128> larsu, seems to stick you at the end of the list if you got there and new entries get added
[09:58] <larsu> ah okay, that makes sense
[09:59] <larsu> ya, just check for NULL (or None)
[09:59] <seb128> mvo, hey btw, how is your cold? feeling better?
[10:00] <mvo> seb128: much better, good enough to play hockey yesterday even :) but wasn't my most spectacular performance, so not fully recocvered yet
[10:00] <seb128> nice
[10:00] <seb128> well, you can't master it every time ;-)
[10:00] <mvo> seb128: yeah, the code is iirc a port from what synaptic is doing when you are at the last column, then it keeps you there (assuming you want to see the progress of the latest item)
[10:00] <mvo> seb128: :)
[10:01] <seb128> mvo, is there a way to "simulate" an update? I wonder in which case that happen
[10:02] <larsu> seb128: most likely when there's no scrolling, because you don't need an adjustment then
[10:03] <seb128> larsu, well, I tried to reproduce by installing updates and resizing that widget to size where it requires scrolling or not without hitting the bug
[10:03] <seb128> oh well, checking None should work
[10:03] <seb128> mvo, is
[10:03] <seb128>         try:
[10:03] <seb128>             iter = self._download_map[uri]
[10:04] <seb128> a way to check if the list of download is displayed or not?
[10:04]  * seb128 is not even sure to understand the logic of this try/except
[10:08] <mvo> seb128: it adds uris it does not know about yet to its internal download dict, if you want I can give this a go now, I would reorganize it a little bit so that the adding is done earlier and the adj is done later
[10:08] <mvo> seb128: so that its easier to follow what is happening (plus add a comment whats going on)
[10:08] <seb128> mvo, if you want to do it (and fix the None case) that would be great ;-)
[10:17] <mvo> seb128: http://bazaar.launchpad.net/~aptdaemon-developers/aptdaemon/main/revision/963 - hopefully a bit clearer now :)
[10:20] <pitti> desrt: could we do a -shim release 6? seems there's not much progress on the remaining failurs, so let's at least fix the known ones now
[10:22] <seb128> mvo, it is, thanks a lot!
[10:22] <Laney> shim shimmy shim
[10:24] <seb128> mvo, bonus point if you SRU that commit to saucy, it's the most report issue on https://errors.ubuntu.com/?release=Ubuntu%2013.10&period=day
[10:27] <mvo> seb128: heh, ok
[10:30] <seb128> mvo, danke ;-)
[10:30] <mvo> seb128: checking out why I get some testfailures curently, but I think its unreleated
[10:30] <seb128> mvo, https://errors.ubuntu.com/problem/607c057bd7dfbb680a4bc490692e13d694f70994 is high ranked as well, would it make sense to just ignore those error (e.g try/except them)?
[10:31] <mvo> seb128:
[10:31] <mvo> Sorry, you are not a member of a group that is allowed to see the data from error reports. Please fill out this form to request access. :/ let me read this form first
[10:32] <seb128> urg
[10:32] <seb128> mvo, that's https://launchpad.net/bugs/1202754
[10:32] <ubot2> Launchpad bug 1202754 in update-manager (Ubuntu Saucy) "update-manager crashed with SystemExit in exit(): 0" [High,Confirmed]
[10:32] <seb128> mvo, https://launchpadlibrarian.net/145273757/Traceback.txt
[10:34] <mvo> seb128: yes, I think that is ok, this is one of those rarther useless reports
[10:34] <seb128> mvo, it's creating lot of apport prompting noise, let's just silent that then ;-)
[10:58] <seb128> Mirv, congrats on getting upload rights for the qt stack ;-)
[10:59] <Mirv> thanks seb128 :)
[11:19] <Laney> mlankhorst: bug #1197921 looks like a you thing
[11:19] <ubot2> Launchpad bug 1197921 in xorg-server (Ubuntu Saucy) "LibreOffice spreadsheet causes full Xorg crash with Anti-Aliasing enabled" [Undecided,New] https://launchpad.net/bugs/1197921
[11:19] <Laney> want to sponsor?
[11:19] <mlankhorst> i can't sponsor pixman
[11:20] <mlankhorst> https://launchpad.net/ubuntu/precise/+queue?queue_state=1
[11:20] <Laney> sure you can
[11:20] <mlankhorst> https://launchpad.net/ubuntu/saucy/+queue?queue_state=1&memo=90&start=90
[11:20] <mlankhorst> besides it's already queued
[11:21] <mlankhorst> requires some sru admin to accept it
[11:21] <Laney> ok
[11:21] <Laney> can you make the status be "In Progress" then?
[11:29] <seb128> lunch, bbiab
[13:04] <GunnarHj> seb128: ping?
[13:05] <seb128> GunnarHj, hey
[13:05] <GunnarHj> seb128: Hello, Seb!
[13:05] <GunnarHj> seb128: I'm thinking of adding a task to bug #991002. The reason is that Bengali (and not Bangla) is used in the "Choose an input source" window in "Text Entry". However, I have failed to figure out which package is affected. Can you possibly give me a hint on how/where that list is created?
[13:05] <ubot2> Launchpad bug 991002 in GLibC "Change name for bn-BD from 'Bengali(Bangladesh)' to 'Bangla(Bangladesh)')" [Medium,Confirmed] https://launchpad.net/bugs/991002
[14:13] <desrt> pitti: sure
[14:29] <mlankhorst> anyone wants to do some testing of mesa 10 before I upload it to trusty?
[14:29] <mlankhorst> I've tested direct + indirect rendering, swrast fallback, piglit runs on the 3 major hw vendors and the fallback to 1.4 (fix for slow unity blur on intel)
[14:36] <seb128> mlankhorst, yes, likely the touch guys and some unity guys, do you have it in a ppa?
[14:36] <mlankhorst> ppa:canonical-x/x-staging
[14:36] <mlankhorst> oh I've done unity testing too
[14:36] <seb128> that's a thrown it all ppa though
[14:36] <mlankhorst> it works, surprisingly
[14:37] <mlankhorst> and it kept working after upgrading to xorg 1.15 too
[14:37] <mlankhorst> sec I'll copy it to ubuntu-x-swat
[14:37] <Laney> haha surprisingly
[14:37] <Laney> confidence inspiring
[14:40] <mlankhorst> Laney: I was more worried about the xmir patch from xorg 1.15 failing than mesa
[14:41] <Laney> :>
[14:41] <seb128> we are not going with 1.15 (yet) anyway
[14:41] <mlankhorst> no I put it in the ppa for testing :P
[14:42] <seb128> desrt, I like how you unassigned yourself from that hud bug ;-)
[14:42] <seb128> desrt, good morning!
[14:42] <mlankhorst> I've copied mesa10 to ppa:ubuntu-x-swat/ppa
[14:47] <desrt> seb128: hi :)
[14:47] <desrt> seb128: larsu made me do it :)
[14:48] <desrt> if it wasn't for him i would had just happily ignored it :p
[14:48] <larsu> desrt: well, I pointed you to it with the comment that you should "do something about it"
[14:48] <seb128> haha
[14:49] <seb128> larsu +1
[14:49] <desrt> *cough*
[14:49] <desrt> seb128: maybe not +1 if you knew what his suggestion about what to do with it was :p
[14:49] <seb128> drop the hud?
[14:49] <seb128> (what do I win? :p)
[14:50] <desrt> for best original idea?
[14:50] <larsu> I did not say that (but think it, of course)
[14:50] <seb128> larsu, desrt: I know you guys :p
[14:50] <desrt> no.  we did not consider this line of thinking :p
[14:50] <larsu> so, qqmlpropertymap is broken in 5.2 :-/
[14:50] <seb128> larsu, "fun"
[14:51] <seb128> good that we didn't land that update yet
[14:51] <larsu> ya
[14:51] <seb128> it means you can just open a blocker bug
[14:51] <larsu> and assign it to mardy \o/
[14:51] <seb128> Mirv, can you get somebody helping looking at a qt 5.2 regression if we open it with a testcase?
[14:52] <seb128> Mirv, didrocks: when is qt 5.2 supposed to land?
[14:52] <didrocks> seb128: it needs to be released first ;)
[14:52] <didrocks> 10th Dec 2013, it seems
[14:52] <didrocks> http://qt-project.org/wiki/Qt-5.2-release
[14:53] <didrocks> then, let's wait for Mirv, I know he's tracking the regressions and fixes
[14:53] <seb128> didrocks, well, http://bazaar.launchpad.net/~unity-team/unity8/trunk/revision/569
[14:53]  * larsu opens a bug in the meantime
[14:53] <seb128> didrocks, oh, I misread the commit message, I though we were making stuff depends on 5.2
[14:53] <larsu> seb128: how do I mark it blocking the qt release?
[14:53] <seb128> there is still the alternative though
[14:53] <didrocks> interesting, so we are stuck on releasing unity8 trunk until Qt is uploaded
[14:53] <didrocks> "nice"
[14:54] <seb128> didrocks, no, I misread that, sorry ;-)
[14:54] <seb128> didrocks, there is a |
[14:54] <seb128> didrocks, Mirv: ^ can you reply to larsu's question about how to mark a bug blocker for 5.2 landing?
[14:54] <didrocks> Mirv would konw
[14:55] <seb128> didrocks, sorry I included you in the pings there because it seems close from eod for Mirv and I supposed you would maybe know ;-)
[14:55] <seb128> didrocks, thanks
[14:55] <didrocks> seb128: I would in this evening meeting, thanks!
[14:58] <GunnarHj> seb128: Did you miss my question around 14:06?
[14:58] <larsu> Mirv, seb128: https://bugs.launchpad.net/ubuntu/+source/qtdeclarative-opensource-src/+bug/1257322
[14:58] <ubot2> Launchpad bug 1257322 in qtdeclarative-opensource-src (Ubuntu) "gsettings-qt doesn't work with Qt 5.2" [Undecided,New]
[14:59] <seb128> GunnarHj, I did read it but was dealing with other pings and forgot, sorry
[14:59] <seb128> larsu, thanks
[14:59] <seb128> GunnarHj, looking
[14:59] <GunnarHj> seb128: Ok, no problem.
[15:00] <seb128> GunnarHj, you should ask attente, he knows better about the text input dialog, he wrote it
[15:00] <GunnarHj> seb128: Ok, I'll do. Thanks!
[15:03] <seb128> attente, hey
[15:03] <attente> seb128, hi
[15:04] <seb128> attente, ^ fyi (Gunnar wondering about why the text entry panel lists Bengali (should be Bangla) ... where is the list coming from?
[15:05] <GunnarHj> attente: Hi! Repeating the q I asked seb128:
[15:05] <GunnarHj> attente: I'm thinking of adding a task to bug #991002. The reason is that Bengali (and not Bangla) is used in the "Choose an input source" window in "Text Entry". However, I have failed to figure out which package is affected. Can you possibly give me a hint on how/where that list is created?
[15:05] <ubot2> Launchpad bug 991002 in GLibC "Change name for bn-BD from 'Bengali(Bangladesh)' to 'Bangla(Bangladesh)')" [Medium,Confirmed] https://launchpad.net/bugs/991002
[15:09] <attente> GunnarHj, seb128, it seems to be /usr/share/X11/xkb/rules/evdev.xml
[15:10] <seb128> xkb-data then
[15:10] <seb128> attente, thanks
[15:10] <attente> i guess if we just change the one description, it might fix it
[15:11] <GunnarHj> attente: So it seems; I'm going to submit a MP then. Thanks!
[15:14] <seb128> GunnarHj, open an upstream bug, I doubt we are going to distro patch that without it
[15:15] <GunnarHj> seb128: Will do.
[15:19] <seb128> mterry, is there plan to make unity-greeter a proper upstart session (or at least run e.g dbus through an upstart-session job)?
[15:24] <mterry> seb128, there was a request for that, and it will probably happen in unity8-greeter.  I don't know about the demand for unity-greeter to have it
[15:25] <seb128> mterry, ted says that bug #1257251 is likely due to that (or the lack of it rather)
[15:25] <ubot2> Launchpad bug 1257251 in indicator-power (Ubuntu) ""exiting: service couldn't acquire or lost ownership of busname" errors on the greeter logs" [Medium,Confirmed] https://launchpad.net/bugs/1257251
[15:26] <mterry> seb128, hmm, is there a symptom or just log errors?
[15:26] <seb128> mterry, log spamming mostly, but it indicates things not being started/stopped as they should, so I wouldn't exclude apport reports or side effects
[15:27] <seb128> mterry, basically my guess is that dbus is going down before the indicator-stop signal is sent and that upstart tries to respawn indicators in between
[15:29] <mterry> seb128, hmm, right.  Because I think we run upstart now for indicators where we didn't before.
[15:29] <seb128> mterry, correct
[15:30] <seb128> mterry, we should at least make sure the indicator-stop signal is sent before taking dbus down, if the greeter is doing both
[15:30] <seb128> oh, it's meeting time
[15:31] <seb128> qengho_, Sweetshark, mlankhorst, Laney, tkamppeter, desrt, attente, larsu: hey
[15:32] <desrt> quiet meeting
[15:33]  * seb128 rings bell
[15:33] <seb128> good morning desktopers :p
[15:33] <attente> hi :)
[15:33] <seb128> seems so
[15:33] <seb128> let's try to get started
[15:33] <seb128> qengho_, hey!
[15:34] <mlankhorst> g'day mate
[15:34] <seb128> ok, maybe qengho_ is still on extended turkey eating w.e ;-)
[15:34] <seb128> Sweetshark, hey
[15:35] <desrt> you know how turkey makes you feel when you've had too much...
[15:35] <mlankhorst> same as chicken!
[15:35] <desrt> nobody is here today!!
[15:35] <seb128> Sweetshark, you have no turkey excuse!
[15:36] <seb128> mlankhorst, hey (at least somebody who is here ;-)
[15:36] <mlankhorst> hey
[15:36] <Laney> *** Ping timeout
[15:36] <desrt> *** mlankhorst quits [Ping timeout]
[15:36] <mlankhorst> preparing mesa 10, and testing it. upload xorg 1.15 to ppa
[15:36] <desrt> damnit
[15:36] <Laney> :D
[15:36] <desrt> Laney wins
[15:36] <mlankhorst> gsd optimus bugs LP #1224254
[15:36] <ubot2> Launchpad bug 1224254 in gnome-desktop3 (Ubuntu Precise) "xrandr Xerrors with the nvidia binary drivers (optimus)" [High,In progress] https://launchpad.net/bugs/1224254
[15:36] <seb128> lol
[15:36] <mlankhorst> some testing on xorg 1.15 too
[15:37] <seb128> mlankhorst, are you claiming credit for tseliot or is it the other way around? ;-) (he has a debdiff of the optimus report)
[15:37] <mlankhorst> ^D
[15:37] <mlankhorst> seb128: oh I helped him find some issues
[15:37] <seb128> oh ok, thanks for that ;-)
[15:37] <mlankhorst> I couldn't reproduce it locally but I had a hunch
[15:37] <seb128> can you share the ppa info again for the mesa 10 update?
[15:37] <seb128> in case other people want to test it
[15:37] <mlankhorst> https://launchpad.net/~ubuntu-x-swat/+archive/ppa/+packages
[15:38] <tseliot> yes, I was sabotaging myself when debugging and mlankhorst helped me realise that :D
[15:38] <seb128> ^ testing of that is welcome
[15:38] <seb128> tseliot, mlankhorst: glad you guys figured it out in any case ;-)
[15:38] <mlankhorst> I've tested the slow dash bug on g33, tested the 3 major vendors and also did smoke test to see if indirect still worked
[15:38] <seb128> seems like a good start
[15:38] <mlankhorst> only broken on glamor-egl, not going to be fixed before 1.15
[15:38] <seb128> hum
[15:38] <mlankhorst> there's a glx rewrite in 1.15
[15:38] <seb128> is that a regression?
[15:39] <mlankhorst> no :p
[15:39] <seb128> are you sure? ;-)
[15:39] <mlankhorst> yes :p
[15:39] <seb128> ok, fine then
[15:39] <mlankhorst> it's fixed by a glx rewrite
[15:39] <mlankhorst> but that is such a massive delta that I'm not going to try to get it in 1.14
[15:39] <seb128> well, let's see about 1.15 that's another topic, need more discussion/planning in any case
[15:39] <seb128> right
[15:40] <seb128> mlankhorst, thanks
[15:40] <mlankhorst>  47 files changed, 3580 insertions(+), 42560 deletions(-)
[15:40] <mlankhorst> though most deletions are autogenerated code
[15:40] <seb128> the diff is nice ;-)
[15:40] <seb128> Laney, hey
[15:40] <Laney> hallo
[15:40] <Laney> • Code reviews on some timezonemap contributions from David Shea at Redhat
[15:40] <Laney> • Porting work to help libav transition along, which went with samba and e-d-s; all got migrated in the end
[15:40] <Laney> • Investigation of a Qt bug with respect to time printing; turned out to be fixed in 5.2
[15:40] <tseliot> BTW thanks a lot for your help mlankhorst!
[15:41] <Laney> • u-s-s work: Rewrite graph axis drawing code in battery panel to more closely reflect the design (have 'big' and 'small' ticks) and to make the line drawing a bit simpler. Look into 'smoothing' the graph but the library didn't work properly.
[15:41] <Laney> • u-s-s: Discover that there's an antialiasing property on Canvas which improves the visual quality quite a lot.
[15:41] <Laney> • u-s-s: Some small reviews too
[15:41] <Laney> • Bisect evolution to find out when the message preview pane went black, find the affected commit & revert it, pinging on the upstream bug
[15:41] <Laney> • Package & upload new glib; exposed some regressions, wiggle jenkins/britney to get the reverted version (which seb128 uploaded, cheers) to migrate
[15:41] <Laney> • In gaps, look at webkitgtk/arm64 now that qemu-arm64 works. Still not there but it inches along.
[15:41] <Laney> • Patch pilot
[15:41] <Laney> • DMB meeting
[15:41] <Laney> NUL
[15:41] <seb128> how is webkitgtk going? did you manage to build enough to hit the errors in qemu? how slow is that?
[15:42] <Laney> yeah
[15:42] <Laney> it's not terrible
[15:42] <Laney> the problem is my knowledge at this point, should file it upstream
[15:43] <seb128> do you think you can get it resolved this week? should we talk about a plan B to force migrate it without arm64?
[15:43] <Laney> it will migrate
[15:43] <seb128> btw there is a new point release, not sure it fixes any arm64 issue?
[15:43] <Laney> nah, trying that one
[15:43] <Laney> the problem is when we try to build something against the new version
[15:43] <Laney> and it doesn't get an arm64 build
[15:44] <seb128> well, 2.3 is still in trusty-proposed
[15:44] <seb128> what is blocking migration?
[15:44] <Laney> i blocked it
[15:44] <seb128> oh ok
[15:45] <Laney> because it's a development release
[15:45] <Laney> so I didn't want to let it migrate if it wasn't going to work
[15:45]  * seb128 wants the new goa (with gtk support in its own binary), is that still blocked on webkit?
[15:45] <Laney> yeah, IIRC
[15:45] <Laney> although we might be able to replicate the split with our current package
[15:47] <seb128> ok
[15:47] <seb128> Laney, thanks
[15:47] <seb128> let's see if webkit clears out
[15:47] <seb128> if it's not done by next week I'm going to have a look to goa, I want that dealt with before holidays if possible
[15:47] <seb128> desrt, hey
[15:47] <Laney> I'll try trunk with the small patch and then forward it upstream
[15:47] <desrt> what's up?
[15:47] <desrt> oh.  right.
[15:47] <desrt> - dconf
[15:48] <desrt> fixing lots of bugs, writing tests, getting coverage up to 100% for most components and finally, a bunch of new features for the phone guys for OEM overrides
[15:48] <desrt> also did the usual random side stuff here and there with small bugs in glib, etc.
[15:48] <desrt> that's all
[15:49] <seb128> desrt, dconf "lots of bugs" ... anything that seems like it happens in practice and should be SRUed?
[15:50] <desrt> no.  mostly RFEs
[15:50] <desrt> dconf doesn't really have real bugs :p
[15:50] <desrt> well... i mean, there are theoretical things...but nothing important
[15:50] <desrt> things like what happens if a client receives an invalid dbus message from the service
[15:50] <desrt> ...but the service doesn't send those messages
[15:51] <desrt> it would be possible to send random dbus messages to programs using dconf and get criticals but.... i don't really think that's SRU-worthy :)
[15:51] <seb128> right, doesn't seem worth SRUing
[15:51] <seb128> desrt, thanks ;-)
[15:51] <seb128> attente, hey
[15:52] <attente> seb128, hi
[15:52]  * desrt was just writing testcases on the basis of "what could possibly go wrong here?" and found some stuff
[15:52] <attente> low-hanging fruit the past week, mostly MPs for some outstanding bugs in unity-gtk-module
[15:52] <attente> looked into the libre-office shortcuts problem, apparently it's fixed upstream now
[15:52] <attente> the compiz MP for handling input switching shortcuts needs some more changes before it can be accepted
[15:52] <attente> also doing some more compiz changes to try to move away from the legacy key grabber in g-s-d under unity
[15:52] <attente> (eof)
[15:52] <qengho_> seb128: I'm ready.
[15:52] <seb128> attente, @lo: great, do you have a commit reference?
[15:52] <attente> seb128, let me find it, one sec
[15:53] <seb128> attente, also to the compiz mp one, just curious what needs fixing there
[15:53] <attente> http://cgit.freedesktop.org/libreoffice/core/commit/?id=d77483f0ab1a7f97ec41adfac66d98696adeef70&h=libreoffice-4-1
[15:54] <attente> seb128, MC Return was worried about regressions
[15:54] <attente> also about whether it would work well enough with CCSM
[15:55] <desrt> MC Return?
[15:55] <desrt> please tell me this is our new name for ted
[15:55] <seb128> one of the compiz active guys
[15:55] <larsu> desrt: LOL
[15:55] <seb128> lol
[15:55] <desrt> damn
[15:55] <larsu> that might have been the funniest thing I've read all week
[15:55]  * attente *whoosh*
[15:56] <larsu> attente: "return;"
[15:56] <attente> oh, heh

[15:57] <attente> seb128, if you want to follow it, here's the thread: https://code.launchpad.net/~attente/compiz/modifier-tweaks/+merge/196300
[15:57] <seb128> attente, thanks, going to read that after the meeting
[15:57] <seb128> larsu, hey
[15:57] <larsu> - got gtk 3.10 ready for landing; pushed patch to solve build issues upstream
[15:58] <larsu> - amended overlay-scrollbar fixes after talking to Cimi and fix warnings (which allegedly led to crashes on some French computers)
[15:58] <larsu> - fixed ubuntu-themes issues with new gtk and overlay-scrollbars
[15:58] <larsu> - ido: merged outstanding request (+/- keys), fix two greeter crashes
[15:58] <larsu> - fixed action issue in indicator-power that the new glib uncovered
[15:58] <larsu> - looked into gsettings-qt not working with 5.2 (confirmed it's a qt issue)
[15:58] <larsu> eof
[15:58] <desrt> larsu: that action patch was awesome, btw
[15:58] <seb128> larsu, thanks, great work on GTK/o-s/theme/etc
[15:58] <larsu> desrt: thanks for making me do the extra bit ;)
[15:58] <larsu> seb128: :)
[15:59] <seb128> GTK 3.10 is in the desktop team ppa for those of you who want to test
[15:59] <desrt> you fixed the issue, fixed some other related conceptual cleanliness issues _and_ removed a net of 50 lines of code
[15:59] <seb128> https://launchpad.net/~ubuntu-desktop/+archive/ppa
[16:00] <desrt> larsu: now... start working on 3.12 :)
[16:00]  * desrt hides
[16:00] <seb128> qengho_, hey, your turn if you are still around ;-)
[16:00] <qengho_> YAY!
[16:00] <qengho_> * Got awesome PPA to streamline build-test-release. armhf isn't 100 hours any m
[16:00] <qengho_> ore.
[16:00] <qengho_> * More apparmor tweaking and testing for chromium-browser.
[16:00] <qengho_> * Tested chromium-browser after libnss change, updated apport reporting. About t
[16:00] <qengho_> o release 31.0.1650.57 to #security.
[16:00] <qengho_> * To-do: apparmor tightening testing more. accessibility on Linux. decide third-party-cookies default.
[16:00] <qengho_> EOF
[16:01] <seb128> qengho_, 30.0.1599.114-0ubuntu0.13.10.2  is stucked in trusty-proposed for a month, do you know what's going on there?
[16:01] <seb128> autopkgtest for chromium-browser 30.0.1599.114-0ubuntu0.13.10.2: FAIL (Jenkins: public, private)
[16:01] <seb128> (http://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html)
[16:02] <seb128> https://jenkins.qa.ubuntu.com/view/Trusty/view/AutoPkgTest/job/trusty-adt-chromium-browser/ARCH=amd64,label=adt/34/console
[16:02] <qengho_> seb128: er, no. I think I remember something from weeks ago, but I don't remember what it was.
[16:02] <seb128>        -> Cannot install libunity-webapps-chromium; apt errors follow:
[16:02] <qengho_> Oh.
[16:02] <qengho_> OH.
[16:02] <Laney>  E: Package 'libunity-webapps-chromium' has no installation candidate
[16:03] <qengho_> I'll look into that. I don't remember
[16:03] <seb128> qengho_, can we get that resolved this week? it sucks to be delay for > 1 month, we should be more on top of such issues
[16:03] <Laney> yeah, pretty sure we pinged about that
[16:03] <seb128> delayed*
[16:03] <seb128> qengho_, thanks
[16:03] <qengho_> Laney: I think so too. And I think it was simple to discover theproblem.
[16:03]  * Laney nods
[16:04] <seb128> it seems like that just got forgotten in the middle of other stuff
[16:04] <seb128> let's get it resolved this week
[16:04] <seb128> qengho_, thanks, let me know if you need help/if we should maybe force the migration over it (check with didrocks though, I think he mentioned loosing tabs/chrome when trying that version)
[16:05] <seb128> (I should try it as well)
[16:05] <seb128> tkamppeter, hey (sorry forgot you earlier)
[16:05] <tkamppeter> - cups-filters: Made PPD-less PCL 5c/e printing working.
[16:05] <tkamppeter> - cups-filters: Released 1.0.42 with full support for PPD-less printing on PWG Raster (IPP Everywhere), PostScript, PDF, PCL 5c/e, and PCL-XL printers and numerous bug fixes.
[16:05] <tkamppeter> - synced some printer driver packages from Debian.
[16:05] <tkamppeter> - Working on Landscape format output bug in Poppler.
[16:05] <tkamppeter> - Bugs
[16:06] <tkamppeter> Note, PPD-less printing is for printing without drivers and printer setup tool on mobile devices.
[16:06] <seb128> ok
[16:06] <seb128> tkamppeter, did you see https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1131854 ?
[16:06] <ubot2> Launchpad bug 1131854 in cups (Ubuntu) "cupsd crashed with SIGABRT in __assert_fail_base()" [High,Confirmed]
[16:07] <qengho_> didrocks: I'm interested in if you have tabs/chrome problem with PPA version, @ https://launchpad.net/~canonical-chromium-builds/+archive/stage
[16:07] <seb128> tkamppeter, it would be nice if you could have a look, that bug got 2424 reports
[16:08] <seb128> tkamppeter, thanks
[16:08] <seb128> ok, my turn
[16:08] <tkamppeter> seb128, will do, but not sure whether it is CUPS, can also be Avahi.
[16:08] <seb128> tkamppeter, thanks
[16:10] <seb128> ok, my turn
[16:10] <seb128>  * tested new GTK, reported some bugs, tested some patches
[16:10] <seb128>  * backported some fixes for nautilus issues
[16:10] <seb128>  * ran into rhythmbox issues with new glib, looked at n-m on touch issues as well, ended up reverting some upstream commit to workaround the issues
[16:10] <seb128>  * ubuntu-system-settings
[16:10] <seb128>    - some code reviews
[16:10] <seb128>    - some easy UI tweaks, small changes to deal with toolkit deprecations, reported some toolkits before/feature requests on the way
[16:10] <seb128>    - looked at bit more to the autopilot tests, almost ready for merging
[16:10] <seb128>  * kept looking at e.u.c, poked at some of the issues, pinged people, trying to get things moving/fixes landing
[16:10] <seb128>  * lot of discussions about bugs, patches, debugging, etc that I didn't list and don't remember in details
[16:10] <seb128>  (just feeling like I've spent most of the week bouncing between bugs/providing debug infos/forwarding those, fixing some, etc)
[16:11] <Laney> fun
[16:11] <larsu> seb128: thanks for helping out with testing gtk
[16:11] <seb128> larsu, yw!
[16:12] <seb128> I should take more notes about all the bugs I bounce in-between, I always fail to remember half of those for the meeting summary
[16:12] <Laney> is it weird that I kind of liked the long dialogs?
[16:12] <larsu> Laney: yes
[16:12] <larsu> have you seen them in a language that has longer words on average?
[16:12] <seb128> Laney, you don't know what you are talking about
[16:13] <Laney> hahaha
[16:13] <seb128> Laney, https://bug719516.bugzilla-attachments.gnome.org/attachment.cgi?id=263099
[16:13] <seb128> Laney, I guess you didn't get that? ;-)
[16:13] <Laney> man, that is claaaaaaaaaaaaaaaassy
[16:13] <seb128> lol
[16:13] <seb128> you are weird indeed :p
[16:13] <desrt> seb128: talking about every single bug during the meeting would be insane
[16:13] <Laney> nah, probably didn't see one that bad
[16:14] <seb128> desrt, yeah, sometime I've a few interesting one/topic worth mentioning though (like those long dialogs ;-)
[16:14] <seb128> one*s*
[16:14] <seb128> I should note those down
[16:14] <desrt> END MEETING
[16:14] <seb128> Sweetshark, hey, still not around?
[16:15] <seb128> desrt, let's see, Sweetshark woke up on another channel, he might want to give his update there
[16:15] <desrt> oh.  nice.
[16:15] <Sweetshark> seb128: reporting in.
[16:15] <Sweetshark> seb128: sorry.
[16:15]  * desrt airlifts some fritzkola to Sweetshark, amazon style
[16:15] <seb128> hey Sweetshark, nice from you to join us ;-)
[16:15] <desrt> wake up, man!!
[16:16] <larsu> desrt: that amazon piece was the most brilliant PR move I've seen in a while
[16:16] <seb128> lol
[16:16] <larsu> free ads in all major pulibcations on a day before the busiest online shopping day in the US
[16:17] <larsu> *publications
[16:17] <seb128> Sweetshark, zzzZZzzzz
[16:17] <Sweetshark> seb128: so, late feature reviews upstream, some work on separating l10n out of the build (should be finished upstream, but needs tweaking in ./debian) EOF
[16:17] <desrt> seb128: maybe we need to up the ante to club mate
[16:17] <larsu> oh yeah
[16:17]  * larsu is out :(
[16:17] <seb128> club mate, no thanks
[16:18] <desrt> seb128: not for you.  for Sweetshark.
[16:18] <seb128> right, it seems like he could need it (and it would mean I would need to get it if he drinks it all)
[16:18] <seb128> Sweetshark, thanks ;-)
[16:18] <seb128> ok
[16:18] <seb128> questions/comments/...
[16:18] <seb128> oh, one comment from me
[16:19] <seb128> we should know soon if there is a desktop week in january/february
[16:19] <seb128> msm was out last week but that's supposed to be discussed this week
[16:19] <desrt> seb128: first week of february, please :)
[16:19] <seb128> I've hinted for that
[16:19] <desrt> and in london...
[16:19] <Laney> thinking london?
[16:19] <Laney> (boo)
[16:19] <desrt> yes.  i'm always looking for a side event to make it worthwhile to go to FOSDEM
[16:19] <seb128> Laney, that would be good, it would one trip for those who want to go to FOSDEM
[16:19] <Laney> but cool, desktop week
[16:19] <seb128> (well, counting London<->Brussel has a short one)
[16:20]  * desrt has a free ride offered from norwich to brussels and back, for that weekend
[16:20] <larsu> +1 for London
[16:20] <Laney> week after fosdem would be preferable
[16:20] <Laney> (if there's a choice)
[16:20] <desrt> week before has a hackfest, for me
[16:20] <desrt> again, in norwich...
[16:20] <Laney> ah, norwich is nice
[16:20] <Laney> what's the hackfest?
[16:20] <desrt> gnome docs
[16:21] <seb128> (</end of meeting>)
[16:21]  * desrt likes to use gnome docs hackfests as a chance to catch up on his documentation in addition to being on hand for all of the other people to ask how stuff in our platform is supposed to work before they attempt to document it
[16:22] <Laney> neat
[16:22] <larsu> desrt: thanks for that. I imagine it improves docs a lot
[16:22] <desrt> larsu: we have a nice pattern down.  and HowDoIs came out of the last time and i was at such an event...
[16:23]  * desrt is still on the fence about howdoi for dconf vendor/framework/app-provided (gdm?) profiles
[16:23] <larsu> desrt: do it!
[16:24] <desrt> "there's this thing that i don't want you to do... but you're going to do it anyway... and you're probably going to do it wrong... so at least let me tell you how to do it right..."
[16:25]  * desrt loves (for example) how ibus uses a system-db and a custom profile to get default values, as an alternative to gsettings schemas
[16:27] <didrocks> qengho: sorry, was in meeting, you want to hurt my chrome again? :p
[16:27] <larsu> desrt: but ... why?
[16:27] <qengho> didrocks: YES!
[16:27] <desrt> larsu: i have no idea.  i'm asking around.
[16:27] <didrocks> qengho: ok, doing ;)
[16:27] <didrocks> (and eventually hating you soon)
[16:27] <larsu> desrt: ah... "love" was sarcastic
[16:27] <qengho> didrocks: I heard you had trouble with a recent chromium. I want to make sure it's all in your head.
[16:28] <didrocks> yeah
[16:28] <didrocks> let's see
[16:28] <desrt> larsu: apparently they came to the conclusion (on their own) that what they were doing was awful and switched to using gsettings
[16:28] <desrt> so win.
[16:28] <larsu> nice
[16:31] <didrocks> qengho: same issue, all my tabs are desperatly white agains
[16:31] <didrocks> I hate you btw ;)
[16:32] <didrocks> hum, I have a bunch of chromium process still running
[16:32] <didrocks> let me try kill everything
[16:32] <qengho> didrocks: Desolé!
[16:33] <qengho> didrocks: Did it complain about locking the profile?
[16:33] <didrocks> qengho: no, no complain at all
[16:33] <didrocks> ok, killed everything
[16:33] <didrocks> and fine then
[16:33]  * qengho boggles.
[16:34] <didrocks> so, even quitting chromium, I have a lot of process left
[16:34] <didrocks> I think that's what interfere between chromium version
[16:35] <desrt> super win.  they're abandoning their internal abstraction and switching to straight-up gsettings
[16:35] <desrt> devhelp style
[16:36] <didrocks> qengho: yeah, I clearly have one process hitting the CPU like crazy
[16:36] <didrocks> and not wanted to die once I'm closing chromium
[16:36] <qengho> didrocks: What does it look like in ps?
[16:37] <didrocks> qengho: before closing chromium: http://paste.ubuntu.com/6515326/
[16:37] <didrocks> qengho: and the hanging ones after closing chromium: http://paste.ubuntu.com/6515331/
[16:38] <seb128> desrt, larsu: I was waiting for you to say "because dconf doesn't abort on missing schemas" :p
[16:38] <larsu> haha
[16:38] <seb128> half joking
[16:38] <seb128> I'm sure some people do it this way because of that
[16:38] <larsu> I know. That makes it so funny!
[16:41] <desrt> seb128: actually, ibus is the only thing on earth that uses dconf this way
[16:41] <desrt> it's truly exceptional
[16:42] <desrt> the only other thing that comes close is gdm, but and it does in order to change the behaviour of _other_ programs that it runs under itself (ie: the login screen session)
[16:44] <qengho> didrocks: Do you mind running Cr in a terminal without and with  --disable-extensions  to see if there's a difference?
[16:44] <didrocks> qengho: sure
[16:47] <didrocks> qengho: yep, it's an extension apparently, it will be quick, I have 5 and 4 of them are google ones :)
[16:47] <qengho> didrocks: if it's sync, it could be  https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1225215
[16:47] <ubot2> Launchpad bug 1225215 in chromium-browser (Ubuntu) "chromium doesn't shut down. Next run gets "Your profile could not be opened"." [Undecided,In progress]
[16:49] <didrocks> qengho: yeah, I didn't get that profile though
[16:52] <didrocks> qengho: hum, all extensions disabled, still hanging
[16:52] <didrocks> qengho: is this option doing anything else?
[16:52] <qengho> Oh, well that's confusing.
[16:53] <qengho> didrocks: Well, it doesn't "disable" them so much as hide the index of them so they don't appear to be installed. So it's not quite the same thing.
[16:53] <qengho> didrocks: I'll get back to you with some ideas and questions. Thank you very much.
[16:53] <didrocks> qengho: oh, really, it seemed to be a little bit more involved seeing how long it was taking :)
[16:53] <didrocks> qengho: thanks!
[16:53] <didrocks> qengho: if that can help, the warning I'm getting: http://paste.ubuntu.com/6515393/
[16:54] <qengho> Thanks, d. None of those look unusual to me.
[16:54] <didrocks> ok
[16:58] <Mirv> seb128: tag qt5.2 https://bugs.launchpad.net/bugs/+bugs?field.tag=qt5.2
[16:59] <Mirv> seb128: qt 5.2 is supposed to land when it's released, that list is empty and we have a image with Qt 5.2 PPA enabled that gives same autopilot results at Qt 5.0.2
[16:59] <Mirv> larsu: ^ the tag
[17:00] <larsu> Mirv: thanks I'll add it
[17:05] <seb128> Laney, did you see any visible different with the antialiasing on? I've a graph that's not smooth but it doesn't look different with it
[17:06] <Laney> yes
[17:06] <Laney> it looks way different to me ...
[17:06] <Laney> sec
[17:08] <seb128> Laney, http://ubuntuone.com/6mCyngMtaJji3Hn8GNKdOb is the result here
[17:08] <seb128> but that graph has lot of things to smooth
[17:09] <seb128> just the 2 glitches in the first segment
[17:09] <Laney> http://ubuntuone.com/2bEGsM1Y6hPS0DhB59BYTj
[17:11] <seb128> ok, it's better indeed, you also have that "width doesn't seem constant" issue, just before the flat segment
[17:11] <Laney> yep
[17:11] <Laney> the canvas implementation doesn't seem the best
[17:11] <Laney> should see what it's like with 5.2
[17:11] <seb128> yeah, let's not spend too much time on a graph though
[17:11] <seb128> that's a pretty minor thing
[17:12] <Laney> well we're using it fine
[17:12] <Laney> nothing we can do to fix that afaik
[17:12] <seb128> the colors look weird as well
[17:12] <seb128> I wonder if I should put more steps in the gradient
[17:12] <seb128> I just did green->yellow->red
[17:12] <Laney> I was wondering if maybe it shouldn't be linear or something
[17:12] <seb128> green->red was not looking nice, but that yellow is a bit "fluo"
[17:12] <Laney> don't know about that kind of thing though
[17:13] <seb128> yeah, me neither
[17:14] <seb128> fluo->neon
[17:14] <seb128> or whatever it's called in english :p
[17:14] <Laney> fluorescent
[17:14] <Laney> or luminous
[17:14] <seb128> thanks
[17:14] <seb128> we say "fluo" as the common/short version of fluorescent
[17:15] <seb128> you guys don't do that?
[17:15] <Laney> nope
[17:15] <seb128> k
[18:13] <seb128> tkamppeter, just saw your poppler bugfix upload, is that patch coming from upstream/upstreamed? (there is no such reference on the bugs you listed nor in the upload)
[18:16] <tkamppeter> seb128, no, but it is on my TODO list for submitting upstream. I have found this bug and created the fix by myself, after seeing https://bugzilla.redhat.com/show_bug.cgi?id=768811 and the related distro patch for cups-filters (which I did not upstreamize as the real bug is in Poppler).
[18:16] <ubot2> bugzilla.redhat.com bug 768811 in cups-filters "Landscape Printing not working" [Unspecified,Closed: errata]
[18:17] <seb128> tkamppeter, ok, thanks. It's nice to upstream first, so you can have the bug reference in the patch upload, but as long as it's upstreamed things are fine I guess
[18:38] <seb128> Sweetshark, if we do another libreoffice upload to saucy, can we get http://cgit.freedesktop.org/libreoffice/core/commit/?id=d77483f0ab1a7f97ec41adfac66d98696adeef70&h=libreoffice-4-1 included (I guess that's in 4.2 for trusty already?)
[18:47] <Sweetshark> seb128: sure.
[18:47] <seb128> Sweetshark, thanks
[20:34] <robert_ancell> desrt, are you a GNOME foundation member?
[20:36] <desrt> yes
[20:40] <robert_ancell> desrt, is https://www.gnome.org/foundation/membership/ not up to date then?
[20:40] <robert_ancell> it seems a lot more sparse than I'd expect
[20:45] <desrt> ya... something is wrong with that page
[20:51] <rickspencer3> robert_ancell, are you around yet?
[20:55] <robert_ancell> rickspencer3, sure am
[20:56] <rickspencer3> hey robert_ancell
[20:56] <rickspencer3> I did a dist-upgrade this afternoon, and now that computer won't get to LightDM
[20:56] <rickspencer3> sadly, it's back in my co-working space
[20:56] <rickspencer3> I had to come home to get back online
[20:57] <rickspencer3> robert_ancell, this is trusty, obviously :)
[20:57] <rickspencer3> also, hi, how are you (and other things a person might say to another person ; ) )
[20:57] <robert_ancell> rickspencer3, I had a problem this morning where i couldn't type into the greeter but an upgrade brought in X and that fixed it
[20:57] <robert_ancell> I'm fully dist-upgraded now and using trusty - do you have any logs?
[20:58] <rickspencer3> robert_ancell, like I say, I don't have access to that 'puter atm
[20:58] <robert_ancell> :(
[20:58] <rickspencer3> it could be x that won't start
[20:58] <rickspencer3> hybrid graphics :/
[20:58] <seb128> little chance to debug that without access to the box...
[20:58] <robert_ancell> rickspencer3, oh, do you have a nvidia card in it?
[20:58] <rickspencer3> robert_ancell, yeah
[20:58] <seb128> robert_ancell, weird, we didn't have any significant xorg changes recently
[20:58] <robert_ancell> rickspencer3, I can't boot with the trusty kernel, nouveau locks up the kernel for me (I think)
[20:58] <robert_ancell> I'm running the saucy kernel by choosing it at grub
[20:58] <rickspencer3> hmmm, not sure I have pre-trusty kernel on it
[20:59] <rickspencer3> I tried the previous kernel but that didn't work either
[20:59] <robert_ancell> I'm running 3.11.0-13-generic
[20:59] <rickspencer3> robert_ancell, ok, I'll poke at it in the morning
[20:59] <seb128> can you got to a vt?
[20:59] <rickspencer3> seb128, no
[20:59] <seb128> e.g ctrl-alt-f1
[20:59] <rickspencer3> no vt
[20:59] <rickspencer3> nada
[20:59] <robert_ancell> me neither
[20:59] <rickspencer3> totally screwed
[20:59] <seb128> ok, so not an xorg issue
[20:59] <seb128> seems like the kernel issue robert_ancell is describing
[20:59] <robert_ancell> though I saw some nouveau errors messages on a text console at one time
[21:00] <seb128> go nvidia :/
[21:00] <rickspencer3> robert_ancell, well, if you don't know what it is off hand, I think I;ll just have to bring my other laptop to my co-working space tomorrow
[21:00] <seb128> thanks guys, you convinced me to stay on intel for my next config ;-)
[21:00] <rickspencer3> and an ethernet cable
[21:00] <rickspencer3> seb128, well, this is hybrid graphics
[21:00] <robert_ancell> seb128, yeah, I always regret not going pure intel
[21:00] <rickspencer3> a total pita
[21:00] <robert_ancell> so is mine
[21:01] <robert_ancell> seb128, hey, still online btw? :)
[21:01] <robert_ancell> seb128, I'm running unity-control-center here
[21:01] <seb128> robert_ancell, hey, seems so ... "still" is rather "back", just back from dinner
[21:02] <seb128> robert_ancell, how does it feel? ;-)
[21:02] <robert_ancell> seb128, pretty much like before, but *much* easier to hack on
[21:02] <seb128> I meant to look at u-s-d and u-c-c this week
[21:02] <robert_ancell> seb128, yeah, I was going to push all the packages into a PPA then do a call for testing
[21:02] <seb128> do you still have work you want to get done on those?
[21:02] <robert_ancell> and review
[21:02] <seb128> or do you feel like we are getting ready for review etc?
[21:02] <seb128> cool
[21:03] <seb128> I'm going to have a look
[21:03] <robert_ancell> there's some small details on u-c-c, but I don't know if we need to bother / solve them right now
[21:03] <seb128> tell me
[21:03] <robert_ancell> I haven't tried running u-s-d yet, but will do that after u-c-c
[21:03]  * seb128 is scared of all the crazyness robert_ancell is doing
[21:03] <robert_ancell> oh, chill out! :)
[21:03] <seb128> that seems backward!
[21:03] <seb128> you should be able to run g-c-c on top of u-s-d
[21:04] <seb128> well at least while the version are in sync, which is the case atm
[21:04] <robert_ancell> but wont be for long
[21:04] <seb128> well, it is atm :p
[21:04] <robert_ancell> 1. two of the icons have changed since we had to rename them and the gnome theme has the different names - not sure if we should copy the icons from the gnome theme over the control-center ones to make them change back
[21:04] <seb128> and that would be a good testcase to make sure you didn't do incompatible changes to dbus or gsettings keys
[21:05] <robert_ancell> 2. Might want some packaging magic to uninstall libgnome-control-center now it doesn't exist
[21:05] <seb128> there is no such magic
[21:05] <seb128> you advocate for Unity users have g-c-c leftover and now you want to clean the small lib in the other direction? ;-)
[21:05] <robert_ancell> 3. Some of the package names for custom panels refer to gnome but they only work in unity now (since they use libunity-control-center)
[21:06] <seb128> you renamed the lib?
[21:06] <robert_ancell> seb128, no, the new g-c-c should probably conflict on it since anything compiled against it wont show in the new g-c-c or u-c-c
[21:06] <seb128> I guess it makes sense... that's not going to be a big transition
[21:06] <robert_ancell> I think I've got all the cases but there could be third party ones or something I've missed
[21:07] <seb128> seems like a pointless change
[21:07] <robert_ancell> seb128, what is?
[21:07] <seb128> renaming the lib
[21:07] <seb128> but at the same time it's not like lot of third party softwares are using it
[21:07] <robert_ancell> but it doesn't work with the new g-c-c, it would be very unclear to give it the old name
[21:07] <robert_ancell> exactly
[21:07] <seb128> those who are can probably rebuild for the new LTS
[21:07] <robert_ancell> we can do this properly since there's not a lot of consumers
[21:07] <seb128> ok, fair enough
[21:08] <seb128> so
[21:08] <robert_ancell> I haven't changed the function calls so it's trivial to recompile (though I was wondering if we should change any prefixes)
[21:08] <seb128> 1. I don't understand the issue enough, do you have a bug report? ;-)
[21:08] <robert_ancell> seb128, It hasn't been released so no bug report
[21:08] <seb128> it feels like we should just ship those icons in our theme or in u-c-c
[21:08] <robert_ancell> seb128, yeah
[21:09] <seb128> 2. just make g-c-c conflicts on the lib
[21:09] <seb128> the apt resolver should be smart enough, assuming there is no user of the lib left
[21:09] <robert_ancell> seb128, but basically, the sound panel uses an icon installed in /usr/share/icons, we have to rename ours since it would conflict with the one in g-c-c. But the icon in the u-c-c/g-c-c package never gets used because there's a different icon in the gnome theme package.
[21:10] <seb128> well, if it's not used just delete it from u-c-c
[21:10] <robert_ancell> seb128, so we should put the used icon into the u-c-c source
[21:10] <robert_ancell> seb128, it should probably provide an icon by default since otherwise it has no icon if you uninstall the theme
[21:10] <seb128> it's u-c-c
[21:10] <seb128> it can depends on our theme
[21:10] <robert_ancell> seb128, sure, then we can delete all the icons
[21:10] <seb128> Unity is a desktop, not a toolbox
[21:11] <seb128> (copy GNOME speech ;-)
[21:11] <robert_ancell> works for me
[21:11] <robert_ancell> I'll just add a dependency on the theme
[21:11] <seb128> +1
[21:11] <robert_ancell> though the used icons are in the gnome theme, so it's a bit weird
[21:11] <robert_ancell> i.e. humanity doesn't override any of these icons afaict
[21:12] <robert_ancell> meh, it's a minor point. Any result which shows the same icons as today will do
[21:12] <seb128> well, the other option is to patch gnome-icon-theme to add them there and patch it out of g-c-c and u-c-c
[21:12] <seb128> but that's more work
[21:12] <robert_ancell> I'll just copy them from gnome-icon-theme to u-c-c
[21:12] <seb128> ok, as long as there is no file conflict
[21:12] <robert_ancell> there wont be
[21:13] <seb128> cool
[21:13] <seb128> 3. is a non issue, let's just do a small transition/rename those panels
[21:13] <seb128> there is like 4 of those
[21:14] <robert_ancell> 4. activity-log-manager is in some sort of crash loop, not sure if that's due to u-c-c or it's just broken in trusty
[21:14] <seb128> it's not broken in trusty
[21:15] <robert_ancell> and 5. activity-log-manager and deja-dup we need to talk to upstream - are their panels only working in unity? Then we should get them to take the patches so they compile against libunity-control-center instead
[21:15] <seb128> you might hit a bug which doesn't have to do with the renaming though
[21:15] <robert_ancell> yeah
[21:15] <robert_ancell> I think I might just do the PPA now and fix that one later
[21:15] <seb128> alm, we are sort of upstream
[21:15] <robert_ancell> I figured we're close enough to upstream for both
[21:15] <seb128> (well Seif is, but I'm not sure he's still interested in it, we co-maintain it)
[21:16] <seb128> deja-dup -> mterry (he's in London this week so offline at this time)
[21:16] <seb128> right
[21:16] <seb128> ok
[21:16] <seb128> did you try GTK 3.10?
[21:16] <robert_ancell> oh there was 6. Is there any way to get update manager to do an apt-get autoremove or similar so g-c-c is uninstalled on GUI dist-upgrades?
[21:16] <robert_ancell> no
[21:16] <seb128> (just pondering if we should mix testing/transition in the desktop ppa)
[21:17] <robert_ancell> seb128, do you think I should just dump all this into the main PPA?
[21:17] <seb128> I'm testing GTK 3.10 in the main ppa
[21:17] <seb128> maybe let's use another one for the first round
[21:17] <robert_ancell> sure
[21:17] <seb128> or let me tomorrow to test your stuff
[21:17] <seb128> I plan to try to move GTK to trusty this week
[21:18] <robert_ancell> I feel it's at the point where I think we should definitely go ahead. I know you and Laney are a bit nervous about the forking
[21:18] <seb128> then we can use the ppa for u-s-d u-c-c next week
[21:18] <robert_ancell> It's all wins for us and the GNOME people
[21:18] <seb128> I'm not nervous about forking
[21:18] <seb128> I'm nervous about you doing it :p
[21:18] <robert_ancell> vote of confidence hah!
[21:18] <seb128> ;-)
[21:18] <seb128> joke aside, the current approach seems fine
[21:19] <seb128> I was nervous about renaming keys
[21:19] <seb128> you didn't do that right?
[21:19] <robert_ancell> It's like that in my current branch, but I'm going to look at reverting that
[21:19] <seb128> renaming the keys?
[21:19] <robert_ancell> yes
[21:19] <seb128> how did you migrate config?
[21:19] <robert_ancell> I hadn't got to that yet
[21:19] <robert_ancell> I was still testing
[21:19] <seb128> ok, so you just reset config for u-s-d?
[21:20] <robert_ancell> we could migrate config, it's not impossible
[21:20] <seb128> "reset"
[21:20] <seb128> start fresh rather
[21:20] <seb128> no, it's not, but that's getting tricky
[21:20] <robert_ancell> seb128, yes, but this was just so I could co-install them and test
[21:20] <seb128> and I would prefer to avoid dealing with migration in a LTS cycle
[21:20] <seb128> because we might just learn from those from people doing LTS upgrades
[21:21] <seb128> we don't want to make the experience suck for those
[21:21] <robert_ancell> seb128, note that you can't run the vanilla g-c-c because we removed some keys from g-s-d - so we did the same thing I'm worried about to GNOME :)
[21:21] <seb128> we did?
[21:21] <seb128> we did revert commits that include new keys?
[21:21] <robert_ancell> for the input methods - we reverted to the old method but didn't leave the new keys in the schema
[21:22] <seb128> oh, that's a bug more than a feature
[21:22] <seb128> but yeah, I'm sure that's going to happen
[21:22] <seb128> I just don't want to learn about upgrade issue by hitting LTS users
[21:22] <robert_ancell> that's where it gets easier if we can rename the schemas, but I'll try and tackle that later if we have time
[21:22] <seb128> we can do the schemas rename next cycle
[21:22] <robert_ancell> sure
[21:23] <seb128> right, let's see
[21:23] <seb128> land the first round and iterate
[21:23] <robert_ancell> ai
[21:23] <seb128> if we get confident about the migration we can discuss it
[21:23] <seb128> otherwise next cycle is fine
[21:24] <robert_ancell> seb128, hmm, I can't add PPAs to ~ubuntu-desktop anymore?
[21:24] <seb128> so let's split the g-c-c schemas in a new binary shared between both as a first step
[21:24] <robert_ancell> yep
[21:24] <robert_ancell> And there's a spelling mistake in the team description
[21:25] <robert_ancell> "since it gives you commit right to bzr."
[21:25] <seb128> robert_ancell, I promoted you back to admin, have fun
[21:25] <robert_ancell> hah! you will regret it ;)
[21:25] <seb128> let's see :p
[21:25] <robert_ancell> oh, I was trying to think of a good name for the PPA
[21:25] <robert_ancell> that wasn't going to be taken the wrong way politically
[21:26] <seb128> uss?
[21:26] <robert_ancell> I'm going to try and be careful so we don't get bad press when we do this
[21:26] <seb128> or ucc
[21:26] <robert_ancell> and that includes u-s-d as well? I guess it implies it
[21:26] <seb128> yes
[21:26] <seb128> or just "settings"
[21:26] <robert_ancell> I called all the branches unity-control-center so I'll stick with that
[21:27] <robert_ancell> seb128, you up much longer?
[21:28] <robert_ancell> I wanted to avoid settings so it wasn't confused with the new settings work
[21:28] <seb128> robert_ancell, I'm about to go back home, so I should be offline for like 15 min, then I'm probably going to do some for hacking for another hour
[21:28] <robert_ancell> seb128, oh, where are you now?
[21:29] <seb128> I went outside for dinner and brought the laptop with me
[21:29] <robert_ancell> Oh, I had a 7 - should we call it unity-control-center 1.0 or 3.6.3? I think 1.0 would be clearer
[21:30] <seb128> 7?
[21:30] <seb128> oh
[21:30] <robert_ancell> yeah, we could do 7 too
[21:30] <seb128> lol
[21:30] <robert_ancell> It's just odd to stick on an obscure 3.6.3 forever
[21:31] <seb128> use our naming scheme?
[21:31] <seb128> 13.12
[21:31] <seb128> or 14.04.0
[21:31] <robert_ancell> but we might never update it for 14.10
[21:31] <seb128> ok, 1.0 it is then
[21:31] <seb128> we should put it under daily landing
[21:31] <seb128> so it's going to be 1.0+daily<something>
[21:32] <seb128> which seems fine
[21:32] <robert_ancell> yes
[21:32] <robert_ancell> oh yay. We can drop the -0ubuntu1
[21:32] <seb128> ;-)
[21:32] <seb128> ok, dropping offline
[21:32] <robert_ancell> bye
[21:32] <seb128> back in 15 minutes or so if you have other questions
[22:16] <seb128> robert_ancell, where is your u-s-d work? I don't see any "settings" on https://code.launchpad.net/~robert-ancell/
[22:17] <robert_ancell> seb128, lp:~ubuntu-desktop/gnome-settings-daemon/unity
[22:17] <seb128> thanks
[22:19] <robert_ancell> seb128, bug 1257505
[22:19] <ubot2> Launchpad bug 1257505 in unity-control-center (Ubuntu) "Create Unity Control Center so can remain on old GNOME Control Center version" [Medium,In progress] https://launchpad.net/bugs/1257505
[22:19] <robert_ancell> trying to get the PPA priority bumped, all the packages are there
[22:21] <robert_ancell> seb128, oh, I noticed you made a change to g-c-c since I branched - can you push that into lp:unity-control-center?
[22:21] <robert_ancell> the 48 change
[22:21] <seb128> robert_ancell, doesn't seem like those builds are a priority right? ;-)
[22:21] <robert_ancell> all the ~ubuntu-desktop stuff is a priority
[22:21] <seb128> robert_ancell, sure, can push there
[22:22] <seb128> hum
[22:22] <seb128> robert_ancell, I branched lp:~ubuntu-desktop/gnome-settings-daemon/unity and the changelog has "gnome-settings-daemon (3.8.5-0ubuntu11.1) saucy; urgency=low"
[22:22] <seb128> is that normal?
[22:23] <seb128> rules has the binary named g-s-d
[22:23] <seb128> things looks wrong
[22:23] <robert_ancell> yeah, I didn't update the changelog
[22:23] <robert_ancell> bzr log should show a bunch of changes though
[22:23] <seb128> ups
[22:23] <seb128> control
[22:23] <seb128> right
[22:23] <seb128> but you didn't rename the binaries?
[22:23] <robert_ancell> not yet
[22:23] <seb128> I though you wanted to make those co-installable?
[22:23] <seb128> oh, ok
[22:23] <seb128> what did you change then?
[22:24] <seb128> just having an import/full source doing the same thing as current trusty is doing?
[22:24] <robert_ancell> yes, that looks right
[22:24]  * robert_ancell tries to find the branch where I did the renaming
[22:25] <seb128> what do you want me to review/test?
[22:25] <robert_ancell> lp:~ubuntu-desktop/gnome-settings-daemon/rename-to-unity
[22:25] <robert_ancell> not u-s-d
[22:25] <robert_ancell> but u-c-c yes
[22:28] <seb128> ok
[22:34] <seb128> robert_ancell, oh, shrug, renaming the binary means patching apps that call g-c-c :/ (I guess that's why you added indicators to your bug)
[22:34] <robert_ancell> seb128, yep, but I think I've got them all
[22:34] <seb128> I doubt that
[22:34] <robert_ancell> I was able to remove g-c-c from my system and reverse-depends seems happy
[22:36] <seb128> robert_ancell, like eog calls g-c-c
[22:37] <robert_ancell> set as background?
[22:37] <seb128> robert_ancell, yes, or cairo dock calls it
[22:37] <seb128> robert_ancell, http://codesearch.debian.net/search?prev=0.82.138&q=gnome-control-center+&skip=182
[22:38] <robert_ancell> well, cairo dock is not necessarily wrong, it's only apps that are specifically in unity that we need to fix
[22:38] <seb128> well, eog is not specific to unity
[22:38] <seb128> but we don't want it to stop working under unity
[22:38] <seb128> who knows what apps out there do the same
[22:38] <robert_ancell> yes, eog should be patches
[22:39] <seb128> that debian codesearch has other stuff
[22:39] <seb128> gnome-color-manager
[22:39] <seb128> gthumb
[22:40] <seb128> gnome-documents? (do we want gnome apps to work under unity?)
[22:40] <seb128> screenlets
[22:40] <seb128> that's about it
[22:41] <robert_ancell> fixable
[22:41] <seb128> which is still an ok list, but it feels like we are creating issues for third parties, scripts, etc
[22:41] <robert_ancell> well, it's a real issue. We can't just pretend it doesn't exist
[22:41] <seb128> which is not the end of the world but annoying
[22:42] <seb128> which do we undermine the experience for our main desktop/users for a flavor?
[22:43] <robert_ancell> I don't think this is going to undermine our main users
[22:44] <seb128> well, it's going to make apps works better under GNOME remix than Unity
[22:44] <seb128> if we miss to patch some
[22:44] <seb128> or if those a third party apps
[22:45] <robert_ancell> they're pretty easy to find and fix
[22:45] <seb128> except is that's e.g chrome
[22:45] <seb128> if*
[22:45] <robert_ancell> it's just an ? $XDG_CURRENT_DESKTOP == Unity ? "unity-control-center" : "gnome-control-center"
[22:45] <seb128> right, if you have access to the source
[22:46] <seb128> well I guess google is going to fix chrome if needed (I didn't check if they use it, making a potential example)
[22:46] <robert_ancell> Yeah, they just have to fix it
[22:47] <seb128> but yeah, I guess that's a limited set and we just need to transition those
[22:58] <seb128> robert_ancell, u-c-c looks fine from a first build/run, I'm going to play with it more tomorrow
[22:58] <robert_ancell> cool, thanks
[22:58] <seb128> calling it a day for today though
[22:58] <seb128> see you tomorrow
[22:58] <robert_ancell> bye
[22:58] <seb128> bye