[00:28] <qengho> Zzzz
[05:05] <pitti> Good morning
[05:39] <hikiko> good morning!
[05:39] <hikiko> hi pitti :)
[05:41] <pitti> hey hikiko!
[05:41] <hikiko> how are you :)
[05:42] <pitti> quite well, thanks! how about yourself?
[05:42] <darkxst> hey pitti hikiko
[05:43] <hikiko> good :)
[05:43] <hikiko> hi darkxst
[05:43] <pitti> hey darkxst, how is it going?
[05:46] <darkxst> pitti, annoyed, every window has massive borders with new gtk+ update
[05:46] <darkxst> seems larsu caused it
[05:50] <darkxst> atleast he reverted a commit, that caused it
[05:55] <didrocks> good morning
[05:56] <pitti> bonjour didrocks !
[05:58] <didrocks> bonjour pitti, ça va ?
[05:59] <pitti> didrocks: ça va bien, merci ! et toi ?
[05:59] <hikiko> good morning didrocks :)
[06:00] <darkxst> hey didrocks
[06:01] <didrocks> hey hikiko, darkxst!
[06:01] <didrocks> pitti: ça va aussi, mais il fait froid !
[06:02] <pitti> en effet !
[06:02] <pitti> "Winter is coming."
[06:02] <didrocks> héhé :-)
[06:02] <darkxst> summer is here ;(
[06:03] <pitti> I don't think that's a thing in GoT
[06:03] <darkxst> right, it would change the story line just a little ;)
[06:04] <darkxst> the wall would melt for one!
[06:04] <pitti> well, not that much. Instead of freezing to death they'd just boil in their armors
[06:05] <pitti> and they could have built the wall out of coconuts
[06:10] <darkxst> pitti, they wouldnt need a wall, it would end up an ocean and all the baddies would drown!
[06:10] <pitti> right after all the goodies :)
[06:11] <darkxst> depends if they can get their boats in, in time
[06:24] <darkxst> Laney, I tested your g-o-a webkit1 revert with g-c-c seems to work fine
[06:32] <darkxst> Laney, though I do wonder, can't we drop the ancient webkit2gtk build from webkitgtk source and add webkit2gtk to main? thats gotta be better than the current situation, and the transition from webkit2gtk-3.0 to -4.0 should be easy
[07:24] <seb128> good morning desktopers!
[07:24] <pitti> bonjour seb128 !
[07:24] <didrocks> re seb128
[07:24] <seb128> hey pitti, didrocks
[07:24] <seb128> wie gehts?
[07:24] <pitti> prima, danke! und Dir?
[07:51] <seb128> gut, danke ;-)
[07:51] <seb128> (sorry didn't see the reply before)
[07:52] <darkxst> seb128, Laney, https://bugs.launchpad.net/ubuntu/+source/webkitgtk/+bug/1469221/comments/10
[07:53] <seb128> darkxst, that would mean have webkitgtk webkit2gtk in main?
[07:53] <darkxst> seb128, but right now you have webkitgtk and also ancient webkit2gtk in main
[07:54] <seb128> ancient webkit2gtk?
[07:54] <darkxst> they are more or less independant builds in the old source package
[07:54] <seb128> k
[07:54] <seb128> well it's a case to argue with the security team
[07:54] <seb128> I've little say in that
[07:54] <darkxst> you will end up with 2 copies of webkit2gtk source in main
[07:54] <seb128> right
[07:54] <darkxst> but only one that builds
[07:55] <seb128> is anything currently using the -3.0 version?
[07:55] <darkxst> seb128, yes, but pretty much everything GNOME upstream supports -4.0
[07:55] <darkxst> also
[07:56] <darkxst> and 3.0 -4.0 is nothing like the hell of going webkit1 to 2
[07:56] <seb128> the question was rather "if we disable the 3.0 build without promoting webkit2gtk can we get no copy in main"?
[07:57] <darkxst> seb128, no, I think yelp and devhelp are in main?
[07:57] <darkxst> g-o-a
[07:57] <seb128> k
[07:57] <seb128> well seems like a case to argue with the security team
[07:57] <seb128> maybe comment on the open MIR about that?
[07:58] <Trevinho> Morning...
[07:58]  * Trevinho has to leave for some blood tests
[07:58] <seb128> hey Trevinho
[07:58] <seb128> Trevinho, oh, nothing serious I hope! good luck
[07:59] <darkxst> seb128, like my other old bug, I couldnt find it!
[08:00] <darkxst> but I will find it and comment there as well
[08:00] <seb128> thanks
[08:00] <didrocks> good morning Trevinho!
[08:09] <larsu> bonjour!
[08:13] <didrocks> hey larsu
[08:14] <larsu> hi didrocks :)
[08:15] <darkxst> https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1466290/comments/20
[08:16] <darkxst> commented there also ;)
[08:16] <seb128> larsu, salut! wie gehts?
[08:16] <darkxst> larsu, can you guard your gtk+ background revert with XDG_CURRENT_DESKTOP==Unity, you broke just about every other DE with that
[08:16] <larsu> hey seb128! Great thanks! And you?
[08:16] <seb128> larsu, I'm good thanks!
[08:17] <seb128> darkxst, do you know why that same code in 3.16 was not creating those issues?
[08:17] <seb128> we might just need another revert
[08:18] <darkxst> seb128, my guess, is larsu didn't just do a clean revert
[08:18] <darkxst> there was a check againt client-decorated also before
[08:19] <darkxst> https://git.gnome.org/browse/gtk+/commit/?h=gtk-3-18&id=74f2d9448f24bbfdaf32ae6b328ed3e126700afe
[08:19] <seb128> we should maybe just add that back?
[08:19] <larsu> no, this wasn't a revert
[08:19] <larsu> putting that check back in will make the original bug come back for csd-windows
[08:20] <larsu> so we might as well remove the whole patch (which I suggest we do for now)
[08:20] <darkxst> larsu, well you have given us a much worse bug
[08:20] <larsu> darkxst: for xfce users?
[08:21] <darkxst> and I don't see how messing with background can fix frame sync issues, other than making them less ugly
[08:21] <larsu> that was the point
[08:21] <darkxst> larsu, gnome-shell, unity
[08:21] <seb128> no
[08:21] <seb128> unity is much better
[08:21] <seb128> the bg color change is really annoying and tiring for the eyes
[08:22] <larsu> darkxst: unity?
[08:22] <larsu> with adwaita, you mean?
[08:22] <darkxst> larsu, with adwaita there is a 5px margin
[08:22] <darkxst> with ubuntu themes there are still square corners on csd windows
[08:23] <seb128> right, but white ones
[08:23] <seb128> which is less noticable/ugly
[08:23] <larsu> darkxst: those square corners were there before, it's a window manager issue
[08:23] <larsu> darkxst: and don't use adwaita on unity, it's broken
[08:23] <seb128> the patch is quite an improvement under Unity
[08:23] <larsu> not saying we shouldn't revert that patch
[08:23] <darkxst> larsu, adwaita on gnome-shell has 50px margines
[08:24] <larsu> I know. You said something about unity just now
[08:24] <seb128> let's not nitpick
[08:24] <seb128> that patch has issues and they are on the list of things to look at
[08:25] <larsu> right. Don't know what the fuss is about
[08:26] <seb128> are xfce, etc implementing the framesync protocol?
[08:26] <seb128> just wondering if that's another case of GTK doing things that work only under GNOME...
[08:26] <seb128> though that probably doesn't matter much for the resolution
[08:27] <larsu> they are most certainly not
[08:28] <seb128> k, so "fix compiz" is not really a solution to this problem
[08:28] <seb128> it would just make it work for us but let it buggy for others :-/
[08:28] <larsu> indeed
[08:29] <larsu> it was my impression that this was only setting the background of the X window and gets overdrawn quickly by gtk anyway
[08:29] <larsu> not sure why this isn't happening
[08:31] <darkxst> larsu, I'm not sure it gets overdrawn, client side decorations are below the X windows
[08:32] <larsu> darkxst: hm? They're painted on X windows just like everything else...
[08:32] <darkxst> so the main content will get overdrawn, but what about the transparent areas, that make it easier to catch the edges of windows etc?
[08:33] <darkxst> although the backgrounds are bigger than even those
[08:35] <darkxst> but anyway can we just revert the patch for now
[08:36] <larsu> yes, we should
[08:39] <seb128> :-(
[08:40] <seb128> I'm unsure if we should
[08:40] <seb128> maybe having it under XDG_CURRENT_DESKTOP hack?
[08:44] <larsu> please no :)
[08:44] <darkxst> seb128,  that was my first suggestion, but really you havent fixed anything with that patch
[08:44] <seb128> darkxst, oh yeah we have
[08:44] <darkxst> yes, you made it less ugly?
[08:44] <seb128> I can use my computer again without having headaches
[08:45] <seb128> the constant color change is really tiring on the eyes
[08:45] <seb128> so yes, less ugly and less physically tiring
[08:45] <seb128> which is a big win
[08:46] <darkxst> sure but at a cost
[08:47] <seb128> right, but it doesn't mean the correct thing to do is to add the initial problem back
[08:47] <czajkowski> .c
[08:47] <darkxst> we never even had the flickering problem
[08:47] <seb128> it started with 3.18
[08:48] <seb128> which was not in the archive for long before we landed that patch
[08:48] <darkxst> seb128, we have been running it for months
[08:48] <seb128> "we"?
[08:48] <darkxst> on the ppa's
[08:48] <darkxst> gnome3
[08:48] <seb128> yeah, unsure how many !GNOME users use those
[08:49] <seb128> GNOME doesn't have the issue because it implements the full frame sync protocol thing
[08:49] <seb128> but any wm that doesn't have it
[08:49] <seb128> and that's most wms out of GNOME
[08:49] <darkxst> seb128, yes, not many
[08:49] <darkxst> and yes NVIDIA fixed that actually
[08:50] <seb128> I'm using intel hwd
[08:50] <seb128> can't say
[08:51] <darkxst> seb128, it wasnt a bug in their drivers
[08:52] <seb128> nvidia fixed what?
[08:52] <seb128> sorry I'm lost there
[08:52] <willcooke> didrocks, taaaa daaaa!
[08:52] <willcooke> morning all
[08:52] <seb128> hey willcooke!
[08:52] <didrocks> willcooke: better server? :p
[08:52] <darkxst> framesync issues in mutter, clutter etc
[08:52] <seb128> right
[08:53] <seb128> well, shame they didn't fix it for all the other desktops :p
[08:53] <darkxst> well the original patch came from compiz?
[08:53] <darkxst> but the followup patches, don't know
[08:56] <seb128> yeah, unsure, and there is little point arguing we should stop there
[08:56] <seb128> bottom line is that the current patch is buggy and we should fix it
[08:56] <seb128> and stock GTK has issues on !GNOME which is what we tried to address
[08:59] <larsu> morning willcooke. Welcome to freenode
[08:59] <willcooke> :)
[08:59]  * didrocks feels that the "no python2" in deja-dup is some kind of cheating/twisting the reality
[09:00] <larsu> didrocks: but it runs with 3?
[09:00] <didrocks> larsu: no
[09:01] <didrocks> larsu: it just try to not install duplicity
[09:01] <seb128> didrocks, yeah, it is
[09:01] <didrocks> which makes deja-dup useless
[09:01] <didrocks> seb128: how so?
[09:01] <seb128> didrocks, it's cheating
[09:01] <didrocks> yeah
[09:01] <seb128> it means users are still going to get python2
[09:01] <didrocks> so, it doesn't run in python3
[09:01] <seb128> oh, sorry
[09:01] <didrocks> seb128: well… what I'm exactly saying :p
[09:01] <seb128> yeah, I was reply to your "* didrocks feels that the "no python2" in deja-dup is some kind of cheating/twisting the reality"
[09:02] <didrocks> ah ok ;)
[09:02] <seb128> right
[09:02] <didrocks> was puzzled for a sec
[09:02] <seb128> sorry, I see how the sequence was confusing ;-)
[09:02] <didrocks> heh, no worry!
[09:02] <larsu> didrocks: lol
[09:02] <didrocks> I'll try to describe my feeling on the MP
[09:02] <didrocks> but yeah, not installing duplicity
[09:02] <didrocks> so, installing on demand
[09:02] <didrocks> and having a useless deja-dup installed by default (as it can't do anything)
[09:03] <didrocks> it sounds to me just to tick a box for ticking it
[09:03] <didrocks> I would prefer in that case to not install it on the image
[09:03] <didrocks> or having a real fix, or having deja-dup working with something else than duplicity (so that as a default, it makes sense)
[09:04] <seb128> what is deja-dup able of doing without duplicity?
[09:04] <Laney> hey
[09:04] <didrocks> seb128: AFAIK, nothing, but I may be wrong
[09:04] <seb128> hey Laney
[09:04] <didrocks> (so yeah, if I'm wrong on that, I withdraw my whole complaint ^)
[09:04] <didrocks> complain*
[09:04] <didrocks> hey Laney
[09:04] <seb128> didrocks, if it's nothing I think there is a case to argue that it should simply be dropped from the iso
[09:04] <didrocks> seb128: yep
[09:05] <seb128> if users need to install something they can as well install a working deja-dup from software-center
[09:05] <didrocks> well, let's see what mterry will tell on the MP, I'm writing something around those lines
[09:05] <larsu> g'day Laney
[09:05] <didrocks> seb128: better for them to install deja-dup directly
[09:05] <Laney> hey france
[09:05] <Laney> hey germany
[09:05]  * larsu misses berlin
[09:05] <Laney> wait
[09:05] <seb128> larsu, where are you atm?
[09:05] <Laney> what???
[09:06] <larsu> seb128: at home
[09:06] <larsu> Laney: you ok?
[09:06] <didrocks> seb128: he claimed independence from Berlin :p
[09:06] <seb128> didrocks, you can argue that having it pre-installed with the on-demand somewhat advertize there is a recommended backup solution
[09:06] <larsu> didrocks is the only one that got it
[09:06] <Laney> larsu: sniffling but okay
[09:07] <seb128> haha
[09:07] <didrocks> seb128: agreed, but still feeling it's just about "ticking a box, no more python2, wooooowww", which is a lie in practice (as most of people will get it if we do that in multiple softwares)
[09:07] <seb128> didrocks, right
[09:07] <seb128> willcooke, do you have xenial somewhere? if so you would maybe like to have a look to https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1515557 ?
[09:07] <seb128> there is a suggestion there
[09:07] <didrocks> yep
[09:07] <seb128> .sidebar-icon {
[09:07] <seb128>     padding-left: 10px;
[09:07] <seb128>     padding-right: 10px;
[09:08] <seb128> that looks like it's the correct thing to do
[09:08] <willcooke> didrocks - can I still edit the pad for Google? ^^
[09:09] <willcooke> seb128, happy to take a look, won't take long, but didrocks has prepared a list of quick and easy things for the Google code thing, this would be a good one to add to that
[09:09] <willcooke> I think
[09:10] <seb128> well, the suggestion is already in the bug so somebody already contributed
[09:10] <didrocks> willcooke: I've moved that to a google doc
[09:10]  * larsu will be back in 15
[09:10] <seb128> but as you want
[09:10] <didrocks> willcooke: and I gave it to community team
[09:10] <willcooke> oki I can fix then
[09:10] <seb128> let's try to not steal credit for the current contributor though
[09:10] <didrocks> (as I put the deadline to it)
[09:10] <didrocks> willcooke: I guess we have enough tasks TBH
[09:11] <Laney> what are you talking about?
[09:11] <seb128> Laney, nautilus pading in the sidebar
[09:11] <Laney> what's that got to do with google code?
[09:11] <seb128> Laney, otherwise didrocks & willcooke about the google code-in project
[09:11] <didrocks> Laney: google code in
[09:11] <seb128> they built a list of easy things to work on
[09:12] <Laney> oh right
[09:12] <Laney> "port shotwell to webkit2"? :)
[09:12] <seb128> lol
[09:12] <willcooke> :D
[09:12] <seb128> yeah, welcome to opensource!
[09:12] <Laney> I actually think that's the only thing that is left to get wk1 off the iso
[09:12]  * didrocks put Laney as a mentor for that one
[09:12] <Laney> looked last night
[09:12] <didrocks> puts*
[09:12] <Laney> assuming I worked on ubiquity... think I did...
[09:12] <seb128> software-center as well, but I guess we assume that one is going away?
[09:12] <Laney> yeah
[09:12] <Laney> well
[09:13] <Laney> https://code.launchpad.net/~laney/software-center/webkit2/+merge/264723 too
[09:13] <Laney> darkxst: if you're happy enough I'll upload this revert, you can argue with security if you want
[09:16] <darkxst> Laney, g-o-a? I am happy enough with that, hopefully it doesnt backfire though
[09:16] <Laney> indeed
[09:16] <Laney> this situation is annoying
[09:17] <Laney> I would have both webkits in main and be done with it :|
[09:17] <didrocks> https://jenkins.qa.ubuntu.com/job/udtc-trusty-tests/2349/testReport/ -> ship it! (all passing, even if public jenkins still has issue mirroring!)
[09:17] <darkxst> it was fine in my testing, and I couldn't find api breakage that would cause hell to fall in
[09:18] <Laney> cool
[09:18] <darkxst> admittedly only tested g-c-c, but not sure if anything else would stress webkit stuff more than that
[09:19]  * seb128 opens datetime calendar and notice didrocks is patch piloting today then decide to let him that evolution patch backport for SRU ;-)
[09:19]  * Laney loves the patch pilot police
[09:19] <didrocks> seb128: you add the patch pilot calendar to track people pilot shift? :p
[09:19] <didrocks> Laney: yeah, it's nice isn't it? :p
[09:19] <seb128> didrocks, I didn't add anything, I added my canonical account
[09:19] <seb128> and datetime pick all the calendar
[09:19] <seb128> I wish I could turn that one off in fact :-/
[09:19] <didrocks> well, you added it to your canonical account :p
[09:19] <seb128> right
[09:20] <seb128> it's sometime handy
[09:20]  * Laney has it in url bar
[09:20] <Laney> maybe in main calendar would be useful too ;-)
[09:20] <Laney> great idea!
[09:20] <seb128> :-)
[09:20] <didrocks> anyway, I already planned to shift it to a nice Friday pilot, want to finish some demoing (after this ubuntu make release announcement)
[09:20] <didrocks> but yeah, will do the SRU as other items in the list :p
[09:21] <didrocks> (would be cool if we could move the shift ourselves in the calendar)
[09:21] <seb128> ok, no worry
[09:22] <seb128> I can try to nag kenvandine instead, he's doing his shift today as well ;-)
[09:22] <Laney> didrocks: you can
[09:22] <Laney> I do it all the time
[09:22] <Laney> most months in fact
[09:22] <didrocks> Laney: oh really?
[09:22] <seb128> happyaron, hey, can you look at https://code.launchpad.net/~brunonova/ubuntu/trusty/ibus/lp1240198_2/+merge/278226 ?
[09:22]  * didrocks tries
[09:23] <Laney> probably have to be logged in
[09:23] <seb128> btw is anybody else having all day events showing on the wrong day?
[09:23] <seb128> in indicator-datetime
[09:23] <seb128> like if I open today it lists "doko tomorrow 00:00"
[09:23] <didrocks> Laney: I have mine shifted
[09:23] <seb128> rather tha ken/didrocks today
[09:23] <didrocks> let's try to add the patch pilot calendar
[09:24] <Laney> seb128: indeed
[09:24] <didrocks> seb128: ah, so it's not indicator-datetime showing up us as piloting today :p
[09:24] <Laney> but only for gcals it seems
[09:24] <seb128> didrocks, well I opened it to see who was pilot to nag them about that evolution patch :p
[09:24] <Laney> I have some birthday calendar from Facebook maybe
[09:24] <Laney> and those are correct
[09:24] <seb128> sorry it felt on you today ;-)
[09:25] <didrocks> ah, moving worked, nice!
[09:25] <seb128> Laney, facebook has a calendar/eds integration?
[09:25] <didrocks> seeing there is mostly unactive patch piloter before Friday, I guess it's a good spot
[09:25] <seb128> didrocks, I often do that when reviewing the recent bugs activity, ping the $pilot_of_the_day
[09:25] <didrocks> (as dholbach did a lot of work yesterday)
[09:25] <seb128> yeah
[09:26] <Laney> I probably added the ical
[09:26] <seb128> there are a few desktop items in there he didn't touch though
[09:28] <darkxst> i'm going to break the calendar and do my next pilot shift on the weekend ;)
[09:28] <seb128> heh
[09:28] <Laney> we'll just leave all the hard stuff
[09:30] <Laney> didrocks: ah yes, it comes up as an invitation in my main calendar
[09:30] <Laney> and from there I can edit it
[09:34] <didrocks> Laney: btw, did you try latest master from dep11 repo? Not sure if you noticed that my patch was merged
[09:36] <Laney> didrocks: not yet, you want to pull & build/install?
[09:36] <Laney> I made it run out of the virtualenv
[09:36] <Laney> could probably automate updating it
[09:37] <didrocks> Laney: ok, let me connect
[09:39] <didrocks> Laney: 5a3a5622c87d0825cd64d50072ed3754700d99ce isn't in master?
[09:40]  * didrocks was wondering why git pull wanted to merge
[09:41] <Laney> no, do pull --rebase (sorry, forgot)
[09:42] <Laney> I didn't propose that yet because not sure it actually fixes anything
[09:42] <didrocks> Laney: doing that!, got it on the reasoning :)
[09:42]  * Laney tries to remember what the config is to pull --rebase by default
[09:42] <didrocks> we'll see if this fixes it for humanity, indeed
[09:43] <willcooke> urgh.  seb128 - I've messed up that commit, it's got some half fixes from other theme work.
[09:43] <didrocks> Laney: oh right, we should do that, one sec
[09:43] <seb128> willcooke, uncommit and try again?
[09:43] <Laney> branch.name.rebase
[09:44] <Laney> willcooke: bzr shelve if you need to get some changes out of the way
[09:44] <Laney> then bzr unshelve to get them back later
[09:44] <didrocks> you need bzr-rewrite package (plugin) for that IIRC
[09:45] <Laney> what is that?
[09:45] <Laney> don't think so
[09:45] <didrocks> ah, it's probably only for bzr rebase then
[09:45] <didrocks> can be wrong
[09:46] <Laney> it's not doing any rewriting
[09:46] <didrocks> yeah, I still thought it was in the same plugin package though and not by default
[09:47] <didrocks> Laney: ok, built and installed
[09:47] <Laney> |O|
[09:47] <didrocks> letting you or the cronjob (if any) doing the run?
[09:47] <Laney> watch http://162.213.34.169/logs/2015/11/ at 1000
[09:48] <didrocks> oki ;)
[09:54] <Trevinho> seb128: nothing serious... Just routine checkup
[09:54] <Trevinho> it took longer than expected.. :/
[09:59] <Laney> hey Trevinho
[10:00] <Trevinho> hi Laney
[10:00] <larsu> morning Trevinho!
[10:00] <Trevinho> larsu: hi
[10:01] <Laney> what's up?
[10:01] <Laney> do you feel much lighter now that you have less blood?
[10:02] <darkxst> vampires?
[10:05] <seb128> Trevinho, k, glad you are doing well!
[10:08] <Laney> didrocks: doh ;-)
[10:10] <didrocks> Laney: yep, probably failed at something :p
[10:10] <didrocks> Laney: looking, don't worry about it
[10:10] <Laney> should probably make the rsync for logs happen even if something fails
[10:10] <Laney> not so useful to only get those if it works :P
[10:10] <didrocks> Laney: heh, indeed :p
[10:11] <didrocks> ah, you redirect stdout/stderr, that's why I wasn't seeing everything
[10:11]  * didrocks looks at logs
[10:11] <Laney> tail the log file
[10:11] <Laney> dep11/logs/...
[10:11] <didrocks> yep, I'm in it
[10:11] <didrocks> and waiting for it to stop
[10:12] <didrocks> oh :p
[10:12] <didrocks> missing import
[10:13] <Laney> I just made it log straight to the public directory
[10:13]  * Laney rm -r dep11/logs
[10:14] <didrocks> Laney: makes sense, removing my -x
[10:15] <didrocks> Laney: this run should be better
[10:17] <Trevinho> Laney: ah, sorry I missed your msg :P... Well I did some checkup... Nothing special (I hope :P). They didn't took too much blood to feel lighter... Maybe it would have been better :)
[10:17] <Laney> heh
[10:18] <Laney> didrocks: nice
[10:18] <Laney> doing a PR?
[10:18] <didrocks> Laney: you mean liek https://github.com/ximion/appstream-dep11/pull/3? :)
[10:18] <didrocks> like*
[10:20] <didrocks> would be nice to add to dep11 a minimal set of tests btw
[10:20] <Laney> sure would!
[10:20] <didrocks> Laney: hum http://162.213.34.169/logs/2015/11/
[10:20] <didrocks> Laney: you just move the LOGDIR, right?
[10:20] <didrocks> and didn't remove a rm I guess? :p
[10:21] <Laney> oh noes
[10:21] <Laney> what happened!!!!!
[10:21] <Laney> bet the rsync deleted it
[10:21] <didrocks> --delete-after
[10:21] <didrocks> yep
[10:22] <Laney> at least the evidence of the import sys is gone :)
[10:22] <didrocks> heh, phew :p
[10:29] <willcooke> larsu, is there an equivalent gtk2 version of the gtk3 widget factory?
[10:31] <larsu> willcooke: yes, gtk-widget-factory
[10:31] <larsu> I don't know if we install that, though
[10:32] <larsu> ah, no package :/
[10:32] <Laney> didrocks: logs should be safe now :p
[10:32] <willcooke> ah
[10:32] <willcooke> I'll use Firefox instead ;)
[10:32] <larsu> ;)
[10:33] <didrocks> Laney: phew! no more hiding :-)
[10:34] <didrocks> Laney: more seriously, don't you have too many issues reboostrapping the nodes when canonistack goes down?
[10:34] <Laney> haven't lost the instance yet
[10:34] <didrocks> (loosing the logs are not great, ok, but the rest)
[10:34] <Laney> it just gets shut down
[10:34] <didrocks> ah, and you have a shared volume?
[10:34] <didrocks> (persistent disk that you can remount)
[10:34] <Laney> for the mirror yeah
[10:34] <didrocks> yeah
[10:34] <didrocks> so ok, not that bad for now
[10:34] <Laney> going to write a charm at some point anyway
[10:35] <didrocks> you will have to :p
[10:35] <Laney> it would be mildly annoying
[10:35] <didrocks> to need multiple machines just to create one?
[10:35] <Laney> nginx config + checkout + virtualenv
[10:35] <didrocks> or something else?
[10:35] <Laney> to rebuild if it goes away
[10:40] <Laney> oh I would have to remember what all the deps are too :P
[10:41]  * Laney git push git+ssh://git.launchpad.net/~ubuntu-desktop/+git/appstream-cloud
[10:41] <Laney> charm will end up there
[10:42] <didrocks> Laney: if you need any help in charming it up, I have some scares still (and so knowledge) of previous attempt… :p
[10:42]  * Laney knows nothing
[10:43] <didrocks> but well, you need to describe the used config on the machine first ;)
[10:43] <Laney> was planning to copy pitti's charm
[10:43] <Laney> his is more complex though, don't need any relations here
[10:43] <pitti> my charm is unique! I don't borrow it to other people
[10:44] <didrocks> :)
[10:44] <pitti> Laney: which charm do you want to copy? want some help?
[10:44] <didrocks> Laney: maybe the ci-train one is easier?
[10:44] <Laney> pitti: not doing it right now, but thanks!
[10:44] <Laney> didrocks: maaaaybe
[10:44] <didrocks> it doesn't have relationships either, pretty single :)
[10:45] <Laney> I guess you can somehow make it depend on a cinder volume
[10:46] <Laney> so that it can re-use the mirror if it exists
[11:02] <larsu> seb128: so the best compromise I can come up with is to set the background to transparent
[11:02] <larsu> which looks odd in unity, but not as bad as the black one
[11:02] <larsu> and works in shell
[11:02] <seb128> larsu, +1 from me
[11:02] <larsu> I tried other things as well, but those require theme changes
[11:02] <larsu> and I think we want to stay minimal here
[11:02] <seb128> that would be better indeed
[11:03] <larsu> Trevinho: while working on this, I noticed that setting a background of #00000000 had no effect, while doing something like #01000000 works
[11:07] <larsu> willcooke: nice work on the theming stuff
[11:07] <seb128> I'm going to do a landing today I think
[11:07] <seb128> with the theme tweaks from willcooke
[11:08] <willcooke> The changes I made to notebook tab colours need to be ignored.  I will delete them
[11:08] <willcooke> they dont work properly yet
[11:08] <willcooke> didrocks has helped me to better organise my branches now so each fix will have its own branch
[11:09]  * larsu hugs didrocks 
[11:10] <darkxst> willcooke, everyone should just move to git branches ;)
[11:11] <willcooke> didrocks, can I delete this one now?  https://code.launchpad.net/~willcooke/ubuntu-themes/ubuntu-themes
[11:11] <willcooke> I dont want any of those changes to exist anywhere and confuse me
[11:12] <didrocks> willcooke: sure, you can :)
[11:12]  * didrocks hugs larsu back
[11:21] <willcooke> larsu, are you looking at the treeview selector heights already?
[11:22] <larsu> seb128, darkxst: please give this a spin if you have some time https://code.launchpad.net/~larsu/gtk/black-flicker-part2/+merge/278432
[11:22] <larsu> willcooke: no
[11:22] <larsu> shall I?
[11:22] <seb128> larsu, sure
[11:22] <willcooke> larsu, lemme see if I can find how to fix it and I'll let you know
[11:25] <darkxst> larsu, I'm off to bed now, but setting background transparent does sound harmless,
[11:27] <larsu> darkxst: setting the background to the background sounds harmless as well :P
[11:27] <larsu> (which is what the other patch did)
[11:28] <darkxst> larsu, yes, will test tomorrow
[11:28] <larsu> thanks
[11:29] <seb128> willcooke, what bug is that one?
[11:30] <willcooke> seb128, well, it's getting stranger now... when you open gedit, and click open you get the tree view up instead of a file browser at the start
[11:30] <willcooke> if you type "t" in that search box you get lots of results
[11:30] <willcooke> but each entry is about 5px high and you cant read them
[11:30] <seb128> willcooke, good that I asked, I just fixed that one, https://bugzilla.gnome.org/show_bug.cgi?id=758585
[11:30] <seb128> https://bugzilla.gnome.org/attachment.cgi?id=316154&action=diff
[11:31] <seb128> I've a package update building as we speak
[11:31] <willcooke> haa!
[11:31] <willcooke> That's how I fixed it as well
[11:31] <willcooke> :)
[11:31] <seb128> sorry ;-)
[11:31] <willcooke> but I found that when I took the padding out from the css, it stayed fixed for the whole session
[11:31] <seb128> I wonder if we should import some of the other rules in our theme
[11:31] <willcooke> seb128, no worries :)  it only took me about 5 mins to work out what was going on
[11:32] <willcooke> yeah, I think that makes sense
[11:32] <seb128> they don't want to move the rules using e.g @theme_bg_color to the common css because it's not sure the theme define those colors
[11:33] <willcooke> seb128, whats your view on the "save changes before closing" dialog buttons?  They look all smushed together, but perhaps they are supposed to be?
[11:33] <Laney> https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1513856
[11:33] <seb128> laney beat me to that one
[11:33] <seb128> but yeah, I think it looks buggy
[11:33] <seb128> unsure what we should do though
[11:33] <seb128> just theming tweaks?
[11:34] <seb128> or move back to non joined buttons?
[11:34] <willcooke> I tried themeing with padding and margins, but it doesn't work
[11:34] <willcooke> oh
[11:34] <willcooke> that reminds me
[11:35] <Laney> yes but they look normal in Adwaita, so maybe we could take some inspiration from them
[11:35] <willcooke> seb128 - how are you fixed for a trip to London on 10th Dec?  Just head back from John and he is free then
[11:35] <willcooke> we could ask John Lea questions like this (^) in person
[11:36] <seb128> willcooke, wfm
[11:38] <seb128> Laney, "normal", they look different from other dialogs like the fileselector but yeah it's less buggy
[11:38] <seb128> it's just a question of whether we want things to be similar or not
[11:39] <Laney> "Linking buttons together can make it move obvious that their function is related"
[11:40]  * larsu goes to lunch
[11:42] <seb128> lunch, bbiab
[11:42] <seb128> larsu, enjoy!
[11:42] <seb128> Laney, where is that quoted from?
[11:42] <Laney> gnome wiki
[11:42] <didrocks> enjoy seb128, larsu
[11:42] <seb128> thanks
[11:43] <seb128> Laney, I think they use that style in gtk fileselector etc but we patched it out
[11:43] <seb128> we should revisit what we do
[11:43] <Laney> we did for message dialogs
[11:43] <Laney> not sure where else
[12:03] <pitti> Laney: argh, lcy01 died again!?
[12:06] <Laney> pitti: seems so :(
[12:06] <Laney> https://portal.admin.canonical.com/85642
[12:06] <Laney> enabled builders 2 hours ago
[12:06] <Laney> but they are disabled
[12:07] <pitti> ah, so they are working on it
[12:07] <pitti> I am doing a manual run, and indeed it's stuck at BUILD/spawning
[12:08] <Laney> well https://launchpad.net/builders/lcy01-06/+history doesn't show that it was enabled 2h ago
[12:08] <Laney> so *shrug*
[12:10] <pitti> Laney: in better news, I now figured out queue inspection in principle
[12:10] <Laney> cool
[12:10] <pitti> currently turning it into nice HTML
[12:10] <Laney> I saw that you added the management plugin
[12:10] <Laney> this works?
[12:10] <pitti> Laney: only for the queue length, what's already exposed on http://autopkgtest.ubuntu.com/running.shtml
[12:11] <pitti> Laney: not the contents -- if you actually use the web UI and inspect the queue, it requeues stuff in a different order
[12:11] <pitti> so I need to use the normal amqp operations
[12:11] <Laney> oh right, I thought that this didn't require that plugin
[12:11] <pitti> so in the end I can probably even drop the management plugin again
[12:12] <pitti> I found that when reading all requests without acking, and then basic_reject()ing them, the queue order isn't changed
[12:12] <pitti> so the mgmt plugin does the inspection in a funny
[12:12] <pitti> ... way
[12:12] <Laney> "if you declare a queue with NO auto acknowledgements and do not ACK the messages that you receive, then you can see everything in it"
[12:13] <pitti> right (where do you read that?) -- the trick is to explicitly reject them
[12:13] <Laney> SO
[12:13] <Laney> https://stackoverflow.com/questions/4700292/using-rabbitmq-is-there-a-way-to-look-at-the-queue-contents-without-a-dequeue
[12:13] <pitti> ah, there
[12:13] <pitti> ah, haven't tried cancel, but I don't want to actually do that for the status queue I'm listening to
[12:14] <pitti> anyway, in my local container debci/rabbit setup I now see stuff
[12:14]  * pitti leaves HTML beautification for after lunch
[12:19] <happyaron> seb128: sure
[13:52] <Trevinho> seb128: I don't remember one thing... What was the rationale for "inode/directory=nautilus-folder-handler.desktop" ? I mean why do we need a different desktop file for opening dirs?
[14:00] <Trevinho> Ah, I guess that's for "--new-window" thing...
[14:00] <seb128> Trevinho, I don't remember the specifics, without that sometime other filemanager would open when clicking on a folder
[14:00] <seb128> but it might have been in the gnome-panel times
[14:00] <seb128> like if you had a directory on your panel
[14:01] <Trevinho> seb128: the thing is that if you now do nautilus -q; and then open it from new device/trash we get that matched to nautilus-folder-handler...
[14:01] <seb128> Trevinho, is that association creating any issue?
[14:01] <Trevinho> Because of gio telling that to us
[14:01] <Trevinho> seb128: however... that desktop file has the "NoDisplay=true" so... maybe I  can filter that out...
[14:01] <seb128> is there another desktop that would be more suitable?
[14:02] <seb128> the idea was to assign nautilus
[14:02] <seb128> rather than getting the xfce file manager
[14:02] <seb128> but I don't think we picked that particular desktop for a good reason, we could probably change to whatever is right
[14:02] <seb128> or try to drop the association and see what happens
[14:02] <Trevinho> seb128: I was thinking to standard desktop file, but... that's something that might not work as per the "--new-window" option
[14:06] <Trevinho> seb128: basically the bad matching happens because org.gtk.gio.DesktopAppInfo tells us that that desktop has been launched, for that pid... So bamf overrides the matching by using it
[14:06] <Trevinho> seb128: however, I think that maybe bamf should ignore the nodisplay desktop files for such thing
[14:07] <Trevinho> we can then use then, if really we don't find anything else that matches
[14:08] <seb128> your call, you know better that matching logic than me
[14:08] <seb128> some people pointed we currently have issues with e.g gedit as well
[14:08] <seb128> since we have compat desktops now
[14:08] <seb128> like upstream renamed gedit.desktop to org.gnome.gedit.desktop
[14:09] <Trevinho> yeah... that makes matching harder, but iirc larsu added a way to get the gtk app id atom and using that, isn't it?
[15:15] <Laney> trouble in the clouds
[15:15] <Laney> launchpadlibrarian.net is broooooooookenn
[15:16] <didrocks> storms? :)
[15:16] <Laney> acid rain
[15:16]  * Laney remembers about LTE
[15:17] <Laney> https://www.youtube.com/watch?v=pmo1VW_wA_o
[15:28] <mterry> didrocks, I replied to your comments on the deja-dup branch. thanks for looking at it!  I would be interested to see if trunk's tests also fail for you (they did for kenvandine)
[15:29] <kenvandine> mterry, didrocks: ah ha!  those are the same tests that failed for me!
[15:30] <willcooke>  #startmeeting Desktop Team Weekly Meeting - 2015-11-24
[15:30] <willcooke> #startmeeting Desktop Team Weekly Meeting - 2015-11-24
[15:30] <meetingology> Meeting started Tue Nov 24 15:30:42 2015 UTC.  The chair is willcooke. Information about MeetBot at http://wiki.ubuntu.com/meetingology.
[15:30] <meetingology> Available commands: action commands idea info link nick
[15:30] <seb128> hey
[15:30] <didrocks> mterry: let me have a look after the meeting (I only tried the tests in a sbuild), what kenvandine did I guess
[15:30] <mterry> So kenvandine isn't actually crazy  ;)
[15:30] <didrocks> hey
[15:30] <willcooke> Roll call: andyrock, attente, desrt,  dgadomski, didrocks, fjkong, happyaron (out), hikiko (out), laney, larsu, qengho, seb128, sweet5hark, themuso (out), tkamppeter, trevinho, robert_ancell (out)
[15:30] <andyrock> \o/
[15:31] <kenvandine> well... maybe i am
[15:31] <didrocks> mterry: that doesn't imply he isn't :p
[15:31]  * mterry shuts up
[15:31] <kenvandine> but the tests really fail :)
[15:31] <Trevinho> hey
[15:31] <desrt>  /o\
[15:31] <dgadomski> hey
[15:31] <desrt> (body scanner pose)
[15:31] <willcooke> :D
[15:32] <hikiko> willcooke, I was about to leave sorry! I emailed you a minute ago I hope you see it!!
[15:32] <willcooke> hikiko, got it - nw
[15:32] <hikiko> bye people!!
[15:32] <willcooke> hikiko,  I can copy & paste
[15:32] <willcooke> cya hikiko
[15:32] <larsu> hey
[15:33] <willcooke> lets get started..
[15:33] <willcooke> #topic andyrock
[15:33] <andyrock> hey all
[15:33] <andyrock> I'm working on the redrawing/damaging issue with unity+nux+compiz
[15:33] <andyrock> i discovered that it's not just about the cursor
[15:34] <andyrock> but that're other cases where we basically redraw randomly
[15:34] <andyrock> like if you open once the shortcut overlay we redraw the shortcut overlay even if it's hidden
[15:34] <andyrock> that's a shame
[15:35] <andyrock> I've already a fix for that (I'll propose it later today)
[15:35] <andyrock> right now I'm working on the cursor redraw issue and more in general trying to understand what's going on when the dash and the hud are open
[15:36] <andyrock> we redraw for no reason and that's can cause slowness
[15:36] <andyrock> and also reviews
[15:36] <andyrock> \eof
[15:36] <willcooke> thanks andyrock
[15:36] <willcooke> andyrock, how are you set for a quick review tomorrow at 10am UTC?
[15:37] <andyrock> I've class but should not be a problem
[15:37] <seb128> andyrock, nice to see work on those redraw issue!
[15:37] <willcooke> andyrock thanks
[15:37] <willcooke> #topic attente
[15:37] <andyrock> seb128 I can't promise to fix them all but I'll try :D
[15:38] <attente> hi guys
[15:38] <attente> debugged/fixed some broken maliit-framework tests
[15:38] <attente> suppress some unused parameter warnings in gdbus-codegen output, filed upstream
[15:38] <attente> packaged maliit-framework and maliit-inputcontext-gtk (<- needs sponsoring), fixed up packaging branch which was out-of-date
[15:38] <attente> want to move QT_IM_MODULE out of livecd-rootfs and into somewhere else, but not really sure where it should go to have it set under u8
[15:38] <attente> updated java non-latin shortcuts ppa for bug #1226962, might try to merge it despite it not being perfect
[15:38] <attente> starting working on gtk single-surface
[15:38] <attente> (eof)
[15:38] <willcooke> thanks attente
[15:39] <willcooke> good comments on that bug, looks great
[15:39] <willcooke> thanks
[15:40] <willcooke> #topic desrt
[15:40] <desrt> hi
[15:40] <desrt> continue work on inotify stuff, looks pretty good now
[15:40] <desrt> helping xclaesse with the dconf confinement stuff
[15:40] <desrt> bugs/reviews
[15:40] <desrt> and starting on a glib release for today
[15:40] <desrt> eof
[15:40] <willcooke> good stuff, thanks desrt
[15:40] <seb128> \o/
[15:40] <xclaesse> :)
[15:40] <seb128> it means we are going to stop receiving reports about that nautilus/trash segfault
[15:41] <desrt> hi xclaesse :)
[15:41]  * seb128 just commented on yet another report
[15:41] <desrt> there's a nautilus/trash segfault again? :(
[15:41] <desrt> can you link me?
[15:41] <seb128> the one I sent a patch for
[15:41] <desrt> probably we want to fix this in stable and not have to wait for unstable
[15:41] <seb128> you didn't do a release since
[15:41] <desrt> oh
[15:41] <desrt> about the release
[15:41] <desrt> gotcha :)
[15:41] <seb128> yeah
[15:41] <seb128> :-)
[15:42] <willcooke> #topic dgadomski
[15:42] <dgadomski> hey, unfortunately I haven't done much in the desktop area this week
[15:42] <dgadomski> * fix for bug #1510824 accepted upstream, released to Xenial, debdiffs for SRUs are prepared and attached
[15:42] <dgadomski> and that would be all, thanks
[15:42] <seb128> dgadomski, I saw your polkit patch got merged, good work ;-)
[15:42] <willcooke> thanks dgadomski!
[15:42] <dgadomski> thanks seb128 :)
[15:43] <willcooke> #topic didrocks
[15:43] <didrocks> Ubuntu Make:
[15:43] <didrocks> - Reviewed and merged CLion work by a new contributor \o/
[15:43] <didrocks> - Added medium and large tests to it
[15:43] <didrocks> - Cut the large tests time by half while adding even more tests \o/ (jenkins + tests enhancements)
[15:43] <didrocks> - Move build dependencies only needed for tests to another ppa (ppa:ubuntu-desktop/ubuntu-make-builddeps) and add it in jenkins tests. This way, people using Ubuntu Make on older release are not impacted by the need of newer version of tests frameworks like pexpect and won't install them. Hook that ppa in Travis CI, our jenkins infra and refresh contributor intro to ask adding that ppa for testing.
[15:43] <didrocks> - Add ZSH completion
[15:43] <didrocks> - Fight some jenkins specific + proxy issues while learning more about some os.environ black magic (thanks pitti, even some python god I knew weren't aware about that :p)
[15:43] <didrocks> - Fix Visual Studio Code which changed its icon path (detected through our testsuite)
[15:43] <didrocks> - Misc fixes and enhancements for i18n, test standardization and jenkins branch build support (mostly described in https://github.com/ubuntu/ubuntu-make/commit/1469477890a10eba2b17d74d461c22567c24838c and incoming blog post)
[15:43] <didrocks> Misc:
[15:43] <didrocks> - Help Laney on and appstream-dep11 fixing some issues when running in virtualenv
[15:43] <didrocks> - MIR ptyprocess to unblock pexpect 4.0 (which was build-dep wait)
[15:43] <didrocks> - Small britney wording consistency work )<-- this extra parenthesis is dedicated to Laney <3
[15:43] <didrocks> - Worked and gather topics and bug reports for Google Code-in students.
[15:43] <didrocks> .
[15:43] <willcooke> another new contributor :D
[15:44] <willcooke> thanks for you work on the Code In project too
[15:44] <didrocks> yep \o/
[15:44] <didrocks> yw
[15:44] <willcooke> #topic FJKong
[15:44] <FJKong> hi
[15:44] <FJKong> not much to update:
[15:44] <FJKong> 2 days sick leave;
[15:44] <FJKong> sogou IM bug fixing:
[15:44] <FJKong> * hot key problem report by users, fixed
[15:44] <FJKong> * inputing window abnormal when typing : working in progress
[15:44] <FJKong> eof
[15:45] <willcooke> thanks FJKong
[15:45] <willcooke> #topic happyaron
[15:45] <willcooke> 1. Finished my zfs-linux packages, uploaded to Debian.
[15:45] <willcooke> 2. Explore about basics of snappy Ubuntu
[15:45] <willcooke> #topic hikiko
[15:45] <willcooke> I am working on the shadows (and basically I messed up a few things And I am now trying to fix the mess... :D) EOF
[15:45] <willcooke> #topic laney
[15:45] <Laney> • Short week + slightly sick week
[15:45] <Laney> • liburcu transition, some random source fixes for this (forwarded + corresponded with maintainers)
[15:45] <Laney> • finish up britney branch after feedback, got that merged
[15:45] <Laney> • some of my Debian merges (lintian, bzr, dbus, vorbis-tools)
[15:45] <Laney> • some other updates (gnome-online-accounts + patch to revert wk2 -> wk1, gvfs)
[15:45] <Laney> • appstream: work with didrocks on getting this to work from a git checkout in virtualenv, running from there now - next: work on charm
[15:45] <Laney> • just found a packet of biscuits (crunch creams)
[15:46] <Laney> • dmb meeting and some chivvying to look at things there
[15:46] <Laney> • fix an oops where we accidentally removed overlay-scrollbar schemas from the default install
[15:46] <Laney> ⁂
[15:46] <larsu> biscuits \o/
[15:46] <willcooke> thanks Laney
[15:46]  * willcooke is reminded there is an email to ev in drafts that he needs to finish 
[15:46] <willcooke> #topic larsu
[15:46] <larsu> random bugs again this week
[15:47] <larsu> - a recent i-sound fix on the phone broke notify osd on the desktoip
[15:47] <larsu> - logging in has a race with xsettings (didn't fix this but spent some time on it)
[15:48] <larsu> - last patch to remove the black flickering broke shadows on gnome shell
[15:48] <larsu> - nautilus menubar (coming seb128, sorry)
[15:48] <seb128> \o/
[15:48] <larsu> (this is annoying as I can't simply backport stuff)
[15:48] <larsu> err... I think there's more
[15:48] <larsu> ah right, the gnome-logs guy asked me to help out with automatically updating the ui when new log messages come in
[15:49] <seb128> what's the xsetting thing about?
[15:49] <larsu> and some internal gdbus issues
[15:49] <larsu> seb128: don't get correct font size when logging in, sometimes
[15:49] <larsu> really annoying
[15:49] <seb128> hum, k
[15:49] <seb128> I never noticed
[15:49] <larsu> I've had it a couple of times now, but not every time
[15:49] <larsu> couldn't find anything that could be causing this though :(
[15:50] <seb128> :-(
[15:50] <seb128> and speaking about gnome-logs ... we said we wanted to install it by default right?
[15:50] <larsu> yes
[15:50] <larsu> I have that on my todo for a but later but helped out since I was pinged anyway
[15:50] <seb128> great
[15:50] <larsu> I think it's </larsu>
[15:51] <seb128> we should stop bothering you with bugs and have a look to gnome-logs and geonames
[15:51] <larsu> :)
[15:51] <seb128> before eoy, so we get new components in
[15:51] <willcooke> thanks larsu
[15:51] <seb128> then we can go back to bugs
[15:51] <larsu> seb128: makes sense. lts and all
[15:51] <seb128> right
[15:51] <willcooke> yeah, good plan
[15:51] <Laney> well I tried assigning them instead of pinging ;-)
[15:51] <seb128> willcooke, sorry for interrupting with questions and comment
[15:51] <willcooke> :) no worries, good time to comment I think
[15:52] <seb128> Laney, yeah, that's probably smarter ;-)
[15:52] <willcooke> #topic qengho
[15:52] <qengho> * found bug that makes new chromium complain. proposed xdg-utils update that fixes it. gave chromium to #security to upload.
[15:52] <qengho> * working on chromium/ozone/mir this week.
[15:52] <qengho> * require more information about Laney's crunch creams. furiously envious.
[15:52] <qengho> * updating snappy packager scripts.
[15:52] <qengho> EOF
[15:52] <willcooke> thanks qengho
[15:53] <willcooke> did you get to the bottom of why hyperlinks from other apps are broken?  Is that the xdg-utils thing?
[15:53] <qengho> willcooke: right. xdg-mime bug.
[15:53] <willcooke> cool
[15:53] <willcooke> #topic seb128
[15:53] <seb128> kenvandine is patch piloting today so maybe he can review xdg-utils merge/update
[15:54] <seb128> otherwise didrocks has a shift on friday
[15:54] <seb128> oh
[15:54] <seb128> hey ;-)
[15:54] <seb128> • debugged u-s-d segfault due to a gsettings schemas key dropped from g-s-d
[15:54] <seb128> • uploaded gnome-control-center move of user icons data to u-c-c, allowing demoting the source to universe
[15:54] <seb128> • fixed small gedit document title regression
[15:54] <seb128> • looked at some langpack translations regression on the ota8 touch candidate
[15:54] <seb128> • discussed indicator-sound/notify-osd regression, helped to test and land the fix from Lars (thanks!)
[15:54] <seb128> • reported some bugs+code changes to make some phone dialogs more consistent
[15:54] <seb128> • libmobiledevice transition
[15:54] <seb128> • looked at the vino update, decided there was too much to revert (they dropped the standalone dialogs) and that it was easier to keep ours and backport some bugfixes, did that
[15:54] <seb128> • spending a bit of time every day to review/triage incoming bugs/errors and help with ongoing britney issues and transitions
[15:54] <seb128> • looked at/fixed some gedit theming issues (just got a patch commited upstream)
[15:54] <seb128> • continued a bit on the nautilus 3.18 update, not an easy update and still quite some work needed
[15:54] <seb128> • spend some time looking at if backporting the upstream g-s-d wacom work to u-s-d was possible, it's a bit work and unsure it's worth the effort
[15:54] <seb128> • started backporting new g-s-d upstream "tz plugin" to u-s-d (to update your tz/notify you that you are in a different tz when travelling), I think I got the changes right but I'm unsure how to test and if we want it (note that it also means installing the new geoclue service)

