[00:38] <Drew_Neilson> hey I heard that there is some talk about moving development of Ubuntu Touch off of the Nexus 4 and onto the Nexus 5.  Is this true?
[00:44] <popey> Drew_Neilson: no
[00:46] <Drew_Neilson> ok, I guess I won't be buying a Nexus 5 then
[00:46] <cwayne1> the community port for it works quite well though
[00:47] <cwayne1> but it's not officially supported
[00:47] <Drew_Neilson> I
[00:47] <Drew_Neilson> I'm a little uneasy with running community ports
[00:48] <cwayne1> that's fair
[00:48] <cwayne1> I personally run it quite often (i do dual boot), worked out pretty well so far :)
[03:27] <botnut> few questions for anyone out there listening
[03:27] <botnut> any phones out there come with ubuntu touch loaded on it already?
[03:27] <popey> botnut: not a great time of day for it, but go for it
[03:28] <popey> not yet
[03:28] <popey> "soon"
[03:28] <popey> see the end of the channel topic ㋛
[03:28] <botnut> so if i wanted to use touch - on an existing phone does it have to run on android - or does it completely replace it?
[03:28] <popey> replaces
[03:28] <botnut> completely?
[03:28] <popey> yes
[03:29] <popey> you can also dual boot on some devices
[03:29] <botnut> interesting - can you do calls, emails, sms/mms, and web browsing with touch when you do that?
[03:29] <popey> yes
[03:29] <botnut> stable or no?
[03:29] <popey> its not finished
[03:30] <popey> still has some bugs
[03:30] <popey> but some people use it as their daily device
[03:31] <botnut> is there an eta on when it will be stable?
[03:31] <botnut> 2015?
[03:31] <popey> there's a plan to release at least one device this year
[03:31] <popey> but we don't make the devices
[03:31] <popey> so that's up to the manufacturer
[03:32] <botnut> gotcha
[03:32] <botnut> thanks for the input - been waiting a long time now for the ubuntu touch phones
[03:32] <botnut> ugh!!!
[03:34] <popey> not long now ☻
[05:07] <pitti> sergiusens: I suppose this is related to disabling udev during boot? once we restart udev do we do a full udevadm trigger? If not, then we at least need to do one for --subsystem-match=block
[05:47] <hackersarchangel> howdy everyone.
[05:48] <hackersarchangel> Trying to understand send-sms under /usr/share/ofono/scripts
[05:48] <hackersarchangel> I keep getting an error related to ValueError: invalid literal for int() with base 10
[05:49] <hackersarchangel> Only reason I’m using that is I’m trying to get debugging information on SMS
[05:49] <hackersarchangel> and see if there is something I need to change to get it working
[06:14] <hackersarchangel> well I have to go to bed, but if anyone has any suggestions on how to debug why SMS is not working but phone calls are you can PM me so I’ll find it in the morning. Thanks to anyone that helps :)
[07:00] <dholbach> ngood morning
[07:50] <zyga> nik90_: hey
[07:50] <zyga> nik90_: how's your new provider :) ?
[07:58] <mvo_> alex-abreu: hi, would you mind if I upload https://code.launchpad.net/~mvo/unity-webapps-qml/update-deps/+merge/233023 ? trivial change that would help with some cross-build setup work
[08:25] <JamesTait> Good morning all; happy Newspaper Carrier Day! :-D
[08:27] <Akiva-Mobile> hey james
[08:38] <justCarakas> does anyone know when there will be a new devel version (current on my phone is 203) because I cant unlock my pincode
[08:39] <justCarakas> balloons: ^
[08:42] <captcavy> can i change my mobile os to ubuntu?
[08:42] <justCarakas> depends on what phone you have captcavy
[08:43] <justCarakas> the official version is for the nexus 4, but there are a lot of ports already by the community
[08:43] <justCarakas> so if your phone is one of those models you can flash it
[08:43] <justCarakas> else you can always try to port it yourself
[08:44] <captcavy> cpu 1.3 dual core ram 1gb
[08:44] <justCarakas> captcavy: http://developer.ubuntu.com/start/ubuntu-for-devices/installing-ubuntu-for-devices/
[08:44] <justCarakas> what brand and model captcavy
[08:44] <zyga> mvo_: hey :-)
[08:44] <captcavy> htc one sir
[08:47] <justCarakas> captcavy: http://forum.xda-developers.com/showthread.php?t=2780273
[08:47] <seb128> mpt, hey
[08:47] <seb128> mpt, if the buttons are the bottom of https://wiki.ubuntu.com/Appearance?action=AttachFile&do=get&target=background.single.phone.png have their labels ellipsized, do you consider it as a bug/design issue?
[08:48] <mpt> seb128, yes, absolutely
[08:48] <seb128> k, I'm opening a bug then
[08:49] <mvo_> zyga: good morning
[08:49] <mpt> seb128, I guess there should be a way to say to the toolkit, “If these buttons fit, put them alongside each other; if they don’t, put them in a stack”
[08:54] <seb128> mpt, yeah, I don't think the toolkit provides that feature
[08:54] <seb128> mpt, well, filed https://bugs.launchpad.net/ubuntu/+source/ubuntu-system-settings/+bug/1365380
[09:08] <seb128> jgdx, hey
[09:08] <seb128> jgdx, so, the phone number info still doesn't display on my krillin, was that supposed to be fixed with yesterday's landing?
[09:51] <mandel> Elleo_, I have been talking with charles_ about an update to do in udm so that the indicator can show some decent titles, I'll have to do some work in the qml plugin so that you can easily set the title of of the downloads and if the should be shown in the indicator
[09:51] <mandel> Elleo_, I hope to have it by the end of the day
[10:59] <nik90_> zyga: Hey
[11:00] <nik90_> zyga: I haven't yet got to working on it since jenkins just got fixed yesterday and we are trying to merge all the branches that stagnated over a week.
[11:00] <zyga> nik90_: ok
[11:00] <zyga> nik90_: if I can help you in any way, just say
[11:01] <nik90_> zyga: hopefully I should be able to work on it tonight and update you tomorrow morning.
[11:01] <nik90_> zyga: will do
[11:02] <sergiusens> pitti: thanks, I'll look into that; and yes most likely related to the udev restart
[11:02] <sergiusens> I don't know where that logic lives though, so I'll need to poke ogra_
[11:02] <ogra_> udev.override iirc
[11:02]  * sergiusens checks
[11:03] <ogra_> we dont run udevadm at all anywhere
[11:03] <ogra_> we also dont "stop" udev explicitly ... thats something the initrd does
[11:03] <ogra_> we only start it delayed after the container is up
[11:05] <ogra_> sergiusens, pitti, i wonder if there is simply a copying of the udev rules into the initrd missing, i would actually expect all this to be handled by the initrd udev already the one running in userspace should just pick up existing bits
[11:06] <ogra_> s/userspace/rootfs/
[11:09] <ogra_> bzoltan, where does the SDK landing stand ? (all other bits should now be ready)
[11:09] <ogra_> (for dev mode)
[11:13] <mpt> Why does “ubuntu-device-flash ubuntu-touch/ubuntu-rtm/devel-proposed” give me 14.04 r11? That’s months out of date.
[11:14] <ogra_> mpt, --channel
[11:14] <mpt> ahhhh ha
[11:14] <ogra_> and there is no "devel-proposed" channel for rtm
[11:14] <ogra_> thats 14.09
[11:14] <mpt> It shows up in --list-channels
[11:15] <ogra_> heh, right ... its an alias to 14.09
[11:15] <om26er> davmor2, Hi!
[11:15] <ogra_> hadnt seen it before, sorry
[11:15] <mpt> thanks ogra
[11:16] <davmor2> om26er: hey
[11:16] <om26er> davmor2, image 21 on mako. I am calling my mako from another phone and there is no ringtone no notification. While the other phone has the dialing tone.
[11:16] <om26er> did you see that bug recently ?
[11:22] <sergiusens> om26er: that is a common operator gimmick when the network is congested
[11:22] <sergiusens> it always gives you feedback before ringing
[11:24] <om26er> bug 1365448
[11:24] <om26er> sergiusens, ^
[11:24] <om26er> that's not operator problem.
[11:24] <sergiusens> oh, that's different
[11:25] <om26er> syslog attached shows something from apparmor
[11:26] <davmor2> om26er: seems to be working fine here
[11:26] <davmor2> popey: do you get a notification when you ring your mako?
[11:28] <om26er> davmor2, its not an always happening issue, I just found myself in this state. Plus I reflashed my phone just a few hours ago.
[11:28] <popey> davmor2: dunno, my phone keeps crashing
[11:28] <mpt> seb128, did you fix the Ubuntu shape on apps in the “Notifications” screen, or would you like a bug report for it?
[11:38] <seb128> mpt, I fixed it, what image are you using?
[11:44] <ogra_> seb128, seemingly rtm
[11:44] <seb128> ogra_, ?
[11:44] <ogra_> seb128, i walked him through to install the latest rtm above
[11:45] <ogra_> so latest rtm image it is
[11:45] <seb128> weird
[11:45] <seb128> mpt, are those icons supposed to be ubuntushaped or not?
[11:45] <ogra_> (in which the change isnt present, i can confirm that)
[11:45] <ogra_> the utopic image has rounded corners ... rtm doesnt
[11:45] <seb128> I wish fixes would flow back to rtm
[11:46] <ogra_> someone needs to land them there
[11:46] <mpt> seb128, it says “14.10 (r22)”
[11:46] <seb128> should the rtm distro be listed on https://launchpad.net/ubuntu/+source/ubuntu-system-settings ?
[11:46] <seb128> r22?
[11:46] <seb128> doesn't sound like rtm
[11:46] <seb128> or did we get 6 images since this morning
[11:46] <ogra_> hmm, no, that definitely isnt rtm
[11:46] <mpt> seb128, it’s from “ubuntu-device-flash --channel ubuntu-touch/ubuntu-rtm/14.09-proposed”
[11:46] <mpt> Is that not what I’m supposed to be using either?
[11:46] <ogra_> you are
[11:47] <ogra_> but thats not whats on your device
[11:47] <seb128> mpt, not sure, ogra should know
[11:47] <seb128> but your device has 14.10 not 14.09
[11:47] <seb128> which is weird
[11:47] <sergiusens> ogra_: if it's a mako it can be, right?
[11:47] <ogra_> oh, mako
[11:47] <ogra_> yeah
[11:48] <cwayne1> mzanetti: just tried dronefly with a 2.0 drone
[11:48] <cwayne1> controls work like a charm, nothing from the camera though
[11:48] <ogra_> seb128, {os|lsb}-release havent been changed ...
[11:48] <sergiusens> seb128: the 14.09 thing is more a cause of confusion
[11:48] <ogra_> right
[11:48] <mpt> 14.09 > 14.10? :-)
[11:49] <ogra_> sergiusens, we should really show the channel name in the settings
[11:49] <seb128> mpt, no, but seems like the fix is in utopic, not 14.09
[11:49] <ogra_> right
[11:49] <sergiusens> http://system-image.ubuntu.com/ubuntu-touch/ubuntu-rtm/14.09-proposed/mako/index.json
[11:49] <sergiusens> confirms, mako is 22
[11:49] <ogra_> someone needs to explicitly land that
[11:49] <seb128> mpt, bugfixes don't flow naturally to rtm
[11:49] <ogra_> seb128, ??
[11:49] <ogra_> bugfixed flow easily
[11:49] <sergiusens> ogra_: I thought there was supposed to be a feature for channel switching
[11:49] <ogra_> you just need to ask for them being moved over
[11:49] <sergiusens> where it would show the current channel
[11:50] <ogra_> (as long as the landing doesnt contain other stuff indeed)
[11:50] <seb128> ogra_, well, seems like not easily enough to have that fix in ;-)
[11:50] <ogra_> seb128, i thinkits rather the fact that ken does merged landings of multiple branches all the time
[11:50] <sergiusens> seb128: it's a pain for me to get stuff in rtm as you still need double testing
[11:50] <seb128> ogra_, well, settings is busy fixing issues
[11:50] <ogra_> which makes landing for him easier
[11:51] <seb128> so we get ton of changes and landings yes
[11:51] <ogra_> but you will also have feature changes in the set
[11:51] <ogra_> bugfix only landings should just go through by definition
[11:51] <seb128> ogra_, no, we don't
[11:51] <seb128> well, nothing that is not required for rtm
[12:01] <cwayne1> mardy: ping
[12:01] <mzanetti> cwayne1: yay!
[12:01] <mzanetti> cwayne1: that's great news that it works fine.
[12:01] <cwayne1> mzanetti: yeah!
[12:02] <cwayne1> i was super excited as soon as I saw that G+ post and had to try it right away :D
[12:02] <mzanetti> cwayne1: hmm... camera shouldn't be too hard
[12:02] <mpt> Sooooo … Any suggestion of what image I should flash for testing?
[12:02] <mzanetti> cwayne1: thing is, I only have a 1.0, so hard to test
[12:02] <ogra_> mpt, yu got the right image (at least for mako)
[12:02] <cwayne1> hmm
[12:03] <cwayne1> mzanetti: maybe i should bring 2.0 to devices sprint for you to test with :P
[12:03] <mzanetti> cwayne1: heh, that'd be great :D
[12:03] <mzanetti> also for us to play with
[12:03] <mzanetti> cwayne1: well, I can give it a shot to blindly add support for the HD stuff, now that I know where to find testers :)
[12:04] <mzanetti> can I ping you occationally with some beta click packages for it?
[12:04] <cwayne1> mzanetti: absolutely
[12:05] <jgdx> Good day, all
[12:05] <jgdx> seb128, think so. What does list-modems say for SimManager.SubscriberNumbers?
[12:07] <seb128> jgdx, is that script supposed to block for like 30s?
[12:07] <jgdx> yeah
[12:08] <jgdx> talking to nsa I think
[12:08] <seb128> lol
[12:08] <seb128> jgdx, SubscriberNumbers =
[12:08] <seb128> e.g no value
[12:08] <mardy> cwayne1: pong
[12:08] <seb128> is that working for anyone on krillin?
[12:09] <jgdx> seb128, right, so that's probably your sim provider's fault
[12:09] <jgdx> seb128, and the blocking is due to the call wait/forward setting being on the network, not locally, on the sim
[12:10] <seb128> k
[12:10] <seb128> jgdx, sim provider's fault? that seems weird to me
[12:10] <cwayne1> mardy: heya, so if i wanted an icon to show up for a click-packaged account-plugin, where would i put it?
[12:10] <seb128> jgdx, shouldn't "get your number" be a standard/supported thing?
[12:10] <jgdx> seb128, I think it's optional and some just don't register it there
[12:11] <seb128> there is no other way to get the number?
[12:11] <jgdx> seb128, I would think, but from reading various bugs and specs, it's not
[12:11] <jgdx> seb128, iPhone let's you input it yourself :|
[12:11] <seb128> :-/
[12:11] <jgdx> s/let's/lets
[12:11] <seb128> k
[12:11] <seb128> thanks
[12:15] <mardy> cwayne1: somewhere in your account plugin, and you'd write its relative path in the .provider file
[12:15] <mardy> cwayne1: "relative" means "relative to the root dir of your click package"
[12:19] <derek-g> is everyone here super-excited about new coming way to package Linux systems (http://0pointer.net/blog/revisiting-how-we-put-together-linux-systems.html) ?
[12:20] <ogra_> not at all, nope
[12:20] <derek-g> ogra_, I'm like "not soon enough Lennart - not soon enough!"
[12:20] <jibel> seb128, I updated bug 1365401, the problem is that the .mo is simply not there.
[12:21] <mandel> charles_, this is for you => https://code.launchpad.net/~mandel/ubuntu-download-manager/properties/+merge/233348
[12:21] <mandel> charles_, I'll create a branch for the click scope to use the new methods to set the information of the application and will propose a merge asap
[12:21] <seb128> jibel, k, seems like a bug for langpack-o-matic/pitti
[12:22] <seb128> pitti, hey, where is the list of the templates that should go in -touch langpacks?
[12:22] <derek-g> ogra_, no srsly - I love the idea. current linux packaging sux.
[12:22] <mandel> charles_, will later update the qml so that the browser can use this and will propose a system settings change so that click updates are shown too
[12:22] <pitti> seb128: yep, I'm currently investigatging this; ah, there's a bug report
[12:23] <seb128> pitti, yeah, please reassign as appropriate ;-)
[12:25] <pitti> seb128, jibel: I'll build fresh langpacks to fix that, we could do with a fresh upstream update anyw
[12:25] <pitti> ay
[12:26] <seb128> pitti, danke
[12:26] <jibel> pitti, merci
[12:27] <seb128> pitti, looking at http://bazaar.launchpad.net/~ubuntu-langpack/langpack-o-matic/main/revision/497 ... it's weird, indicator-power was in this list but yet it's displayed translated?
[12:28] <pitti> seb128: yes, that was not the cause of that bug, just some cleanup
[12:28] <pitti> seb128: these three indicators can't be directly translated in LP in their projects, they need an ubuntu upload
[12:28] <seb128> pitti, what was making the mo missing from the langpack?
[12:28] <seb128> just to know for next time
[12:28] <mandel> Elleo_, I'd like to land the following => https://code.launchpad.net/~mandel/ubuntu-download-manager/expose-logger/+merge/225685
[12:29] <pitti> seb128: this commit was just for merge-touch-upstream-translations which will update translations from trunk (for quicker turnaround), it doens't remove translations
[12:29] <pitti> seb128: well, that's what I'm still trying to figure out; they were still present last week
[12:29] <seb128> k
[12:29] <pitti> but then I apparently did something wrong when constructing one of the latest updates
[12:29] <seb128> let me know when you found it
[12:29] <seb128> find
[12:40] <rickspencer3> cyphermox_, is the BT indicator supposed to disappear after I turn off BT, or is that a bug?
[12:51] <pitti> rickspencer3: FTR, you can switch it back on in system-settings, but I'd still consider it a bug
[12:51] <pitti> curiously we had had exactly the same bug on the desktop until early utopic
[12:51] <pitti> now it just gets grayed out
[12:51] <rickspencer3> pitti,  interesting
[12:51] <rickspencer3> pitti, it's quite annoying to not be able to toggle it there
[12:52]  * ogra_ thought that was a design decision
[12:52] <rickspencer3> I logged a bug a while back, but I want to ascertain if it's by design :)
[12:53] <rickspencer3> ogra_, interesting ... if so, a decision made by someone who doesn't use the phone?
[12:53] <pitti> well, if that's an explicit decision, it's IMHO a really bad one
[12:53] <ogra_> could be
[12:53] <nik90_> pitti: hey, can I make a request to backport autopkgtest 3.4 to trusty pls :) ?
[12:53] <pitti> as it doesn't give you any clue how to revert the action
[12:53] <ogra_> i dont know if our designers dogfood what they design :P
[12:53] <rickspencer3> mpt, JohnLea ^ I'm asking about the fact that when I toggle off BT in the indicator, it makes the BT indicator disappear
[12:53] <rickspencer3> I'm curious if this is a bug or is by design?
[12:53] <rickspencer3> in any case, it is currently one of my most serious annoyances on the phone :)
[12:53] <pitti> nik90_: you can just download and use the .deb on trusty, but I can file a backport request, yes
[12:54] <nik90_> pitti: that's what I did yesterday
[12:54] <nik90_> pitti: but I would lose out on updates then to autopkgtest
[12:54] <JohnLea> rickspencer3, this problem came up in user testing and should be fixed by the updated indicator reveal interaction
[12:54] <pitti> nik90_: how do you mean?
[12:54] <rickspencer3> JohnLea, wow, we had to user test that?
[12:54] <rickspencer3> we really need more dogfooding :)
[12:55] <pitti> nik90_: oh, you mean if there will be any SRUs to autopkgtest
[12:55] <nik90_> pitti: as in if you issue an update say 3.4.1, then I won't get it if I install the deb
[12:55] <rickspencer3> JohnLea, can you tell me more about "updated indicator reveal interaction"?
[12:55] <pitti> nik90_: yeah, I just synced 3.4.1 to utopic :)
[12:55] <rickspencer3> that sounds like feature work, and I haven't heard any plans for that
[12:55] <pitti> nik90_: but it's the same with backports, they also need an explicit update
[12:55] <nik90_> pitti: oh
[12:55] <ogra_> rickspencer3, shake your phone til the indicators reveal
[12:55] <ogra_> :)
[12:55] <JohnLea> rickspencer3, no, we didn't need to test for it, we knew it was an issue before testing, that's why a solution was already designed for this exact problem before user testing was even complete ;-)  But user testing validated this issue
[12:56] <pitti> nik90_: TBH, if you want the latest and greatest, just run it out of git -- that's what we do on our production CI
[12:56] <rickspencer3> JohnLea, so, my second question ... is there feature work that you expect to happen to fix that?
[12:56] <JohnLea> rickspencer3, hard to describe, best way to understand it to play with the prototype we have built
[12:57] <rickspencer3> I'll take that as a "yes" you are expecting feature work to fix it
[12:57] <nik90_> pitti: ah ok. Will do that
[12:57] <JohnLea> rickspencer3, yup ;-)
[12:57] <pitti> nik90_: you still need a trusty-backports?
[12:57] <JohnLea> rickspencer3, if you would like to play with the prototype ping vesa and he can send to the launchpad link (I don't have it to hand)
[12:57] <nik90_> pitti: I suppose not. I can just ask people to get the latest and greatest from https://gitorious.org/autopkgtest
[12:58] <pitti> nik90_: err no, not that one -- git://git.debian.org/git/autopkgtest/autopkgtest.git :)
[12:58] <nik90_> pitti: althought that repo seems empty
[12:58] <nik90_> pitti: ah yes
[12:58] <nik90_> I wondered
[12:58] <pitti> Vcs-Git:
[12:59] <pitti> nik90_: and then just replace "adt-run" with /your/checkout/dir/run-from-checkout
[12:59] <nik90_> pitti: ack
[12:59] <JohnLea> rickspencer3, we discussed this at the phone execution and phone leaders meeting yesterday so it is on ppl's radar.  Next step for this specific item is for Vesa to have a meeting with dednick, this is booked in.  BTW, we are tracking resolutions to the user testing issues in the following sheet https://docs.google.com/a/canonical.com/spreadsheets/d/1lpOjog_XSXyu4RRAxNjFIju0IGoJ4GgIy5W6adbQcao/edit#gid=1175362251
[13:06] <mpt> rickspencer3, we didn’t need user testing to reveal the problem (it was flagged last year), we needed user testing to be persuasive enough about it :-)
[13:06] <rickspencer3> not sure who was arguing about it, but
[13:07]  * rickspencer3 shrugs
[13:07] <rickspencer3> so long as we fix it
[13:07] <rickspencer3> it's quite vexing
[13:07] <rickspencer3> however, at least toggling it off doesn't freeze the phone anymore :)
[13:07] <seb128> rickspencer3, do you turn it off that often? is that to spare battery?
[13:07] <rickspencer3> seb128, yes
[13:08] <seb128> does it make that much difference? I used to do that on my android phone, but figured out that bt wasn't using that much, I usually just turn data off nowadays
[13:08] <seb128> (same on my ubuntu phone, though that one doesn't last for a week without charge so I can't tell much of the impact of bt)
[13:08] <rickspencer3> seb128, yes
[13:09] <seb128> k, good to know
[13:09] <rickspencer3> if I turn off bluetooth, my phone makes it through the night charged
[13:09] <rickspencer3> if I leave it on, it is flat in the morning
[13:09] <seb128> (and weird at the same time)
[13:09] <rickspencer3> seb128, well, my other option is to ensure that my BT earbuds are really off
[13:09] <rickspencer3> but it's so much easier to just turn of BT on the phone
[13:09] <seb128> oh, that only happen if you have devices connected?
[13:09] <rickspencer3> seb128, I assume so, yeah
[13:09] <seb128> k, that explains why I see little impact ;-)
[13:10] <seb128> I only connect my car to bt
[13:10] <rickspencer3> ah
[13:10] <rickspencer3> seb128, the other issue is, sometimes my BT earbuds are connected, but in my pocket
[13:10] <rickspencer3> and the phone has no way to know I can't hear :)
[13:11] <seb128> hehe
[13:11] <rickspencer3> I guess I could be more vigilant about turning off the earbuds, but using the UI on the phone is so much simpler and also definitive
[13:11] <seb128> I got bitten a few times by that
[13:11] <seb128> connected to the laptop for testing
[13:11] <rickspencer3> hehe
[13:11] <seb128> and the phone was set on autoconnect
[13:11] <didrocks> or implement NFC in a chip that you put in your ears ;)
[13:11] <seb128> and I was wondering why the sound was not working on the phone anymore :p
[13:12] <rickspencer3> hehe
[13:12] <seb128> speaking of annoyance
[13:12] <seb128> is anyone working on the fact that the clock is often off by a few minutes when waking up?
[13:13] <seb128> I've been late a few times recently due to that
[13:13] <seb128> "oh, it's only 41, still some time"
[13:13] <seb128> where it was like 46
[13:13] <seb128> charles, ^
[13:16] <hackersarchangel> morning everyone
[13:19] <rickspencer3> seb128, oh man, glad to hear that is happening to someone else
[13:19] <rickspencer3> its happening way less than it used to though
[13:20] <rickspencer3> seb128, we for sure need a bug report for that, I think
[13:20] <seb128> yeah, still happening though
[13:22] <jibel> seb128, rickspencer3 there was a bug for that and mark fix released, but obviously not fixed. I'll file a new one.
[13:23] <seb128> jibel, thanks, that's what I though
[13:24] <rickspencer3> thanks jibel
[13:25] <rickspencer3> jibel, could you please tell me in the link when you have it, and if you include info that I could add to the bug when I observe the issue, that would be super great :)
[13:26] <seb128> rickspencer3, the output from the command mentioned on https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1328646/comments/36 is probably useful
[13:27] <seb128> of course now that I want to try that the clock is correct
[13:27] <dbarth> seb128: hey
[13:27] <dbarth> seb128: i think https://code.launchpad.net/~dbarth/ubuntu-system-settings/location-apps/+merge/232575 is in better shape now
[13:27] <rickspencer3> seb128, right, exactly :)
[13:27] <rickspencer3> it's a very "sometimes" thing
[13:33] <cyphermox_> rickspencer3: it is supposed to disappear, but most agree that's wrong :)
[13:38] <ogra_> sergiusens, why dont i see ro.adb.secure on mako ... did we explicitly rip that out ?
[13:38] <sergiusens> ogra_: I have no knowledge of that
[13:38] <ogra_> hmm, k
[13:43] <mvo_> alex-abreu: hi, would you mind if I upload https://code.launchpad.net/~mvo/unity-webapps-qml/update-deps/+merge/233023 ? trivial change - or will a new version land anyway soon(ish)?
[13:43] <sergiusens> Saviq: hey, how easily can you reproduce the hintsystem issue?
[13:44] <sergiusens> is it just reboot until it happens?
[13:45] <alex-abreu> mvo_, you can definitely do it yes
[13:45] <mvo_> thanks!
[13:46] <charles> seb128, that sounds similar to the rendering bug that dednick fixed recently in unity8
[13:46] <seb128> cyphermox_, if you need a bug for tracking that, https://bugs.launchpad.net/ubuntu/+source/indicator-bluetooth/+bug/1285951
[13:46] <charles> seb128, how recently did the the "clock is off by a few minutes" bug happen to you?
[13:46] <seb128> charles, yeah, that's still happening though (and the indicator info are correct on dbus)
[13:46] <seb128> charles, 15 minutes ago on the current rtm image
[13:47] <Saviq> sergiusens, flashing triggers it especially, reboots not so much
[13:47] <Saviq> sergiusens, so like 75% of flashes I end up with the hint being wrong
[13:47] <charles> seb128, just to confirm I'm reading you correctly, the time string that the indicator's putting out on the bus is the correct time, but the time being rendered on the screen is out of sync & wrong?
[13:47] <sergiusens> Saviq: on mako, right? I'm doing that with no luck
[13:47] <seb128> charles, correct
[13:48] <seb128> charles,
[13:48] <Saviq> sergiusens, both mako and krillin
[13:48] <seb128> charles, the lock screen/indicator were indicating 28 and the dbus call/real clock was 32
[13:48] <Saviq> sergiusens, I'm not wiping though
[13:48] <sergiusens> Saviq: when it happens to you again, can you run udevadm --debug trigger --subsystem-match=block
[13:48] <sergiusens> Saviq: I wiped and didn't; same
[13:50] <Saviq> sergiusens, flashing now, let's see
[13:50] <charles> seb128, open a unity8 ticket for it and ping dednick about it, this sounds like a variant of bug #1328646
[13:50] <seb128> charles, k, jibel said he would open a bug
[13:50] <charles> ack
[13:50] <sergiusens> Saviq: thanks; I'm trying to avoid a workaround here :-)
[13:51] <charles> jibel, you might want to reference back to 1328646 and when you file & ping dednick, since this sounds like a similar bug or a regression to that
[13:52] <charles> jibel, could you send me the bug # after you file it?
[13:52] <jibel> charles, it is not a regression, more likely similar bug but the time difference is just a few minutes
[14:04] <cwayne1> mardy: so i included an icon in my click pkg and used a relative path in the .provider, but nothing shows up still
[14:05] <mardy> cwayne1: what version of ubuntu-system-settings-online-accounts do you have installed?
[14:05] <cwayne1> mardy: 0.4+14.10.20140827-0ubuntu1
[14:07] <mardy> cwayne1: this fix landed just yesterday: 0.4+14.10.20140903-0ubuntu1
[14:08] <cwayne1> mardy: ah ok
[14:08] <cwayne1> mardy: did it land in rtm as well
[14:10] <jibel> rickspencer3, charles bug 1365530
[14:29] <mardy> cwayne1: I don't know, sorry
[14:31] <cwayne1> mardy: looks like its not in RTM yet, got it working on devel-proposed
[14:35] <ogra_> bzoltan, i think you missed my ping earlier, how is the sdk landing for the adbd swithc looking ?
[14:35] <bzoltan> ogra_:  landed today on both Utopic and Trusty
[14:35] <bzoltan> ogra_:  feel free to test
[14:35] <ogra_> yay
[14:35] <ogra_> well, i ran into some unexpected behavior on krillin first ...
[14:36] <ogra_> but good to know it landed ... that was the last external change i needed
[14:37] <bzoltan> ogra_:  if you have the 3.1.1+14.10.20140903.3-0ubuntu1 version of the qtcreator-plugin-ubuntu package then it should do the trick
[14:38] <ogra_> bzoltan, awesome, perfect !
[14:41] <hackersarchangel> new bug, not sure if it’s Google (I doubt it) or the Accounts program. When adding a Google account, instead of exiting the tool that creates them it goes to an Ubuntu page.
[14:42] <hackersarchangel> And since I can’t exit that without hitting cancel or closing System-Settings, it doesn’t make the account.
[14:42] <ogra_> hackersarchangel, the html is slightly to big ... there is an accept button next to the cancel
[14:43] <ogra_> try scrolling sideways
[14:43] <hackersarchangel> I mean once I hit that.
[14:43] <hackersarchangel> It then asks me for permission to accept Ubuntu for the various components.
[14:43] <hackersarchangel> Then it dumps me to the Ubuntu page instead of exiting.
[14:43] <dobey> hackersarchangel: that sounds like a bug in the oauth plug-in in ubuntu-system-settings-online-accounts
[14:43] <hackersarchangel> Ok, I wasn’t sure where to label it so I didn’t even file anything.
[14:44] <dobey> or in online-accounts itself possibly
[14:44] <hackersarchangel> But I agree that sounds right.
[14:44] <dobey> file it against ubuntu-system-settings-online-accounts
[14:44] <hackersarchangel> Just something I noticed trying to re-add my Google accounts for work/personal.
[14:44] <hackersarchangel> Ok.
[14:44] <hackersarchangel> Will do.
[14:45] <ogra_> note down the channel and image number in the bug too
[14:45] <seb128> dbarth, mardy: is that location panel working for you? here it lists camera + 3 empty lines (e.g without title/icons)
[14:45] <hackersarchangel> ok so channel utopic-proposed, #221
[14:45] <hackersarchangel> correct?
[14:45] <ogra_> yep
[14:46] <hackersarchangel> Awesome. I’m contributing in some small way!
[14:46] <ogra_> most of us test the rtm image (which due to extra QA is a bit behind)
[14:46] <ogra_> so it is important to know in advance that th eutopic image is broken before we sync that stuff over into rtm
[14:47] <hackersarchangel> Right. Is RTM just the utpoic image?
[14:47] <hackersarchangel> **utopic
[14:47] <hackersarchangel> or is that somewhere else (I’m using Multi-Rom to image my phone)
[14:47] <ogra_> rtm is the "release to manufacturer" image that will be sent out to OEMs that build phones
[14:48] <dbarth> seb128: the 3 empty lines are probably the same issues i fixed in that location branch
[14:48] <ogra_> packages that enter utopic need an extra sync into a special archive
[14:48] <ogra_> to show up in rtm
[14:48] <seb128> dbarth, what location branch?
[14:48] <dbarth> seb128: the trust store registers all access requests, even fom unconfined apps
[14:48] <dbarth> seb128: https://code.launchpad.net/~dbarth/ubuntu-system-settings/location-apps/+merge/232575
[14:48] <ogra_> we have a group of QA people explicitly testing each bit that is supposed to be synced
[14:49] <hackersarchangel> Gotcha, so I personally am not able to test RTM because it’s not public (like I was already thinking)
[14:49] <ogra_> it is public :)
[14:49] <hackersarchangel> Also what language is this being coded in because I’m willing to at least make an effort to help in coding as well.
[14:49] <ogra_> http://system-image.ubuntu.com/ubuntu-touch/ubuntu-rtm/14.09-proposed/mako/
[14:50] <ogra_> ubuntu-device-flash --list-channels |grep rtm
[14:50] <ogra_> ;)
[14:50] <hackersarchangel> Ah. That may not be in Multi-Rom, and that’s my only problem is I need this phone for a daily driver and I can’t seem to nail it down just yet.
[14:50] <hackersarchangel> A couple of broken things with my carrier I think, but I need to have a good sit-down and look at it.
[14:51] <hackersarchangel> Mainly trying to troubleshoot SMS issues, once I get that fixed I can make this my daily driver.
[14:52]  * ogra_ uses his ubuntu phone as daily driver :)
[14:53] <hackersarchangel> ogra_, any idea as to why I can make phone calls but not send SMS? Or at least where to start digging, syslog wasn’t helpful in debugging.
[14:53] <ogra_> what device is that ? nexus4 ?
[14:54] <dobey> Tassadar: hi. any chance to get the ubuntu-rtm channels building for hammerhead?
[14:54] <Tassadar> uuh
[14:54] <Tassadar> um
[14:55] <Tassadar> not sure there's the space for it
[14:55] <Tassadar> how long version history do you need (this includes deltas)?
[14:55] <dobey> i don't know, deltas would be good to have, yes
[14:56] <hackersarchangel> nexus 5
[14:56] <hackersarchangel> using an MVNO on Sprint
[14:56] <hackersarchangel> and it’s not MMS I’m worried about
[14:56] <Tassadar> dobey: devel-proposed has 20 right now
[14:56] <Tassadar> I'll add rtm with 5
[14:57] <Tassadar> *devel-proposed has 10
[14:57] <dobey> oh, 20 is way too many
[14:57] <dobey> maybe make devel-proposed have 5 too?
[14:58] <dobey> hmm, i wonder what is required exactly on the server, for it to work with system-image
[15:00] <Chipaca> kenvandine: hiya. any chance you'll be shepherding verterok's tests branch through the train?
[15:00] <Tassadar> dobey: what's different in rtm?
[15:00] <Tassadar> also, which channel of rtm?
[15:01] <Tassadar> because ubuntu-touch/ubuntu-rtm is just a "flavour", it has several channels
[15:01] <dobey> right, it has 14.09 and 14.09-proposed
[15:01] <kenvandine> Chipaca, yes, i plan to
[15:01] <dobey> 14.09-proposed would be the one to start with i guess
[15:02] <Tassadar> of 14.09 and 14.09 proposed have the same sheme as devel and devel-proposed, it takes less space
[15:02] <Tassadar> (the images are shared between them)
[15:02] <Tassadar> okay, I'll add those to
[15:02] <Tassadar> two
[15:02] <dobey> ok
[15:02] <Chipaca> kenvandine: excellentastic
[15:02] <Tassadar> I wonder if my android app can handle ubuntu-touch/ubuntu-rtm/ path (it has two levels
[15:02] <Tassadar> )
[15:02] <hackersarchangel> ogra_ it’s a Nexus 5 on Sprint’s network using an MVNO
[15:03] <Chipaca> kenvandine: i'll be building on the tests tomorrow when adding functionality to the helper, thus why i asked
[15:03] <kenvandine> Chipaca, cool
[15:03] <Chipaca> i'm sure "thus why" is wrong
[15:03] <Chipaca> anyway. tea and code.
[15:03] <Tassadar> hmm
[15:04] <dobey> Tassadar: do you know if the actual server reuires the python/etc bits? or can i just rsync static content?
[15:04] <Tassadar> well the things which generate the server content need python
[15:04] <sergiusens> Saviq: no luck?
[15:04] <Tassadar> if you just wanna host it, you just need webserver
[15:04] <Tassadar> oh, 14.09 and 14.09-proposed are just aliases
[15:04] <Tassadar> that's solved then)
[15:05] <dobey> Tassadar: right. i'm just wondering if i need to run the python on the server, or if i can run it locally and then rsync the output somewhere
[15:05] <Tassadar> you can run it locally
[15:07] <dobey> Tassadar: because i have 4TB of RAID locally, and a hosting plan with basically infinite space. so i was thinking maybe i could set up something to get them built locally, and host the images on my web host
[15:07] <Saviq> sergiusens, had problems flashing...
[15:07] <Saviq> sergiusens, but the dbus call comes up empty now...
[15:07] <cwayne1> mzanetti: btw, could you send me a .click for the latest release of tagger?
[15:07] <sergiusens> Saviq: empty? that's more concerning
[15:08] <Saviq> sergiusens, http://pastebin.ubuntu.com/8234208/
[15:09] <sergiusens> Saviq: what if you specify a partition? (append p[1-9])
[15:09] <dobey> anyway, need to get lunch
[15:09] <Saviq> sergiusens, all empty
[15:10] <Saviq> sergiusens, firing udevadm now
[15:10] <sergiusens> pitti: is that possible ^^
[15:10] <Saviq> sergiusens, still empty... :/
[15:11] <sergiusens> Saviq: I don't understand how this is possible
[15:11] <Saviq> sergiusens, shall I reboot or pick some more details up from the device?
[15:11] <sergiusens> Saviq: maybe udisks2 died, can you kill it?
[15:11] <Tassadar> oh wait
[15:12] <Tassadar> devel is alias of 14.09
[15:12] <Tassadar> not the other way around
[15:12] <Tassadar> interesting
[15:12] <Saviq> sergiusens, still empty ¿?
[15:14] <kenvandine> pmcgowan, i found a new branch from diego for the update on battery stuff, i created a MP for it to see if we get a CI build
[15:14] <kenvandine> pmcgowan, i haven't looked at it closely yet
[15:14] <sergiusens> Saviq: missing an arg
[15:14] <pmcgowan> kenvandine, great thanks
[15:17] <Saviq> sergiusens, you mean the actual partition path?
[15:17] <Saviq> sergiusens, still empty
[15:17] <Saviq> sergiusens, I started with the path
[15:17] <sergiusens> Saviq: adb shell gdbus introspect --system -p -d org.freedesktop.UDisks2 -o /org/freedesktop/UDisks2/block_devices/mmcblk0 /org/freedesktop/UDisks2/block_devices/mmcblk0p2 | grep System
[15:17] <jgdx> kenvandine, seb128, time for a review of a small fix? https://code.launchpad.net/~jonas-drange/ubuntu-system-settings/fix-1365167-numerous-custom-background-issues/+merge/233376
[15:18] <seb128> jgdx, k
[15:20] <Tassadar> dobey: okay, it is generating the images, will be ready in about an hour
[15:20] <Tassadar> it is following flo on the s-i.u.com, so it will start at image version 22
[15:21] <seb128> jgdx, those issue are not that numerous btw
[15:22] <pmcgowan> seb128, just 3 ;) I exaggerate
[15:22] <jgdx> seb128, pat's words :p
[15:22] <jgdx> also, there were three issues, so…
[15:23] <seb128> pmcgowan, btw it's suboptimal to list differents issue in one report like that
[15:23] <seb128> it makes it confusing to know what to do when you fix only 1 of the issues
[15:23] <seb128> list the bug to be closed? don't? hold on the other fixes? open new bugs
[15:23] <seb128> it also makes crossed discussions about the different points confusing
[15:23] <seb128> or said differently, please don't do that ;-)
[15:23] <kenvandine> seb128, ugh... merge conflict in his branch, that complicates things
[15:23] <seb128> kenvandine, who?
[15:24] <kenvandine> seb128, in this branch he's using the BatteryInfo from the battery panel
[15:24] <kenvandine> diego
[15:24] <seb128> ah
[15:24] <pmcgowan> seb128, I thought they were related, but ack
[15:24] <kenvandine> i assume that is different than what he did in the other branch that you didn't like right?
[15:24] <kenvandine> seb128, ^^
[15:24] <seb128> kenvandine, yes, he was using qtsystems
[15:24] <kenvandine> ok
[15:25] <seb128> though the battery info are buggy on krillin
[15:25] <kenvandine> so this is better then
[15:25] <seb128> like the last charge info is sometime weird
[15:25] <seb128> jgdx, that background branch is buggy for me, if I pick an image and do "cancel" it's added to customs anyway... is that wanted, it feels wrong
[15:25] <jgdx> seb128, that's the core of the issue
[15:26] <kenvandine> i guess i need to fix the conflicts and resubmit
[15:27] <seb128> jgdx, "cancel" feels wrong, and that dialog has no title, it's confusing
[15:27] <seb128> jgdx, I guess the first step imports, then the dialog is a "do you want to use it"?
[15:27] <seb128> but having no title and just "cancel"/"define" doesn't convey that
[15:27] <seb128> to me it looked like "cancel the import?"
[15:27] <seb128> pmcgowan, ^
[15:27] <jgdx> where is that?
[15:27] <jgdx> I get "Preview" then "Cancel" / "Set"
[15:27] <seb128> jgdx, background panel :p
[15:28] <seb128> I click "add image"
[15:28] <seb128> pick one in gallery
[15:28] <pmcgowan> seb128, agree its confusing
[15:28] <seb128> click "pick" (or whatever is the right button in english)
[15:28] <seb128> it bounces me back to u-s-s with a preview of that image
[15:28] <seb128> with a dialog with no title
[15:29] <seb128> and "cancel" "set" buttons at the bottom
[15:29] <seb128> if you do "cancel" there it adds the image anyway
[15:29] <seb128> which is confusing
[15:29] <seb128> I liked it better before when it was undoing the action
[15:29] <jgdx> that part is not quite up to speed with the design, I think it would make sense if it was
[15:30] <jgdx> dialog with no title though, I get a semi transparent title
[15:31] <seb128> oh
[15:31] <seb128> it's just that I can't read it on that image/with that contrast
[15:31] <seb128> I see it after rotating
[15:32] <jgdx> that step should be "Choose Area" really. And you should be able to zoom/pan the image.
[15:33] <seb128> k
[15:33] <seb128> well, at default of having that, the buttons should be like
[15:33] <seb128> "import only" "set as current"
[15:33] <seb128> or something like that
[15:33] <seb128> rather than "cancel" "define"
[15:34] <seb128> speaking of "set as current"
[15:34] <seb128> is the "unlock with pin" dialog from the unity8 lock supposed to use the custom image like the lock screen itself?
[15:34] <seb128> Saviq, mterry, ^ do you know?
[15:35] <Saviq> seb128, yes
[15:35] <Saviq> seb128, ah wait
[15:35] <Saviq> no
[15:35] <Saviq> dunno
[15:35] <mterry> seb128, what's the unlock with pin dialog?
[15:35] <Saviq> don't think so
[15:35] <Saviq> mterry, passcode lockscreen vs. set passcode
[15:36] <mterry> Saviq, seb128: ah you mean the background image for the greeter -- design asked that we *not* use it for the lockscreen
[15:36] <seb128> mterry, sorry, passcode
[15:36] <seb128> whatever is the second option in security
[15:36] <seb128> the one where you put some digits to unlock your greeter
[15:36] <seb128> shrug
[15:36] <mterry> seb128, right -- design wanted that to be the purple background
[15:36] <seb128> the background story is poor
[15:36] <seb128> like you pick a custom bg
[15:37] <seb128> it's used in lock
[15:37] <seb128> but not in dialpad unlock
[15:37] <seb128> and then dash does it own stuff not using the image either
[15:37] <seb128> mterry, thanks
[15:37] <seb128> if I open a bug it should be against ubuntu-ux then I guess?
[15:37] <mterry> seb128, sure
[15:38] <seb128> mterry, btw, I tried to change from swipe unlock to passcode unlock from setting on current rtm this morning, I got an error about the auth type not supported and the ui then displayed "unlock with passphrase" selected
[15:38] <pitti> sergiusens: sorry, was in a meeting -- possible that the gdbus introspect is empty? that usually means that this object doesn't exist
[15:38] <pitti> Saviq: ^
[15:38] <seb128> mterry, is that known?
[15:38] <pitti> Saviq, sergiusens: check udisksctl dump ?
[15:38] <seb128> mterry, I picked "swipe" and it changed it without asking me anything
[15:38] <sergiusens> pitti: yeah, the calling was wrong
[15:38] <mterry> seb128, I'm investigating some weirdness around password switching and policykit and all that right now
[15:38] <mterry> seb128, not asking anything is expected
[15:39] <mterry> seb128, if you've already authenticated recently
[15:39] <mterry> seb128, that's policykit caching your auth
[15:39] <sergiusens> pitti: should of known about that tool sooner! thanks :-)
[15:39] <pitti> sergiusens: heh :)
[15:39] <Saviq> pitti, sergiusens http://paste.ubuntu.com/8234473/
[15:40] <sergiusens> Saviq: so     HintSystem:                 false
[15:40] <Saviq> sergiusens, ah
[15:40] <sergiusens> for mmcblk0p*
[15:40] <Saviq> sergiusens, and I think I had too many paths after the gdbus call...
[15:40] <Saviq> somehow I got convinced that's needed
[15:41] <sergiusens> Saviq: is that after running udevadm?
[15:41] <seb128> jgdx, what do you use "fix commited "for btw? (asking because that's the second time I see you use it in a way that feels wrong to me)
[15:41] <sergiusens> Saviq: gdbus confuses me a bit tbh
[15:41] <Saviq> sergiusens, yes
[15:41] <sergiusens> I always end up installing qdbus
[15:41] <Saviq> sergiusens, udevadm doesn't help
[15:42] <sergiusens> pitti: so what if running udevadm trigger doesn't help? Any other suggestion based on ogra_s comment of not restarting udev at all?
[15:42] <jgdx> seb128, merged
[15:42] <seb128> jgdx, when do you use "fix released" then?
[15:42] <seb128> jgdx, fix commited is an "open" status
[15:42] <Saviq> seb128, at least https://wiki.ubuntu.com/SecurityAndPrivacySettings#Phone shows actual dialogs
[15:42] <seb128> e.g it makes the bug still listed
[15:42] <Saviq> seb128, I didn't see any visual designs of that though
[15:42] <pitti> sergiusens: for marking a device as internal? did you check that it's correct in udevadm info --export-db ?
[15:43] <chris______> can someone help me install the new Ibuntu 14.04 this is my first time here
[15:43] <pitti> sergiusens: i. e. did the value get applied, and thus is it a problem on the udev/rule or udisks side?
[15:43] <seb128> Saviq, well, that's the settings side, not the greeter one
[15:43] <Saviq> sergiusens, http://paste.ubuntu.com/8234792/
[15:43] <Saviq> seb128, yes, didn't you ask about the settings side (for setting PIN)?
[15:43] <Saviq> aaagh
[15:43] <Saviq> passcode
[15:43] <jgdx> seb128, I mainly use statuses for my own benefit. To remember where they are. If that's wrong, I'm happy to change my wicked ways
[15:44] <seb128> Saviq, not, I asked about the unity8 screen you get when unlocking the screen
[15:44] <chris______> really not sure how this works how do i speak with someone to help me
[15:44] <sergiusens> pitti: from Saviq's pastebin above, I don't see anything that matches UDISK in there
[15:44] <seb128> jgdx, well, when a fix is uploaded to the distro we use "fix released" so the bug is seen as closed
[15:44] <Saviq> seb128, ok, I'm lost then
[15:44] <sergiusens> pitti: so the udev rule didn't apply
[15:44] <hackersarchangel> chris______: refer to the topic
[15:44] <seb128> jgdx, I assume that's the right one for 1221908
[15:44]  * Saviq reads question again
[15:44] <hackersarchangel> it’s linked to the install guide
[15:45] <hackersarchangel> if any of that is unfamiliar to you, it’s not recommended to try it as it’s still development software
[15:45] <seb128> mterry, k, let me know if you need debug info from my log (or from the next time it happens
[15:45] <pitti> sergiusens: is there a bug # for all that? I've only ever heard bits and pieces of that problem, but don't have the whole picture; a bug is better to attach all the udev/udisks debug data to
[15:45] <jgdx> seb128, okay
[15:45] <sergiusens> pitti: it's the bug you commented on
[15:45] <chris______> hackers archangel where do i find the topic?
[15:45] <pitti> sergiusens: so udevadm trigger --subsystem-match=block doesn't help?
[15:45] <sergiusens> Saviq: can you attach this data there?
[15:46] <pitti> sergiusens: with --verbose it even shows what it does, mmcblk should be amongst it
[15:46] <sergiusens> pitti: nope; I'm just a middleman here, I can't reproduce; it's basically me passing messages between you and Saviq
[15:46] <chris______> where do i find a topic?
[15:46] <Saviq> pitti, sergiusens http://paste.ubuntu.com/8234974/
[15:46] <seb128> Saviq, well, it feels weird that if you set an unlock bg, the lock screen display it, but then you swipe the artwork away and you get the purple default one with a dialpad on top to enter your passcode, then you unlock and get yet another one for the dash
[15:46] <Saviq> and still HintSystem false
[15:47] <pitti> Saviq: right, that should apply any udev rle
[15:47] <pitti> rule
[15:47] <pitti> Saviq: what is the udev rule in question?
[15:47] <sergiusens> pitti: ACTION=="add", KERNEL=="mmcblk0*", ENV{UDISKS_SYSTEM}="1"
[15:47] <Saviq> that
[15:47] <pitti> oh
[15:47] <sergiusens> pitti: I wonder if it's the ACTION
[15:47] <pitti> where's "change"?
[15:48] <pitti> yeah, it needs that too
[15:48] <pitti> and udevadm trigger defaults to "change"
[15:48] <pitti> --action=add if you want to do that
[15:48] <sergiusens> pitti: what's the syntax for doing that? ACTION="add|change" ?
[15:48] <pitti> (but don't do that)
[15:48] <pitti> right
[15:49] <sergiusens> Saviq: might hacking that in without a reboot?
[15:49] <sergiusens> I'll add that to lxc-android-config
[15:51] <Saviq> sergiusens, checking
[15:52] <Saviq> sergiusens, \o/
[15:55] <sergiusens> thanks pitti and Saviq
[15:55] <pitti> cool!
[15:56] <Saviq> sergiusens, so think that'll fix the issue?
[15:56] <sergiusens> no just need to figure out if we need to run udevadm once the system settles
[15:56] <sergiusens> Saviq: well you had to un udevadm yourself
[15:57] <seb128> jgdx, the "remove" menu you get if you hold press on the image doesn't seem to be in the spec (https://wiki.ubuntu.com/Appearance#Phone)?
[15:58] <jgdx> seb128, true. I sat that branch back to WIP. I have an idea on how to address the bug and your comments.
[15:59] <nik90_> seb128: hey, is there any particular reason why settings-app doesn't use the header to show the search field like the address book, clock app does?
[15:59] <nik90_> seb128: I could propose a MP for it if you want.
[15:59] <seb128> jgdx, the popup was already there ... is that wanted? I'm asking because it's limited to the previous rectangle which means there are only a few chars that fits, which doesn't look good, especially in locales where the word to fit is longer than english
[16:00] <seb128> nik90_, let me find you the bug, matthew wontfixed that
[16:00] <jgdx> seb128, I don't know.
[16:00] <seb128> jgdx, ok, I'm going to just file the bug
[16:00] <jgdx> seb128, thanks.
[16:00] <nik90_> seb128: oh :/
[16:01] <seb128> nik90_, https://bugs.launchpad.net/ubuntu/+source/ubuntu-system-settings/+bug/1351091
[16:02] <Tassadar> dobey: okay, the image is ready
[16:03] <Tassadar> and it looks like my app can handle the flavour name, nice
[16:03] <Tassadar> but is there anything different in ubuntu-rtm? Oo
[16:03] <seb128> jgdx, https://bugs.launchpad.net/ubuntu/+source/ubuntu-system-settings/+bug/1365577
[16:03] <hackersarchangel> https://bugs.launchpad.net/ubuntu/+source/ubuntu-system-settings-online-accounts/+filebug/656cd69e-3449-11e4-b8d4-d485646cd9a4?
[16:03] <hackersarchangel> ....
[16:04] <hackersarchangel> lemme get a proper link xD
[16:05] <hackersarchangel> https://bugs.launchpad.net/ubuntu/+source/ubuntu-system-settings-online-accounts/+bug/1365569
[16:05] <hackersarchangel> There we go. Finally had a moment to get it all filled out and such.
[16:06] <sergiusens> pitti: mind eyeballing this http://paste.ubuntu.com/8237747/ please?
[16:08] <seb128> Saviq, mterry: opened https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1365578 ... feel free to reassing to ubuntu-ux or whatever is the right triaging
[16:11] <dobey> Tassadar: it's a different distribution on launchpad. all the packages aren't the same as in the normal utopic channels, and it's the focus of testing right now, so it would be good to be able to run it on n5 too
[16:11] <Tassadar> kay.
[16:11] <Tassadar> the 14.09 is empty btw, and I'll have to manually enable it once it has images in it
[16:12] <Tassadar> so notify me when an image is proposed if you remember or need the not-proposed channel
[16:17] <seb128> mterry, Saviq: are the "show indicators/launcher on greeter" settings supposed to work, or did the unity8 side didn't land?
[16:18] <Saviq> seb128, on rtm is in silo 7
[16:18] <Saviq> seb128, in utopic it landed last week
[16:18] <seb128> Saviq, thanks
[16:18] <seb128> I'm on rtm
[16:19] <seb128> seems like the settings landing without unity
[16:19] <seb128> which means we show uis that don't work
[16:19] <seb128> but if that's pending fix that's good enough ;-)
[16:20] <kenvandine> bfiller, is there a bug to track the work to make dialer-app use the dialpad sounds settings?
[16:22] <bfiller> kenvandine: I think I forgot to do that, let me file one now
[16:22] <kenvandine> bfiller, thx
[16:22] <kenvandine> seb128, ^^
[16:23] <seb128> bfiller, kenvandine, thanks
[16:24] <bfiller> kenvandine, salem_ : https://bugs.launchpad.net/telephony-service/+bug/1365583
[16:29] <nik90_> charles: would you like to me test https://code.launchpad.net/~charlesk/indicator-datetime/lp-1354400-add-snooze/+merge/233154 ? Or should I rather wait for the silo PPA?
[16:29] <nik90_> charles: sry just too excited to wait :P
[16:32] <charles> hm, I thought thostr_ was adding that to a silo already, but I don't see it and looks like he's EODed
[16:32] <charles> nik90_, maybe tedg could make a silo for us
[16:32] <charles> no, he's afk too
[16:33] <nik90_> charles: no worries
[16:33] <charles> nik90_, so it'll likely be a couple of hours; if you want to test now go ahead and do it w/o the silo :)
[16:33] <nik90_> charles: but we should try to silo it in before we hit traincon-0..otherwise we will be blocked for some time
[16:34] <charles> nik90_, +1
[16:37] <salem_> bfiller, ok, I can fix this the telephony-service
[16:39] <bfiller> salem_: cool, just sync with kenvandine on the name of the new setting
[16:39] <salem_> bfiller, ok
[16:48] <dobey> Tassadar: cool, thanks
[16:59] <Elleo_> mandel: sounds a reasonable plan to me, I'm on holiday sailing at the moment, so can't really look at anything until monday I'm afaid
[17:17] <dobey> Elleo_: i believe the correct phrasing of that statement is "I'm on a boat!"
[17:31] <ahayzen> Hi, anyone else have no network indicator on #221 ?
[17:32] <hackersarchangel> It’s been sporadic with me.
[17:32] <hackersarchangel> Was doing it on 219 and 220 as well I think.
[17:32] <ahayzen> usually a restart would resolve  but i just did maybe another is required
[17:33] <hackersarchangel> Well it’s not consistent for me though. Almost as if it’s not pulling the state of the network
[17:33] <ahayzen> hackersarchangel, yeah it has been the same for me over the past few images strange
[17:34] <ahayzen> davmor2, popey, have you seen the network indicator sometimes not appearing after boot?
[17:34] <hackersarchangel> mkay so it’s not a specific to one person issue.
[17:35] <ahayzen> hackersarchangel, exactly thought i may have just broken something
[17:36] <dobey> ahayzen: what device?
[17:36] <ahayzen> dobey, nexus 4 (mako)
[17:36] <hackersarchangel> nexus 5 for me.
[17:36] <dobey> oh, ok
[17:37] <dobey> i haven't seen it happen on my mako
[17:37] <dobey> but have seen it happen quite a bit on my n5
[17:37] <ahayzen> dobey, its been a bit random.... now on the 4th boot it has appeared
[17:37] <dobey> usually just the modem doesn't come online or something though
[17:37] <hackersarchangel> hey dopey, what carrier do you have on your N5?
[17:38] <ahayzen> dobey, interesting i wiped my /var/crash network files....and then it booted fine and there is a new one in there for indicator-network-service
[17:38] <dobey> hackersarchangel: t-mo
[17:39] <hackersarchangel> darn lol
[17:40] <hackersarchangel> I have Sprint and I’m having issues with SMS. ahayzen thanks for mentioning the /var/crash folder, I had no idea that existed, and that is showing some SMS files, so something to parse over later.
[17:40] <ahayzen> dobey, hackersarchangel this is the .crash that was generated (note on the boot where it did work) http://pastebin.ubuntu.com/8246143/
[17:42] <dobey> ok
[17:42] <ahayzen> dobey, is ^^ of any use to anyone?
[17:43] <dobey> ahayzen: is your phone configured to automatically upload crash reports?
[17:44] <ahayzen> dobey, erm....maybe....i can manually submit if you want?
[17:44] <ahayzen> dobey, oh i see the .uploaded file
[17:44] <dobey> you probably don't need to do anything then, and it should already be on errors.ubuntu.com
[17:45] <dobey> so hopefully someone will look at it soon
[17:45] <ahayzen> dobey, i should be able to see it somewhere?...
[17:45] <ahayzen> ah damn i don't have permission
[17:47] <dobey> ahayzen: in the privacy settings under system settings, it should have a link or whatever that should take you to the current list of reports from your device
[17:48] <ahayzen> dobey, yeah i got a list of ids but then if i click them i'm not a member of a group to view the error report? oh well at least it is up there for someone
[17:49] <dobey> oh
[18:07] <om26er_> awe_, Hi!
[18:08] <om26er_> awe_, I call my phone, the screen turns on, I hear the ringtone but no notification for calls
[18:08] <om26er_> bug 1365448
[18:11] <awe_> om26er, that sounds like a telephony-service bug, not ofono.  If you hear the ringtone, then ofono has created a call object
[18:17] <om26er> awe_, ok, I talked to telepathy guy and he directed to apparmor guys
[18:18] <jdstrand> if it was apparmor, you should see a denial with 'grep DEN /var/log/syslog'
[18:18] <awe_> om26er, ok, I'll keep any eye on it
[18:18] <awe_> someone catch the hot potato
[18:18] <awe_> ;)-
[18:19]  * ogra_ hands out welding gloves
[18:19] <jdstrand> hey, if there is a denial, I'll jump on it! :)
[18:19] <om26er> jdstrand, https://launchpadlibrarian.net/184014253/that.log
[18:19] <om26er> there is ;-)
[18:20] <jdstrand> those denials are in mediascanner
[18:20] <om26er> jdstrand, scroll to the bottom
[18:20] <jdstrand> ah
[18:20] <jdstrand> why is ofono trying to start pulseaudio? shouldn't it already be running?
[18:21] <awe_> huh?
[18:21] <awe_> ofono doesn't talk to pulseaudio
[18:21] <jdstrand> apparmor="DENIED" operation="exec" profile="/usr/lib/telepathy/telepathy-ofono" name="/usr/bin/pulseaudio" pid=6206 comm="telepathy-ofono" requested_mask="x" denied_mask="x" fsuid=32011 ouid=0
[18:21] <salem_> om26er, here I am
[18:21] <awe_> that's "telepathy-" ofono
[18:22] <salem_> jdstrand, this is telepathy-ofono.
[18:22] <jdstrand> sure
[18:22] <awe_> which is a Qt layer we wrote to interface telepathy to ofono
[18:22] <jdstrand> point is, why is *it* starting ofono?
[18:22] <jdstrand> staring pulseaudio
[18:22] <jdstrand> meh, too many conversations at once
[18:22] <awe_> is pulse dbus-activated?
[18:22] <salem_> jdstrand, tp-ofono starts before pulse, and it queries pulse for the available output devices.
[18:23]  * awe_ ducks out of the conv
[18:23] <jdstrand> salem_: this is a very new denial. is this new functionality?
[18:23] <salem_> jdstrand, yes, we recently landed a change in tp-ofono to deal with audio routes.
[18:23] <salem_> jdstrand, but I personally never had that error here. this is new to me.
[18:23] <jdstrand> salem_: is this on the image or something from a silo?
[18:24] <salem_> jdstrand, this is in the image already
[18:24] <jdstrand> tp-ofono should not be executing pulseaudio
[18:24] <salem_> rsalveti, ^
[18:24] <jdstrand> I'm ok with adding the /proc read entries, but pulseaudio should be started by the session, not executed by tp-ofono
[18:25] <salem_> jdstrand, well, in that case, we need to change the telepathy service job to depend on the pulseaudio upstart job.
[18:26] <jdstrand> that makes a lot of sense to me
[18:26] <salem_> jdstrand, we just need rsalveti opinion on this, as he was the one adding the pulse code and he knows more about the internal.
[18:28] <jdstrand> salem_: is there a but on this?
[18:28] <jdstrand> bug*
[18:28] <salem_> jdstrand, the only problem I see here is that we should start telepathy as early as possible, otherwise if an sms is received in the meantime from ofono and the service is not running, that message will be lost.
[18:29] <salem_> awe_, can we ask urfkill to online modems only after the telepathy service is running?
[18:29] <salem_> just to avoid the scenario I described above.
[18:30] <jdstrand> having tp-ofono start pulseaudio is going to not have pulseaudio be properly managed by the sessoin
[18:30] <awe_> salem_, I wasn't following the conversation, but that doesn't sound like a trivial change
[18:31]  * jdstrand -> meeting
[18:31] <awe_> salem_, can you a file a bug and add your reasoning?  There's still re-work to the initial onlining of the modem, however this would add another level of asynchronicity
[18:32] <salem_> awe_, ok, thanks
[18:32] <rsalveti> jdstrand: pulseaudio gets started by the first one calling it
[18:33] <rsalveti> we also have an upstart job for it, we can block auto-start, something I have on my list
[18:33] <awe_> rsalveti, right dbus-activation
[18:33] <awe_> ;D
[18:34] <rsalveti> salem_: but why is this an issue now?
[18:34] <jdstrand> apparently a change landed in tp-ofono and it is trying to launch pulseaudio cause nothing else tried to
[18:34] <om26er> awe_, In some instances when I restart my phone, my sim isn't picked up, says 'No SIM' a restart mostly works. are there any logs you would want to see ?
[18:35] <salem_> rsalveti, the initial problem is that om26er is experiencing some apparmor denials.
[18:35] <rsalveti> right, but we landed that a few days ago already
[18:35] <jdstrand> but it isn't doing dbus activation. it is doing a straightup exec
[18:35] <rsalveti> jdstrand: guess that's just how pulse works
[18:36] <awe_> om26er, which phone?
[18:36] <om26er> awe_, mako
[18:36] <rsalveti> salem_: but I don't see why such denial would block anything
[18:36] <rsalveti> for example, it could fail to start pulse right after booting the phone
[18:36] <awe_> om26er, sure... the output of /usr/share/ofono/scripts/list-modems
[18:36] <rsalveti> but later on, pulse would already be started
[18:36] <awe_> and possibly the syslog
[18:37] <awe_> which if you want, you can filter for "ofonod" messages
[18:37] <salem_> rsalveti, unless the qpulseaudio engine is getting locked waiting for pulse to start
[18:37] <om26er> awe_, http://paste.ubuntu.com/8252387/
[18:37] <rsalveti> salem_: right, but it gets started at some point
[18:37] <awe_> om26er, not powered online
[18:37] <rsalveti> because we even have an upstart job starting it
[18:37] <awe_> most likely you're hitting urfkill saved-states bug
[18:38] <awe_> checkout /var/lib/utrfkill/saved-states
[18:38] <awe_> if WWAN soft=true, this explains
[18:39] <om26er> awe_, soft=false http://paste.ubuntu.com/8252399/
[18:39] <salem_> I have the same error here, but soft=false
[18:39] <rsalveti> salem_: jdstrand: at that stage pulse is probably up already
[18:39] <rsalveti> salem_: wonder if we got a new apparmor rule that blocks the communication with pulse
[18:40] <salem_> rsalveti, that could be it, but I don't know if something has changed there. I have the latest image and I dont see this error.
[18:40] <awe_> om26er, not sure, please a file a bug with the image #, list-modems output, and the syslog
[18:40] <om26er> awe_, ok
[18:40] <awe_> I'll investigate, but am a bit backed up atm
[18:41] <awe_> om26er, what image?
[18:41] <salem_> awe_, sorry, soft=true here, I looked the wrong section.
[18:41] <rsalveti> salem_: jdstrand: will try to investigate the issue
[18:41] <om26er> awe_, 221
[18:42] <awe_> rtm?
[18:42] <rsalveti> first I need food
[18:42] <om26er> awe_, no, its utopic
[18:43] <awe_> om26er, can you try rtm?
[18:43] <jdstrand> rsalveti: we didn't get a new apparmor rule
[18:43] <om26er> awe_, ok, I'll flash that.
[18:43] <jdstrand> sorry was in a meeting
[18:43] <awe_> it shouldn't make a diff, but it's what most are focusing on
[18:43] <awe_> s/most/most if not all/
[18:44] <jdstrand> rsalveti: basically, something changed and it sounds like it works ok if pulseaudio happens to have started, but if it didn't tp-ofono is doing an exec() to start pulse
[18:45] <jdstrand> which I think is wrong. pulse should be managed by the user's session, not launched by various process directly
[18:47] <rsalveti> jdstrand: right, I still have a bug to fix which is disabling the auto-start, and have that handled by upstart
[18:47] <rsalveti> not sure though why it seems pulse failed to start after tp-ofono tried starting it
[18:49] <jdstrand> rsalveti: apparmor blocked tp-ofono from starting it. maybe you meant you wonder why pulseaudio wasn't already started when tp-ofono started?
[18:50] <sergiusens> jdstrand: on some boots I get this: 2014/09/04 15:46:54 Cannot mount /org/freedesktop/UDisks2/block_devices/mmcblk1 due to: org.freedesktop.UDisks2.Error.NotAuthorizedCanObtain: Not authorized to perform operation
[18:50] <sergiusens> jdstrand: any idea how I can make that not be "racy"
[18:51] <sergiusens> davmor2: I think you are being hit by that too ^^
[18:52] <jdstrand> sergiusens: it sounds like the user's seat isn't set up yet. I'm going to refer you to mdeslaur since he has more knowledge here
[18:52] <davmor2> sergiusens: could be.
[18:52]  * kenvandine streams youtube videos to drain the battery intentionally
[18:53] <mdeslaur> sergiusens: what's mounting that?
[18:53] <sergiusens> mdeslaur: "ciborium", user session
[18:53] <sergiusens> mdeslaur: it works most of the time, and then sometimes it doesnt
[18:54] <mdeslaur> ciborium?
[18:54] <sergiusens> mdeslaur: just want to know if my upstart job should wait for something
[18:54] <sergiusens> mdeslaur: yes
[18:54] <nik90_> rsalveti: is this what I think it is https://code.launchpad.net/~rsalveti/indicator-datetime/adding-media-role/+merge/233299 :D
[18:56] <sergiusens> mdeslaur: in the end, it's just a dbus call to Mount from udisks2  on the proper path
[18:58] <mdeslaur> sergiusens: that's weird...I'm really not sure why that would fail like that
[18:59] <mdeslaur> sergiusens: perhaps pitti has an idea
[18:59] <sergiusens> well this is what triggered me asking about the manual override stuff a while back
[19:00] <sergiusens> but I never saw it again and assumed it was my massive tinkering on the system
[19:00] <sergiusens> not the case today
[19:01] <mdeslaur> it needs to be able to talk to policykit, and the user needs a session
[19:01] <rsalveti> jdstrand: why it seems it didn't start after that
[19:01] <mdeslaur> if your job is in the user session, both conditions should be satisfied
[19:02] <rsalveti> nik90_: yeah, this is for the right role when playing alarm
[19:02] <jdstrand> rsalveti: yes, by something else. that is weird. perhaps pulseaudio was crashing
[19:02] <rsalveti> then my next step is to be able to control volume separately per role
[19:02] <nik90_> rsalveti: :) :) cool
[19:02] <sergiusens> mdeslaur: it is; it's just "racy" it seems
[19:02] <rsalveti> jdstrand: yeah, anyway, will try to put the real fix in there
[19:02] <rsalveti> which is not allowing apps to start pulse
[19:03] <sergiusens> mdeslaur: the job starts after unity8 in the sequence of events
[19:03] <jdstrand> \o/
[19:04] <mdeslaur> sergiusens: I guess you'll have to try and see why policykit is denying it
[19:04] <sergiusens> mdeslaur: any tools to do that? or logs
[19:05] <mdeslaur> sergiusens: not sure...is there anything relevant in /var/log/auth.log?
[19:07] <mdeslaur> perhaps that is the first service to use policykit, which results in dbus starting the service, but then it gives up before it comes up...
[19:07] <mdeslaur> not quite sure
[19:08] <mdeslaur> maybe try more than once?
[19:10] <sergiusens> mdeslaur: ok, I can try that; I see a bunch of errors for ofono and logind in auth.log but nothing related to my stuff
[19:14] <sergiusens> like this one Sep  4 15:58:03 ubuntu-phablet dbus[740]: [system] Rejected send message, 2 matched rules; type="method_return", sender=":1.26" (uid=0 pid=1967 comm="ofonod -P stktest,provision,sap,udev,dun,smart,hfp") interface="(unset)" member="(unset)" error name="(unset)" requested_reply="0" destination=":1.2" (uid=0 pid=861 comm="/usr/bin/powerd ")
[19:19] <kenvandine> pmcgowan, btw... i'm making some headway with the battery-check branch ;)
[19:19] <kenvandine> it honor's isCharging nicely
[19:19] <kenvandine> but... remainingCapacity seems buggy
[19:19] <kenvandine> buggy == useless atm :/
[19:19] <pmcgowan> ah
[19:20] <pmcgowan> kenvandine, not sure of the design, is to just to warn the user? not prevent update right?
[19:20] <kenvandine> i'm still working on it though, just need to drain my battery some more ;)
[19:20] <kenvandine> yeah
[19:20] <pmcgowan> ok great
[19:20] <kenvandine> prevent updates when capacity < 50% and not charging
[19:20] <pmcgowan> where is the MR for loction stuff,got a link handy?
[19:20] <pmcgowan> hmm prevent is pretty strong
[19:20] <kenvandine> https://code.launchpad.net/~dbarth/ubuntu-system-settings/location-apps/+merge/232575
[19:20] <pmcgowan> and 50% is large
[19:21] <kenvandine> yeah... i guess we can tweak that
[19:21] <pmcgowan> let me check the design to see
[19:21] <pmcgowan> unles you did
[19:21] <kenvandine> i didn't
[19:21] <kenvandine> either way we need to get remaining capacity somehow :)
[19:24] <pmcgowan> kenvandine, found some guidance
[19:24] <pmcgowan> Whenever the phone is not connected to power and the battery charge is below a safe level, the prompt should have the text “Connect to power before installing the system update.” and only a “Not Now” button (bug 1306752).
[19:25] <pmcgowan> that says download but dont install, and I would say safe level is more like 25% which is where I think we turn indicator red
[19:25] <pmcgowan> I think even 10% is fine
[19:26] <pmcgowan> and if I plug in the prompt needs to change to install and reboot
[19:26] <kenvandine> 10% is risky
[19:26] <kenvandine> what if it's wrong
[19:26] <pmcgowan> right
[19:26] <kenvandine> yeah, i have it changing the prompt when plugged in
[19:26] <pmcgowan> thats what got me thinking, but is it a little wrong or unreliable
[19:27] <pmcgowan> could it say 90 when its 3? or is it just +-10%
[19:29] <jdstrand> jhodapp: hi! ping re> https://code.launchpad.net/~jdstrand/media-hub/1356883/+merge/231962
[19:29] <jdstrand> jhodapp: I added a few more updates. can you review that and apply to trunk so it ends up in the next upload (should go to rtm too)
[19:31] <jhodapp> jdstrand, ok, I've got quite a few to review but I'll put yours in the queue :)
[19:31] <jdstrand> mine is certainly going to be the easiest to review :)
[19:31] <jhodapp> indeed
[19:49] <jgdx> mpt, hey, looking at bug 1365577. Should we remove the action altogether?
[20:02] <mterry> Who knows cgroups?
[20:14] <popey> mterry: ogra_ i think?
[20:14] <mterry> popey, I poked hallyn too in another channel, but no luck yet.  ogra_ do you know enough to help debug this logind/cgroup thing?
[20:15] <ogra_> popey, lol ... you got a high opinion of me ...
[20:15]  * ogra_ guesses he knows less about cgroups than mterry
[20:15] <popey> Actually I do.
[20:24] <jhodapp> elopio, one small comment on your MR
[20:27] <elopio> jhodapp: I will make the change because I don't understand much about laws, but according to the GPL guide, you must put only the years that you touched the file. And if you use a year range instead of listing all the years, you have to explain that usage on your project.
[20:27] <elopio> that's boring, so I'll just make the change :)
[20:27] <jhodapp> elopio, huh, interesting...never knew that
[20:27] <jhodapp> elopio, either way then...I'm sure it varies per country too
[20:29] <elopio> jhodapp: https://www.gnu.org/licenses/gpl-howto.html
[20:29] <elopio> jhodapp: I pushed the change.
[20:29] <elopio> jhodapp: one thing that I do think it's important is that your copyright headers are missing a paragraph.
[20:29] <elopio> but I won't push to change that yet. Better wait for the next cycle.
[20:30] <jhodapp> elopio, k, thanks
[20:32] <jhodapp> elopio, approved
[20:32] <elopio> jhodapp: thanks. When is your next release?
[20:35] <jhodapp> elopio, you'll want to talk to bill's team, they're in charge of mediaplayer-app
[20:35] <jhodapp> elopio, or just propose your MR for a silo
[20:36] <elopio> I would prefer to wait for their next release. But as this is making krillin fail, lukasz might want to get it faster.
[20:36] <elopio> bfiller: any scheduled date for releasing a new mediaplayer?
[20:36] <lool> kenvandine: heya
[20:37] <kenvandine> hey lool
[20:37] <bfiller> elopio: have things been merged there that need a release?
[20:37] <dobey> elopio: that view of the GPL is a bit nonsense. listing every consective year is not sensible. it only makes sense to list separate years, if there was a year where there were no commits to that code. so a projected started in 2010, but with no changes in 2013, and you're adding a change now, "2010-2012, 2014" would make sense
[20:37] <lool> kenvandine: ubuntu-system-settings has this accountsservice-ubuntu-schemas (>= 0.0.3+14.10.20140829) dep, but that's broken with current accountsservice-ubuntu-schemas in ubuntu-rtm
[20:37] <dobey> but it's overly pedantic, and it's not 1990 where nobody uses version control, any more
[20:37] <bfiller> elopio: send me the list of MR's you'd like released and I can do it
[20:37] <kenvandine> ?
[20:38] <lool> kenvandine: probably you meant to bump accountservice-ubuntu-schemas to 0.0.4, then use 0.0.4~?
[20:38] <kenvandine> lool, mterry had bumped that too, it was in silo 3 for rtm
[20:38] <lool> mterry: ^
[20:38] <kenvandine> but this morning i noticed it wasn't in silo 3 anymore...
[20:39] <kenvandine> it was there along with unity8 and system-settings
[20:39] <kenvandine> but this morning there was just the 2 packages
[20:39] <lool> dunno
[20:39] <mterry> kenvandine, right but when someone added a new key to the schemas package, they probably should have bumped the version to 0.0.4 so that system-settings could depend on a clean ">= 0.0.4" line
[20:39] <kenvandine> i thought someone had published it
[20:40] <kenvandine> lets check to see if the changes we needed made it to rtm
[20:41] <lool> kenvandine: I suspect you have enough in there, but with the ~ the version check isn't satisfied:
[20:41] <lool>  accountsservice-ubuntu-schemas | 0.0.3+14.10.20140829~rtm-0ubuntu1 | ubuntu-rtm/14.09/universe | all
[20:41] <kenvandine> yeah
[20:41] <kenvandine> i see my dialpadSoundsEnabled setting did land in rtm
[20:42] <lool> kenvandine: yeah, DialpadSoundsEnabled is there
[20:42] <kenvandine> looks like mterry's setting too
[20:42] <kenvandine> so we just need to make that dep stronger
[20:43] <lool> it feels to me using 0.0.4 might have hinted to look after it, but wouldn't have avoided it; you want to suffix the upstream version with a ~ in case it gets backported
[20:43] <lool> because it's native
[20:44] <lool> and was backported
[20:44] <lool> so ideally we bump it to 0.0.4
[20:44] <lool> and depend on >= 0.0.4~
[20:44] <lool> but really what needs to happen now is updating the dep to 0.0.3+14.10.20140829~
[20:45] <lool> what I dont get is how images can possibly build with this
[20:45] <elopio> bfiller: just this one: https://code.launchpad.net/~canonical-platform-qa/mediaplayer-app/fix1359040-skip_seekbar/+merge/231508
[20:46] <mterry> lool, ah... I forgot about that trick
[20:46] <kenvandine> lool, it isn't an issue for utopic-proposed
[20:46] <kenvandine> because it doesn't have the ~
[20:46] <lool> why is it that this change ended up in silo 4 (HERE stuff)?
[20:47] <lool> that's what I dont get
[20:47] <lool> and not in ubuntu-rtm
[20:47] <kenvandine> because rtm is outdated
[20:47] <kenvandine> failed QA on friday
[20:47] <kenvandine> so we're trying to sync that up
[20:47] <lool> so we've landed stuff in utopic that would have broken in rtm, then we tried landing stuff on our own, that pulled the other changes with the HERE changes
[20:47] <kenvandine> yeah
[20:48] <kenvandine> so there was a bug fix included that introduced a regression
[20:48] <kenvandine> on friday
[20:48] <lool> there's a big flaw here that we might land unrelated breakage
[20:48] <kenvandine> which mterry has fixed and we landed last night
[20:48] <kenvandine> after your HERE stuff
[20:48] <kenvandine> lool, indeed...
[20:48] <kenvandine> that's the downside of syncing the package
[20:48] <lool> it's not just the syncing concept
[20:48] <kenvandine> the alternative though is duplicate MPs
[20:49] <kenvandine> yeah
[20:49] <lool> it's like, *any* issue that we discover from QA at the time of pushing to rtm but that is already in utopic
[20:49] <lool> any other random change in the same package might go into rtm
[20:49] <lool> like here: QA wont retest everything, they would look at testing the wizard (at least that's what I did)
[20:50] <lool> but changes to the settings would go unnoticed
[20:50] <lool> not part of the expected changes in that landnig
[20:50] <kenvandine> yeah, but shouldn't the changes file in the rtm PPA be a hint?
[20:50] <lool> hmm good point
[20:50] <kenvandine> should show the changelog since last trm
[20:50] <kenvandine> rtm
[20:51] <lool> kenvandine: so you're saying we should not try to land that silo of ours until you've fixed this other bug
[20:51] <kenvandine> yes
[20:51] <kenvandine> not in rtm that is
[20:51] <kenvandine> and it has been fixed in utopic now
[20:51] <lool> kenvandine: would you mind landing a change to set the dep correctly? just suffixing with ~
[20:51] <kenvandine> since your landing
[20:51] <kenvandine> sure
[20:52] <kenvandine> but... now we have dbarth in line to land soon
[20:52] <lool> ah and we didn't pick up the change because we were already landed in utopic
[20:52] <kenvandine> i need to step in front of him :)
[20:52] <lool> he wont be installable in rtm anyway
[20:52] <lool> he can add it to his branch if he likes
[20:52] <lool> if it goes in soon
[20:52] <lool> I dont know
[20:53] <lool> I wonder if it's ok for me to pick up the latest source from utopic in the RTM silo when it's fixed
[20:53] <lool> or will that break citrain?
[20:53] <lool> dbarth: you around?
[20:54] <kenvandine> lool, we don't know if his will go in soon... we need to test a little more
[20:54] <kenvandine> this is quick and easy... not much to test
[20:54] <dbarth> lool: yes
[20:54] <lool> kenvandine: ok; would you be able to land this? this is holding up location service stuff
[20:54] <kenvandine> lool, the latest utopic settings is in silo 7
[20:54] <kenvandine> i think
[20:54] <lool> dbarth: if you try to land you ubuntu-system-settings related changes in rtm, it wont be installable there; we need to fix a dep
[20:55] <kenvandine> sorry... silo 15 for rtm
[20:55] <lool> dbarth: we'd like to land it now (before your landing) to unblock the preceeding landing
[20:55] <kenvandine> lool, that was what sil2100 did this morning to test the fixes that failed QA friday
[20:55] <lool> kenvandine: ok; do you need to coordinate with citrain, or can you go straight away?
[20:55] <kenvandine> that's waiting for QA to verify i think
[20:56] <kenvandine> oh... says ready to build?
[20:56] <lool> sorry, we should move to ci-eng
[20:56] <dbarth> lool: go ahead, i'll wait on the side
[20:56] <lool> thanks
[20:56] <lool> dbarth: to be clear, this is unrelated to the HERE changes, we're blocked by it too  :-)
[21:33] <mterry> ogra_, how can I see a change manifest for touch images for non-mako-devel-proposed (which i can see here: http://people.canonical.com/~ogra/touch-image-stats/ )
[21:33] <mterry> ogra_, specifically, the krillin channel for devel-proposed?
[21:33] <ogra_> mterry, the rootfses are identical for one channel
[21:33] <ogra_> so the arch doesnt matter
[21:33] <mterry> ogra_, OK, I just have to be able to match image numbers?
[21:34] <ogra_> http://people.canonical.com/~ogra/touch-image-stats/ has all utopic builds ... http://people.canonical.com/~ogra/touch-image-stats/rtm/ has all rtm builds
[21:34] <mterry> ogra_, is there an easy trick for that?
[21:34] <ogra_> nope, not an easy trick ...
[21:35] <ogra_> mterry, http://ci.ubuntu.com/smokeng/utopic/touch/ ... the second part of the version is the rootfs id
[21:35] <ogra_> this would be non-krillin rtm http://ci.ubuntu.com/smokeng/utopic/touch_stable/
[21:46] <sergiusens> Chipaca: do you have go 1.2 and 1.3 coinstalled?
[21:46] <Chipaca> sergiusens: maybe. why?
[21:47] <Chipaca> sergiusens: who's asking?
[21:47] <sergiusens> Chipaca: I want to ping pong between both, that's all :-)
[21:47] <Chipaca> sergiusens: I do have both installed, yes
[21:47] <sergiusens> just want to know how much pain it involves
[21:47] <Chipaca> switching environs, is all
[21:48] <sergiusens> Chipaca: how did you get 1.3?
[21:48] <sergiusens> with niemeyer's deb generator?
[21:48] <Chipaca> sergiusens: the same way i got 1.2, downloaded the binary distribution
[21:48] <sergiusens> oh, no packaging :-)
[21:48] <Chipaca> correct
[21:50] <Chipaca> sergiusens: i don't know whether the packages are co-installable, i haven't looked. they could be, but i very much doubt it
[21:50] <Chipaca> because otherwise it wouldn't be /usr/share/go/, it would be /usr/share/go1.2/ or somesuch
[21:53] <sergiusens> Chipaca: I'll download 1.3 and keep 1.2 packaged
[21:53] <sergiusens> Chipaca: do you know if we will get 1.3 for utopic at all?
[21:53] <Chipaca> sergiusens: I very much doubt it, at this point
[21:53] <Chipaca> sergiusens: it would be sweet, though
[21:53] <om26er> which directory have unity8 upstart log ?
[21:53] <Chipaca> we get client-side ssl resume whatsit thing
[21:53] <sergiusens> Chipaca: I don't even know what I'd want from that release :-P
[21:54] <Chipaca> sergiusens: client-side ssl resume whatsit thing
[21:54] <Chipaca> :)
[21:54] <sergiusens> Chipaca: I saw you imported net/[something] in your code
[21:54] <Chipaca> sergiusens: ssl session resumption, supported server-side in go 1.1 i think, but only 1.3 for client side
[21:55] <sergiusens> Chipaca: 1.3 is in debian/unstable
[21:55] <Chipaca> sergiusens: in our code? we import *everything* :)
[21:55] <Chipaca> not really, but it feels like it sometimes
[21:55] <Chipaca> sergiusens: yes, 1.3 is in debian/unstable, and broke stuff
[21:55] <sergiusens> oh
[21:55] <sergiusens> so we are not getting it :-P
[21:56] <nhaines> I'm going to peek at the rtm build on my N5.
[21:57] <Chipaca> sergiusens: https://lists.launchpad.net/canonical-tech/msg08182.html
[21:57] <sergiusens> Chipaca: there are no outstanding bugs for golang-go 1.3 though
[21:57] <Chipaca> sergiusens: poke the people responding to that mail?
[21:58] <sergiusens> looks for *that* email
[21:59] <nhaines> Requires a reboot for input; Ubuntu doesn't allow reboot.  Well, abandoning testing in 30 seconds.  Maybe next time.
[22:00] <sergiusens> Chipaca: oh, golang-gc; that's why
[22:03] <Chipaca> sergiusens: ?
[22:04] <sergiusens> Chipaca: gcc-go
[22:04] <Chipaca> sergiusens: ah
[22:05] <Chipaca> sergiusens: if that broke, and if the go packages aren't coinstallable, we aren't getting 1.3 :)
[22:05] <Chipaca> sergiusens: maybe we should make a co-installable 1.3?
[22:34] <n-iCe> hello guys, is ther whatsapp for ubuntu?
[22:38] <nhaines> n-iCe: no.  This is also a question for Whatsapp and not us.  :)
[22:39] <n-iCe> ok
[22:39] <n-iCe> thanks