[00:29] <pngo_> I can ssh login via terminal, but can not via thunar );
[00:30] <pngo_> before ubuntu re-installation I had no problems with thunar
[04:38] <lotuspsychje> good morning
[04:38] <lotuspsychje> you guys read this yet:
[04:38] <lotuspsychje> http://www.omgubuntu.co.uk/2015/01/meizu-announce-triple-boot-ubuntu-phone-month
[04:42] <nhaines> Nope.  What's it about?
[04:42] <nhaines> Also, Betteridge's law of headlines says "no".
[04:43] <lotuspsychje> well like always is meizu confusing users
[04:43] <lotuspsychje> we can only hope 1 of the three Os will be ubuntu touch
[04:43] <lotuspsychje> what do you think?
[04:45] <nhaines> It's possible.
[04:45] <lotuspsychje> im almost sure that Bq phone will be sold out right away for tha price
[04:46] <lotuspsychje> imagine all the users using ubuntu
[04:46] <nhaines> We'll have to see.  It's hard to predict these kinds of things.
[04:46] <nhaines> All I know is that I'll get to hold one soon.
[04:47] <lotuspsychje> you reserved one?
[04:48] <nhaines> No, but aside from other various plans in the works, I'm going to grab aquarius's at SCALE.  :P
[04:48] <lotuspsychje> :p
[04:48] <nhaines> But I expect my Nexus 5 to be featured at the Ubuntu booth at SCALE. :P
[04:48] <lotuspsychje> im curious if they changed alot on the inside, other then you guys developed it
[04:49] <nhaines> That's up to the OEMs.
[04:49] <lotuspsychje> they have their own developers right
[04:51] <nhaines> Hardware and software engineering are orthagonal, though.
[04:51] <nhaines> bq (and probably Meizu) are paying Canonical to do the hardware enablement.
[04:51] <lotuspsychje> ah i see
[04:52] <lotuspsychje> how come canonical cant reveal stuff then<?
[04:52] <lotuspsychje> they must know already whats gonna happen with what company
[04:53] <nhaines> Because no software vendor of any platform is allowed to do so.
[04:53] <lotuspsychje> right
[04:53] <nhaines> The OEMs work with carriers, and jointly they make the announcements.  Never the software vendors (who are under NDA).
[04:55] <lotuspsychje> im planning to start a repair/ubuntu store soon something like system76 with ubuntu machines in my country
[04:55] <lotuspsychje> do i have obligations to canonical?
[04:56] <nhaines> You're going to have to discuss it with Canonical I'd imagine.
[04:56] <lotuspsychje> kk
[06:56] <ramsrambo> Hi! I wanna install ubuntu on my MTV Slash Swipe telecom tablet with MT8389 CPU on it
[06:56] <ramsrambo> Is it possible?
[06:59] <lotuspsychje> !devices | ramsrambo
[08:32] <dholbach> good morning
[08:35] <ranveer> hi
[08:35] <ranveer> how to create a rom for a phone?
[09:34] <JamesTait> Good morning all; happy Skeptics Day! :-D
[09:35] <nhaines> Sounds like my kind of day!
[09:38] <nerochiaro> ondra: good morning, can you please ping me when you have a minute ?
[09:47] <nhaines> So I updated my phone from ubuntu-rtm/14.09 r12 to r13, and now there's no sound device detected.
[11:07] <davidcalle> Hello all, I'm having an MMS issue : can send, can't receive. Any idea where to start debugging that?
[11:07] <mandel> davidcalle, there are several daemons that take care of that, one is nuntium and the other one is udm
[11:08] <mandel> davidcalle, can you grab the logs for both of them, the should both have it in the system logs dir
[11:18] <davidcalle> mandel, so, udm log is at /var/log/ubuntu-download-manager/ubuntu-download-manager.INFO , but where is the nuntium one?
[11:18] <davidcalle> udm -> http://paste.ubuntu.com/9728346/
[11:18] <mandel> davidcalle, AFAIK it is started by upstart
[11:24] <davidcalle> mandel, right, I wasn't looking in ~/.cache : here it is http://pastebin.ubuntu.com/9728436/
[11:27] <mandel> davidcalle, looks like there is one of the fields from the mms format that is not correctly decoded by nuntium, if you show me the logs from udm (uploader) I can take a look to see if it was indeed sent (or at least uploded)
[11:28] <mandel> davidcalle, udm just does a http request, qhen changing to wap we need to read the feedback in nuntium.. we need sergiusens to take a look at what is going on exactly, he was the poor soul that read the specification
[11:34] <davidcalle> mandel, uploader logs : http://pastebin.ubuntu.com/9728486/
[11:36] <mandel> davidcalle, as fas as I can see the issue is reading the push notification in the nuntium side, can you file a bug with the logs and the information of you service provider? It is very very important to add the service provider information since each of them has implemented mms in a diff way (hurray for standards!!!!)
[11:37] <mandel> sergiusens, ^^
[11:38] <davidcalle> mandel, odd thing is that MMS with that sim worked fine a few weeks ago. sergiusens, which specific logs do you need for that bug report?
[11:38] <davidcalle> (...or maybe I just *thought* they worked fine :) )
[11:41] <davidcalle> thanks mandel
[11:41] <mandel> davidcalle, well, is client code, someone could have change something in the server.. it is weird, but could happen
[11:42] <mandel> davidcalle, would be nice to know if those messages ever got back, and maybe log the 200 response from the server (yes, they do send a response as a 200 even if it is an error and it is emebded as html)
[11:49] <davidcalle> mandel, oh my. What I know for sure is that, since last week receiving an mms from someone else or myself is consistently failing (when it's from me, it's marked as sent on the phone and visible on the sent mms history from the service provider).
[11:50] <davidcalle> Works on Android.
[11:50] <mandel> davidcalle, yet, the mms is not received in the other side, correct? That looks like we are nto parsing the 200 with the error correctly in the nuntium side
[11:50] <mandel> davidcalle, either we are screwing up with the formatting to the mms or something of the kind
[11:54]  * davidcalle is doing one more test with a benevolent co-worker.
[12:13] <davidcalle> mandel, so, just confirmed that sending works fine. Receiving (or the moment I'm supposed to receive) doesn't trigger anything new in the nuntium log.
[12:14] <mandel> davidcalle, ok, you have to wait for the push notification to grab the mms.. might take some time
[12:14] <mandel> davidcalle, not too long, but some time
[12:14] <davidcalle> mandel, ok, I'm keeping tail -f nuntium.log running anyway.
[12:15] <mandel> davidcalle, perfect
[12:15] <mandel> davidcalle, while we wait, I'll have lunch :)
[12:15] <davidcalle> mandel :)
[13:04] <davidcalle> After 1h, I guess it's safe to say that nuntium has failed to notice these mms (no new log).
[13:08] <davidcalle> mandel, sergiusens ^
[13:55] <jgdx> abeato, hi, how does mtksettings behave when the sim/modem does not offer umts?
[13:56] <abeato> jgdx, do you mean how it behaves for the slot that is just 2G?
[13:57] <mandel> davidcalle, yes, is not getting it
[13:57] <jgdx> abeato, I mean if umts is lacking/not supported at all
[13:58] <abeato> jgdx, in that case the property Has3G should not appear
[13:59] <jgdx> abeato, great. +1
[14:03] <cwayne> why isn't timezone set automatically by location?
[14:03] <nomanx> hello all
[14:07] <danrik> what does ubuntu-touch do for data syncrhonization?
[14:07] <danrik> I mean - where is data going to be stored?
[14:08] <danrik> Would there be an option to sync to user-owned data storage?
[14:18] <mandel> kenvandine, I need to delete that merge proposal and do a new one, I hope is not a big issue
[14:18] <kenvandine> mandel, no problem
[14:21] <pete-woods> can anyone help me with my store uploads
[14:21] <jgdx> kenvandine, new libqofono debs fixed nailed it. However, it will require a (sensible) change to all users of the ofono manager.
[14:21] <jgdx> s/fixed/
[14:21] <pete-woods> I'm getting an error "New version: 1.0.18-134 (missing upload) on 2015-01-13 14:20 - 0 minutes ago"
[14:21] <pete-woods> this is if you dig into the feedback tab
[14:22] <kenvandine> jgdx, great!
[14:23] <kenvandine> jgdx, so we need a code change in settings?
[14:26] <jgdx> kenvandine, seems so. manager.modems is not prepopulated.
[14:27] <kenvandine> jgdx, bummer, so uploading libqofono will break settings...
[14:27] <jgdx> yes
[14:27] <kenvandine> i guess i need to add a Breaks: ubuntu-system-settings << blah
[14:28] <jgdx> indeed
[14:28] <kenvandine> jgdx, what's the exposure like?  just 2 plugins right?
[14:28] <jgdx> kenvandine, privacy, about, cellular, phone
[14:28] <jgdx> so four
[14:29] <kenvandine> jgdx, can you prepare the fix?
[14:29] <jgdx> kenvandine, yeah, but should we not use a shared component for this?
[14:29] <kenvandine> this is going to make it much harder to land the fix in rtm... but it's a must
[14:30] <kenvandine> jgdx, you mean our own wrapper for manager?
[14:32] <jgdx> kenvandine, not exactly. A component that creates the libqofono bindings we need. Right now that's done per plugin.
[14:32] <jgdx> but that'll be an overkill for e.g. about, since it does not need more than one or two bindings, as opposed to cellular which needs tons
[14:33] <kenvandine> yeah, i don't think we should optimize for API breaks
[14:33] <kenvandine> this shouldn't be common
[14:33] <mterry> rickspencer3, in bug 1409003, you say you can't reproduce anymore with image 190.  Have you had any "luck" since filing with reproducing it?
[14:34] <kenvandine> jgdx, and i guess the actual break is the fix for the issue you were looking for :/
[14:34] <kenvandine> so not worth patching it out
[14:34] <rickspencer3> mterry, no, no one can reproduce it, including me
[14:35] <jgdx> kenvandine, what do you mean 'patching it out'?
[14:43] <cwayne> Elleo: got launching cutespotify from scope working :)
[14:44] <Elleo> cwayne: awesome :)
[14:45] <Elleo> cwayne: it'd be cool to have your spotify scope aggregated in the music scope, is that planned?
[14:45] <cwayne> Elleo: unsure, good idea though
[14:46] <Elleo> cwayne: I'm going to try and figure out why the URI handler stuff isn't getting called if cutespotify has to be launched first at the weekend, which should make that more useful too
[14:46] <cwayne> Elleo: i wonder if we could package both app and scope in one click.. it'd be fun to try as the app's cpp and the scope's go :)
[14:46] <cwayne> Elleo: awesome
[14:46] <Elleo> cwayne: I'd certainly be cool with that
[15:05] <seb128> mterry, rickspencer3, that bug, I see regularly a similar one, not sure it's the same issue, but phone doesn't resume when pressing the power button, it takes some 10-15s and it's really slugish
[15:05] <rickspencer3> seb128, right, so I think that is different
[15:06] <rickspencer3> seb128, I think what happens there is that apps are shutting down and don't get quite enough time to finish their work before the phone suspends
[15:06] <ogra_> seb128, do you have a custom wallpaper for the lock screen ?
[15:06] <rickspencer3> so when you resume, they all race to finish their work
[15:06] <rickspencer3> I believe this is being fixed
[15:06] <ogra_> iirc there were issues with scaling down the image which causes slowness on resume
[15:06] <seb128> ogra_, yeah, but a small one and it's not happening in a consistant way
[15:06] <ogra_> ah, k
[15:07] <seb128> the screen doesn't turn on for 15 seconds and when it does there is the power down dialog
[15:07] <seb128> and I often can't unlock
[15:07] <seb128> it's like the phone was in a busy loop
[15:07] <ogra_> weird, i never have that
[15:07] <seb128> even when I manage to unlock it's slugish
[15:07] <seb128> I've that like every other day
[15:07] <seb128> rickspencer3, I doubt it's it, I often have no app running or used in the past day
[15:08] <seb128> rickspencer3, I mostly use my phone as a phone, e.G just sms and calls and that happens sometimes when I didn't use anything since I booted it
[15:08]  * ogra_ shakes his head ... 
[15:08] <seb128> it usually happens when I'm outside though, not when home
[15:08] <ogra_> ... as a phone ... lol
[15:08] <seb128> ogra_, :-)
[15:08] <rickspencer3> seb128, does that happen when you are away from home?
[15:08] <ogra_> :)
[15:08] <seb128> yes
[15:09] <rickspencer3> seb128, does it happen when you are at home?
[15:09] <seb128> no
[15:09] <seb128> as I just wrote
 it usually happens when I'm outside though, not when home
