[08:16]  * didrocks just back from Boston
[08:20] <didrocks> sil2100: Mirv: hey, how is it going?
[08:21] <sil2100> didrocks: morning!
[08:22] <sil2100> didrocks: rather fine... but I'm not sure what's the status of daily-release right now
[08:22] <didrocks> Mirv: sil2100: can we sync up in a hangout in a few?
[08:23] <didrocks> so that I can give you the status, story and so on…
[08:23] <didrocks> just expect to see a really tired didrocks ;)
[08:23] <sil2100> didrocks: ok, fine with me in ~20-30 min, let's wait for Mirv ;)
[08:23] <didrocks> sure, good plan ;)
[08:23] <sil2100> didrocks: how was the flight? When did you return back home?
[08:24] <jibel> Good morning didrocks! you arrived home safely ?
[08:24] <jibel> Hi sil2100
[08:24] <didrocks> sil2100: I returned back home 10 minutes ago
[08:24] <didrocks> jibel: yeah, uneventful! how was yours?
[08:24] <didrocks> sil2100: so, it's technically still Sunday for me :p
[08:25] <sil2100> :O
[08:25] <sil2100> 10 minutes ago?!
[08:25] <jibel> didrocks, good flight, arrived 20min earlier than schedule, so exceptional. but then we had to wait for a free parking stand :)
[08:26] <didrocks> sil2100: yeah, I left Sunday evening
[08:26] <didrocks> jibel: ahah, really worthed arriving in advance :p
[08:26] <sil2100> jibel: morning!
[08:26] <jibel> didrocks, how was your WE in Boston?
[08:26] <sil2100> didrocks: damn! You should have a day off now and sleep!
[08:27] <sil2100> Mirv: piiing! ^
[08:27] <didrocks> sil2100: well, I have to sync up with you first ;)
[08:27] <didrocks> jibel: excellent! Boston is a really beautiful city, I wasn't expecting that
[08:27] <didrocks> also, I saw mterry on Sunday
[08:28] <didrocks> hum, I'll need to sync up with dbarth as well
[08:29] <sil2100> :<
[08:29] <didrocks> dbarth: around for a hangout?
[08:29] <didrocks> need to talk about webapps
[08:32] <jibel> didrocks, Good you enjoyed Boston. Now GO TO BED!
[08:32] <didrocks> well, I need people around first ;)
[08:33] <didrocks> and going to bed at that time is ensuring it will be a fail tonight
[08:33] <didrocks> jibel: btw, we had fun with a lxc failure on Friday evening
[08:33] <didrocks> (what a week)
[08:33] <didrocks> but stgraber got a fix
[08:33] <sil2100> Again?
[08:34] <dbarth> didrocks: yup
[08:34] <didrocks> sil2100: yeah, because of a wrong upgrade
[08:34] <didrocks> (well, latest lxc broke)
[08:34] <didrocks> but latest latest fixes it now ;)
[08:34] <jibel> didrocks, yep I saw that last week on my machine, something with mountall IIRC
[08:34] <didrocks> right
[08:34] <didrocks> all fixed normally now
[08:35] <jibel> It is fixed, I verified this morning
[08:38] <Mirv> sil2100: pong pong :)
[08:38] <Mirv> didrocks: just fine, eager to get daily releases back online :)
[08:39] <sil2100> didrocks: we have contact with Mirv ! Hangout guys?
[08:40] <Mirv> fine by me, at least as soon as I find a headset
[08:40] <didrocks> sil2100: Mirv: I'm talking with dbarth right now, will ping you later
[08:40] <sil2100> ah, ACK
[08:40] <Mirv> ok. kind a Sunday you have.
[08:40] <sil2100> ;)
[09:14] <sil2100> didrocks: then in the meantime I go grab late breakfast
[09:14] <didrocks> sil2100: sure sure
[09:15]  * Mirv -> lunch
[09:41] <ricotz> didrocks, hi :)
[09:41] <didrocks> hey ricotz
[09:42] <ricotz> didrocks, the gnome-session update in saucy might have been a bit rushed
[09:42] <ricotz> it seems better to keep using 3.8.x if there are no problems resolved by 3.9.90
[09:42] <sil2100> ;)
[09:43] <sil2100> didrocks: when can we connect btw.? I want you resting already ;p!
[09:43] <didrocks> ricotz: who uploaded it? Sorry, I'm just back from Boston and totally jetlag/out of the loop
[09:43] <ricotz> didrocks, while gnome-session 3.9.91 requires a new gnome-desktop3 which kind of requires a running mutter/gdm
[09:44] <ricotz> didrocks, ah i see, i think jbicha did
[09:44] <didrocks> ricotz: can you sync up with him to revert it?
[09:44] <ricotz> didrocks, i decided to ping you while seb isnt here ;)
[09:44] <ricotz> will do, see it as note for now then
[09:45] <didrocks> ricotz: yeah, I'm in a middle of 100 things right now, so I think jbicha will be available before me ;)
[09:45] <ricotz> didrocks, don't worry then, thx
[09:45] <didrocks> ricotz: just reping me tomorrow when I'm fresh and not in a crazy timezone mindset ;)
[09:45] <ricotz> heh ;)
[09:46] <tkamppeter> I have applied a bug fix to Cairo, can someone upload it for me? Bug 968785.
[09:46] <ubot2`> Launchpad bug 968785 in ghostscript (Ubuntu) "ghostscript runs for indefinitely long period of time when called by foomatic-rip" [High,Incomplete] https://launchpad.net/bugs/968785
[11:05] <sil2100> didrocks: ping! Hangout
[11:06] <sil2100> asac: ^
[11:07] <asac> sil2100: ok
[11:07] <asac> one sec
[11:07] <didrocks> coming
[11:34] <didrocks> sil2100: I rerun the sdk stack
[11:35] <sil2100> didrocks: ACK, I'm looking on unity8 now
[11:35] <sil2100> didrocks: you SLEEP!
[11:36] <didrocks> sil2100: was I looking that bad? :p
[11:36] <sil2100> No ;) But when I think about it that you got back from Boston just today in the morning, I feel tired myself!
[11:37] <didrocks> ahah, sorry to make you feel tired ;)
[11:37] <didrocks> ok, maybe the fact that I'm working laying on carpet is not a good sign
[11:37] <didrocks> but I feel good that way
[11:43] <lool> qengho: heyo, asac has other issues than the chrome disappearing with latest chromium-browser; notably with google docs; is this something reported / that you know of already?
[11:44] <sil2100> Wohoo, daily-build is so CLEAN
[11:45] <didrocks> cleanly empty! ;)
[11:47] <sil2100> didrocks: spinning off unity8!
[11:47] <didrocks> \o/
[12:15] <pitti> Good morning
[12:24] <didrocks> hey pitti!
[12:24] <didrocks> enjoying your trip apparently? ;)
[12:24] <pitti> didrocks: bonjour Didier, ça va ? survived the flight?
[12:25] <didrocks> pitti: apparently yeah. Still surviving the jetlag though (arrived at home 4 hours ago now and still awake \o/)
[12:25] <pitti> erk
[12:25] <didrocks> didn't succeed to sleep during the flight, so still Sunday for me :p
[12:25] <didrocks> pitti: how was yours? uneventful?
[12:25] <pitti> didrocks: both of the planes were an hour late, so in the end the tight connection worked out
[12:26] <pitti> broken panel in the first, broken battery in the second
[12:26] <pitti> like, even Friday 13 itself was delayed by a day :)
[12:26] <didrocks> ahah, happy that you got there in a piece then!
[12:27] <didrocks> no broken pitti :p
[12:27] <pitti> yeah, indeed; I'm just beginning to get the usual cold, though
[12:27] <pitti> there is NO escape!
[12:28] <didrocks> ah, finally, an ubuflu! I was afraid nobody would get one :)
[12:28]  * didrocks hugs pitti
[12:28] <didrocks> (with care to not grab the cold)
[12:29] <pitti> hah
[12:30] <didrocks> pitti: you should have stayed a little bit more to Boston
[12:30] <didrocks> I was alone, but it was lovely
[12:37]  * desrt yawns
[13:33] <didrocks> thanks Mirv!
[14:28] <tkamppeter> xnox, hi
[14:29] <xnox> tkamppeter: heya!
[14:29] <tkamppeter> xnox, I Have a problem with PackageKit when adding package sources, it does not install the GPG key, see
[14:29] <tkamppeter> http://paste.ubuntu.com/6101343/
[14:30] <tkamppeter> xnox, it seems to be caused by some change in PackageKit, as system-config-printer did not change and current Saucy package works perfectly on Raring.
[14:34] <xnox> tkamppeter: it cloud be a dbus/glib change wince it is expecting a UINT64 or UINT32 bit value but that's not what it is getting. Maybe the signature should be prefixed with 0x ?
[14:35] <xnox> tkamppeter: I don't think it's my domain =/ try debugging it with pdb to see what values it's receiving and why install-printerdriver.py:35 is reporting warnings.
[14:39] <tkamppeter> xnox, I have done the same thing with pure Python now, without system-config-printer, once with the unchanged key and once with the key with 0x preceded. See http://paste.ubuntu.com/6115179/
[14:43] <tkamppeter> xnox, do you know whom I can ask? Who has made this package? r should I replace the small Python script by C or shell, to avoid the Python bindings?
[14:43] <jbicha> didrocks: I don't think there's any need to revert gnome-session, 3.9.90 works fine and there are unlikely to be more 3.8 releases; we just can't upgrade to 3.10
[14:44] <didrocks> jbicha: can you discuss with ricotz? I have no personal opinion about it and he brings that on
[14:44] <xnox> tkamppeter: right, so on command line I did: $ sudo /usr/sbin/aptd
[14:44] <xnox> tkamppeter: then I opened D-feet and org.freeddesktop.PackageKit appeared on the system bus.
[14:44] <xnox> tkamppeter: and indeed there is no CreateTransaction method.
[14:45] <ricotz> jbicha, i am fine with that, but carefully looking at the recent changes for cherry-picking fixes is needed then
[14:46] <xnox> tkamppeter: there is however org.debian.apt dbus-interface with "AddVendorKeyFromKeyserver / from File" etc. but at that point one can already use something like python-apt.
[14:46] <tkamppeter> xnox, this means that pk.install_signature() is not compatible with aptd any more due to API changes?
[14:47] <xnox> tkamppeter: well, either packagekit api changed, or aptd changed or both.
[14:47] <tkamppeter> xnox, who is resposible for that?
[14:47] <xnox> tkamppeter: currently in saucy there is https://launchpad.net/ubuntu/+source/aptdaemon/1.1.1-0ubuntu1 done by glatzor which FTBFS and thus still not available. It seems to have plenty of bugfixes.
[14:48] <xnox> tkamppeter: not sure who is responsible.
[14:48] <ricotz> jbicha, e.g. https://git.gnome.org/browse/gnome-session/commit/?id=2040b88847ed1ee11182caac96b0f09c553c646e, or even https://git.gnome.org/browse/gnome-session/commit/?id=ac9fd0dc97a17674cb082f80df0b1fcc45bc92bf
[14:49] <xnox> tkamppeter: try pulling that newer package, rebuild locally (ignoring the test-failure, or better fix them) and check if it fixes the issues with system-config-printer for you?!
[14:49] <tkamppeter> xnox, good idea, thanks.
[14:50] <jbicha> ricotz: the first commit needs rebasing of some Ubuntu patches, the second commit should be fine though
[14:50] <jbicha> and we wouldn't have gotten either of those by sticking with 3.8 either
[14:50] <ricotz> jbicha, i guess it might be easier to take 3.9.91+ and revert things
[14:52] <ricotz> jbicha, the argument for going with 3.8.4 would be to avoid clashes with gnome3 ppa where we don't want to revert things
[14:53] <jbicha> I think we'd need a ffe to upgrade gnome-session any further for saucy but you can upgrade further with the gnome3 ppas
[14:55] <ricotz> ok
[15:02] <tkamppeter> xnox, that's it, aptdaemon 1.1.1 solves the problem. Thank you very much.
[15:06] <xnox> tkamppeter: right, then please help to fix it's test-suite failures, such that we release saucy with aptdaemon 1.1.1 =)
[15:35] <didrocks> sil2100: falling asleep, leaving now, please do feel free to publish (and continue on the rest) once you are confident. See you!
[16:05] <tedg> Does someone know why we'd be getting this cli-common error?
[16:05] <tedg> https://jenkins.qa.ubuntu.com/job/libappindicator-saucy-armhf-autolanding/3/console
[16:05] <tedg> What do the cli dh rules do?
[16:07] <cyphermox> sil2100: what pieces are we publishing atm?
[16:08] <Laney> tedg: you asked that exact question before
[16:08] <sil2100> cyphermox: for now none, we're more or less ready to publish unity8, sdk and apps, but we have some AP failures going on
[16:08] <Laney> The job broke and didn't install the build deps
[16:09] <alberts> Hi! Can someone look at this fix for nautilus - https://code.launchpad.net/~albertsmuktupavels/nautilus/white-screen-fix/+merge/180231
[16:09] <tedg> Laney, Oh, so this is the same thing with dh rules needing to be on the base image.
[16:09] <tedg> Like the dh_click stuff
[16:09] <tedg> But, wait, why only on ARM then?
[16:10] <Laney> no
[16:10] <Laney> dpkg-checkbuilddeps: Unmet build dependencies: python-all-dev cli-common-dev (>= 0.5.7) libnunit-cil-dev dbus-test-runner xvfb valac mono-devel (>= 2.4.3) python-gtk2-dev gtk-sharp2-gapi libgtk2.0-cil-dev libdbus-glib-1-dev (>= 0.82) libindicator-dev (>= 0.3.90) libindicator3-dev (>= 0.3.90) libdbusmenu-glib-dev (>= 0.5.90) libdbusmenu-gtk-dev (>= 0.5.90) libdbusmenu-gtk3-dev (>= 0.5.90) libgirepository1.0-dev
[16:10] <Laney> it should have installed those
[16:11] <Laney> in particular missing cli-common-dev makes that error happen
[16:12] <tedg> Okay, so fginther it seems that the ARM images don't have cli-common-dev installed on them.  Can we fix that please?
[16:12] <fginther> tedg, yes, should be able to
[16:13] <tedg> Laney, It seems that the images do a "dh clean" before installing the build-deps, so if the needed dh scripts aren't there, they fail.
[16:13] <Laney> that would happen
[16:13] <Laney> the build deps should have been installed; error with the job
[16:14] <tedg> Really I think it should install the build deps before doing dh clean.  Not sure why it doesn't.
[16:14] <tedg> fginther, Thanks!
[16:15] <fginther> tedg, ugh, cli-common-dev requires 154 packages
[16:16] <Laney> why don't you do the source package build with -nc?
[16:16] <Laney> it's freshly checked out so won't be dirty
[16:17] <cyphermox> sil2100: you planning on releasing everything? what about services?
[16:19] <tedg> fginther, That's a bunch!
[16:22] <sil2100> cyphermox: we're not planning on releasing that
[16:22] <sil2100> cyphermox: we have a schedule for releases:
[16:23] <cyphermox> hrm
[16:23] <sil2100> cyphermox: https://docs.google.com/a/canonical.com/spreadsheet/ccc?key=0Au6idq7TkpUUdGNWb0tTVmJLVzFZd0doV3dVOGpWemc#gid=0
[16:23] <cyphermox> MTP ;)
[16:23] <cyphermox> mtp is in services, that's the one I'm interested in
[16:24] <cyphermox> it's already been preNEWed, btw. slangasek looked at it
[16:35] <cyphermox> sil2100: can I run the stack anyway with just mtp? we'll just wait before publishing?
[16:38] <sil2100> cyphermox: I think there was a talk about MTP today, so I guess it's ok to spin the stack
[16:39] <sil2100> cyphermox: just asac would have to make sure all is green
[16:39] <cyphermox> aye
[16:39] <cyphermox> asac: ^^ I'd like to land MTP, ok to spin the stack with just it?
[16:42] <fginther> tedg, cli-common-dev is installed on all the arm boxes, is there an MP I need to rerun?
[16:47] <asac> cyphermox: aftrer we pushed unity8/sdk
[16:47] <cyphermox> asac: ack
[16:47] <asac> whats the status on that? did we get confirm that eerything is good and pushed it?
[16:47] <tedg> fginther, Yes please, https://code.launchpad.net/~jbicha/libappindicator/misc-debian-control-fixes/+merge/180032
[16:47] <ogra_> asac, see -touch
[16:47] <ogra_> asac, sil2100 is on it
[16:48] <asac> ogra_: whats the summary
[16:48] <asac> lots of stuff was talkeda bout
[16:48] <asac> -> touch
[16:48] <ogra_> still testing
[17:32] <sil2100> kenvandine: https://code.launchpad.net/~sil2100/cupstream2distro-config/mir_switch_to_next_PPA/+merge/185871 <- can you take a look? The Mir guys asked for this
[18:14] <sil2100> cyphermox, kenvandine: later this day, check this branch and redeploy for the US guys on the Mir sprint ;) -> https://code.launchpad.net/~sil2100/cupstream2distro-config/mir_switch_to_next_PPA/+merge/185871
[18:15] <asac> sil2100: how long befrore you drop off?
[18:16] <sil2100> I should be gone already so not super long, I have a strange headache now as well!
[18:16] <kenvandine> sil2100, sure
[18:59] <sil2100> kenvandine: do you have a moment for this? https://code.launchpad.net/~sil2100/cupstream2distro-config/extra_pkgs_for_services/+merge/185905 ?
[18:59] <sil2100> kenvandine: I'll redeploy anyway ;)
[19:01] <kenvandine> hey sil2100, sorry, let me look
[19:01] <cyphermox> I do
[19:02] <cyphermox> don't redeply now please
[19:02] <kenvandine> cyphermox, thx :)
[19:02] <cyphermox> if the mir team just wants to write code for post-saucy, this is the wrong way to "fix" it
[19:03] <sil2100> cyphermox: I think they want to write fixes for saucy
[19:03] <sil2100> Not post-saucy
[19:03] <sil2100> cyphermox: since they want to have those changes released to saucy later
[19:03] <cyphermox> well, the result is the same really
[19:03] <sil2100> cyphermox: at least that's how I understood kgunn
[19:03] <cyphermox> they should do saucy bugfix in a saucy branch
[19:03] <cyphermox> and upstream development in turnk
[19:03] <cyphermox> *trunk
[19:04] <sil2100> There is no trunk, and I think they only want to do bugfixes for saucy for now
[19:04] <sil2100> I mean, trunk is for saucy still
[19:04] <sil2100> cyphermox: but best if you discuss that with kgunn
[19:04] <cyphermox> from there we can just change the target branch for saucy to whatever they name their change, and trunk for further devel
[19:04] <kgunn> sil2100: cyphermox ....our trunk is for saucy
[19:05] <sil2100> cyphermox: ^
[19:05] <kgunn> our trunk is sacred, so anything landing there...we want in saucy
[19:05] <cyphermox> kgunn: you don't expect to be doing any development not expected to land in saucy?
[19:05] <cyphermox> alright
[19:05] <sil2100> cyphermox: as I said, trunk is for saucy, there is no 'upstream development', they work for saucy only
[19:05] <cyphermox> sil2100: but then the PPA change is still incorrect, daily-build-next is explicitly not saucy
[19:05] <kgunn> cyphermox: correct...for the moment...and totally understand, if/when we get to doing dev that's not going into saucy
[19:05] <kgunn> we would branch ourselves
[19:06] <cyphermox> kgunn: ack
[19:06] <cyphermox> well for now anything in trunk does end up in saucy, that's all good
[19:06] <sil2100> cyphermox: well, true, but Didier uses it temporarily for saucy stuff as well
[19:06] <cyphermox> sil2100: the ppa change would make mir build in a ppa that could have random other stuff for future releases.
[19:06] <sil2100> cyphermox: I remember last week he used it as well
[19:07] <cyphermox> yes, for a very specific reason, to avoid building against Mir :)
[19:07] <cyphermox> since we purged the daily-build ppa completely
[19:07] <alberts> Hi! Does anyone knows what version of gtk will be used in ubuntu 14.04?
[19:07] <cyphermox> kenvandine: what's your opinion? feels to me like this should all be a no-op
[19:08] <cyphermox> alberts: whatever stable version of Gtk will be available, I'd say
[19:08] <cyphermox> alberts: depends on roadmap, let me check
[19:11] <cyphermox> alberts: I'm not sure. 4.0 by then maybe? I have no idea
[19:11] <cyphermox> there's a 3.9.14 tagged in git so there is a possibility I guess
[19:11] <alberts> cyphermox: thanks!
[19:12] <kenvandine> cyphermox, sil2100: not sure, so sending it to daily-build-next means not saucy, so yeah... a no-op
[19:12] <cyphermox> well, the ppa itself doesn't change where we land stuff
[19:12] <kenvandine> well, not totally a no-op... it still gets sent there
[19:12] <kenvandine> oh... that's where it builds it
[19:12] <kenvandine> not the dest
[19:13] <cyphermox> but I'm not sure we should possibly break what builds in next with an old mir
[19:13] <kenvandine> that is scary then
[19:13] <alberts> can someone look at this fix? https://code.launchpad.net/~albertsmuktupavels/nautilus/white-screen-fix/+merge/180231
[19:13] <kenvandine> should it maybe stay in experimental for now?  so it doesn't taint anything?
[19:14] <alberts> ubuntu 13.10 probably will be last ubuntu supporting multiple screens as with gtk 3.10 multi screen support has removed. it would be nice if this bug is fixed at least in this ubuntu version.
[19:14] <cyphermox> well if it's meant to be bugfix I'm fine with it building in the daily-build ppa... that's what it's for anyway
[19:15] <cyphermox> as long as there truly are no non-bugfix commits, but even then we can see it since it's manual publishing
[19:15] <kenvandine> true... so then just not making the change makes sense
[19:15] <sil2100> cyphermox: I didn't want to build it in daily-build PPA since I only want things in daily-build which we are considering to release in the nearest time
[19:15] <cyphermox> alberts: my concern wasn't with the fact that it's run only once per screen or not, but with whether there is an upstream-acceptable alternative to using the constructor to handle this
[19:15] <sil2100> cyphermox: while not slowing down the development of the Mir guys
[19:16] <sil2100> So maybe a different PPA?
[19:16] <cyphermox> sil2100: you wouldn't be slowing things down for Mir people
[19:16] <cyphermox> bugfix is just that -- bugfix
[19:16] <cyphermox> so if it's bugfix that lands in Mir trunk as kgunn mentions, you really don't need to change anything
[19:17] <sil2100> cyphermox: well, I'm tired now, so I don't care much now - so if you think it's ok to have it in daily-build, then ACK
[19:17] <cyphermox> I think it's perfectly safe and fine
[19:18] <cyphermox> doh, why did kgunn leave, we still need him :D
[19:18] <alberts> cyphermox: upstream has removed background drawing. so i guess there is no alternative. or I don't understand something?
[19:18] <cyphermox> alberts: that said, I don't feel strongly about it, just mildly prefer to see a patch that has received the blessing from the gnome people
[19:19] <ricotz> cyphermox, hi :), just wanted to ask if you are going to take a look at network-manager 0.9.8.4?
[19:19] <cyphermox> ricotz: I will, soonish
[19:19] <cyphermox> ricotz: got to land one patch first, then I'll be updating the packaging for 0.9.8.4
[19:19] <ricotz> cyphermox, great!
[19:19] <cyphermox> we should be able to land that this week
[19:20] <cyphermox> ricotz: do you need anything in particular?
[19:20] <alberts> cyphermox: so what should I do to get that fix accepted?
[19:21] <ricotz> cyphermox, nothing particular, i was about to take a look to get it into gnome3 ppa (which currently has 0.9.8.2), i will leave it to you then ;)
[19:21] <cyphermox> kenvandine: want to give your opinion on alberts' patch too? I don't feel strongly against the patch, though I think there is a better way to do this... but I'm not sure any of us have time to spend working on it
[19:21] <cyphermox> ricotz: ack
[19:22] <cyphermox> ricotz: there is a bunch of memory fixes and stuff like that, so a good idea to land anyway
[19:25] <alberts> cyphermox: it is not my patch. Its old patch which was rejected with "seems a bit simple to me, we don't want to construct a new object each time, rather we want one per screen". But it is already [with patch] constructed once per screen.
[19:25] <kenvandine> cyphermox, not really, i'm pretty distracted right now by content-hub
[19:25] <cyphermox> kenvandine: ack
[19:27] <cyphermox> alberts: I still think the fix is slightly incorrect, but let's just get it out of the way
[19:27] <cyphermox> alberts: it's for saucy right?
[19:29] <alberts> cyphermox: yes, but I have created merge proposal for precise too. what would be correct way to fix it? Maybe I could try to fix it myself...
[19:33] <cyphermox> alberts: let's done one thing at a time :)
[19:34] <cyphermox> alberts:  if you want to see your name in changelog, could you also update changelog to bump the version and apply the patch? do you know how to do that
[19:37] <alberts> cyphermox: I don't care about seeing my name in changelog. I just want it to be fixed. so do i need to do something now?
[19:38] <cyphermox> nah, I can handle it from here
[19:40] <tedg> fginther, Thanks, it looks like that patch landed!
[19:40] <fginther> tedg, \o/
[21:01] <jasoncwarner> hey Laney , still around? was wondering if we are still missing anything for datetime settings in system settings?
[21:11] <thumper> o/ jasoncwarner
[21:14] <Laney> jasoncwarner: hi, here for two minutes
[21:14] <Laney> jasoncwarner: https://wiki.ubuntu.com/TimeAndDate#Phone
[21:14] <Laney> We don't have the "Setting the time & date automatically ..." bit
[21:15] <jasoncwarner> Laney: is that needing the location service? (which is landing this week, I think)
[21:15] <Laney> mmm, I don't know exactly what that provides
[21:15] <Laney> I didn't know which API to use to ask if there's internet access
[21:16] <Laney> I think I started a thread about it on ubuntu-phone a few weeks ago but didn't get a clear answer
[21:17] <jasoncwarner> Laney ok. since you are heading off, mind following up on that tomorrow and driving to an answer? if need be, grab lool or chickencutlass and get a definitive answer.
[21:17] <Laney> I think this http://doc.qt.digia.com/qtmobility-1.2/qml-networkinfo.html is the thing
[21:17] <Laney> but it didn't work, maybe due to missing backend
[21:17] <Laney> I'll try it again
[21:18] <Laney> oh yes, wait, I'm remembering more
[21:18] <Laney> it has some complicated notion of 'informative' carriers and stuff
[21:23] <Laney> jasoncwarner: More remembering; the 'automatic' timezone selection doesn't do anything either
[21:23] <Laney> I think ofono provides this
[21:23] <Laney> Ken has been doing settings for things that need ofono as he has a device whereas Seb and I don't
[21:32] <ochosi> Laney: sorry to bother you again with this, but you mentioned before that ubuntu also has a logout issue (i pinged you about xubuntu and our session taking forever to end when logging out, because you submitted that logind patch)
[21:33] <Laney> ochosi: nothing more to report
[21:34] <ochosi> so this still hasn't been debugged yet in ubuntu?
[21:34] <Laney> not by me anyway
[21:34] <ochosi> ok, any idea whom i could ask about this?
[21:35] <Laney> I don't think anyone is doing so
[21:35] <ochosi> ppl just too busy with mir and the phone-stuff?
[21:35] <Laney> pitti might know best how to start looking but I doubt he has began to debug this one either
[21:36] <Laney> basically phone things for 13.10
[21:36] <Laney> Ideally I'll get more time for desktop bugs soon
[21:37] <Laney> anyway, in the absence of that it'd be great for someone else to prod at it
[21:37] <ochosi> yup
[21:37] <ochosi> we'll see whether we get anywhere, but i guess i'll ask pitti first for some pointers
[21:37] <Laney> maybe the ubuntu GNOME guys have the same problem
[21:37] <Laney> try asking them too
[21:38] <ochosi> they use gdm though, no?
[21:38] <Laney> logind though
[21:38] <ochosi> true
[21:38] <ochosi> any names in the u-gnome team you can recommend?
[21:39] <Laney> I recommend that you go ask in #ubuntu-gnome and hang around for a reply
[21:39] <Laney> got to go now, see you tomorrow
[21:39]  * Laney waves
[21:40] <ochosi> sure, thanks Laney !
[23:01] <cyphermox> alberts: I haven't forgotten you, just busy and I ran into issues merging your branch
[23:01] <cyphermox> I'll get back to it soon