[07:53] <didrocks> good morning
[08:04] <oSoMoN> good morning
[08:10] <kvalo> kamstrup: good morning. sorry to bother you again, but can you do review again? https://code.launchpad.net/~kvalo/indicator-network/settings-tech-control/+merge/50972
[08:11] <kvalo> kamstrup: andy already reviewed it, so you can just take a quick peek.
[08:11] <kamstrup> kvalo: i don't have time right now - but maybe you can run over some of the reviews Ted requested?
[08:11] <kamstrup> kvalo: ok - maybe in an hour or so
[08:11] <kvalo> kamstrup: ok, I can ask ronoc as well. no worries.
[08:11] <kamstrup> kvalo: i'm just taking some heat for some place issues an I urgently need to address them
[08:12] <kvalo> kamstrup: I'll go through ted's reviews
[08:12] <kvalo> kamstrup: yeah, I'm can imagine the heat
[08:15] <MacSlow> greetings everybody
[08:59] <kvalo> ronoc: morning. if you have time, can you check this one: https://code.launchpad.net/~kvalo/indicator-network/settings-tech-control/+merge/50972
[09:02] <ronoc> kvalo, sure
[09:03] <kvalo> ronoc: thanks
[09:10] <ronoc> kvalo, all good done
[09:10] <kamstrup> didrocks: ! a libzeitgeist release! https://launchpad.net/libzeitgeist/0.3/0.3.4 This time without the gio module - and this release is rather critical as it fixes a data corruption bug with the zg
[09:11] <kvalo> ronoc: excellent, thanks
[09:11] <didrocks> kamstrup: thanks, trying to get everything together
[09:11] <didrocks> kamstrup: does it work with the current zg natty stack?
[09:11] <kamstrup> didrocks: yups
[09:16] <didrocks> kamstrup: do you have a bug list of what it fixes?
[09:19] <kamstrup> didrocks: meh, if only I could target bugs to closed milestones then I could whip you up a nice LP report :-S
[09:19] <didrocks> kamstrup: I have a script doing that
[09:20] <didrocks> kamstrup: but yeah, just for now, give me the list of bugs please :)
[09:20] <didrocks> (looking at the commits as well)
[09:22] <kamstrup> didrocks: it is https://bugs.launchpad.net/libzeitgeist/+bug/724199 and https://bugs.launchpad.net/libzeitgeist/+bug/718472
[09:23] <didrocks> kamstrup: excellent, thanks!
[09:23] <didrocks> kamstrup: should I just restart the places + make a search to check everything is ok?
[09:24] <kamstrup> didrocks: something like that - you may wanna manually kill and run the files place so you can tail stdout
[09:24] <didrocks> kamstrup: ok
[09:25] <kamstrup> ronoc: hey - hows the sound stuff coming along?
[09:25] <kamstrup> ronoc: didrocks is going to a very scarce resource today so we need to cut the release of libunity very early today
[09:25] <didrocks> kamstrup: I need to upload the place to remove libzeitgeist-gio as a dep
[09:25] <ronoc> kamstrup, good, haven't done anything since last night, just going through bugs
[09:25] <ronoc> kamstrup, cool will look at it right away
[09:26] <didrocks> kamstrup: but the places needs new libunity as well :)
[09:26] <didrocks> it's official, today will be "awesome"
[09:27] <kamstrup> didrocks: exactly - i'll just quickly check with ronoc if we'll land the soundmenu API today or we're gonna have to punt it for next week
[09:27] <didrocks> excellent :)
[09:27] <kamstrup> didrocks: look at the bright side - if you survive today you can do some serious slacking off tomorrow - assuming that we haven't broken everything of course ;-)
[09:28] <didrocks> kamstrup: ahah, if I have nothing to do tomorrow, I'll be start looking finally at Alt + F2 :)
[09:28] <didrocks> starting*
[09:30] <didrocks> kamstrup: hum, if we remove the gio module without getting the new datahub, there is no worry then?
[09:34] <kamstrup> didrocks: it only means we wont log app popularity until we have the new datahub
[09:34] <kamstrup> didrocks: so a slightly wrong result set for popular apps, but that's a it
[09:35] <didrocks> kamstrup: ok, I understood all of your stack correctly then \o/ sounds good for a transition*
[09:35] <kamstrup> didrocks: yes
[09:47] <didrocks> kamstrup: ok, libzg ready to be pushed
[10:24] <htorque> MacSlow: hello, should the super key overlays for the places icons already show anything? they are empty here.
[10:26] <MacSlow> htorque, wait for the release... the stuff for the places superkey-overlays will be part of that
[10:26] <htorque> MacSlow, ok, will do, thanks
[10:27] <MacSlow> htorque, last evening I finished that and only pushed this morning
[10:36] <MacSlow> hey iainfarrell
[10:36] <htorque> MacSlow, oh, so it should be in trunk then (because that's what i'm testing)? i see 1..0, 'w', and 't', but the places' overlay is empty
[10:37] <iainfarrell> MacSlow: hey
[10:37] <MacSlow> htorque, you mean "applications" and "files" ?!
[10:37] <htorque> MacSlow, yes
[10:37] <MacSlow> htorque, they get their label from /usr/share/unity/place/<bla>.place
[10:38] <MacSlow> htorque, if there's not entry Shortcut=x in section [Entry:Files] nothing will show
[10:39] <MacSlow> htorque, if you want to try now just add them yourself
[10:39] <MacSlow> htorque, but be reminded that those are meant to be coming from localized .place files
[10:40] <htorque> MacSlow, thanks, adding the shortcut key worked - i was just wondering if it currently should show anything at all :)
[10:46] <htorque> MacSlow, talking about localization - it doesn't seem to accept umlauts (english system, german keyboard layout)
[10:47] <htorque> worth a bug report or just not yet done?
[10:47] <MacSlow> htorque, file a bug... after the realease... I'll look into it (you may assign me to it)
[10:47] <htorque> release is planned for later today?
[10:47] <MacSlow> correct
[10:47] <htorque> great, will do, thanks again
[11:04] <rodrigo_> hmm, libindicator 0.3.19 isn't packaged yet it seems, any idea when it will be?
[11:05] <rodrigo_> ah, sorry, it is indeed
[11:10] <rodrigo_> njpatel, does the pkg_check_modules thing in CMakeLists.txt allow checking for version numbers? I added a check for indicator but it seems to ignore it
[11:11] <njpatel> rodrigo_, erm, I have no idea :/
[11:11]  * njpatel hates CMake
[11:11] <rodrigo_> ok, will google
[11:11] <rodrigo_> yeah, /me doesn't like it neither
[11:11] <rodrigo_> why does unity use it?
[11:13] <didrocks> agateau: ^^
[11:13] <didrocks> rodrigo_: because compiz uses it
[11:14] <rodrigo_> ah
[11:14] <rodrigo_> agateau, do you happen to know about pkg_check_modules?
[11:15] <agateau> rodrigo_: yes you can check for a minimum version number iirc
[11:15] <rodrigo_> agateau, seems to ignore it:
[11:15] <rodrigo_> pkg_check_modules(SERVICE_DEPS REQUIRED gobject-2.0 gio-2.0 gtk+-2.0 gthread-2.0 indicator >= 0.3.19 x11)
[11:16] <rodrigo_> I used a bigger number to check, and cmake didn't complain about the indicator version
[11:16] <agateau> rodrigo_: maybe get rid of the spaces before and after >=? (not sure)
[11:16] <rodrigo_> ah, ok, trying
[11:17] <rodrigo_> no, same thing, it ignores it
[11:17]  * rodrigo_ googles more
[11:17] <aruiz> can I join the CMake hatred?
[11:17] <aruiz> *grrrrr*
[11:17] <rodrigo_> aruiz, please :)
[11:18] <agateau> rodrigo_: I have 0.3.19 here, so maybe it just finds it
[11:19] <rodrigo_> agateau, I added it myself, and tried using 1.3.19, and still no complains, it just goes over
[11:20] <rodrigo_><EMAIL_ADDRESS>shows a pkg_check_modules(LIBXML2 REQUIRED libxml-2.0>=2.6.32)
[11:20] <rodrigo_> so, for some reason, it's not woking for me :(
[11:21] <agateau> rodrigo_: mmm did you rm CMakeCache.txt?
[11:21] <rodrigo_> no
[11:21] <rodrigo_> ok, that seems to do it indeed!
[11:22] <agateau> good
[11:22] <rodrigo_> well, not really:
[11:22] <rodrigo_> --   package '>=' not found
[11:22] <rodrigo_> --   package '0.3.19' not found
[11:22] <rodrigo_> hmm
[11:22] <agateau> rodrigo_: that is the spaces I think
[11:22] <rodrigo_> yes
[11:22] <rodrigo_> yes, now it works
[11:32] <jfi> Kaleo, you are really 100% sure that unity-2d is supporting 'unity_launcher_entry_set_count' (natty)? I cannot make it works, do you have a working example or some documentation (except the very basic info from wiki) ?
[11:34] <kamstrup> njpatel: can I get you to try out r148 of lp:~kamstrup/unity-place-files/reentrancy-hack if it works I'll merge to master and port the fixes to u-p-a
[11:35] <njpatel> trying now
[11:35] <kamstrup> njpatel: i just discovered another nasty way dupes could slip through my net - but it should be tight now :-)
[11:36] <kamstrup> i daresay it works extremely well here now
[11:36] <kamstrup> better than it ever has at least :-)
[11:36] <njpatel> I'll be the judge of that! MUHAHAHAH
[11:38] <njpatel> kamstrup, can still reproduce, but harder. I am not kidding, but "asshat" is my new word that causes the bug :)
[11:39] <kamstrup> lol
[11:39] <njpatel> do you want a trace?
[11:39] <kamstrup> njpatel: why not
[11:41] <njpatel> kamstrup, http://paste.ubuntu.com/571668/
[11:41] <kamstrup> njpatel: and which group are the remaining results in?
[11:42] <kamstrup> 0 or != 0 being the important point
[11:42] <njpatel> kamstrup, 4
[11:42] <jfi> Kaleo, ha spotted the gtk loop seems required, forget about my noise, it works  fine
[11:42] <kamstrup> 4 again!?
[11:42] <njpatel> yeah :/
[11:42] <kamstrup> oh right...
[11:43] <kamstrup> njpatel: 4 is not favs - but a catch-all group used in global mode
[11:43] <njpatel> kamstrup, unless i'm reading it wrong, heres the output of "Clone" http://paste.ubuntu.com/571670/
[11:43] <njpatel> aaah
[11:43] <kamstrup> njpatel: can you check if you can repro with the SetSearch() ie *not* the SetGlobalSearch()
[11:43] <njpatel> sure, hold up
[11:44] <njpatel> kamstrup, nope, normal search works fine
[11:44] <njpatel> asshat yields no results
[11:44]  * njpatel is just happy it didn't pick up a picture of him
[11:44] <kamstrup> njpatel: when I look up d018e7d35fffe9e0815f2a5eab7d03e4 in a rainbow table it doesn't say "launcher.avi" but something very naughty...
[11:45] <njpatel> hah
[11:45] <kamstrup> njpatel: so I guess it means that non-global is working?
[11:45] <njpatel> it's launcher.avi from my blog! I was being all egotistical and browsing my old posts
[11:45] <njpatel> kamstrup, non-global is working fine
[11:45] <kamstrup> njpatel: riiiiiight
[11:45] <kamstrup> njpatel: that's progress!
[11:46] <njpatel> kamstrup, I actually had a question, why don't we just call SetSearch for global search again?
[11:46]  * njpatel forgets
[11:46] <njpatel> it would make the daemons quite simple, right?
[11:46] <kamstrup> njpatel: SetSearch() takes the active section into account and such - and it does grouping differently
[11:46] <kamstrup> njpatel: yes
[11:47] <kamstrup> njpatel: my life would be 30-40% better
[11:47] <njpatel> right, but aren't the results still added by most->least importance? despite of grouping?
[11:47] <njpatel> I mean, I could ignore the grouping and keep the section as 0
[11:48] <njpatel> kamstrup, ^ /me needs to actually address messages
[11:48] <kamstrup> njpatel: the issue is we have a mix of relevancy-ranked and time-sorted
[11:49] <njpatel> time-sorted was for section !=0 right?
[11:49] <Kaleo> jfi: ok :)
[11:49] <kamstrup> njpatel: for time-sorted results we can iteratively trim down the result set as you type because sorting is stable
[11:49] <njpatel> right
[11:49] <kamstrup> njpatel: and not so much for relebancy ranked - we need to rebuild the result set for those
[11:49] <kamstrup> njpatel: exactly
[11:50] <njpatel> interesting
[11:50] <kamstrup> njpatel: the bug here is
[11:50] <kamstrup> njpatel: is that for global results we always override the group id with 4
[11:50] <njpatel> also, I guess, we don't want to have installable applications showing in the global search
[11:50] <njpatel> coolio
[11:50] <kamstrup> njpatel: thus me failing to remove the relevancy-sorted results which I expect to have group==0
[11:50] <njpatel> right
[11:51] <kamstrup> sigh
[11:51] <kamstrup> this is some complex shit
[11:51] <njpatel> this global vs. only one SetSearch() can wait for another day, sorry for taking you off track :)
[11:52] <kamstrup> njpatel: but I think the real question here is if it makes sense to do both relevancy- and time based sorting in global mode
[11:52] <kamstrup> njpatel: not sure it does
[11:53] <njpatel> I think relavancy is key, I mean, ZG takes time into account when it does it's ranking, right?
[11:53] <kamstrup> njpatel: nope - the relevancy is pure textual at this point
[11:53] <njpatel> ah
[11:53] <kamstrup> njpatel: other than that we can sort by popularity or recency
[11:53] <kamstrup> those are the options
[11:54] <njpatel> recency would make sense for global I thin
[11:54] <kamstrup> njpatel: my gut instinct tells me we should sort by recency in global mode
[11:54] <njpatel> :)
[11:54] <kamstrup> lol
[11:54] <kamstrup> njpatel: we're in sync today
[11:54] <kamstrup> scary
[11:54] <njpatel> i know, the world is gonna be screwed!
[11:55] <kamstrup> njpatel: the idea being that the dash search is for something you expect to be readily available aka "recent"
[11:55] <njpatel> exactly
[11:55] <kamstrup> njpatel: and when you know that the stuff is mentally far away you need to dig into the files place
[11:55] <kamstrup> njpatel: ok - I'll create a dedicated code path for global search that only does recency sorting and we can see how it works
[11:56] <njpatel> sounds like a plan!
[12:03] <rodrigo_> hmm, unity trunk doesn't start for me
[12:03]  * rodrigo_ debugs
[12:05] <aruiz> kenvandine, ping me when you're around :-)
[12:21] <kamstrup> njpatel: ok r129 for you testing plessure
[12:22] <kamstrup> pleasure as well
[12:22] <njpatel> I'll do both
[12:22] <njpatel> for my pressure
[12:22] <njpatel> ;)
[12:23] <didrocks> kamstrup: once you will fix in the application place bug #https://bugs.launchpad.net/bugs/721289
[12:23] <didrocks> kamstrup: think to set fix commited for the unity task (and ensure it's milestone for this week as well) please :)
[12:25] <kamstrup> didrocks: yeah apps are not fixed yet - just working out the kinks in the files place with njpatel and then porting that to the apps once I have a firm grasp
[12:25] <didrocks> kamstrup: sure, it's just kind reminder for auto release note :)
[12:27] <njpatel> kamstrup, asshat works!
[12:27] <njpatel> I mean, it doesn't. You know what I mean
[12:27] <njpatel> no bad results :)
[12:27] <njpatel> kamstrup, btw, applications place doesn't have this issue at all, from what I can tell
[12:30] <kamstrup> njpatel: it does - it just a lot more unlikely to hit it
[12:30] <njpatel> ah, oaky
[12:30] <njpatel> okay(
[12:30] <njpatel> okay*
[12:30] <njpatel> wow
[12:31] <dbarth_> njpatel: what's the branch jay has ready for the a11y fix?
[12:31] <dbarth_> apinheiro: ^^
[12:31] <kamstrup> njpatel: so - can you play a little around with local vs global search and check if everything is as expected
[12:31] <njpatel> dbarth_, lp:~unity-team/nux/nux.event-fixes/ & lp:~unity-team/unity/unity.scrolling-improvements/
[12:31] <njpatel> kamstrup, yep, I'm doing a lot of that as part of my testing, so will let you know if something weird happens
[12:31] <apinheiro> njpatel, ok thanks
[12:32] <kamstrup> njpatel: ok - I have a good feeling about this - so i'll merge to trunk and start porting the apps place. Then let's hope nothing major shows up :-)
[12:32] <njpatel> shweet
[12:33] <apinheiro> lamlex, could you take a look to this merge proposal:
[12:33] <apinheiro> https://code.launchpad.net/~apinheiro/unity/Bug723699?
[12:33] <apinheiro> it is not a really complex thing
[12:33] <apinheiro> is use gconf instead of gsetting for the accessibility check
[12:54] <dbarth_> cool, thanks
[12:54] <dbarth_> apinheiro: don't wait on lamalex, he is not up yet and may not have the bandwidth for a review today
[12:55] <apinheiro> dbarth_, ok, so as rodrigo_ already reviewed it
[12:55] <apinheiro> can I just merge it?
[12:55] <dbarth_> apinheiro: yes, easier
[12:55] <apinheiro> ok, thanks
[12:55] <dbarth_> apinheiro: go ahead, i approved it as well
[12:56] <rodrigo_> apinheiro, just pushed my last changes to the ref_state_set branch, although the panel service is hanging on dbus for me, so couldn't test it, so if it does for you, could you have a look?
[12:56] <dbarth_> njpatel: you on board with the change here: https://code.launchpad.net/~apinheiro/unity/Bug723699/+merge/50963 ?
[12:56] <dbarth_> njpatel: ie can that go into the release today?
[12:57] <njpatel> dbarth_, +!
[12:57] <njpatel> dbarth_, +1
[12:58] <rodrigo_> apinheiro, ditto for https://code.launchpad.net/~rodrigo-moya/unity/accessible-name-for-indicators/+merge/51120 , will try testing them after lunch
[12:59] <rodrigo_> njpatel, having dbus hangs on the panel service with trunk, any idea?
[12:59] <apinheiro> rodrigo_, have you tested the gconf branch?
[12:59] <apinheiro> probably it is still a gsettings thing
[12:59] <rodrigo_> apinheiro, yes
[12:59] <rodrigo_> apinheiro, no, I've changed the gsettings key locally, so that it starts correctly
[13:00] <njpatel> rodrigo_, nope :/ haven't experienced that
[13:00] <rodrigo_> so it's indeed hanging in dbus, that's what it shows in the output
[13:00] <rodrigo_> ok, out for lunch, probably it will work later, if I give it time to relax :)
[13:00] <dbarth_> apinheiro: merge at will
[13:00] <apinheiro> dbarth_, ok
[13:01] <njpatel> where "will" =  now, please :)
[13:05] <kamstrup> njpatel: the apps place is not listing Available apps - your bug or my bug?
[13:05] <njpatel> kamstrup, mine, I've switched it off for now as I don't have activation support
[13:06] <kamstrup> njpatel: ok fair enough, i was afraid something had gone b0rked on my side
[13:47] <kenvandine> aruiz, ping
[13:47] <kenvandine> aruiz, can you do a release for lo-menubar?
[13:47] <kenvandine> i really want to get the package uploaded asap
[13:50] <aruiz> kenvandine, I can roll a quick one, yes
[13:51] <lamlex> dbarth_: why wouldn't I have the bandwidth for a review? I know I have a lot of bugs on my plate, but something to mix it up is more than welcomed
[13:51] <lamlex> unless nvidia got uploaded today.. then that's another story
[13:51] <aruiz> kenvandine, but I will roll another one tomorrow with a bigger set of changes
[13:52] <aruiz> nvidia is making us all happy aren't they?
[13:53] <kenvandine> aruiz, that is fine
[13:54] <aruiz> kenvandine, give me 10 minutes and I'll do the merge and release
[13:54] <kenvandine> thx
[13:54] <aruiz> kenvandine, btw, I don't remember if I told you that this package should depend on libreoffice-gtk
[13:55] <kenvandine> you didn't, but i'll make sure it does
[13:55] <aruiz> yeah
[13:55] <aruiz> thanks
[14:13] <aruiz> kenvandine, done
[14:13] <aruiz> :-)
[14:14] <kenvandine> woot
[14:14] <kenvandine> thx aruiz
[14:14] <aruiz> np
[14:14]  * aruiz goes back to refactor
[14:14] <aruiz> refactor+fix
[14:14] <aruiz> that is
[14:19] <njpatel> TheMuso, ping, any status on the icon-only-indicators-dont-have-accessible-names?
[14:25] <tedg> njpatel, I plan on getting the indicator-application side of that out today.
[14:25] <tedg> njpatel, The other ones do mostly.
[14:25] <tedg> njpatel, They pass up to libindicator I believe.
[14:25] <njpatel> alrighty, something that can land for Monday's unity release?
[14:26] <tedg> njpatel, Do you guys have the panel service part done?
[14:26] <boulabiar> bug #724051
[14:26] <boulabiar> sorry !
[14:26] <njpatel> tedg, that's what I was asking TheMuso about, I thought he was working on the branch
[14:26] <njpatel> rodrigo_, ^
[14:26] <njpatel> https://bugs.launchpad.net/libindicator/+bug/691677
[14:26] <tedg> njpatel, I talked to him and he thinks rodrigo_ is working on it.
[14:27] <njpatel> :)
[14:27] <njpatel> #691677
[14:27] <njpatel> bug #691677
[14:27] <njpatel> there you go
[14:27] <njpatel> rodrigo_, are you working on this bug ^ ? what's the status
[14:28] <kamstrup> didrocks: omg! i love the new super-a and super-f shortcuts!
[14:28] <didrocks> kamstrup: heh :)
[14:29] <njpatel> didrocks, I think we need to make the super key timeout a little longer
[14:29] <njpatel> didrocks, i'm not fast enough for it most times :)
[14:30] <didrocks> njpatel: open a bug, I can do that I guess, just need to think about it
[14:30] <didrocks> njpatel: oh timeout
[14:30] <njpatel> right
[14:30] <didrocks> sorry, I was thinking the display
[14:30] <njpatel> don't want to make a bug for that :)
[14:30] <didrocks> njpatel: ok, can fix that in trunk in a minute :)
[14:30] <njpatel> shweet
[14:30] <didrocks> njpatel: in fact, I based on super timeout <= show_launcher_animation
[14:31] <njpatel> didrocks, yeah, I saw that, but I think it needs to be independent and we can tweak until we get it right
[14:31] <njpatel> didrocks, main reason being different types of keyboards etc, so it'll take some playing around with
[14:31] <didrocks> njpatel: sure
[14:31] <didrocks> njpatel: uno memento
[14:33] <didrocks> njpatel: doubling ~250ms looks nice to me, wdyt?
[14:34] <njpatel> yes
[14:34] <njpatel> that's the same timeout I use for live-search
[14:34] <didrocks> njpatel: nice!
[14:34] <didrocks> pushed :)
[14:34] <njpatel> thanks!
[14:34] <didrocks> yw
[14:34] <njpatel> i'm just getting a review on my branch and then releasing!
[14:35] <jcastro> morning guys
[14:35] <jcastro> PSA: Post release please tag up more bitesize bugs
[14:42] <njpatel> jcastro, will do
[14:43] <jcastro> I look forward to the goodies today *nom*
[14:46] <apw> i assume unity corefumping on login is a known issue
[14:46]  * apw throws his laptop in the bin
[14:49] <rodrigo_> njpatel, tedg: https://code.launchpad.net/~rodrigo-moya/unity/accessible-name-for-indicators/+merge/51120
[14:49] <rodrigo_> njpatel, I didn't know the branch had landed until today
[14:49] <njpatel> rodrigo_, awesome! I'll review
[14:50] <rodrigo_> njpatel, well, let me first merge with apinheiro_afk's gconf branch first
[14:50] <njpatel> rodrigo_, an idea, we have another release on monday, so we can merge this after todays, as we don't want to block on a new indicator release
[14:51] <njpatel> does that sound okay?
[14:51] <rodrigo_> njpatel, yes, sure
[14:51] <njpatel> basically we merge it as soon as I've made the release
[14:51] <njpatel> shweet
[14:55] <lamlex> uuhggh my body is in so much pain
[14:55] <lamlex> picked up running yesterday
[14:56] <lamlex> apparently no matter how fast you can ride a bike, it doesn't mean you can run
[14:59] <bcurtiswx> bug #724350
[15:00] <kenvandine> tedg, seb128: how do you guys feel about displaying the evolution shortcuts that are in the messaging menu in the unity launcher too?
[15:00] <kenvandine> http://ubuntuone.com/p/en6/
[15:01] <tedg> kenvandine, No issue, but I think the Unity launcher should have calendar as well.
[15:02] <seb128> bcurtiswx, it's fixed in trunk and gds has been uploaded with a breaks
[15:02] <kenvandine> tedg, that would be nice, but not as trivial as changing the OnlyShowIn
[15:02] <seb128> bcurtiswx, i.e you can close this bug
[15:02] <kenvandine> tedg, oh, you mean opening the calendar
[15:02] <kenvandine> makes sense
[15:02] <tedg> kenvandine, Why not?  "evolution --calendar" no?
[15:02] <kenvandine> i can add that
[15:02] <bcurtiswx> seb128, great.  Figured i'd get the report out since I was in the middle of the crash. Thx :)
[15:03] <seb128> kenvandine, shouldn't that be automatically working already?
[15:03] <kenvandine> i thought you meant calendar events
[15:03] <kenvandine> seb128, not really
[15:03] <seb128> bcurtiswx, you can downgrade gsettings-desktop-schemas as a workaround
[15:03] <kenvandine> just gotta change the OnlyShowIn in the desktop file
[15:03] <kenvandine> seb128, i'll do it now
[15:03] <seb128> kenvandine, ok great
[15:03] <seb128> kenvandine, I though it was supposed to list the same entries than the indicators
[15:03] <seb128> in any case we want those yes
[15:04] <kenvandine> tedg, don't forget my evolution-indicator branch :)
[15:06] <tedg> kenvandine, Yeah, and mterry's datetime branch.
[15:06]  * tedg has lots of reviews
[15:10] <seb128> kenvandine, ok, evolution-indicator, roll a new tarball there is a crasher fix in trunk as well which didn't get uploaded and would be nice to get
[15:11] <kenvandine> seb128, i will
[15:11] <seb128> thanjks
[15:11] <seb128> -j
[15:12] <kenvandine> just waiting for tedg to merge my branch :)
[15:13] <rodrigo_> njpatel, apinheiro_afk: ready for review -> https://code.launchpad.net/~rodrigo-moya/unity/accessible-name-for-indicators/+merge/51120
[15:13] <lamlex> didrocks: so I was talking to vish about our bug workflow and use of opinion
[15:13] <rodrigo_> tedg, the accessible_desc string seems to be empty for all indicators, am I missing some indicator update?
[15:14] <didrocks> lamlex: can we discuss that later? I'm on 15 package release right now :/
[15:14] <njpatel> rodrigo_, apinheiro_afk okay, but please do not commit anything to trunk right now, I'm making a release
[15:14] <lamlex> oh sure
[15:14] <lamlex> didrocks: ping me when you're free :)
[15:14] <rodrigo_> njpatel, yes, sure
[15:14] <tedg> rodrigo_, Uhm, it won't be filled for any app indicators, but I believe that at least sound is setting it.
[15:14] <didrocks> lamlex: won't be today :)
[15:14] <lamlex> ok
[15:14] <apinheiro_afk> rodrigo_, ok, thanks for the hing, I would review it woon
[15:14] <apinheiro_afk> soon
[15:15] <rodrigo_> tedg, hmm, seems not for me, so I guess it hasn't been released yet?
[15:15] <tedg> ronoc, ^ are you setting the accessible desc in indicator-sound?
[15:18] <ronoc> tedg, no ,still waiting for luke's resubmitted merge reqest
[15:18] <ronoc> request even
[15:19] <tedg> ronoc, Ah, hmm.  Kinda needs to get in today.... can you fix it?
[15:19] <ronoc> tedg, there were problems with the merge request last week
[15:19] <ronoc> tedg, seriously ? okay one sec I'll see I can find the branch
[15:20] <tedg> ronoc, Well, not sure if it'd need an FFe or not... but it seems like it'd be close.
[15:20] <ogra> didrocks, any news about the nux fix? we would really like to have working armel images again (they are not building since two weeks now)
[15:21] <didrocks> ogra: today is the release
[15:21] <didrocks> it will come today
[15:21] <ogra> goo
[15:21] <ogra> d
[15:21] <ogra> :)
[15:21] <ogra> thanks
[15:21] <ogra> just wanted to make sure, sorry for appearing pushy
[15:21] <tedg> ronoc, Probably depends on how easy it will be for you to fix it.  If it's easy, let's not wait on the back-and-forth and just fix and merge.  If there's a bunch of things, I think it might be worth the paperwork.
[15:22] <ronoc> tedg, okay
[15:23] <apw> is the 'accessibility' key assertion crash in unity known?
[15:25] <apw> njpatel, ^^
[15:25] <njpatel> apw, yeah, will be fixed today
[15:26] <njpatel> apw, are you running packages or trunk?
[15:26] <apw> i am running whats in the archive .. thats what we are meant to do
[15:26] <apw> else its not dogfooding
[15:27] <apw> how did a startup crash get through our testing before upload
[15:27] <didrocks> ogra: hum, it seems the patch wasn't attached to https://bugs.launchpad.net/nux/+bug/721118
[15:27] <didrocks> ogra: where is it?
[15:27] <ogra> didrocks, i think janimo sent it upstream
[15:27] <ogra> to jay he said
[15:28] <janimo> didrocks, hello
[15:29] <didrocks> janimo: hey, where is your patch?
[15:29] <janimo> didrocks, I believe I have a merge request for nux in LP
[15:29] <ronoc> tedg, on its way ...
[15:29] <didrocks> janimo: ok, you didn't attach to the bug, we found it again, thanks
[15:29] <janimo> didrocks, right. I am not sure I knew there was a bug
[15:30] <janimo> didrocks, can I get commit rights to nux? Whom do I talk to?
[15:30] <didrocks> I opened on purpose for serious things :)
[15:30] <didrocks> janimo: jay
[15:30] <janimo> ok thanks
[15:30] <bcurtiswx> seb128, workaround confirmed to fix my bug
[15:30] <seb128> bcurtiswx, ok
[15:31] <tedg> ronoc, Great, thanks!
[15:34] <jcastro> kamstrup: Do we have c# bindings for libunity?
[15:34] <jcastro> I don't think we do
[15:35] <ronoc> jcastro, no
[15:35] <ronoc> not that I'm aware of
[15:36] <ronoc> Python C and Vala
[15:36] <jcastro> waiting on python still
[15:36] <kenvandine> i think python might work with todays release
[15:36] <kenvandine> *think*
[15:36] <ronoc> jcastro, hmm I thought the release today creates the bindings automagically
[15:36] <kamstrup> jcastro: no, and I think they are unlikely to happen until mono starts supporting GI
[15:37] <kenvandine> i really miss those quicklists in tomboy
[15:37] <jcastro> ugh man, so we need GI in mono, so we can get bindings, so we can port tomboy
[15:37] <kamstrup> kenvandine, jcastro: Python should work on todays release - although there is some weird stuff going on with the pygi override paths, so there might be hickups
[15:38] <jcastro> kamstrup: nice
[15:38] <kamstrup> kenvandine: you can still do static quicklists for tomboy...
[15:38] <kenvandine> kamstrup, i need to look at the fix for that stuff, i am getting the same errors in libgwibber with GI
[15:38] <jcastro> does the launcher support any of the older non launcherAPI things? Like, can we use the older way of getting quicklists?
[15:38] <kenvandine> yeah, but the recent notes was the useful thing
[15:38] <kamstrup> kenvandine: the Makefile.am magic you did for Dee is the right way to do it
[15:39] <kenvandine> i'll add the static shortcuts now
[15:39] <kenvandine> yay
[15:39] <kamstrup> kenvandine: if I understood pitti and didrocks discussion correctly there is some packaging magic to convert the paths to something ubuntu expects
[15:39] <kenvandine> i need to create an overrides for libgwibber then
[15:39] <kenvandine> dh_python i think
[15:39] <kamstrup> sounds familiar :-)
[15:40] <kenvandine> i wish i could have gotten gwibber-service using Dee this cycle...
[15:40] <kenvandine> too late now :/
[15:40] <kenvandine> oh well, i'll start hacking on it soon so it is ready :)
[15:42]  * popey hugs kenvandine
[15:43] <kenvandine> thx popey
[15:43] <kenvandine> :)
[15:43] <ronoc> tedg, what version of libindicator should i pin against ? (can't remember from what you said last week_)
[15:44] <tedg> ronoc, 0.3.19 I believe.
[15:44] <ronoc> tedg, lovely
[15:44] <lamlex> MacSlow: can you verify this? https://bugs.launchpad.net/unity/+bug/721811
[15:47] <njpatel> apw, running trunk is super-dogfooding, so it's a valid question :) In anycase, the error I was speaking about only happened this week, and we havent' had a upload since last week, so your running into something else
[15:55] <apw> is it expected that OSD's have hard square edges now ?
[15:57] <kenvandine> sigh, the only static menus i can add for tomboy are new note and search... but now i found out that those command line switches aren't working
[15:58] <ronoc> kenvandine, tedg -> https://launchpad.net/indicator-sound/third/0.6.1
[15:58] <ronoc> with Lukes stuff
[15:58] <kenvandine> great
[15:58] <kenvandine> thx
[15:58] <ronoc> np
[15:58] <tedg> Thanks ronoc!
[15:59] <ronoc> no probs
[16:02] <and471> kvalo, hey
[16:08] <MacSlow> lamlex, yup... that's a bug
[16:08] <lamlex> thanks MacSlow
[16:08] <MacSlow> lamlex, I know to fix that you can assign me to that one
[16:08] <lamlex> ok, i will mark triaged and assign to yo
[16:23] <bdmurray> I was thinking the http://wiki.ubuntu.com/DebuggingCompiz page coudl use some love.
[16:49] <dbarth> kenvandine: hiya; ido is in for the release today?
[16:49] <dbarth> kenvandine: klattimer is needing it for things i-datetime
[16:49] <kenvandine> dbarth, if it is ready
[16:50] <kenvandine> i haven't heard
[16:50] <klattimer> kenvandine: it's merged
[16:50] <klattimer> https://code.launchpad.net/~karl-qdh/ido/ido.extra-passthrough-api/+merge/50938
[16:50] <kenvandine> ok, does bratsche still handle releasing that?
[16:51] <bratsche> I can release something if you need me to.
[16:51] <bratsche> But I should hand that off to someone else to start doing soon.
[16:56] <didrocks> apinheiro_afk: rodrigo_: think to target your bug against the current release once they are fix committed so that our script can automatically close them: https://bugs.edge.launchpad.net/unity/+bug/723699
[16:56] <didrocks> thanks :)
[16:56] <rodrigo_> didrocks, I can't set a milestone on bugs, it seems
[16:57] <didrocks> rodrigo_: just ping njpatel or I then :)
[16:57] <rodrigo_> ok, ping didrocks :)
[16:57] <didrocks> rodrigo_: heh, on which one (apart from this one ;))
[16:58] <rodrigo_> you also want the bug #s??? :)
[16:58] <rodrigo_> yes, hold on a second
[16:58] <apinheiro_afk> didrocks, ah sorry, I thought that I needed to close it by hand
[16:58] <didrocks> apinheiro_afk: basically, we have a script to create changelog now :)
[16:58] <apinheiro_afk> didrocks, ok
[16:59] <didrocks> apinheiro_afk: all you need is to target a "unity" master task against the right milestone
[16:59] <didrocks> apinheiro_afk: and once it's fix committed, it's automatically closed at next release
[16:59] <rodrigo_> didrocks, https://bugs.launchpad.net/unity/+bug/715297 , https://bugs.launchpad.net/unity/+bug/715299 and https://bugs.launchpad.net/unity/+bug/721322
[16:59] <didrocks> and included in the changelog
[16:59] <didrocks> rodrigo_: excellent, thanks!
[17:00] <didrocks> rodrigo_: all are fixed then?
[17:01] <apinheiro_afk> didrocks, so we still need to set the bugs as "fix commited", right?
[17:01] <rodrigo_> didrocks, no
[17:02] <rodrigo_> didrocks, waiting for review for 1 of them, and half done branches for the other 2
[17:02] <dbarth> bratsche: yes, can you do one release again please
[17:03] <didrocks> rodrigo_: oh, I didn't explain it clear enough then :)
[17:03] <didrocks> apinheiro_afk: rodrigo_: so basically, when you land a branch in trunk
[17:03] <didrocks> set it to fix committed
[17:03] <didrocks> ensure it's milestoned against next target
[17:03] <didrocks> (asking people to milestoned if not done)
[17:04] <didrocks> is it more clear? :)
[17:04] <rodrigo_> didrocks, yes! :)
[17:04] <apinheiro_afk> didrocks, ok thanks
[17:05] <didrocks> thanks a lot :-)
[17:27] <apinheiro> njpatel, now I have a problem with the panel service
[17:28] <apinheiro> both with the trunk and rodrigo_ branch
[17:28] <apinheiro> it starts, but then in execute on_name_lost
[17:28] <apinheiro> it is not a crash, it exit himself
[17:28] <apinheiro> any idea?
[17:29] <njpatel> apinheiro, another panel service is running?
[17:29] <rodrigo_> seems to be the same issue I had this morning
[17:29] <njpatel> apinheiro, I'm not sure, panel-main.c is pretty simple, I'd hve a look there
[17:29] <apinheiro> njpatel, ah yes
[17:29] <njpatel> :)
[17:29] <apinheiro> for any reason is there
[17:29] <apinheiro> I guess that I need to kill it by hand, right?
[17:29] <njpatel> yep
[17:29] <apinheiro> njpatel, ok thanks
[17:30] <bcurtiswx> how do i kill the ubuntu 1 sync daemon ?
[17:30] <njpatel> bcurtiswx, u1sdtool --quit
[17:30] <njpatel> bcurtiswx, and if notify-osd keeps pinging you, killall notify-osd to empty the queue
[17:31] <bcurtiswx> no, my CPU fan is on high because of it
[17:31] <dbarth> jcastro: hey jorge, i've spotted the windowmatching pb page on the wiki
[17:31] <dbarth> that's cool stuff
[17:31] <jcastro> yeah
[17:31] <dbarth> DBO: have you seen it: https://wiki.ubuntu.com/Unity/WindowMatching
[17:31] <DBO> yes
[17:31] <jcastro> totally community contributed. :p
[17:31]  * DBO waits for the next question
[17:31] <dbarth> it's good to have in mind for the next weeks when you return to bamf
[17:31] <dbarth> don't run, i was not going to ask
[17:32] <dbarth> yet
[17:32] <jcastro> DBO: ok so have you fixed all of that yet?
[17:32]  * jcastro runs
[17:32] <DBO> wait wait!
[17:32] <DBO> I get to return to bamf in a couple weeks
[17:32] <DBO> BAMF BABY IM COMING HOME
[17:32] <njpatel> no you don't
[17:32] <DBO> DAMNIT
[17:32] <njpatel> but you do need to fix the bug where kde apps can't be launchers
[17:33] <njpatel> at some point
[17:33] <njpatel> I mean, who uses kde right?
[17:33] <dbarth> yeah
[17:33] <DBO> hwhat?
[17:33] <dbarth> o/
[17:33] <DBO> what makes you think thats a bamf bug?
[17:33] <njpatel> its not
[17:33] <njpatel> its a launcher bug
[17:33] <njpatel> but bamf reminded me of it
[17:33] <DBO> oh, okay
[17:33] <DBO> all is forgiven
[17:34] <jcastro> https://code.launchpad.net/unity/+activereviews
[17:34] <jcastro> If someone can review Andrea's branches that would be swell
[17:36] <DBO> doing
[17:36] <DBO> now
[17:36] <dbarth> njpatel: is the multimonitor ready for trunk?
[17:37] <dbarth> branch
[17:37] <njpatel> mirco fixed it all up, just needs review
[17:37] <njpatel> we'll land it tomrorow
[17:37] <njpatel> tomorrow
[17:37] <dbarth> kewl
[17:39] <DBO> jcastro, done
[17:39] <jcastro> thank you sir
[17:40] <DBO> njpatel, whats going on with the clip thing we talked about
[17:40] <njpatel> which clip thing?
[17:40] <DBO> with multimonitor
[17:40] <njpatel> nothing yet, will ask jay/sam to fix that next week
[17:41] <DBO> so its not really ready :P
[17:43] <njpatel> oh, yeah :)
[17:43] <njpatel> i meant the branch
[17:43] <njpatel> there will be many muli monitor bugs to fix yet :)
[17:45] <dbarth> rodrigo_: is this branch still relevant btw? or can it be scratched?
[17:45] <dbarth> https://code.launchpad.net/~rodrigo-moya/unity/correct-gsettings-path/+merge/44479
[17:46] <rodrigo_> dbarth, no, njpatel rejected it, let me remove it
[17:47] <dbarth> rodrigo_: anything else i can do to help you get all of your branches merged in?
[17:48] <dbarth> there is a little bit more developer time available now that the thursday upload is in
[17:49] <rodrigo_> dbarth, apinheiro is reviewing them, as soon as he approves, I'll ping njpatel for a 2nd review, so I'm ok now
[17:49] <apinheiro> dbarth, yes you are right, this is not a branch valid anymore
[17:49] <apinheiro> I will remove it
[17:50] <apinheiro> I mean the "correct gsettings thing"
[17:50] <apinheiro> ups
[17:50] <apinheiro> sorry
[17:50] <apinheiro> I though you were talking about the correct gsetting name
[17:50] <apinheiro> "toolkit-accessibility" instead of "accessibility"
[17:50] <apinheiro> forget this comment
[17:53] <dbarth> nw
[17:53] <dbarth> so it seems that everything is lined up for tomorrow morning
[17:53] <dbarth> apinheiro: how is jay's new branch?
[17:53] <dbarth> apinheiro: did that help you get the rest of the launcher working
[17:53] <dbarth> ?
[17:54] <apinheiro> I didn't test it yet, as the coding part of the launcher can be done without it, and then I started with the review of rodrigo branches
[17:54] <apinheiro> right now I'm doing a system upgrade
[17:55] <apinheiro> required due the libindicator version dump
[17:55] <apinheiro> dbarth, but I will try it after that
[18:17] <kvalo> kenvandine: hi. I created a new release of indicator-network: https://launchpad.net/indicator-network/trunk/0.3.5
[18:19] <kenvandine> kvalo, thx
[18:29] <and471> kvalo, quick question (if you are here), at what point will we say goodbye to indicator-network-settings(1)
[18:31] <kvalo> and471: I think as soon as we have added connect/disconnect and edit buttons for all devices
[18:32] <kvalo> and471: and that will happen soon
[18:32] <and471> cool
[18:32] <and471> kvalo, see ya then
[18:34] <kvalo> and471: bye
[18:38] <elijah__> hello
[18:39] <elijah__> i need halp
[18:39] <elijah__> is U
[18:39] <elijah__> is unity creating their own file manager to replace nautiluS?
[18:40] <elijah__> hello?
[18:41] <elijah__> dajklfjskl\
[18:51] <kenvandine> dbarth_, klattimer, bratsche: ido release coming?
[18:54] <bratsche> kenvandine: Sure, I'll do it now
[18:55] <kenvandine> thx
[18:55] <kenvandine> tedg, and do you have the indicator-datetime changes in queue that require the new ido?
[18:56] <tedg> kenvandine, I don't think yet... I'd have to check, I think klattimer is still working on them.
[18:57]  * kenvandine notes today is feature freeze :)
[18:57] <kenvandine> klattimer, ^^
[18:58] <bratsche> Hmm, I'm getting errors in idocalendarmenuitem.c
[19:01] <tedg> bratsche, Hmm, I am as well... I swear I didn't yesterday...
[19:05] <bratsche> tedg: idocalendarmenuitem.h:63:12: error: old-style parameter declarations in prototyped function definition
[19:05] <bratsche> But it looks normal to me?
[19:05] <bratsche> Oh wait
[19:05] <bratsche> Missing a ;
[19:07] <bratsche> Fixed
[19:16]  * tedg is smoke testings the craziest dbusmenu release ever
[19:28] <bratsche> kenvandine, https://launchpad.net/ido/trunk/0.2.1
[19:28] <kenvandine> bratsche, thx
[19:28] <bratsche> kenvandine: Sorry it took awhile.. I had to come up with a good commit message for the last commit.
[19:28] <bratsche> These things are important. :)
[19:29] <kenvandine> :)
[19:37] <kenvandine> bratsche, there was one symbol removed in this release, was that intentional?
[19:37] <kenvandine> - ido_calendar_menu_item_get_calendar@Base 0.1.10
[19:37] <bratsche> tedg ^
[19:37] <tedg> kenvandine, Which one?
[19:38] <tedg> Is Unity totally fubar for anyone else?
[19:38] <kenvandine>  ido_calendar_menu_item_get_calendar@Base
[19:38] <kenvandine> nope
[19:39] <tedg> kenvandine, Yeah, we dropped that as we wrapped all the functions.  We could put it back if you're worried about the ABI.
[19:39] <tedg> Sorry, I didn't think about ABI at the time.
[19:39] <kenvandine> i would prefer
[19:40] <kenvandine> and i can cherry pick that to keep from needing a tarball and all
[19:46] <tedg> Ugh, is Empathy supposed to have an inactive "Room" menu on the contact list?
[19:46] <kenvandine> yes
[19:46] <kenvandine> oh
[19:46] <tedg> Oh, I figured it was a bug :)
[19:46] <kenvandine> no...
[19:46] <kenvandine> i think that is your bug :)
[19:46] <tedg> Uhg
[19:46] <kenvandine> it usually has inactive items under it if you don't have an account enabled that support group chat
[19:46] <kenvandine> tedg, sounds like the same bug chrisccoulson_ was talking about in firefox
[19:46] <kenvandine> tedg, what was the verdict for ido_calendar_menu_item_get_calendar@Base, putting it back?
[19:46] <chrisccoulson_> tedg - yeah, i've got lots of inactive items in the firefox menus since yesterdays dbusmenu update ;)
[19:46] <chrisccoulson_> the edit menu is a good example there
[19:48] <tedg> Uhg, today is just sucking.
[19:48] <chrisccoulson_> yes :)
[19:49] <chrisccoulson_> i'm totally stuck with bug 724202 and bug 720895 :(
[19:49] <chrisccoulson_> tedg - any ideas? :)
[19:53] <tedg> chrisccoulson_, I'd just make sure to get a current trunk.  There's so many fixes, I'm loosing track of all of them individually.
[20:09] <jcastro> hey kenvandine
[20:09] <jcastro> https://wiki.ubuntu.com/Unity/LauncherAPI
[20:09] <jcastro> got time to add a Python sample now that we have GI in libunity?
[20:09] <kenvandine> not today
[20:10] <kenvandine> tomorrow :)
[20:10] <jcastro> you have to use it for something anyway right?
[20:11] <jcastro> I was thinking between you and U1, whoever had to use it first could document it real quick so I can get the word out to upstream app authors
[20:23] <tedg> Uhg, it seems libindicate is killing empathy, not dbusmenu.
[20:23] <tedg> That makes it all better.
[20:24] <kenvandine> killing?
[20:27] <TheMuso> tedg: Whats the status of libappindicator blocking with KDE folks?
[21:10] <kenvandine> tedg, how's it looking? i am going to have to leave pretty soon
[21:10] <tedg> kenvandine, Releasing dbusmenu now.  Can't get anything to fail anymore :-/
[21:10] <kenvandine> at least for a bit, but i'll be back
[21:11] <tedg> kenvandine, Then I'll go through the others.
[21:11] <kenvandine> how about adding that symbol to ido? going to do that too?
[21:11]  * kenvandine never got a real yay or nah on that
[21:11] <tedg> kenvandine, Oh, I thought you were just going to distro patch it in.
[21:12] <kenvandine> yeah, i will
[21:12] <kenvandine> is it committed somewhere?
[21:12] <kenvandine> i was hoping to just cherry pick from trunk
[21:13] <tedg> Ah, okay.  I can do that.
[21:16] <kenvandine> tedg, would it help if i proposed a branch for that?
[21:16]  * kenvandine is all for helping :)
[21:16] <tedg> kenvandine, Sure, that'd be great.  Thanks!
[21:18] <kenvandine> i am having a terrible time accessing LP
[21:34] <kenvandine> didrocks! your back!
[21:34] <kenvandine> you should be sleeping :)
[21:34] <kenvandine> or drinking
[21:34] <didrocks> kenvandine: yeah, and yeah ;)
[21:34] <didrocks> kenvandine: all my week has been already long…
[21:37] <kenvandine> tedg, oh man... replaced all the /** with /*
[21:37] <tedg> kenvandine, In the defaults?  Yeah, only way I could get it out fo the gtk-docs :-/
[21:38] <kenvandine> oh, ok...
[21:38] <kenvandine> just the defaults, so all new stuff
[21:38] <kenvandine> i guess not really since i already had it... just makes reviewing a little harder :)
[22:43] <lamalex> can someone give this a tes? https://bugs.launchpad.net/unity/+bug/722242


[02:30] <RAOF> Hm. Network manager seems to have decided to abort.
[04:36] <cyphermox> RAOF: how?
[04:36] <cyphermox> RAOF: actually, please file a bug; I was on my way to bed :)
[04:38] <RAOF> cyphermox: Jan 29 14:24:37 RedTail NetworkManager[15605]: FATAL: Failed asserting path component: hfp/B876
[04:38] <RAOF> 3F78EB76_98D6F7BA3A76
[04:38] <RAOF> Jan 29 14:24:37 RedTail kernel: [ 1719.722823] traps: NetworkManager[15605] trap int3 ip:7f45df
[04:38] <RAOF> 909f90 sp:7fffff1bd290 error:0
[04:38] <RAOF> cyphermox: Sure. Launchpad it is :)
[04:39] <cyphermox> right, I just went to check and I see there is another such report, just no crash dump
[04:39] <cyphermox> ah
[04:39] <cyphermox> boo
[04:40] <cyphermox> do you need a phone to be connected via bluetooth to your system?
[04:40] <RAOF> No.
[04:40] <cyphermox> because I bet if there is one and you remove the pairing, it will work fine
[04:41] <RAOF> cyphermox: Correct!
[04:41] <cyphermox> woohoo!
[04:41] <cyphermox> sorry about that
[04:42] <RAOF> Heh, no problem.
[04:43] <cyphermox> there's an interaction between ofono and how it presents bluetooth devices that I hadn't expected, and clearly failed to test appropriately
[04:43] <RAOF> I should test my bluetooth headset again, too. :)
[04:43] <cyphermox> if ever you need to have your phone paired for a good reason between now and when I fix the bug; you may want to stop ofono
[04:44] <RAOF> Cool, thanks.
[04:44] <cyphermox> that should make things work, too... at the price of losing the modem thingies
[04:45] <RAOF> I've never managed to get the modem thingies to work, so that's no great loss :)
[04:50] <cyphermox> O.o
[05:21] <tmpRAOF> Internet sharing over bluetooth, is what I meant.
[06:52] <pitti> Good morning
[06:53] <pitti> larsu: sure, the "try out" has worked on utopic already :) https://wiki.ubuntu.com/SystemdForUpstartUsers#Switching_init_systems
[07:01] <pitti> larsu: ATM you need to be root to read the journal, that's probably your problem?
[07:01] <pitti> larsu: there's a bug about making the readable as adm; I plan to fix that by vivid
[07:23] <darkxst> pitti, larsu or systemd-journal group, but adm would be nicer
[07:23] <pitti> yeah, adm is meant for this; it's a bug
[07:50] <seb128> good morning desktopers
[07:51] <pitti> bonjour seb128 !
[07:51] <seb128> lut pitti, ça va ?
[07:51] <pitti> seb128: ça va bien ! et toi ?
[07:51] <seb128> thanks for the logind and cdrom eject fixes :-)
[07:51] <seb128> ça va bien aussi !
[07:52] <pitti> seb128: c'était mon plaîsir :)
[08:36] <willcooke> g'morn
[08:36]  * larsu dislikes english breakfast
[08:36] <larsu> good morning all
[08:37] <larsu> pitti: thanks!
[08:39] <larsu> desrt says hello. He seems tired.
[08:40] <pitti> hey larsu, guten Morgen
[08:40] <pitti> larsu: greetings to desrt!
[08:40] <larsu> :)
[08:42] <seb128> hey willcooke
[08:42] <seb128> larsu, but they have tea!
[08:44] <didrocks> larsu: tomorrow, you will have belgian breakfast!
[08:45] <willcooke> what's that? Coffee and a cigarette?
[08:46] <willcooke> wakka wakka wakka - I'm here all week
[08:46] <didrocks> (oh no!)
[08:46]  * didrocks should use a plausible excuse
[08:47] <didrocks> "oh, there is a strike on trains"
[08:47] <willcooke> Does the dash support any kind of themeing?  Can the colour scheme be changed?
[08:48] <willcooke> Specifically, a new High Contrast option
[08:48] <didrocks> willcooke: the colour adapts from your wallpaper
[08:48] <didrocks> (as for the launcher)
[08:48] <didrocks> basically, it's the dominant color of it
[08:48] <willcooke> but could I force it to be, say, white text on a black background?
[08:49] <didrocks> I remember there were some discussion to set that in the theme
[08:49] <didrocks> I'm unsure it's supported though
[08:49] <willcooke> Yeah, I think it's not
[08:49] <didrocks> wouldn't be hard if needed though
[08:49] <didrocks> (remember also that we limit by design the number of theme you can choose by UI)
[08:55] <seb128> didrocks, I think it's about a11y rather than look
[08:55] <seb128> the question is, I mean
[08:59] <willcooke> thanks seb128
[08:59] <willcooke> I've said that in theory it can be done, but that we'd need to spend time working on it
[08:59] <willcooke> good enough for now
[08:59] <seb128> i guess so
[09:01] <willcooke> Is it me or does Chromium feel like it's getting bulkier and slower?
[09:03] <Laney> yo
[09:09] <seb128> hey Laney, wie gehts?
[09:09] <seb128> willcooke, since when/compared to what?
[09:10] <willcooke> seb128, nothing so specific.  Since a few months, maybe 4 or 5, and compared to what I think I remember it performing like.
[09:10] <willcooke> :)
[09:10] <seb128> k
[09:10] <seb128> I can't tell because mine keeps hitting segfault in the dri code for months
[09:10] <seb128> waiting for the next update which is supposed to resolve that
[09:11] <seb128> I've mostly stopped using it meanwhile though
[09:17] <willcooke> I should try ffox again
[09:18] <Laney> hey seb128, doing good!
[09:18] <Laney> you?
[09:18] <seb128> good as well, thanks!
[09:19] <Laney> supposed to snow today
[09:19] <Laney> exciting
[09:19] <Laney> bet it breaks the train tomorrow though /o\
[09:19] <Laney> larsu: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=768269
[09:29] <Laney> totally didn't notice this: http://www.bbc.co.uk/news/uk-31032930
[09:38] <marga> Yeah, at that magnitude, it would be weird to notice it
[09:38] <marga> At least, from where I'm from, cars starting on an avenue when the light turns green generate more vibrations
[09:44] <willcooke> seb128, there's a setting to change the transparency of the launcher - can I do the same in the dash itself?
[09:44] <seb128> willcooke, you can turn the bluring off, dunno about other changes
[09:45] <willcooke> I've reached the same conclusion, thanks seb128
[09:45] <seb128> yw
[09:45] <seb128> willcooke, https://bugs.launchpad.net/ubuntu/+source/ubuntu-system-settings/+bug/1415509 ... do you know of a device to buy that does bluetooth ssp pairing?
[09:47] <seb128> willcooke, I've commented on bug asking that as well
[09:47] <willcooke> thx seb128
[09:47] <willcooke> It feels like something that would be trivial to implement
[09:47] <willcooke> so I'll ask bregma what he thinks too
[09:48] <mlankhorst> morning
[09:48] <willcooke> OT:  When I push to bzr is the a reason for it to just sit there doing seemingly nothing?
[09:48] <willcooke> morning mlankhorst
[09:49] <seb128> willcooke, no, it can be slow but should indicate progress
[09:49] <willcooke> hrm
[09:50] <willcooke> I must be doing something wrong theb
[09:50] <willcooke> then
[09:50] <seb128> what did you do exactly and what is outputed?
[09:51] <willcooke> I downloaded this project with bzr
[09:51] <willcooke> https://code.launchpad.net/pushbullet-indicator
[09:51] <willcooke> fixed a few things
[09:51] <willcooke> and now I want to push it back up with this
[09:51] <willcooke> bzr push lp:~willcooke/pushbullet-indicator/pushbullet-indicator
[09:51] <willcooke> but nothing happens
[09:51] <willcooke> it just sits there doing nothing
[09:54] <willcooke> errr
[09:54] <willcooke> ok
[09:54] <willcooke> ignore
[09:54] <willcooke> now it just works
[09:54] <willcooke> And now I've got to clean up all this chicken blood
[09:55] <willcooke> If the sacrifices are working, I say keep doin' them
[10:03] <larsu> Laney: thanks! Good morning!
[10:03] <larsu> didrocks: yes \o/
[10:42] <larsu> Laney: have you tried gnome-builder? hergertme just told me that there's a ppa for it now
[10:42] <larsu> could be something for universe next cylce, no?
[10:43] <Laney> have not, but yes sure
[10:43] <Laney> I imagine we'd get that via Debian
[10:43] <larsu> makes sense
[10:43] <Laney> who did the PPA?
[10:43] <Laney> could help them upload it there
[10:44] <Laney> willcooke: seen http://www.theguardian.com/business/2015/jan/28/british-airways-airmiles-avios-changes ?
[10:46] <larsu> Laney: this is it https://launchpad.net/~inizan-yannick/+archive/ubuntu/dev
[10:46] <larsu> depends on new gnome crack, of course
[10:47] <Laney> seems so
[10:47] <Laney> should be ok next cycle though
[10:47] <willcooke> Laney, https://twitter.com/8none1/status/560432919412736000
[10:48] <Laney> this guy has his finger on the pulse
[10:48] <willcooke> Sticking it to the man
[10:51] <tkamppeter> Hi, after working mainly on SRUs for Utopic and Trusty in the last weeks I have started Vivid in a virtual machine today. It is called "Next" and has a phone-like GUI. Is this the standard now?
[10:52] <Laney> I think you downloaded the wrong image
[10:54] <Laney> or at least I really hope so ...
[10:54] <tkamppeter> Laney, I downloaded vivid-desktop-amd64.iso on http://cdimage.ubuntu.com/ubuntu-desktop-next/daily-live/current/. There is no http://cdimage.ubuntu.com/ubuntu-desktop/daily-live/current/
[10:54] <Laney> get rid of /ubuntu-desktop/, it's just /daily-live/
[10:55] <tkamppeter> Laney, where do I find the correct one?
[10:57] <tkamppeter> Laney, when I picked the download page with Google I have overlooked the "next" in the URL and the ISO file name has no "next", is identical to the normal name, should have the "next" to warn the user.
[11:01] <tkamppeter> Laney, searching "ubuntu vivid iso" on Google finds all flavors including Next but NOT the standard desktop.
[11:12] <Laney> tkamppeter: I made a symlink to maybe do a little bit of SEO for that particular problem.
[11:23] <tkamppeter> Laney, thanks.
[11:50] <Sweet5hark> seb128: sooo, arm64/ppc64el will be more work. While LibreOffice itself has a trivially portable buildsystem, there are the dependencies that we ship internal copies of (e.g. coinmp, libetonyek etc.) and those use ...
[11:51] <Sweet5hark> ... fscking autotools, which is too braindead to simply build on a new arch.
[11:53] <Sweet5hark> Laney: remember when I joined in violently stabbing autotools a few days ago without a concrete reason on my own, in the firm belief I will soon have one?
[11:53] <Sweet5hark> didnt take long.
[11:58] <Sweet5hark> https://launchpadlibrarian.net/196087597/buildlog_ubuntu-vivid-powerpc.libreoffice_1%3A4.4.0~rc2-0ubuntu3_FAILEDTOBUILD.txt.gz <- something broken in -proposed wrt libsuitesparse-dev?
[12:06] <willcooke> seb128, aaeeiiii - BT keyboards are expensive!
[12:08] <willcooke> oh, good ol' ebay
[12:08] <willcooke> Seems the proper branded ones are expensive.  No-name imports are a bit more realistic
[12:21]  * didrocks goes to catch his train
[12:21] <didrocks> will see how the 3G is stable there, ttyl!
[12:21] <willcooke> o/
[12:21] <didrocks> but I have some offline work with me :)
[12:46] <seb128> Sweet5hark, yeah, something seems wrong in proposed installability for those
[13:04] <didrocks> sucks, no plug in that train :/
[13:07] <seb128> didrocks, how long is the train?
[13:07] <larsu> didrocks: enjoy your trip!
[13:07] <seb128> the trip I mean
[13:12] <pitti> didrocks1: who needs plugs these days :)
[13:12] <didrocks1> seb128: 3h30-3h40
[13:12] <didrocks1> thanks larsu
[13:12] <didrocks1> I should have enough battery
[13:12] <didrocks1> (was disconnected, not sure you received my messages)
[13:12] <didrocks1> ahah :)
[13:12] <pitti> didrocks: we didn't
[13:13] <Laney> didrocks: do you have to change somewhere?
[13:13] <didrocks> Laney: no, direct to Brussells (stopping at Paris and Lille)
[13:13] <Laney> convenient!
[13:14] <didrocks> "lyon" ;)
[13:14]  * Laney roars
[13:14] <pitti> wow, 3:30, c'est très rapid !
[13:14] <didrocks> pitti: TGV for the win :)
[13:15] <pitti> didrocks: heh, nomen est omen
[13:15] <didrocks> pitti: well, there is one issue with TGV… This is 3G
[13:15]  * didrocks gets longer and longer lags
[13:16] <didrocks> will probably work offline for a bit, need to save phone battery as well
[13:17]  * didrocks has a huge systemd rebase to do anyway…
[13:28] <soren> Which process is responsible for capturing things like Ctrl-Alt-T to spawn a terminal? Every now and again, it'll stop working (until I reboot) and I'd like to see if I could fix it.
[13:29] <soren> (In Trusty, fwiw)
[13:32] <qengho> willcooke: are you getting bulkier and slower?
[13:37] <willcooke> qengho, pure coincidence
[13:37] <willcooke> I think it's the JS in G+ which is the cause
[13:47] <willcooke> I think this is going to run over ~ 10 mins
[13:47] <willcooke> Sweet5hark, that was to you ^
[14:01] <qengho> seb128: care to try the chromium at  ppa:canonical-chromium-builds/stage ?
[14:02] <Sweet5hark> willcooke: huh?
[14:06] <seb128> qengho, surely can do
[14:27] <tsdgeos> seb128: tedg says you'd be the one to get https://bugs.launchpad.net/ubuntu/+source/zeitgeist/+bug/1415374 patched up in the distro, that right?
[14:27] <seb128> tsdgeos, you are on the right channel at least :-)
[14:28] <seb128> I didn't touch zg much but others here did
[14:28] <seb128> (though didrocks is currently away in a train)
[14:28] <seb128> tsdgeos, thanks for pointing it out
[14:28]  * tedg starts singing "didrocks will be coming round the mountain"
[14:28] <tsdgeos> ok
[14:29] <tsdgeos> seb128: i'm here if you need me
[14:29] <seb128> Laney, ^ maybe want to help on that? ;-)
[14:29] <tsdgeos> otherwise we can do it on monday
[14:29] <seb128> tsdgeos, thanks
[14:29] <tedg> seb128, They'd also like to fix that for rtm branches.
[14:29] <tsdgeos> or we can talk at fosdem if you're there
[14:29] <seb128> I can try to have a look, but not likely today
[14:29] <seb128> didrocks and Laney are at fosdem, I'm coming but only during the w.E
[14:29] <seb128> but sure grab any of us there :-)
[14:30] <willcooke> SNOW!
[14:30] <willcooke> and lightning
[14:30] <tsdgeos> i'm only on the WE too
[14:30] <tedg> willcooke, Forget the dandruff shampoo again, did we?
[14:30] <seb128> willcooke, does it mean you are never being able to leave .uk?
[14:31] <tsdgeos> willcooke: forecast said snow, but now doesn't
[14:31] <tsdgeos> or at least the one i read
[14:31] <seb128> willcooke, like when it starts snowing they ground planes and stop trains, right? ;-)
[14:32] <willcooke> they do in the UK
[14:37] <tkamppeter> willcooke, snow? SUN! (but lightning we have in the afternoon).
[14:39] <seb128> Trevinho, should setting com.canonical.Unity.Interface text-scale-factor should make unity change the corresponding gtk setting?
[14:40] <Trevinho> seb128: yes
[14:40] <seb128> Trevinho, it's not working in vivid :-/
[14:40] <Trevinho> seb128: as if the scaling != 1.0 is not matching
[14:40] <Trevinho> mhmh
[14:41] <seb128> Trevinho, if I set it to 1.25 (which unity-control-center -> a11y -> big text does) nothing changes
[14:42] <Trevinho> mh, and same for the related gsetting value I guess... mhmh
[14:42] <Trevinho> weird, the code is quite simple..
[14:42] <Trevinho> although there was a timeout to avoid troubles, but it shouldn't be affected by this case
[14:47] <seb128> Trevinho, can you confirm the issue?
[14:48] <seb128> mitya57, yeah, do you know if somebody is looking at updating qtsystems?
[14:48] <seb128> our snapshot is quite outdated
[14:50] <Trevinho> seb128: i'm not in vivid currently
[14:50] <Trevinho> I'll check soon
[14:50] <seb128> Trevinho, utopic probably has the same issue ... what do you use?
[14:51] <Trevinho> I'm now on trusty
[14:52] <seb128> oh ok, does it work there?
[14:55] <kenvandine> mitya57, we've found that the current qtsystems snapshot we have doesn't work with upower 0.99
[14:55] <kenvandine> mitya57, it'd be nice to get that updated, but not sure what it might break
[14:56] <kenvandine> according to the rdepends, only ubuntu-system-settings... which is where we're feeling the upower pain
[14:56] <kenvandine> so if the API breaks, but fixes the upower issue... we could update settings accordingly
[14:56] <seb128> kenvandine, not at lot probably, seeing the rdepends
[14:57] <seb128> kenvandine, basically the bindings are used by settings, the lib is used by ubuntu-download-manager and cordova as well, but should be easy to check those
[15:00] <Laney> tsdgeos: ok, ta, I'll try to handle that soon
[15:01] <Laney> ricotz: you have commit to zeitgeist?
[15:02] <Laney> want to review and commit https://bugs.freedesktop.org/show_bug.cgi?id=88846 ?
[15:13] <tsdgeos> ah, rainCT is at google now, i remember back when he was too young to drink beer, man i'm old
[15:15] <ricotz> Laney, yes I have
[15:16] <mitya57> seb128, kenvandine: I never touched qtsystems (only Timo did), but I can update it
[15:17] <mitya57> kenvandine: I can build a new snapshot and check if u-s-s still builds against it
[15:17] <kenvandine> mitya57, please do :)
[15:17] <kenvandine> mitya57, and if you can point me at a test build, i can do some testing
[15:17] <kenvandine> mitya57, i think i might need to make some changes in u-s-s to support it
[15:18] <Laney> check runtime, the QML parts won't fail the build
[15:18] <kenvandine> yeah
[15:20] <mitya57> Then I will let kenvandine do it :)
[15:20] <Laney> wimp :p
[15:21] <ricotz> Laney, is the reporter on irc?
[15:21] <kenvandine> mitya57, i'm happy to :)
[15:22] <Laney> ricotz: it's tsdgeos
[15:22]  * tsdgeos waves
[15:24] <ricotz> tsdgeos, looks interesting and valid -- why don't you attach a proper patch? ;)
[15:24] <tsdgeos> ricotz: the definition of proper patch varies from house to house
[15:25] <tsdgeos> that's my reason
[15:25] <ricotz> tsdgeos, meaning it is maintained in git, so "git format-patch -1" would do
[15:26] <tsdgeos> ricotz: i can do that if that's what you want
[15:26] <ricotz> tsdgeos, please do
[15:30] <tsdgeos> ricotz: there
[15:33] <seb128> mitya57, I'm happy to test the updated package as well, if you work on the updat
[15:33] <seb128> mitya57, thanks
[15:34] <ricotz> tsdgeos, thanks pushed
[15:35] <tsdgeos> ricotz: tx
[15:35] <mitya57> kenvandine, seb128: does u-s-s use QStorageInfo (or its qml variant)?
[15:36] <seb128> mitya57, yes
[15:36] <seb128> mitya57, it uses it to list the logical drives and get their used/free space info
[15:37] <mitya57> then it needs either qt5.4 or older qtsystems :(
[15:37] <mitya57> Because it was moved from qtsystems into qtbase during 5.4 cycle
[15:37] <seb128> well, the update qtsystems would be part of the qt5.4 transition
[15:37] <seb128> updated
[15:37] <seb128> so that's fine
[15:38] <seb128> or if you don't want to mix those, we can land qt5.4, then migrate settings, then land qtsystems
[15:38] <mitya57> No, I just thought that qtsystems update is more urgent for you
[15:38] <mitya57> I can put it into qt5.4 ppa
[15:39] <seb128> well, it would have been nice if it was not coupled to qt5.4
[15:39] <seb128> but kenvandine thought it wouldn't be that easy
[15:39] <seb128> so it's the way it is :/
[15:40] <seb128> the reason we are looking at it is because the new upower makes the qtsystems battery bindings buggy
[15:40] <seb128> which is probably fixed in newer versions
[15:40] <kenvandine> yeah... i'll take what i can get :)
[15:40] <mitya57> In theory I could try to use a snapshot from autumn (and it would probably build against 5.3), but using the latest snapshot and 5.4 is easier for me
[15:41] <kenvandine> 5.4 should be fine
[15:41] <seb128> kenvandine, a snapshot from autumn could be nice for rtm though?
[15:41] <seb128> if that fixes the upower issues
[15:41] <kenvandine> sure
[15:41] <seb128> so not sure, maybe updating vivid now to a pre-qt5.4 version would be useful
[15:42] <seb128> to update to current then with qt5.4
[15:42] <kenvandine> isn't 5.4 happening real soon?
[15:42] <seb128> mitya57, not sure if you feel like doing that, if not just focus on 5.4 and we can look at the older snapshot on our side if we need it
[15:42] <seb128> kenvandine, you know how those things go... :-)
[15:42] <kenvandine> true :)
[15:42] <mitya57> let me try 5.4 first, starting a test build
[15:43] <seb128> thanks
[15:43] <kenvandine> thanks
[15:43] <seb128> willcooke, btw when you said expensive/less so for the keyboard, what price range was that about?
[15:43] <kenvandine> if we see that it really fixes it... it might be worth trying trying a slightly older snapshot against 5.3 to see
[15:46] <seb128> yeah
[15:47] <willcooke> hrm - I crashed unity playing the Compiz settings
[15:47] <willcooke> seb128, expensive was around 70 GBP
[15:47] <willcooke> seb128, cheap on ebay < 10
[15:50] <seb128> willcooke, k, the "Wedge Mobile Keyboard" from microsoft can be found for around 60EUR, not as expensive as 70GBP but still expensive
[15:51] <willcooke> yeah!
[15:51] <willcooke> I'm trying to find more info on the cheap ones, but it's hard to come by
[15:53] <mitya57> Hmm, the examples are not installing for some reason
[16:04] <mitya57> seb128, kenvandine: built in ppa:mitya57/test2
[16:04] <seb128> mitya57, thanks
[16:04] <kenvandine> mitya57, thanks!
[16:04] <kenvandine> i'll take it for a drive
[16:05] <mitya57> you'll also need qt5.4 from ppa:ci-train-ppa-service/landing-005 probably
[16:25] <seb128> willcooke, http://www.amazon.co.uk/HP-K4000-Bluetooth-Keyboard-Mac/dp/B00M0F7TJI/ref=sr_1_2 seems to be ssp compliant (it's listed on https://launchpad.net/~timchen119/+archive/ubuntu/bluez4-ssp)
[16:27] <willcooke> nice find seb128
[16:47] <seb128> qengho, great, that chromium update seems to work fine, at least I can use use google map again without getting a sad face page :-)
[16:47] <seb128> no error on start either
[16:47] <willcooke> \o9/
[16:47] <willcooke> \o/
[16:47] <qengho> seb128: excellent! Thank you.
[16:49] <seb128> qengho, thanks for the update, looking forward seing that landing, chromium feel smooth again :-)
[16:54] <chrisccoulson> qengho, do you know why chromium doesn't turn on the scroll animator (smooth scrolling) by default?
[16:55] <qengho> chrisccoulson: er, no.
[16:55] <chrisccoulson> qengho, I turn it on in oxide, and it works great
[16:56] <qengho> chrisccoulson: It probably doesn't work on something obscure.
[16:56] <qengho> A guess.
[16:57] <qengho> chrome://flags/#enable-smooth-scrolling
[17:03] <willcooke> Toys!
[17:03] <willcooke> Ooh, smooth scrolling is nic
[17:03] <willcooke> e
[17:05] <tjaalton> is totem still on 3.10 because of the same issues that other parts of gnome hasn't been updated?
[17:07] <Laney> https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1393067
[17:08] <tjaalton> ah, thanks
[17:08] <Laney> Will try to look at the work to see what it's like and what needs doing still, maybe next week while some of us are together
[17:10] <tjaalton> current totem craps out completely if gstreamer-vaapi is installed, so wanted to know if a newer version might work
[17:10] <tjaalton> filed this as bug 1416005
[17:10] <Laney> try the PPA that darkxst mentions there
[17:10] <tjaalton> yep
[17:12] <Laney> otherwise check with hadess, I know a few releases back it was known to not work
[17:14] <tjaalton> yeah, it didn't even try vaapi, now that part is fixed
[17:18] <Laney> tjaalton: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=762579
[17:19] <tjaalton> nice
[17:21] <tjaalton> looks like clutter-gst is at 3.0.3 now
[17:29]  * didrocks back
[17:32] <Laney> hey didrocks
[17:32] <Laney> make it ok?
[17:32] <didrocks> Laney: yeah, everything was on schedule :)
[17:32] <didrocks> I have 2 small beds in my room though
[17:32]  * didrocks quite sad to not be able to spread
[17:33] <didrocks> ok, time to send systemd's ML patches!
[17:35] <pitti> oh, hey didrocks
[17:35] <didrocks> hey pitti :)
[17:38] <Laney> didrocks: go ask if they have a different one
[17:38] <didrocks> Laney: well, not a biggie TBH :)
[17:39]  * Laney will remember to check at check in now, thanks for the tip ;-)
[17:39] <didrocks> heh, no worry! :)
[17:43] <pitti> didrocks: I think the complaint about "current->fd = 0;" was that 0 is a valid fd, so it's not an adequate initializer for "nothing connected yet"
[17:47] <didrocks> pitti: yeah, that's what I did change, I wasn't sure if he wanted another initiliazation
[17:55] <didrocks> Laney: wifi is excellent though in my room
[17:56] <didrocks> maybe I shouldn't change for this :)
[17:56] <Laney> hehe
[17:56] <Laney> lucky you ;-)
[17:56] <didrocks> ok, need to do some cycling as I can't run
[17:56] <Laney> I'm off now to buy a new coat which can stand up to the weather in .be
[17:56] <didrocks> let's see what the gym is looking like
[17:56] <didrocks> Laney: yeah, you need that :)
[17:56] <didrocks> see you Laney!
[17:57] <Laney> might not be around much tomorrow morning, will see
[18:03] <seb128> I've a feeling that channel is going to be quiet tomorrow
[18:04] <pitti> seb128: come join us :)
[18:04] <seb128> pitti, :-)
[18:07] <willcooke> When didrocks says "checking out the gym" he really means "bar" right?
[18:08] <pitti> willcooke: that's just the Belgish word, you know
[18:08] <willcooke> seb128 that keyboard mzanetti linked to looks sweet!
[18:08] <willcooke> pitti, LOL!
[18:09] <seb128> lol
[18:09] <seb128> willcooke, oh, nice indeed
[18:09] <willcooke> expensive, but nice
[18:20]  * willcooke -> EOD
[18:24] <kenvandine> mitya57, your qtsystems update didn't fix the upower issue :/
[20:21] <andyrock> seb128, i'm looking into the text-scaling-factor issue
[20:21] <andyrock> seems like we are not getting the gsignal "changed::text-scaling-factor"
[20:22] <andyrock> still not sure why
[20:22] <andyrock> something is blocking it
[20:22] <andyrock> do you have any idea what it could be?
[21:38] <andyrock> seb128, found it! I'm going to complete the fix tomorrow
[21:41] <seb128> andyrock, sorry, I was out when you pinged, great that you found it, thanks
[21:42] <andyrock> basically in Unity we read the value of a gsettings and then we connect to the signal
[21:42] <andyrock> used to work before
[21:42] <seb128> right, I was going to say
[21:42] <seb128> it's one of the glib changes from previous cycle
[21:43] <andyrock> seb128, we need to update that all over unity
[21:43] <seb128> sorry about that
[21:43] <seb128> andyrock, shouldn't be too difficult to fix it though, right?
[21:45] <seb128> andyrock, there is a bug open if that's useful for you for tracking
[21:46] <seb128> oh, I see that you found it
[21:47] <andyrock> yeah we just need to invert the order of few lines
[21:49] <seb128> andyrock, great, thanks for working on it