[15:09] <seb128> but I don't need to receive smses for it to happen
[15:09] <rickspencer3> seb128, ok, so I think that what you have there is the Location Service/Network Manager bug that tvoss fixed
[15:09] <ogra_> did these QtNetworking changes ever make it in ?
[15:09] <seb128> rickspencer3, oh ok, is that on a rtm image yet?
[15:10] <rickspencer3> seb128, yes, quite recently, but not a promoted image, I think
[15:10] <rickspencer3> seb128, it was when I was testing that fix in a silo last Friday that I ran into the mysterious vanishing sms issue
[15:10] <seb128> rickspencer3, I'm using r188
[15:10] <seb128> rickspencer3, http://people.canonical.com/~lzemczak/landing-team/ubuntu-rtm/188.commitlog suggests it has the nm fix?
[15:11] <ogra_> 188 is definitely the last promoted one
[15:12] <rickspencer3> seb128, so you think you have the fix and you are still getting it?
[15:12] <rickspencer3> I was getting it solidly 100% of the time
[15:12] <rickspencer3> I am on r191 and never get it anymore
[15:13] <seb128> rickspencer3, r188 has the fix if I read correctly the url I just shared
[15:13] <seb128> and I got that bug today at lunch
[15:13] <seb128> so yeah, still getting it
[15:13] <seb128> to me the issue looks a bit similar to bug #1409003
[15:13] <seb128> expect I don't need to receive smses to have it
[15:14] <ogra_> https://lists.ubuntu.com/archives/rtm-14.09-changes/2015-January/000996.html
[15:14] <ogra_> that is in 189
[15:14] <rickspencer3> seb128, if your phone settles after 10 or 15 seconds, then I think it's the "the system needs time to finish doing work before suspending" bug
[15:14] <seb128> ogra_, that change is a settings one to display the correct mac
[15:14] <seb128> ogra_, http://people.canonical.com/~lzemczak/landing-team/ubuntu-rtm/188.commitlog is the nm fix
[15:14] <ogra_> right
[15:14] <seb128> "dbus daemon spinning with NM AP properties change event"
[15:15] <seb128> rickspencer3, which is weird, because that's a freshly booted phone that I didn't use
[15:15] <seb128> like there is no app running
[15:15] <seb128> but alright
[15:15] <rickspencer3> seb128, yeah, not sure it's app's tbh, not sure what it is
[15:15] <seb128> rickspencer3, in those cases it's normal that it takes > 10s for the screen to turn on and then that the shutdown dialog displays?
[15:15] <rickspencer3> seb128,  a lot of people are getting what you describe
[15:16] <seb128> k
[15:16] <rickspencer3> seb128, hmmmm, that sounds like much more like the "fixed" NM/Location issue
[15:16] <seb128> anyway, I'm happy to help debugging that one by providing info
[15:16] <seb128> if anybody is interested feel free to ping me
[15:16] <seb128> rickspencer3, I mentioned it because it looked a bit like the bug you asked about earlier
[15:16] <rickspencer3> seb128, thanks
[15:16] <rickspencer3> seb128, I'm not trying to dismiss your concerns, at all
[15:16] <seb128> rickspencer3, I've the nm fix, so either that doesn't work or there is another similar issue
[15:17] <rickspencer3> just trying to slot it into my mental model
[15:17] <rickspencer3> seb128, yeah
[15:17] <rickspencer3> it could be that I just had bad luck, and the sms thing was a coincidence
[15:17] <rickspencer3> and since then I've had good luck, since I don't get the issue so bad
[15:17] <seb128> I get that issue several times a week
[15:17] <seb128> I'm going to try to look at the dbus traffic next time
[15:18] <rickspencer3> but I definetly get the issue where I turn on the phone, the power dialog is there, and it is hard to dismiss because the phone feels busy
[15:18] <rickspencer3> seb128, that would be awesome
[15:18] <seb128> the issue is that I usually get it outside when I don't have my laptop with me to adb to the device
[15:18] <rickspencer3> of course, it happens when you need to use your phone, if you are anythink like me
[15:18] <seb128> rickspencer3, do you know if there is a bug open about the busy/power dialog issue?
[15:19] <seb128> yeah, today it happened at lunch when I wanted to call somebody :p
[15:19] <rickspencer3> mterry, ^ ?
[15:19] <rickspencer3> seb128, for some reason, I think mterry is on it
[15:19] <mterry> seb128, there are a couple bugs...
[15:20] <seb128> mterry, hey, ok, I'm regularly getting one of those, so if you need debug info I can try to get some ;-)
[15:20] <seb128> just let me know
[15:20] <mterry> seb128, bug 1383277 or bug 1409003 might be relevant to you
[15:21] <mterry> seb128, I am having a hard time reproducing myself.  I can sometimes get it to happen on my everyday phone, but when I try with a test phone, no luck
[15:22] <mterry> seb128, which version are you on?
[15:22] <seb128> mterry, r188
[15:22] <mterry> OK, that's the latest promoted one, I believe?  k
[15:22] <mterry> that also implies krillin I think?
[15:23] <mterry> I've been trying to reproduce on mako
[15:23] <mterry> (my dogfood phone is mako and is able to hit it)
[15:23] <mterry> seb128, what are your symptoms?  Does it involve an incoming text or call?
[15:23] <seb128> mterry, yeah, krillin
[15:23] <seb128> no, none of those
[15:24] <seb128> it usually involve being outside for some hours and wanting to text somebody or check what time it is
[15:24] <mterry> seb128, does it sound like https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1383277/comments/20 ?
[15:24] <seb128> I never get it when working/connected to the computer/at home
[15:25] <ogra_> when logged in via adb the phone doesnt suspend
[15:25] <mterry> seb128, do you get it disconnected from computer but still at home?
[15:25] <seb128> mterry, sort of
[15:25] <mterry> seb128, i.e. if you are on wifi and hanging out at home?
[15:25] <seb128> mterry, I don't think I noticed it at home no
[15:25] <seb128> could be when out of wifi range or something
[15:25] <dholbach> Saviq, could it be that https://bugs.launchpad.net/ubuntu/+source/unity-scope-click/+bug/1343263 is at large again?
[15:26] <dholbach> at least jounih mentioned this behaviour to me
[15:26] <seb128> mterry, usually for the it's "press the power button, nothing happens, press again wondering if the first press worked, get puzzled wondering if the phone ran out of battery, see the phone turning on with the shutdown dialog displayed"
[15:26] <seb128> mterry, like it takes > 10s to turn the screen on, and it usually has the power down dialog by then
[15:27] <ogra_> well ...
[15:27] <ogra_> the second press causes the dialo to appear
[15:27] <seb128> mterry, but I usually press several time the button so I'm unsure your on/off caase
[15:27] <seb128> next time I'm going to try to be patient and just press once and wait some 10s
[15:27] <ogra_> yeah
[15:28] <ogra_> i think the dialog behaves just fine ... the bug is the delay
[15:29] <seb128> right
[15:29] <ogra_> did you check /var/crash if it got files whose timestamps match your delay ?
[15:29] <seb128> no crash
[15:29] <ogra_> might be apport kicking in on resume and immediately eating all resources
[15:29] <ogra_> k
[15:38] <rickspencer3> ogra_, is there something that I could install on my phone that would make a log of what processes are taking up CPU at a certain time?
[15:38] <rickspencer3> it seems like:
[15:38] <rickspencer3> 1. we can only reproduce the bug in real life, we don't have lab conditions where we can trigger it
[15:38] <ogra_> well
[15:38] <ogra_> whatever you would install would have to keep the phone from suspend
[15:38] <rickspencer3> 2. we can't get info about what it is actually doing
[15:39] <rickspencer3> ogra_, arg
[15:39] <mterry> ogra_, well the dialog shouldn't be showing....  The problem is that the delay seems to be blocking handling the "power button released" signal so the phoen thinks you were holding down the power button
[15:39] <ogra_> to be able to operate :)
[15:39] <rickspencer3> classic debugging of an issue in production
[15:39] <ogra_> yeah
[15:39] <ogra_> mterry, right, i just mean that the bug isnt in the dialog but in the phone behavior
[15:40] <rickspencer3> right, we need some way to find out what is keeping the phone busy on resume
[15:40] <mterry> ogra_, right -- the last issue like this that I fixed was in unity8's event handling, but not sure where this one lies yet.  Still can't reliably reproduce in lab conditions  :)
[15:40] <ogra_> yeah, i have never seen it at all
[15:40] <ogra_> and i used my phone for 4 weeks on the same image
[15:40] <mterry> ogra_, lucky  :)
[15:40] <rickspencer3> I have to say, it's light years better now that the NM/Location issue is fixed
[15:41] <mterry> ogra_, no need to brag  ;)
[15:41] <rickspencer3> that made my phone unusable
[15:41] <rickspencer3> I got into the habbit of turning it off before i left the house, and then turning it on again when I was out of range
[15:41] <rickspencer3> of my AP
[15:42] <rickspencer3> ogra_, so, there is nothing that can log processes that can be suspended when the phone suspends?
[15:42] <ogra_> well, we would have to integrate it with the lifecycle somehow
[15:42] <rickspencer3> hmmm
[15:42] <ogra_> so it gets stopped with suspend and immediately gets started on resume
[15:42] <rickspencer3> sounds like that might be a useful debugging tool
[15:43] <rickspencer3> ogra_, could we simply write an app that does that, and write an app armour profile that gives it necessary permissions?
[15:43] <ogra_> but if you run something like top from a script or some such i guess it would keep you awake if you dont integrate it with the lifecycle
[15:43] <ogra_> sure, would have to be unconfined etc
[15:43] <rickspencer3> ogra_, how hard would that be to write?
[15:44] <ogra_> i guess not harder than an other unconfined app :)
[15:44] <rickspencer3> ogra_, well, I don't know enough to write an app that runs top and makes a log, etc...
[15:45] <rickspencer3> do you think that's something you could write in an hour or so?
[15:45] <rickspencer3> or *cough* that someone could write?
[15:45] <ogra_> not atm, i'm fully swamped with snappy stuff atm
[15:45]  * rickspencer3 nods
[15:54] <dobey> logs processes that can be suspended, or logs processes that /were/ suspended?
[15:55] <rickspencer3> mterry, ogra_ so tvoss tells me that I can just use top in the terminal
[15:55] <ogra_> dobey, loges the cureent process state constantly ...
[15:55] <ogra_> hmm
[15:56] <ogra_> that *might* work, but will indeed onyl show you the state after you unlocked
[15:56] <dobey> ogra_: but it can't do that if it's suspended before other things get suspended?
[15:56] <ogra_> you want to know what happens before you unlock
[15:57] <ogra_> dobey, well, we need a snapshow of the processes between resume and unlock ...
[15:57] <dobey> so i think it would have to be something outside the lifecycle
[15:57] <ogra_> *snapshot
[15:58] <dobey> it would have to run when powerd gets the "resume" signal, and stop when the screen is unlocked, right?
[15:58] <rickspencer3> ogra_, oh? I thought we just wanted to know what was so busy after resume
[15:59] <ogra_> dobey, well, it can go on running
[15:59] <ogra_> important is that it starts as soon as the system resumes and takes top snapshots or some such
[16:00] <dobey> well you need to know when the screen was unlocked in the log i guess, so you know where the breaking point is
[16:00] <ogra_> just dumping them to a log file every second
[16:10] <seb128> kenvandine, hey, was it really better to workaround that password entry mask issue in settings than fixing the sdk?
[16:12] <kenvandine> seb128, it's debatable as to it even being a bug, it's more of a design thing
[16:12] <kenvandine> the SDK doesn't directly provide it, it's from the Qt TextField
[16:12] <kenvandine> which behaves the same way
[16:12] <seb128> kenvandine, design/mpt clearly stated it's a bug on the mp
[16:13] <seb128> kenvandine, did you read his comment?
[16:13] <kenvandine> i think so :)
[16:13] <kenvandine> at one point i read them all... i also tested it without our sdk
[16:13] <kenvandine> and it did the same thing
[16:13] <seb128> hum, k
[16:13] <mpt> Do you get a curse put on you if you change Qt code? ;-)
[16:14] <kenvandine> mpt, no... of course not :)
[16:14] <kenvandine> mpt, and i did re-open the sdk task
[16:14] <kenvandine> because i'd rather it be fixed in the sdk
[16:14] <mpt> I saw that, thank you
[16:14] <kenvandine> but until they agree, we worked around it
[16:14] <kenvandine> inconsistency bugs me... i really want to see it handled in the sdk
[16:15] <kenvandine> but the debate went on long enough, so we jfdi
[16:18] <mpt> I must have missed the debate … I don’t see anyone in the bug report claiming that it shouldn’t be fixed in the toolkit, at least
[16:18] <kenvandine> mpt, the toolkit task got closed
[16:18] <kenvandine> and we had some chats on irc
[16:19] <kenvandine> pmcgowan, ^^  fyi
[16:20] <mpt> Oh, true. (I was confused by the later shuffling from the project to the package.)
[16:20] <kenvandine> pmcgowan, i'll defer the beating on this to you :)
[16:21] <kenvandine> mpt, you can try to convince pmcgowan to bump the priority for the sdk :)
[16:22] <pmcgowan> kenvandine, mpt no debate, just need to get to it
[17:08] <seb128> tedg, hey, have you seen bug #1410176 ?
[17:11]  * tedg looks
[17:13] <tedg> seb128, Pretty sure that's related to this Vala/Pulse bug, I have a work around in a branch that's in review. https://bugzilla.gnome.org/show_bug.cgi?id=741485
[17:13] <seb128> tedg, great, thanks
[17:14] <seb128> tedg, did you try the change Luca suggested on that bug to the pulse vapi?
[17:15] <popey> ricmm: is bug 1404302 on your radar?
[17:15] <tedg> seb128, I *think* so, but I'm not sure (before holiday). Much current on my system doesn't have it.
[17:16] <tedg> seb128, But honestly, I think that's just horrible defaults by Vala. Why would you assume a callback isn't async.
[17:16] <tedg> Anyway, tired of arguing it.
[17:17] <seb128> k
[17:19] <tedg> seb128, The work around isn't hard, you just have to not capture variables.
[17:40] <seb128> tedg, well, I'm not picky on how we fix it, just decide on one way and get the fix submitted for review ;-)
[17:42] <mandel> kenvandine, is there a way to test the pausable downloads in an easy way? I remeber you had a script to follow
[17:45] <kenvandine> mandel, i just install old clicks
[17:45] <mandel> kenvandine, do you have a url of one so I can grab it?
[17:51] <kenvandine> mandel, sure... hang on
[17:52] <kenvandine> http://people.canonical.com/~alan/clicks/2014-10-28-204844/
[17:52] <kenvandine> mandel, i tend to grab a few from there
[17:59] <mandel> kenvandine, thx
[17:59] <ogra_> stgraber, was the addition of the "hidden" field in channels.json announced somewhere ?
[18:00] <ogra_> we just had quite some confusion with the channels vanishing
[18:07] <stgraber> ogra_: it's been there right from the beginning
[18:07] <ogra_> well, the hiding of the -proposed channels is new
[18:43] <sergiusens> ogra_: --show-image for the channel should also work fine
[19:03]  * kenvandine wonders how some of these tests ever passed
[19:04] <kenvandine> jgdx, on my rtm device, the about page tests are all failing because it was expecting a PageComponent
[19:04] <kenvandine> instead of ItemPage
[19:04] <kenvandine> no idea how the vivid tests are passing!
[19:04] <kenvandine> -        if name == b'PageComponent':
[19:04] <kenvandine> +        if name == b'ItemPage':
[19:04] <netlore-mobile> 13 seems better than 12 here at least
[19:05] <kenvandine> fixes the about tests on rtm... still puzzling how this passes on vivid!
[19:06] <netlore-mobile> I stopped using proposed last year because I wanted to make phone calls... . is it better now?
[19:14] <dobey> huh
[19:17] <kenvandine> pmcgowan, bingo!  the rtm test failures started with upower 0.99 transition... we need to sync python3-dbusmock to rtm
[19:17] <kenvandine> for the dbusmock template
[19:18] <kenvandine> the version in utopic and vivid includes a fix for a regression
[19:21] <pmcgowan> kenvandine, awesome
[20:16] <ahayzen> Hi, I have this issue on rtm mako where init and dbus-daemon are using in total ~10% CPU constantly...is there any way I can see what it is doing?
[20:19] <pmcgowan> ahayzen, https://wiki.ubuntu.com/DebuggingDBus#How_to_monitor_the_system_bus
[20:19] <ahayzen> pmcgowan, thanks
[20:20] <dobey> oh my, where has all my battery gone
[20:20] <pmcgowan> ahayzen, you could try running dbus-monitor right off I think
[20:20] <dobey> and i don't even have wifi enabled right now
[20:21] <ahayzen> pmcgowan, lots of mtp stuff..."starting".."stopping"
[20:22] <pmcgowan> ahayzen, definitely open a bug and add that data
[20:23] <ahayzen> pmcgowan, .... i'm using the terminal app as last time i plugged it in it stopped...
[20:23] <pmcgowan> ahayzen, sure, interesting
[20:23] <ahayzen> pmcgowan, so i need to dump the output into a file first :)
[20:24] <tvoss> pmcgowan, mind giving me backlog
[20:24] <pmcgowan> tvoss, http://pastebin.ubuntu.com/9734780/
[20:25] <tvoss> pmcgowan, thanks
[20:25] <tvoss> pmcgowan, should we track on a separate bug?
[20:25] <pmcgowan> tvoss, I think so
[20:25] <mandel> kenvandine, so.. udm was fix, the issue is that horrible three boolean state tracking code, cleaning that crap as we speak :-/
[20:26] <tvoss> pmcgowan, okay, we can converge bugs if we find that they are related
[20:26] <ahayzen> pmcgowan, this was the output... http://pastebin.ubuntu.com/9734788/ ... which project do i report it against?
[20:27] <pmcgowan> tvoss, what do you think ^^
[20:28] <kenvandine> mandel, oh, so part of the problem was in udm?
[20:28] <mandel> kenvandine, no no, talking with udm the memory management
[20:28] <mandel> kenvandine, and the tree bool state tracking
[20:28] <kenvandine> ok
[20:28] <mandel> kenvandine, plus async calls and threads == lots of crap
[20:29] <tvoss> pmcgowan, probably best to start with mtpd
[20:29] <tvoss> pmcgowan, ahayzen https://launchpad.net/mtp
[20:30] <ahayzen> pmcgowan, interesting as soon as i unplug it, it goes back to the 10% cpu with init, dbus-daemon, mpdecision
[20:30] <ahayzen> tvoss, thanks
[20:30] <tvoss> ahayzen, sure, thanks for reporting :)
[20:31] <pmcgowan> ahayzen, that could explain some things, good find
[20:35] <pmcgowan> ahayzen, please pass me the bug # when filed
[20:35] <ahayzen> tvoss, pmcgowan, i've reported bug 1410506, if i find any more info/steps i'll add it to the bug
[20:35] <pmcgowan> great
[20:35] <tvoss> ahayzen, thx
[20:35] <ahayzen> pmcgowan, i wonder if its worth restarting and seeing if i can get it into the bad state again...
[20:36] <pmcgowan> sure
[20:43] <ahayzen> pmcgowan, ok managed to get it to happen again :)
[20:44] <ahayzen> pmcgowan, i'll double check and then add my steps to the bug
[20:44] <pmcgowan> awesome
[20:44]  * ahayzen hopes it isn't random
[20:48] <popey>    /23
[20:48] <popey> bah
[20:49] <ahayzen> pmcgowan, i've updated the steps, do you think it matters which version of mtp is on the PC end?
[20:51] <pmcgowan> ahayzen, it could
[21:11] <jgdx> cyphermox, pmcgowan: bluetooth audio works well on krillin in my volvo, FYI. +++
[21:12] <jgdx> kenvandine, suddenly it started failing?
[21:17] <kenvandine> jgdx, still passes in vivid
[21:17] <kenvandine> but afaict it shouldn't pass in vivid
[21:18] <kenvandine> it passes with my fix on rtm and it fails without my branch
[21:18] <kenvandine> so puzzling
[21:18] <kenvandine> jgdx, but... the real fix for the problem brendand hit was dbusmock in rtm
[21:18] <kenvandine> i have a sync from vivid prepared in silo 3
[21:21] <pmcgowan> jgdx, nice
[21:28] <jgdx> kenvandine, what's up with dbusmock?
[21:28] <colombeen> hi guys, first time here... just wanted to know if there are any phones being developed atm with ubuntu phone os?
[21:28] <kenvandine> jgdx, the upower template had a regression
[21:28] <jgdx> kenvandine, oh
[21:28] <kenvandine> which was fixed in the version we have in utopic and vivid
[21:28] <kenvandine> but never made it to rtm
[21:28] <jgdx> fun
[21:28] <kenvandine> took a while to figure that out...
[21:29] <jgdx> !devices | colombeen
[21:29] <jgdx> colombeen, not sure that answers your question, actually.
[21:29] <kenvandine> the logs do not really tell you that upower template was broken
[21:29] <jgdx> kenvandine, but services missing will be logged?
[21:30] <jgdx> or maybe it just failed silently?
[21:30] <kenvandine> jgdx, not missing...
[21:30] <jgdx> k
[21:30] <kenvandine> signal emitted with wrong signature
[21:30] <kenvandine> not logged
[21:31] <kenvandine> jgdx, what i don't understand is the AboutPage tests
[21:31] <kenvandine> https://code.launchpad.net/~ken-vandine/ubuntu-system-settings/about_page_test_fix/+merge/246350
[21:31] <kenvandine> jgdx, ^^
[21:31] <kenvandine> all the tests in test_about fail on rtm, because of that
[21:32] <kenvandine> but they are passing on vivid... puzzling
[21:32] <kenvandine> weee
[21:36] <kenvandine> jgdx, woot... with silo 3 and silo 22 I get 100% AP test pass :)
[21:36] <jgdx> kenvandine, +1, though I still don't understand that piece of code.
[21:36]  * jgdx dances
[21:36] <jgdx> but then stops.. https://wiki.ubuntu.com/Networking#cellular-connection
[21:44] <jgdx> mpt, ^ that's really hard to do
[21:46] <pngo_> how can I install calendar-app?
[21:48] <pmcgowan> pngo_, in the app scope search for it, go to the store and download
[21:48] <colombeen> !help
[21:48] <colombeen> !commands
[21:49] <pngo_> pmcgowan, how come pkcon install calendar-app is not working?
[21:49] <pmcgowan> whats it doing?
[21:50] <pngo_> can not find package
[21:51] <pmcgowan> pngo_, its not installed by default, did you copy it over to the phone
[21:51] <pmcgowan> pngo_, easier to get it from the store
[21:51] <pngo_> pmcgowan, Im trying to stay away from store
[21:52] <pmcgowan> pngo_, do you have the .click for the app?
[21:52] <pmcgowan> pngo_, then do
[21:53] <pngo_> pmcgowan, not sure what .click is
[21:53] <pmcgowan> adb shell sudo -Hu phablet pkcon install-local  /pathtoclickonthephone
[21:53] <pmcgowan> oh
[21:53] <pmcgowan> its like a deb but different
[21:53] <pmcgowan> click package for apps
[21:53] <colombeen> any phones that actually run ubuntu phone os like they should (completly working and without needing android on the device)? was looking on the page with devices but couldn't find what i was looking for (maybe i missed it)
[21:54] <pmcgowan> colombeen, we use the hardware device support from android only
[21:54] <pngo_> pmcgowan, how and where do I install .click?
[21:54] <pmcgowan> colombeen, there is a phone announced with an OEM coming out in europe soon
[21:55] <colombeen> pmcgowan, which company?
[21:55] <colombeen> haven't seen this anouncement
[21:57] <colombeen> are you still there? pmcgowan?
[21:58] <popey_> colombeen: bq
[21:58] <popey_> colombeen: http://www.omgubuntu.co.uk/2014/12/bq-ubuntu-phone-launches-in-europe-this-february
[21:58] <nexus4user> hi, i have Q
[22:00] <nexus4user> following this guide   https://developer.ubuntu.com/en/start/ubuntu-for-devices/installing-ubuntu-for-devices/ i've got an error  mkdir /root/.cache: permission denied ,pls help
[22:03] <dobey> pngo_: you can install the calendar app from the store scope
[22:06] <rickspencer3> is anyone up who can help someone with Ubuntu device flash?
[22:07] <rickspencer3> sergiusens, ogra_ if you guys are up around and have the time, nexus4user is having some trouble installing
[22:09] <pmcgowan> nexus4user, what command did you run to flash
[22:09] <sergiusens> nexus4user: are you running as root?
[22:09] <nexus4user> not anymore :D
[22:09] <sergiusens> nexus4user: run as a normal user and that will go away
[22:10] <pmcgowan> nexus4user, you may want to use the stable channel
[22:10] <dobey> s/may/will/ :)
[22:11] <pmcgowan> :0
[22:13] <nexus4user> what should I refer to as stable channel?
[22:14] <pmcgowan> ubuntu-device-flash query --list-channels mako
[22:14] <pmcgowan> channel is ubuntu-touch/stable
[22:17] <nexus4user> thanks!
[22:17] <nexus4user> going to try it now
[22:17] <nexus4user> will come back shortly with some feedback
[22:18] <nexus4user> how long should it take
[22:19] <ahoneybun> depends on your internet speed nexus4user
[22:20] <nexus4user> it is fast :D I have already downloaded six archives
[22:20] <nexus4user> from devel
[22:26] <dobey> all the files aren't 300 MB :)
[22:40] <jgdx> kenvandine, getting some test failures with the new libqofono, investigating
[23:01] <kenvandine> jgdx, ok
[23:17] <jgdx> kenvandine, seems our mocking stopped working.
[23:22] <jgdx> kenvandine, I understand why, and fixed it.
[23:24] <jgdx> any libqofo object will not create a dbusinterface if it's not in the modem's list of interfaces. Which is exactly what will fix the 'dead' bindings we're seeing when removing/adding interfaces.
[23:25] <jgdx> but when InterfaceChanged is sent from the modem, the binding will pick it up and start acting accordingly
[23:25] <jgdx> our mocks do not do this
[23:40] <mandel> kenvandine, please take a look at https://code.launchpad.net/~mandel/ubuntu-system-settings/fix-pause/+merge/246367
[23:40] <mandel> kenvandine, but we need to move that logic to state machine, I'll do that asap