[03:33] <pitti> Good morning
[04:32] <Mirv> pitti: morning. some reviews needed. ubuntu-system-settings starts depending on content hub (both in universe) http://pastebin.ubuntu.com/6053813/ , unity-greeter-session-broadcast stops building its libraries for now and dbus changes http://pastebin.ubuntu.com/6053814/ (http://bazaar.launchpad.net/~indicator-applet-developers/unity-greeter-session-broadcast/trunk.13.10/revision/22)
[05:04] <pitti> hey Mirv
[05:04] <pitti> looking
[05:05] <Mirv> hey pitti
[05:05] <pitti> http://pastebin.ubuntu.com/6053813/ -> was there a MIR filed?
[05:06] <pitti> http://pastebin.ubuntu.com/6053814/ ack
[05:07] <Mirv> pitti: I don't see one https://bugs.launchpad.net/ubuntu/+source/ubuntu-system-settings - that's seb128's package for a large part, I should ask him when he's around now that FF is behind us
[05:07] <pitti> https://launchpad.net/ubuntu/+source/content-hub/+bugs rather, but no bugs there
[05:08] <Mirv> yes, neither for content-hub
[05:08] <Mirv> maybe this week will be the week of MIRs
[05:09] <Mirv> the setting stack can wait untils seb128 is here in a couple of hours
[08:00] <Laney> morning all
[08:03] <darkxst> pitti, Laney Hi
[08:06] <Laney> hey darkxst
[08:08] <seb128> hey Laney, how are you? had a good w.e?
[08:08] <Laney> hi seb128, yeah it was good thanks, not much sleep but still nice ;-)
[08:08] <Laney> have some bruises from paintballing too
[08:08] <Laney> how was yours?
[08:08] <seb128> oh, you did paintball, nice!
[08:08] <Laney> yeah!
[08:08] <seb128> mine was relaxing, no bruises :p
[08:09] <Mirv> morning seb128
[08:09] <Laney> I lent someone my jumper as he was going to be fired on more by everyone else and then the rules changed and I ended up being pummeled wearing just a t-shirt :P
[08:09] <seb128> Mirv, hey
[08:09] <seb128> Laney, utch
[08:10] <Mirv> seb128: settings stack would need acking of the dependency add on content-hub. Martin was interested generally on the MIR plans of content-hub etc
[08:10] <seb128> Mirv, +1, I approved that MR
[08:10] <seb128> what "plan"?
[08:11] <Mirv> ok
[08:11] <Mirv> seb128: well, I guess if everything on the touch images is planned to be MIRd
[08:11] <Mirv> I know there is a lot queued already
[08:11] <seb128> I've no clue when we want to MIR stuff
[08:12] <seb128> does it matter?
[08:13] <Mirv> he did mention earlier that it's unfortunate that phablet images contain software that isn't officially supported
[08:14] <ogra_> seb128, we should MIR everything before release
[08:14] <Mirv> so I think that's the main question, although much larger topic than just settings/hubs
[08:14] <pitti> hey darkxst
[08:14] <pitti> good morning Laney
[08:14] <pitti> bonjour seb128
[08:14] <Laney> ola pitti
[08:14] <seb128> ogra_, pitti: hey
[08:15] <seb128> ogra_, "release", being saucy release?
[08:15] <ogra_> moin
[08:15] <Laney> args
[08:15] <ogra_> seb128, yeah ... we should at least try
[08:15]  * pitti waves to ogra_, too
[08:15] <Laney> my original gpg key expiry date has passed
[08:15] <seb128> ogra_, good luck :p
[08:15] <Laney> now every chroot is complaining
[08:15] <ogra_> that should be a september target
[08:15] <darkxst> pitti, any ideas about bug 1219588? I am getting mouse flat notifications every 10 mins ;(
[08:15] <ubot2`> Launchpad bug 1219588 in upower (Ubuntu) "wireless mouse battery percentadge incorrect" [Undecided,New] https://launchpad.net/bugs/1219588
[08:16] <seb128> ogra_, the issue is that MIR team is not going to scale for those reviews, it's basically down to mterry and he's overbusy on greeter work and other stuff
[08:16] <seb128> ogra_, not to mention security reviews
[08:16] <ogra_> seb128, yeah, i know, thats why i said "try" :)
[08:16] <pitti> darkxst: probably the same bug as bug 1103064
[08:16] <ubot2`> Launchpad bug 1103064 in upower (Ubuntu) "power indicator shows Logitech wireless keyboard and mouse batteries with 0%" [Low,Confirmed] https://launchpad.net/bugs/1103064
[08:16] <ogra_> we sholdnt release official images without having all bits on the image supported imho
[08:17] <seb128> pitti, Mirv: in any case, content-hub is the content picker for the phablet, it's being done by kenvandine and gusch, I doubt we can do without a content picker, that's the only way to e.g select files to add to email, messages, gallery, etc
[08:17] <pitti> darkxst: as it happens I reviewed a proposed upstream branch for fixing Logitech wireless devices; I'll build a PPA package from this soon
[08:17] <ogra_> but if we cant make it, we simply cant
[08:17] <Mirv> in general news, all of cu2d green except for Apps and Unity that have known test related bugs reported and contacted upon
[08:17] <pitti> seb128: sure; I'm fine with the diff, I was just pointing out that it needs a MIR
[08:17] <seb128> pitti, it doesn't, system-settings is in universe
[08:17] <pitti> eh?
[08:18] <pitti> seb128: we build phone images from universe?
[08:18] <pitti> seb128: but then, sure
[08:18] <Laney> what's what ogra_ was just talking about
[08:18] <ogra_> pitti, even fromn PPAs still
[08:18] <seb128> pitti, of course, 90% of the new components didn't get through MIR yet
[08:18] <Laney> s/what/that/
[08:18] <pitti> ah
[08:19] <Mirv> ogra_: we still haven't disabled all PPAs?
[08:19] <pitti> Mirv: so, then ignore the MIR bit for now :)
[08:19] <ogra_> pitti, PPA usage was a task planned to be fixed by august first ...
[08:19] <ogra_> obviously ddint make it
[08:19] <seb128> pitti, well "of course"... things are crazy, we keep landing new stuff, the goal so far is to drop the ppa use, we didn't think yet about getting stuff in main
[08:19] <ogra_> Mirv, the demo-assets packages are still in the PPA ...
[08:19] <ogra_> and the webapps-demo packages too
[08:19] <pitti> seb128: as far as I read, we plan to upgrade 13.10 phone installs to some 14.04 daily snapshots after some time anyway, right? so doesn't matter that much I guess
[08:20] <ogra_> and all core apps come from the core apps PPA
[08:20] <Mirv> ogra_: and I guess phone-app being replaced really-soon-now
[08:20] <darkxst> pitti, ok thanks
[08:20] <ogra_> (they are supposed to be click packages soon though, that will solve itself)
[08:20] <ogra_> Mirv, phone-app is gone since last week
[08:20] <seb128> pitti, I don't know the specific, ogra_ just said that we should try to go through MIR with everything before saucy release, not sure how realistic that is
[08:20] <ogra_> seb128, that we try ?
[08:21] <ogra_> i hope thats very relaistic :)
[08:21] <Mirv> ogra_: \o/
[08:21] <seb128> ogra_, no, that we manage to get MIR team and security team to review all that
[08:21] <seb128> ogra_, or we need more people to do reviews
[08:22] <ogra_> seb128, yeah, i'm not that unrealistic to say we'll make it :)
[08:22] <ogra_> buut the paperwork should at least be done for all packages by release
[08:23] <seb128> right
[08:23] <Laney> we should finish the archive reorg instead :-)
[08:24] <ogra_> Laney, feel free, nobody holds you back :)
[08:24] <Laney> hrhr
[08:24] <pitti> Laney: well, however we reorg the archive, we still need some kind of Component Inclusion Report/Review for stuff that we support
[08:24] <ogra_> ++
[08:25] <Laney> there's something but it won't be as heavy as MIRs iirc
[08:25] <pitti> how could it be any less heavy?
[08:28] <Laney> Hmm, can't remember the details
[08:28] <Laney> But I think there was some classes of things that weren't going to need a full review
[08:46] <Laney> seb128: Help
[08:46] <Laney> I don't understand what you mean by this: "* The design says "Switching to “4-digit passcode” should display a “Choose Passcode” alert with “New passcode” and two fields, “Cancel” and “Set” buttons. "
[08:46] <Laney> The current version has only 1 entry (I guess it's a type/type again to make sure there is no typo)"
[08:46] <Laney> OH
[08:46] <Laney> I do now
[08:47] <Laney> what does type/type mean though?
[08:47] <seb128> sorry I meant "password confirmation dialog"
[08:47] <seb128> e.g:
[08:47] <seb128> type your passorwrd
[08:47] <seb128> type your password again
[08:47] <Laney> ah yes
[08:47] <seb128> type/type again
[08:47] <seb128> ;-)
[08:47] <Laney> I didn't parse the text correctly
[08:47] <Laney> either mpt's spec or your comment
[08:47] <Laney> :P
[08:47] <seb128> yeah, it was not written nicely
[08:48] <seb128> well, I'm unsure
[08:48] <seb128> mpt's spec has a "2 entries..." somewhere
[08:48] <Laney> yeah
[08:48] <Laney> "two fields"
[08:48] <seb128> it's worth checking with him
[08:49] <Laney> doing in #-touch
[09:23] <seb128> pitti, did the "need to import translation templates from daily build ppa" ever go anywhere?
[09:24] <pitti> seb128: hm, no response from launchpad in bug 1201485
[09:24] <ubot2`> Launchpad bug 1201485 in langpack-o-matic "Need to import translations for the unity daily builds" [Undecided,Triaged] https://launchpad.net/bugs/1201485
[09:25]  * pitti pings Steve and Willian in #u-devel
[09:25] <seb128> thanks
[10:23] <mpt> Laney, seb128: I shall change that to a sheet with three fields ... Three successive dialogs is an interrogation.
[10:25] <Laney> mpt: I thought it was two, but maybe the same applies
[10:26] <mpt> Laney, yeah, true, the first dialog containing one field and the second containing two fields
[10:26] <Laney> indeed
[10:26] <Laney> mpt: Can you include what to do when the inputted value is wrong?
[10:32] <seb128> mpt, the "about this phone: storage" on the google doc, in the things to update you should add "list extra categories" (e.g movies, audio, pictures, other files)
[10:34] <mpt> Laney, https://wiki.ubuntu.com/SecurityAndPrivacySettings?action=diff&rev2=28&rev1=27
[10:35] <mpt> seb128, why?
[10:35] <mpt> oh, right, the erratum
[10:35] <Laney> cheers
[10:36] <mpt> done
[10:38] <seb128> mpt, thanks
[10:40] <seb128> mpt, do I read correctly from the notes that "GPS" should be dropped from the main screen?
[10:45] <mlankhorst> seb128: does the kernel need any special support to run desktop sessions in saucy? my nexus7 doesn't work correctly
[10:45] <seb128> mlankhorst, try asking ogra_, I think he said we would need a special kernel for the n7
[10:45] <seb128> we don't support desktop on it, just touch
[10:46] <mlankhorst> yeah I know, but still..
[10:48] <mlankhorst> seb128: can I force a fallback to the old desktop session?
[10:49] <mpt> seb128, yes
[10:50] <ogra_> mlankhorst, iirc the tegra has an issue if you want to run X without having fbcon in the kernel
[10:51] <ogra_> touch doesnt use fbacon
[10:51] <ogra_> err
[10:51] <ogra_> fbcon
[10:51] <mlankhorst> ogra_: well the xserver initializes, but nothing gets started
[10:51] <ogra_> right
[10:52] <ogra_> touch also hands over device handling to the container
[10:52] <ogra_> s/handling/initialization/
[10:52] <ogra_> once we have Mir, XMir should work though
[10:54] <ogra_> mlankhorst, i think your best move would be to install raring desktop and dist-upgrade
[10:54] <ogra_> touch is surely not suited well for testing X
[10:55] <mlankhorst> ogra_: yeah it's the path I took, but I was hitting a bug with xorg init
[10:55] <mlankhorst> and from some digging looks like saucy changed to using systemd init
[10:56] <ogra_> lol
[10:56] <ogra_> surely not :)
[10:56] <ogra_> but you most likely hit a bug with plymouth
[10:56] <ogra_> make sure to disable all the upstart jobs for it ... or force that console-setup runs from the initrd
[10:57] <ogra_> either will make it boot
[11:28] <mlankhorst> ogra_: only error I'm getting in .xsession-errors is init: Unable to register as subreaper: Invalid argument
[11:28] <ogra_> oh, thats a kernel issue then
[11:29] <mlankhorst> thought so
[11:29] <ogra_> bug 1218415
[11:29] <ubot2`> Launchpad bug 1218415 in linux-maguro (Ubuntu) "upstart needs subreaper prctl support for touch kernels < v3.4" [Medium,Fix released] https://launchpad.net/bugs/1218415
[11:39] <mlankhorst> oops, still on the old nexus7 kernel, which I guess was the desktop kernel
[11:40] <ogra_> as i said, the new -grouper kernel wont have fbcon
[11:41] <mlankhorst> yeah, it's sad that they can't have the nexus7 as supported for desktop
[12:26] <lool> Hey, gvfs-backends is broken after the libimobiledevice rebuild; it needs porting to the new libimobiledevice API; this was done upstream in gvfs 1.17.3; upstream even has a 1.17.90
[12:27] <lool> I only saw bug fixes / cleanups, no new features in these
[12:27] <lool> is someone working on this update?  would be good to get for beta1
[12:28] <seb128> lool, hey, thanks for working on that ... not sure about the update, pitti is the one who usually does the gvfs update
[12:28] <seb128> pitti, ^ did you start on those?
[12:28] <lool> I saw there are some commits of his upstream  :-)
[12:28] <pitti> je peux le faire
[12:29] <seb128> pitti, ça serait bien, merci!
[12:29] <lool> pitti: ce serait super pour https://lists.ubuntu.com/archives/ubuntu-release/2013-September/002528.html
[12:29] <lool> pitti: merci  :-)
[12:30] <lool> pitti: grep-ing the build log, there seemed to be other potential bugs of the type "incompatible pointer type" in the log; outside of libimobiledevice, these are probably not new, but if you are tempted to have a look...  :-)
[12:30] <lool> pitti: I suspect https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1214204 is fixed with new version
[12:30] <ubot2`> lool: Error: launchpad bug 1214204 not found
[12:30] <lool> ubot2`: it's because it's private
[12:30] <ubot2`> lool: I am only a bot, please don't think I'm intelligent :)
[12:31] <lool> ubot2`: not pretending you are
[12:31] <ubot2`> lool: I am only a bot, please don't think I'm intelligent :)
[12:31] <lool> see
[12:31] <pitti> someone please teach ubot2` some eliza!
[12:31] <pitti> ubot2`: how do you feel today?
[12:31] <ubot2`> pitti: I am only a bot, please don't think I'm intelligent :)
[12:31] <pitti> booring
[13:00] <seb128> sil2100, don't add the pot to the upstream lens, that was just needed once to "bootstrap" launchpad (it needs a pot to import)
[13:02] <sil2100> seb128: ah, ok, then I'll just add the changelog entry, ok?
[13:02] <seb128> sil2100, yes
[13:03] <sil2100> Mirv, seb128: I think both AP machines are down ;/ Looking on what's up
[13:08] <sil2100> jibel: ping
[13:08] <sil2100> jibel: could you take a look on what's wrong with jenkins and the AP machines?
[13:08] <sil2100> jibel: it looks as if they're not visible on jenkins
[13:09] <sil2100> jibel: rebooting the machines didn't help
[13:09] <jibel> sil2100, looking
[13:10] <sil2100> jibel: thanks!
[13:14] <sil2100> jibel: I don't see the jenkins slaves being ran on the test machines?
[13:16] <jibel> sil2100, right because "Error: Invalid or corrupt jarfile /var/run/jenkins/slave.jar"
[13:17] <jibel> sil2100, it should be good now
[13:18] <sil2100> jibel: \o/ thanks!
[13:18] <jibel> yw
[13:21] <sil2100> seb128: I already pushed the modified version, can you +1 that branch so we can merge it?
[13:22] <seb128> sil2100, done
[13:25] <sil2100> THanks!
[13:27] <sil2100> jibel: btw. do you know a thing or two about the mediumtest jobs, or is that more of a Francis-thing? ;)
[13:28] <jibel> sil2100, I know nothing about these jobs :)
[13:58] <pitti> lool, seb128: uploading gvfs 1.17.90 (will be blocked by freeze, though)
[13:59] <seb128> pitti, danke
[14:22] <seb128> Laney, around?
[14:23] <Laney> seb128: yes
[14:24] <seb128> Laney, you looked a bit to the AS custom property stuff last week
[14:24] <seb128> gdbus call --system --dest org.freedesktop.Accounts --object-path /org/freedesktop/Accounts/User32011 --method org.freedesktop.DBus.Properties.Set com.canonical.unity.AccountsService launcher-items "<[{'defaults' : <true>}]>""
[14:24] <seb128> Laney, I want to transform that to qt code
[14:25] <seb128> Laney, do you know how to format the "<[{'defaults' : <true>}]>"
[14:25] <seb128> should that be a QVariant?
[14:26] <seb128>     userInterface.call("Set",
[14:26] <seb128>                        "com.canonical.unity.AccountsService",
[14:26] <seb128>                        "launcher-items",
[14:26] <seb128>                        "<[{'defaults' : <true>}]>");
[14:27] <seb128> e.g I guess the last argument there is in buggy format
[14:27] <Laney> hmm
[14:27] <Laney> Almost certainly not that
[14:27] <seb128> right
[14:27] <Laney> sec
[14:27] <seb128> well, I copied the gdbus line and started replacing bits
[14:27] <seb128> I'm just not sure what to do with the "defaults: true"
[14:30] <seb128> Laney, looking to https://code.launchpad.net/~mterry/unity8/launcher-items/+merge/181061 is helping I think
[14:30] <seb128> QList<QVariantMap> items;
[14:30] <seb128> QVariant::fromValue(items))
[14:31] <Laney> http://qt-project.org/doc/qt-5.1/qtdbus/qdbustypesystem.html
[14:32] <seb128> items << QVariantMap().insert("defaults", true)
[14:32] <seb128> Laney, ^ does that seems about right do you?
[14:37] <Laney> seb128: sec, otp
[14:38] <seb128> Laney, no hurry, I did that: http://paste.ubuntu.com/6055372/
[14:38] <seb128> seems to build fine, I can't really test it though, since the unity side didn't land yet
[14:42] <Laney> seb128: well, I think it'd be at runtime that you see any problems
[14:42] <Laney> you could try adding a property with a matching type to security-privacy and see if that works
[14:44] <seb128> Laney, ok, I can test on my desktop in fact
[14:44] <seb128> Laney, the unity8 work from mterry landed
[14:44] <seb128> Laney, thanks ;-)
[14:44] <Laney> I don't understand what type that is though
[14:44] <Laney> is a{sv} or something else?
[14:45] <seb128> Laney, + <property name="launcher-items" type="aa{sv}" access="readwrite">
[14:45] <Laney> ah
[14:45] <Laney> hence the extra QList, I did wonder
[14:45] <Laney> yeah if you install the files from unity8 you should be able to test that
[14:45] <seb128> I've it in d-feet
[14:45] <seb128> so on the right way
[15:06] <lool> pitti: should we request a hint to pass it though?
[15:06] <lool> pitti: Seems there are some crashes for ios users that might be worth fixing for beta1?
[15:36] <seb128> lool, you can try asking on -release about it
[15:39] <lool> seb128: I thought pitti might have a reason not to ask for it
[15:39] <lool> I've asked for libgpod to be hinted earlier today
[15:39] <lool> seb128: if you think gvfs is low risk, I can ask for it
[15:39] <lool> I've looked at the git log, and it seemed fine
[15:40] <seb128> Laney, ^
[15:40] <seb128> opinion?
[15:41] <Laney> no opinion
[15:41] <Laney> can you get someone else to look at it?
[15:41] <Laney> Trying to unconfuse myself about s-s atm
[15:42] <lool> I can try to confirm whether I get the same bug as the reporter and whether it's fixed, at least we know it's good enough on this backend which is one of the only ones updated
[15:42] <lool> trying that now
[15:43] <seb128> sil2100, when is the next tick?
[15:57] <lool> seb128, Laney, pitti: After testing, I can confirm that I got some error popups on login with an ipad plugged (bus timeout blahblah) and when clicking on the automatically added mount points in nautilus; when upgrading to pitti's packages, I got nice dialogs on login offering to import pictures, and nautilus allowed to browse the device
[15:58] <Laney> lool: Maybe you could ask Colin (or Stéphane if he's still around) in #ubuntu-release to consider it
[15:58] <Laney> lool: Otherwise I'll look in a bit when I get done with this branch
[15:59] <Laney> thanks for your testing/work
[16:01] <pitti> lool: no particular reason not to ask for it, just that it might unduly set back the image testing
[16:01] <Laney> We're not on full on image testing yet
[16:02] <pitti> lool: https://jenkins.qa.ubuntu.com/view/Saucy/view/AutoPkgTest/job/saucy-adt-gvfs/121/ is happy anyway
[16:02] <pitti> and I tested it locally, of course
[16:02] <pitti> we have fairly good test coverage these days (just not the ipod stuff, but lool just tested that manually)
[16:02] <lool> pitti: please say so on -release  :-)
[16:02] <lool> that you've tested it and that we've good coverage
[16:03] <lool> pitti: on #ubuntu-release that is
[16:03] <sil2100> seb128: 20:00
[16:03] <sil2100> seb128: we missed the tick due to machine problems
[16:03] <sil2100> seb128: I wasn't sure if it made sense to re-run everything or maybe wait for the next tick probably
[16:04] <pitti> lool: done
[16:04] <lool> thanks
[16:04] <seb128> sil2100, ok, do you think you could retry the sdk stack while you are still around?
[16:05] <seb128> sil2100, I would like to see it published today, the new optionselector landed and I need it
[16:05] <Laney> \o/!
[16:06] <sil2100> seb128: hm, ok
[16:07] <sil2100> seb128: running!
[16:07] <seb128> sil2100, thanks ;-)
[16:59] <sil2100> jibel: are you around? :)
[17:00] <seb128> sil2100, please tell me that the machines are not screwed again ;-)
[17:00] <sil2100> seb128: eeeeh ;)
[17:01] <sil2100> seb128: they *look* hanged up, wanted jibel to check what's up
[17:01] <seb128> :-(
[17:02] <sil2100> ;/
[17:03] <sil2100> seb128: ok, screw that, we don't have too much time so I'll restart the machines and re-run SDK
[17:03] <seb128> sil2100, thanks
[17:10] <jibel> sil2100, I'm around, I'll have a look
[17:13] <sil2100> jibel: thanks! ;) Restarted them already though... the jobs were standing and doing nothing, the containers were accessible and seemed ok
[17:14] <jibel> sil2100, okay
[17:14] <jibel> sil2100, when you say "them" should I understand that not only intel was stuck?
[17:15] <sil2100> jibel: yes, the strange thing was that both intel and nvidia were stuck, so maybe the SDK stack has something broken?
[17:15] <jibel> sil2100, it could be, because previous freezes we had only affect intel
[17:28] <seb128> sil2100, jibel: I doubt it's a sdk bug, the log looked like dbus timeouts (again)
[17:29] <sil2100> seb128: *sighs*
[17:30] <sil2100> seb128: today is an unlucky day, I would gladly publish unity, but I'm not sure if the tests were indeed sane
[17:30] <sil2100> seb128: since only one machine finished
[17:31] <seb128> sil2100, let's be safe and publish tomorrow rather
[17:32] <seb128> sil2100, most things are blocked by the freeze anyway
[17:32] <sil2100> Indeed
[17:37] <sil2100> seb128: ok, we're officially screwed
[17:37] <sil2100> seb128: the AP machines are gone AGAIN
[17:37] <sil2100> jibel: ^
[17:38] <sil2100> jibel: help us, today everything is more unreliable than before it seems!
[17:39] <Laney> ze sky, eet eez falleeng
[17:39] <sil2100> Laney: I hope not!
[17:45] <seb128> sil2100, :-(
[17:46] <sil2100> seb128, jibel: aborting those builds, since it's impossible for it to finish now, so at least the next tick will run ;/
[17:47] <seb128> sil2100, ok
[17:47]  * seb128 shakes fist at the qa lab
[17:48] <sil2100> What the heck is happening
[17:53] <sil2100> seb128: I *probably* restarted the testing slaves
[17:53] <sil2100> So I hope the 20:00 tick will kick in and finish
[18:09] <jibel> seb128, sil2100 I'll monitor 1800UTC tick after dinner
[18:10] <sil2100> jibel: thanks :) Strange thing since the slaves don't seem to start up after a soft-reboot