[15:54] <seb128> (sorry, busy week ;-)
[15:55] <willcooke> thanks serb
[15:55] <willcooke> oops
[15:55] <willcooke> seb128,
[15:55] <seb128> yw!
[15:55] <willcooke> #topic Sweet5hark1
[15:57] <seb128> did I disconnect?
[15:57] <attente> i'm wondering too
[15:57] <willcooke> dont think so, just waiting
[15:57] <seb128> k
[15:57] <seb128> no Sweet5hark1 it seems...
[15:57] <willcooke> #topic tkamppeter
[15:58] <tkamppeter> - ippusbxd: Further testing to try to solve the problem with the HP DeskJet Ink Advantage 2540, ending up with some improvements but without the solution of the problem.
[15:58] <tkamppeter> - HPLIP: Packaged and uploaded 3.15.11.
[15:58] <tkamppeter> - Ghostscript: Checked status of MIRs for syncing with Debian: openjpeg still missing (but now chances are higher that it gets into Main as Poppler needs it, too).
[15:58] <tkamppeter> - Set up a Xenial virtual machine (Used "devel" as distro name in sources.list to automatically always use current devel branch).
[15:58] <seb128> somebody should offer Sweet5hark1 an alarm reminder device
[15:58] <tkamppeter> - Bugs.
[15:58] <willcooke> thanks tkamppeter
[15:59] <willcooke> tkamppeter, saw your mail re: print dialogues - will follow up with Prod Man to get it scheduled
[15:59] <willcooke> #topic Trevinho
[15:59] <Trevinho> · Improved bamf upstart support
[15:59] <Trevinho> · made spread for application windows dynamic (it updates on new windows, or title changes when using filtering)
[15:59] <Trevinho> · Meeting with Kylin guys (https://wiki.ubuntu.com/Ubuntu Kylin/Meeting/2015/20151119)
[15:59] <Trevinho> · Added quicklist to expo launcher icon to switch workspaces.
[15:59] <Trevinho> · Making BAMF not to give priority to launched NoDisplay .desktop files (fixes nautilus being confused)
[15:59] <Trevinho> · Working in better launcher-filemanager integration, by allowing management of Trash/Devices independently.
[15:59] <Trevinho> 
[15:59] <willcooke> thanks Trevinho
[15:59] <tkamppeter> willcooke, OK, thanks.
[16:00] <willcooke> #topic robert_ancell
[16:00] <willcooke> No update this week, but I spoke to him earlier this week
[16:00] <willcooke> He's working on GNOME software
[16:01] <willcooke> we have a list of people to speak to, but so far so good
[16:01] <willcooke> non-root REST api over UNIX socket should be landing in Snappy soon
[16:01] <willcooke> #topic any other business
[16:02] <Laney> yeah
[16:02] <Laney> should look at the calendar thing
[16:02] <attente> seb128: what are those wacom changes in upstream g-s-d? are they fixing a crash?
[16:02] <seb128> Laney, yeah, did you try it?
[16:02] <seb128> i've that on my list but didn't do it yet :-/
[16:02] <Laney> no but could do
[16:03] <seb128> could be useful to have feedback from several people on the interactions
[16:03] <seb128> I'm going to look at the e-d-s integration bit
[16:03] <seb128> we need that for our $solution
[16:03] <seb128> willcooke, did you try/look at both?
[16:03] <Laney> you mean the thunderbird one?
[16:04] <willcooke> seb128, I haven't looked at either
[16:04]  * willcooke adds it to his list
[16:04]  * didrocks just tried it
[16:04] <didrocks> remember that I added some easy task for google-code-in
[16:05] <didrocks> don't jump on them before we are sure nobody will work on it :)
[16:05] <seb128> Laney, yes
[16:05] <didrocks> (like changing default color, and so on)
[16:05] <seb128> right
[16:05] <Laney> where is this list?
[16:05] <seb128> didrocks, "it" was the GNOME or the tb one? or both?
[16:05] <didrocks> GNOME
[16:05] <didrocks> if the calendar thing is that one :)
[16:06] <didrocks> Laney: uno momento
[16:06] <didrocks> Laney: https://docs.google.com/document/d/1rww6mkoQhhuijQx4yBHzMngM3HABeFx4tS7mLs2kMIA/edit#heading=h.e2psrcqwe9c2
[16:08]  * willcooke is summoned elsewhere
[16:08] <Laney> hmm
[16:08] <Laney> are these tasks agreed?
[16:08] <willcooke> I'm end the meeting, we can carry on calendar discussions in a mo.
[16:08] <willcooke> and Google Code In
[16:08] <willcooke> #endmeeting
[16:08] <meetingology> Meeting ended Tue Nov 24 16:08:43 2015 UTC.
[16:08] <meetingology> Minutes:        http://ubottu.com/meetingology/logs/ubuntu-desktop/2015/ubuntu-desktop.2015-11-24-15.30.moin.txt
[16:08] <seb128> attente, https://bugs.launchpad.net/ubuntu/+source/unity-settings-daemon/+bug/1277733 is the wacom thing
[16:09] <seb128> attente, see bug description
[16:09] <Laney> like maybe we like headerbars now and do we want to add a patch to change the default colour that will be carried forever?
[16:09] <attente> seb128: thanks
[16:09] <seb128> attente, yw
[16:09] <Laney> perhaps that can be in the theme
[16:09] <Laney> or somewhere else
[16:09] <seb128> attente, do you have a wacom device? or were just asking?
[16:09] <attente> seb128: actually i found last week that plugging in a wacom tablet ends up restarting u-s-d repeatedly
[16:09] <didrocks> Laney: I made the list reviewed by seb128 and willcooke to have another opinion
[16:10] <seb128> attente, oh :-/
[16:10] <attente> so i thought maybe there were fixes upstream
[16:10] <didrocks> Laney: I still think we should have an ubuntu feeling to gnome calendar
[16:10] <didrocks> not have an application looking out of place (and so, use the ubuntu default theme color)
[16:10] <seb128> attente, do you still have access to the tablet? I might ask you to test my backport branch once it's done
[16:10] <seb128> didrocks, +1
[16:10] <attente> seb128: yep, i have it
[16:10] <seb128> attente, great, thanks
[16:10] <Laney> I'm saying that it is in sync
[16:10] <Laney> and it would be good to keep it so
[16:10] <attente> i whip it out on the odd occasion i have to play pictionary online :)
[16:11] <Laney> you will get a patch to change the default colour in the source
[16:11] <seb128> Laney, colors can probably be tweaked from the css nowadays no?
[16:11] <Laney> maybe
[16:11] <didrocks> I guess otherwise it's a bug in upstream's code
[16:11] <didrocks> that we should fix :)
[16:12] <Laney>   /* FIXME: We should handle calendars colours better */
[16:12] <Laney>   if (!gdk_rgba_parse (out_color, e_source_selectable_get_color (extension)))
[16:12] <Laney>     gdk_rgba_parse (out_color, "#becedd"); /* calendar default colour */
[16:12] <Laney> I bet you get a patch to change that
[16:12] <Laney> unless the task is specified
[16:13] <seb128> well, we are the ones talking to the students so we can iterate if needed
[16:13] <seb128> but yeah better to specify in front where we can
[16:13] <Laney> don't feel like I'm getting much traction
[16:13] <Laney> lets move on
[16:14] <seb128> I think we all prefer non-downstream-patching solutions if we can get that yes
[16:14] <seb128> if that's what you were getting at
[16:17] <Laney> It's not very likely that the code in student is going to end up maintaining gnome calendar for us
[16:17] <Laney> so the burden of maintaining the work in the long term falls on us if the patch is in Ubuntu only
[16:18] <seb128> yeah, I doubt the intend was to have a code patch in Ubuntu
[16:18] <seb128> the goal is to have the theme tweaked to have the app look better
[16:18] <seb128> if it's not as easy as theme tweaks it might be off scope for the code-in
[16:18] <seb128> those are for young students and supposed to be easy
[16:19] <seb128> we just didn't know that those parts were not css themable
[16:19] <seb128> though some of the other UI bits might still be?
[16:21] <Laney> ok, I guess each one should be in a bug report in the end
[16:21] <Laney> which describes the required solution
[16:23] <seb128> +1
[16:23] <didrocks> sounds like Laney wants to open bug report
[16:24] <didrocks> (which won't be use in the google code-in format description, as it will be filed on google's website)
[16:25] <Laney> it doesn't really sound like that
[16:25] <Laney> but it's not going to be good if people write code that gets rejected
[16:25] <Laney> you can't give links?
[16:26] <didrocks> Laney: you can I guess, unsure, I was just asked to gather a list. All other tasks that the community team gather don't have bug reports associated
[16:27] <didrocks> maybe check with them? They are the ones handling this, I don't have access to the backend
[16:30] <Laney> looks like you get free text
[16:30] <Laney> and people submit their stuff on the website directly
[16:35] <mterry> didrocks, kenvandine: yay!  Using an sbuild, I can reproduce the failures.  Oddly, I don't get them locally, in a pbuilder, or in a PPA.  But sbuild hits it.  So at least I see the same thing you do
[16:35]  * mterry will work on a fix
[16:35] <didrocks> mterry: weird that sbuild != PPA for once and closer to pbuilder :p
[16:35] <kenvandine> i had the failures without sbuild too
[16:35] <didrocks> mterry: but yeah for reproducing!
[16:36] <mterry> kenvandine, yeah I can't explain that  :)
[16:36] <kenvandine> sbuild for wily and vivid and locally on vivid
[16:36] <kenvandine> on both of my boxes
[16:36] <mterry> kenvandine, but at least now I see the same symptom
[16:36] <kenvandine> weird
[16:36] <kenvandine> anyway, glad you reproduced it
[16:38]  * Sweet5hark1 just woke up again -- should have accepted sick leave for today.
[16:44] <willcooke> Sweet5hark1, no worries, get better
[16:45] <Sweet5hark1> willcooke: Ill do my best.
[17:07] <xclaesse> desrt, got a minute for your advice on the 3 FIXME in my settings backend?
[17:07]  * didrocks waves good evening and good night
[17:07] <Laney> night didrocks
[17:07] <ricotz> pitti, hmm, xdiagnose pulls python3.4 again
[17:07] <didrocks> see you tomorrow Laney!
[17:07] <seb128> night didrocks
[17:07] <didrocks> and seb128 :p
[17:07] <xclaesse> didrocks, fait de beaux rêves ;-)
[17:07] <seb128> ;-)
[17:07] <didrocks> xclaesse: héhé, merci, toi aussi !
[17:08] <xclaesse> 12h ici ;-)
[17:10] <pitti> ricotz: the rebuild? I just dropped a no-op option from debian/rules
[17:12] <ricotz> pitti, yes, 3.8.2
[17:12] <ricotz> before it properly depended python3.5
[17:19] <kenvandine> qengho, hey i was sponsoring your xdg-utils patch
[17:19] <pitti> ricotz: hm, odd; do you know if that changed in python-defaults or so? I can't see what in http://launchpadlibrarian.net/227445991/xdiagnose_3.8.1build1_3.8.2.diff.gz woudl have caused that
[17:19] <kenvandine> but the debdiff didn't apply cleanly, since there had been another xenial upload
[17:19] <kenvandine> i cleaned that up so the debdiff applied
[17:19] <kenvandine> but one of the patches doesn't apply
[17:19] <kenvandine> debian/patches/handle-multiple-exec-lines.patch
[17:20] <kenvandine> qengho, ^^
[17:20] <ricotz> pitti, yeah, it is clearly caused by the toolchain itself then, I would assume doko might have an idea
[17:21]  * Laney gets juju working
[17:21]  * Laney server dude now
[17:22] <seb128> Laney, you are a charming guy! ;-)
[17:25] <seb128> willcooke, ok, so I did https://git.gnome.org/browse/gedit/commit/?id=9da514288905d5b8013ddd0f2e1bdd29aded61a5 which is what upstream agreed to move in the common section
[17:26] <seb128> willcooke, do you want maybe to have a look at https://git.gnome.org/browse/gedit/plain/gedit/resources/css/gedit.adwaita.css and see what we should move to our gedit.css in our themes?
[17:26] <willcooke> seb128, looking...
[17:26] <seb128> willcooke, we already have some of the bits
[17:26] <willcooke> I'll copy it over and try it out...
[17:27] <seb128> willcooke, the sidepane close buttons (if you have documents open/the document section selected) look a bit nicer I think
[17:27] <seb128> like they are less big square blocks
[17:27] <seb128> also we should take the
[17:27] <seb128> GeditStatusbar {
[17:27] <seb128>     border-top: 1px solid @borders;
[17:27] <seb128> it makes a line displayed between the textview and the statusbar
[17:27] <seb128> willcooke, thanks
[17:28] <seb128> willcooke, I'm going to do a theme landing with the pending fix tomorrow or the day after that
[17:28] <willcooke> seb128, ack
[17:28] <seb128> *fixes even
[17:28] <qengho> kenvandine: some patch with "|sed" earlier doesn't handle .desktop files with many Exec lines well. My path there is an attempt to make sure that the bug doesn't show up again. It's not important for anything other than keeping future versions from being buggy.
[17:29] <qengho> kenvandine: thank you for looking.
[17:29] <kenvandine> qengho, that patch was sponsored by mterry since your debdiff was created
[17:30] <desrt> xclaesse: sorry.  was eating lunch.  happy to help now.
[17:30] <kenvandine> qengho, anyway, i'm done piloting i need to get back to other things now
[17:30] <kenvandine> sorry i couldn't get it uplaoded
[17:30] <kenvandine> uploaded
[17:30] <xclaesse> desrt, np, was going for lunch now ;-)
[17:31] <xclaesse> desrt, btw, what TZ are you?
[17:31] <desrt> k.  hit me up when you get back
[17:31] <desrt> EST
[17:31] <desrt> 12:30 here
[17:31] <qengho> kenvandine: the only patch that's important is the one that makes mime defaults update .config location, not only .local/share/applications/ .
[17:31] <xclaesse> ah, same here, Montréal :)
[17:31] <qengho> kenvandine: ah. Dang.
[17:31] <desrt> ← toronto
[17:31] <qengho> kenvandine: okay.
[17:31] <willcooke> seb128, are you getting any double-click / single-click oddness, especially in gedit in the normal file open window?
[17:32] <willcooke> seb128, like, *sometimes* a single click opens a folder, and sometimes its a double click
[17:32] <seb128> willcooke, yes, it's quite annoying, I was just being grumpy here about that
[17:32] <willcooke> :) glad it's not just me
[17:32] <seb128> I do open -> other documents and want to select files and I'm used to double click to open and single click around
[17:32] <willcooke> I'm trying to work out the best way to recreate
[17:32] <seb128> and single click validates things now
[17:33] <seb128> bah
[17:33] <willcooke> I think we need to keep that behaviour as it used to be
[17:33] <seb128> it seems they screwed up the delay
[17:33] <seb128> like if you single click a folder
[17:33] <seb128> then single click again it takes it as a double click
[17:33] <seb128> or it opens selected folders on single click
[17:33] <seb128> either way confusing
[17:33] <Laney> it's always the selected file
[17:34] <Laney> I think
[17:34] <seb128> always the selected file that what?
[17:34] <Laney> that opens with a single click...
[17:34] <seb128> right, I wonder if that's wanted
[17:34] <seb128> it's confusing
[17:35] <seb128> the change is wanted
[17:36] <seb128> the side effect is a bug which got fixed with https://git.gnome.org/browse/gtk+/commit/?id=c619c862503ccf54c9afbdb0708a3376ce1728fb
[17:36] <Laney> https://git.gnome.org/browse/gtk+/commit/gtk/gtkfilechooserwidget.c?h=gtk-3-18&id=fb0a13b7f070a14312dafa1e4df6ba03cf33be01
[17:36] <seb128> which is actually the bit that annoys me
[17:36] <seb128> when you double click the folder it opens on first click then open a file in it with the second
[17:36] <Laney> nod
[17:37]  * seb128 asks if they can backport that fix to 3.18
[17:37] <Laney> it is
[17:37] <seb128> hum
[17:37] <seb128> it should be in .5
[17:38] <seb128> doesn't work though :-/
[17:39]  * seb128 comments on the bug
[17:40] <seb128> I'm also not convinced by the behaviour, would be curious to know mpt's/design opinion on that
[17:40] <seb128> it makes the UI feels unreliable, it behaves differently in different situations and it's not obvious why
[17:41] <seb128> but I guess the goal was for touch and the patch was supposed to make it no do that for mouse events?
[17:41] <willcooke> with a mouse it just feels plain broken.  I dont think we can expect users to learn a new way of doing things at this point.
[17:42] <willcooke> we should start a list of things to talk to John about on 10 Dec, seb128 can we wait that long?
[17:42] <mpt> “make our own double-click determination”? That sounds like fun
[17:42] <seb128> willcooke, we sure can
[17:44] <Laney> talk to mclasen?
[17:45] <seb128> I commented on the bug
[17:45] <seb128> waiting to see what pbor says
[17:45] <seb128> his commit feels like "shouldn't do that for mouses"
[17:45] <seb128> since he wrote to ignore button 2/3 events
[17:46] <Laney> that's not the same as willcooke was talking about with "plain broken" and not learning a new thing
[17:47] <Laney> that is a judgement on the entire feature
[17:47] <seb128> well my understanding is that the feature is meant for touch
[17:47] <seb128> e.g finger use
[17:47] <seb128> willcooke's point is probably for mouse users
[17:47] <willcooke> indeed
[17:48] <Laney> you didn't say that in your comment
[17:48] <seb128> need to go for a bit but I can comment a bit more/ask pbor directly later on IRC
[17:48] <Laney> it's a mclasen feature, he was just fixing a bit of it
[17:49] <seb128> right, well if pbor's fix does what I understand it should do then I don't think we have an issue
[17:49] <seb128> otherwise we need to ask mclasen
[17:49] <seb128> bbiab
[17:50] <Laney> not if you hate the entire single click feature
[17:50] <seb128> shrug
[17:50] <seb128> I hate it for mouses
[17:50] <seb128> not for touch
[17:50] <Laney> then you need to speak to him
[17:50] <seb128> ok, need to go
[17:50] <seb128> oh, right
[17:50] <seb128> I understand what you mean
[17:50] <Laney> not trying to be difficult, I just don't think that fix is meant to turn it off for mice
[17:50] <seb128> right, it's going to make the file not open
[17:50] <seb128> but selected instead?
[17:51] <seb128> but yeah, good point
[17:51] <Laney> it's probably meant to fix accidental double clicks or something
[17:51] <seb128> I'm going to report a new bug/talk to mclasen I guess
[17:51] <Laney> but still single clicking on a selected item is meant to open it
[17:51] <seb128> right
[17:51] <seb128> sorry for being slow to get what you meant
[17:51] <seb128> going to file a bug later
[17:51] <seb128> need to go for now ;-)
[17:51] <Laney> ok!
[17:51] <Laney> laters
[17:52] <willcooke> cheers Laney
[17:57]  * Laney gives up on juju + lxd
[17:57]  * Laney tries the canonistack instead
[18:23] <Laney> http://10.55.60.153/
[18:23] <Laney> 'mazin
[18:26] <seb128> Laney, not loading from here ... is that a public ip?
[18:27] <seb128> willcooke, btw about that single/double click, we might want to talk to design before reporting upstream, would be better to have a bug with some contructive input/design recommendation
[18:27] <seb128> rather than just "it sucks, was better beforfe"
[18:28] <willcooke> :)
[18:28] <willcooke> good plan
[18:37] <mterry> kenvandine, didrocks: fixed deja-dup tests in sbuild (kenvandine, the issue I found was around HOMEs that didn't exist -- I still don't know why it was failing for you)
[19:07] <willcooke> DAMN IT GEEEEEDDIITTTTTTTTT
[19:07] <willcooke> keeps crashing and loosing my in-line style in the selector
[19:07]  * willcooke has got wise to it now 
[19:08] <willcooke> I've been saving a text file with every change I make
[19:08] <willcooke> but yeah, gedit is super crashy for me
[19:09] <jpds> willcooke: apt-get install vim
[19:11] <willcooke> :D
[19:32] <attente> ugh... i disabled maliit, and now i can't adb into the device because the screen is locked and i need maliit to unlock it
[19:32] <willcooke> wakka wakka wakka
[19:33] <attente> lol
[19:33] <willcooke> I can't think of a hacky work around, but popey might know.  he's good at that sort of thing
[19:34] <attente> is it possible to use a hardware keyboard? i don't actually have one lying around though
[19:34] <willcooke> dunno, I think otg is enabled now
[19:35] <willcooke> ogra_ might know as well ^
[19:35] <attente> i wonder if sshd is running on this thing
[19:35] <willcooke> only if you enabled it I think
[19:46] <Sweet5hark1> good news: at least build-arch finishes with 5.1.0~alpha/xenial
[19:47] <willcooke> \o/
[19:48] <willcooke> other good news, my css selectors are working at last :)
[19:49] <seb128> willcooke, report the crash if you can get a backtrace
[19:49] <willcooke> seb128, will do, once I've got these gedit theming sorted
[19:49] <willcooke> I'm on a roll :)
[19:49] <seb128> let me know tomorrow morning if you need help to get the bt
[19:49] <willcooke> thx seb128
[19:50] <seb128> np!
[19:50] <seb128> on that calling it a day
[19:50] <seb128> have a good evening everyone
[19:50] <willcooke> cya seb128
[20:46] <willcooke> hi robert_ancell
[20:46] <willcooke> bye robert_ancell
[20:47] <robert_ancell> willcooke, heh
[20:47] <willcooke> I'm admitting defeat with these themes for the day and going to watch tv before it's 11pm again
[20:47] <willcooke> ah crap
[20:47] <willcooke> I still haven;t sent that follow up to ev - will do tomorrow
[20:47] <willcooke> g'night!