[00:19] <lpotter> pngo_: Settings->Cellular->Carrier->APN->
[00:24] <pngo_> lpotter: I can not find APN option
[00:31] <pngo_> I read this: http://askubuntu.com/questions/413438/no-mobile-data-on-nexus-4-ubuntu-touch
[00:31] <pngo_> but I'm not sure how to change options
[00:38] <strigoi818303> Hello room, anyone here worked with the droid incredible 2?
[00:42] <hardtail> does anyone know how to install ubuntu on an asus transformerbook t100?
[00:45] <pngo_> my cellular data has stopped working. can someone tell me what is device name ex: wlan0 to activate it.
[03:40] <pngo_> I would like to back up my txt messages.
[04:14] <Azh> Hey   y'all
[06:23] <Puneet> Hi
[06:23] <Puneet> I have some issues with my Ubuntu 14.04
[06:24] <Puneet> Recently I bought new HP laptop with Ubuntu 12.04 as default OS
[06:24] <Puneet> and upgraded it to 14.04 but post upgrade, I am facing some issues
[06:25] <Puneet> like touchpad stopped working
[06:25] <Puneet> can someone guide me how to fix this?
[06:25] <Puneet> I goggled and try to fix it but could not find the solution
[06:28] <tbr> that's a general #ubuntu thing though
[06:36] <Puneet> Can someone guide me to resolve this issue?
[06:37] <tbr> go to the #ubuntu channel. this channel is about phones.
[07:27] <dholbach> good morning
[09:40] <JamesTait> Good morning all; happy Animation Day! :-D
[11:40] <asac> pitti: can you confirm that our retracers for rtm distro use the right symbol in general nowadays?
[11:40] <asac> ogra was wonderingf if thats the case
[11:41] <asac> ogra_: so i dont have a crash of unity at all  in /var/crash that is newer than oct 24
[11:41] <ogra_> asac, as long as we dont have errors.u.c for rtm having thr retracers doesnt help much ... we also need to get the info somehoe
[11:41]  * asac removes all files
[11:41] <asac> ogra_: we have afaik
[11:41] <asac> bdmurray: ^^
[11:41] <ogra_> i do have a crash right after reboot usually
[11:42] <asac> ogra_: do you have a oops id?
[11:42] <ogra_> unity8, mediascanner-service-2.0, ubuntu-app-launch_desktop-hook
[11:42] <pitti> asac: unsure, I don't run errors.u.c., that's bdmurray's territory; Brian? ^
[11:42] <ogra_> these three are crashing rather reliable here
[11:43] <asac> pitti: right, but the retracing machinary is supposed to do its job, right?
[11:43] <ogra_> ubuntu-app-launch is a recoverable error though ..
[11:43] <asac> ogra_: do you have oops for your crashes?
[11:43] <ogra_> i have a .crash file
[11:43] <pitti> asac: yes, it should; the pieces (ddebs, apt sources, logic etc.) are all there
[11:44] <asac> ogra_: can you paste /var/log/upstart/whoopsie.log ?
[11:45] <asac> so right after reboot i get https://errors.ubuntu.com/oops/b1bc3df0-5e97-11e4-abd6-fa163e373683
[11:45] <ogra_> http://paste.ubuntu.com/8718395/
[11:46] <ogra_> asac, yeah, thats a recoverable error
[11:46] <asac> ogra_: https://errors.ubuntu.com/oops/3f6b473c-5e83-11e4-a8bb-fa163e373683
[11:46] <ogra_> ignore that ... doesnt do harm (apart from producing noise ... cwayne is aware of it)
[11:46] <asac> ogra_: https://errors.ubuntu.com/bucket/?id=/usr/bin/unity8%3A6%3A__assert_fail_base%3A__GI___assert_fail%3A__GI___pthread_mutex_lock%3A__gthread_mutex_lock%3Astd%3A%3Amutex%3A%3Alock
[11:47] <asac> thats the crash you see
[11:47] <asac> looks reasonably ok from retracing pov
[11:47] <asac> playbackstatus
[11:48] <asac> started on oct 10
[11:53] <asac> pitti: any hope that https://errors.ubuntu.com/oops/47162672-5e98-11e4-a34f-fa163e22e467 might get retraced etc.?
[11:53] <asac> or is that fail?
[11:54] <pitti> asac: I don't know what's wrong; I can't look in the errors.u.c. logs
[11:55] <pitti> but it was reported just now, and I think bdmurray said that the retracers have quite some backlog
[11:55] <ogra_> asac, that only has 9 failures in rtm ...
[11:55] <ogra_> (see the "derivatives" column in the table)
[11:56] <ogra_> the actual thing must be way higher
[11:59] <asac> pitti: kk. guess showing retracing status would help figuring if this is going to get better
[11:59] <ogra_> we're looking for a unity8 crash with at least two, if not three digit occurence in rtm
[11:59] <asac> ogra_: well, might be there are various variants
[11:59] <asac> this one surely is real and made my phone screen go black
[11:59] <asac> hehe
[11:59] <ogra_> sure, youre might just be a side effect
[12:00] <asac> might be we get various random ones, instead of just one big one
[12:00] <ogra_> but many people see it often ... the occurence must be really high
[12:00] <ogra_> smoke tests also see constant ones during unity8 tests
[12:01] <asac> really?
[12:01] <asac> then lets go for those
[12:01] <asac> no question asked
[12:01] <asac> fix those and world will be at least more stable :P
[12:02] <ogra_> scoperunner and unity8 itself
[12:02] <sergiusens> asac: ogra_ try this one https://bugs.launchpad.net/ubuntu/+source/unity-scope-scopes/+bug/1386653
[12:02] <ogra_> and media-hub-server at times
[12:02] <sergiusens> ogra_: I know you complained about it at least ;-)
[12:03] <ogra_> sergiusens, nice one
[12:03] <asac> sil2100: ogra_: can we file a bug about the unity8 automation crashers?
[12:03] <ogra_> sergiusens, we are researching unity8 restarts atm though ...
[12:03] <asac> maybe there is something in that?
[12:03] <ogra_> asac, yes
[12:03] <asac> you got it already?
[12:03] <ogra_> asac, i talked to Saviq about it during the sprint ...
[12:04] <sergiusens> ogra_: yeah, I can't triage the bug but should go into the list
[12:04] <asac> do we have a bug?
[12:04] <ogra_> and he was saying he had some ideas but no solution yet
[12:04] <ogra_> no, no bug filed yet
[12:04] <asac> i am sure this will become a big prio
[12:04] <asac> ogra_: sil2100: can you file one so we can track this?
[12:04] <asac> thanks
[12:04] <asac> just post a bug about super crashy RTM phone and point to the automation crashes we see
[12:11] <sil2100> asac: we have one bug for overall smoketesting automation failures, but I guess one separate for this issue might be good
[12:11] <ogra_> so going bachwards through the images i see unity8 crashes in about every second image ... also media-hub ... what i see *constantly* though is unity-scopes_scoperunner
[12:12] <ogra_> (during the uniry8 tests that is)
[12:12] <ogra_> so we shoulld perhaps rather forcus on scoperunner since unity8 and media-hub might just be fallout
[12:24] <JStalin> hi, why I cannot add a contact from recent calls list
[12:24] <JStalin> clicking on a number instantly starts dial
[12:26] <tbr> JStalin: tap and hold
[12:26] <popey> JStalin: i see two ways to do that
[12:27] <popey> JStalin: swipe up recent, swipe number left and tap "add contact"
[12:27] <popey> JStalin: or, swipe up recent, tap number, tap "add contact"
[12:28] <JStalin> when i tap and hold it switches to select mode, when the only thing i can do is remove items from the list
[12:29] <JStalin> but swipe left
[12:29] <tbr> for me that opens a context menu
[12:29] <JStalin> amazing
[12:29] <JStalin> :P
[12:29] <JStalin> it works
[12:29] <JStalin> thanks
[12:29] <JStalin> i don't know how i couldn't noticed it
[12:30] <JStalin> thank you, poor battery life on nexus5 though
[12:30] <popey> how poor?
[12:40] <JStalin> well, i suppose it was fully powered up in the morning or almost fully, although it was powered only by usb connected to computer
[12:40] <JStalin> and now, after 8 hours its almost dead
[12:40] <JStalin> and i didn't do much, just used some wifi at work, answered few calls
[12:40] <ogra_> well, in the recent rtm images there were a good bunch of power related fixes
[12:41] <ogra_> but no idea how much of that was actually driver related for the supported devices and how much was generic
[12:41] <ogra_> (you would indeed only benefit from the generic fixes on N5)
[12:41] <JStalin> afaik it should update automatically, right?
[12:42] <ogra_> if you are on the rtm-proposed channel you would have gotten tzhem with one of the latest images
[12:54] <pngo_> I got new sim card and cellular data stopped working since than. How can I fix it?
[12:58] <jgdx> pngo_, what device are you using? What build of ut?
[12:59] <pngo_> nexus 4. ubuntu 14.10(r243)
[13:00] <zhsj> hi, anyone uses Meizu MX3? is there any available img to flash?
[13:00] <pngo_> jgdx: nexus4, ubuntu 14.10 (r243)
[13:00] <ogra_> pngo_, thats dead beef ...
[13:00] <ogra_> you should really use ubuntu-rtm instead
[13:01] <pngo_> ogra_: can I get a link?
[13:01] <ogra_> just use the rtm or rtm-proposed channel with ubuntu-device-flash
[13:02] <pngo_> ok thank you
[13:02] <ogra_> the --list-channels option should show all rtm channels and the right syntax to use
[13:02] <jgdx> pngo_, and while you're at it, install ofono-scripts
[13:03] <jgdx> pngo_, if the upgrade doesn't fix it, the output from list-modems is very helpful (remember to redact any personal information)
[13:03] <ogra_> also refrain from using versioned channels (14.09 in case of rtm or 14.10 or utopic or vivid ... ) better use devel or devel-proposed ... these are aliases and get moved to the next release automatically ... while all versioned ones (or the ones with release names) stop being updated at some point
[13:05] <ogra_> jgdx, ofono-scripts is preinstalled ;)
[13:05] <jdstrand> barry: hello again. trying to use 'sudo system-image-cli -b 0 -c ubuntu-touch/ubuntu-rtm/14.09-proposed -vvv' on a device to change channels from promoted to proposed, but it is just hanging: http://paste.ubuntu.com/8719192/
[13:06] <jdstrand> barry: (mako)
[13:06] <jdstrand> E1028 07:35:23.824100 25217 apparmor.cpp:112]  org.freedesktop.DBus.Error.Disconnected:Not connected to D-Bus server
[13:06] <jdstrand> that came up a couple of times
[13:06] <jdstrand> so did: W1028 07:35:23.826511 25217 manager.cpp:140]  bc951ef547fc49faa52fe0ba891aaca8could not be stored in the db
[13:06]  * ogra_ blames dbus-cpp :) 
[13:07] <ogra_> our constant blame target recently
[13:07] <jgdx> ogra_, k, thanks
[13:07] <jgdx> :)
[13:20] <jdstrand> barry: ah, it finally timed out: http://paste.ubuntu.com/8719334/
[13:38] <barry> jdstrand: that assertion error *should* be fixed by the udm fix that's in flight
[13:39] <jdstrand> barry: so, I need to install that silo to change channels?
[13:40] <jgdx> seb128, titles that are the text properties of some listelements, shoulnd't they also benefit from the new title element you created (in uss)?
[13:40] <barry> jdstrand: doesn't look like udm is in a silo yet
[13:41] <seb128> jgdx, do you have an example?
[13:41] <jdstrand> hmm
[13:41] <filmee24> hi, ive installed ubuntu on my wetab tablet, but i would upgrade to ubuntu touch, how can i install it?
[13:41] <jdstrand> I guess I'll just need to test my stuff in the emulator
[13:41] <jdstrand> barry: thanks
[13:41]  * jdstrand wonders if the emulator fix for rtm landed yet
[13:42] <jdstrand> barry: thanks
[13:42] <barry> jdstrand: yeah.  i'll keep watching it
[13:43] <jgdx> seb128, time and date -> set time and date
[13:44] <jgdx> huuuge problem for my guerilla testers
[13:44] <filmee24> i would install ubuntu touch on ubuntu tablet
[13:44] <popey> filmee24: i dont think we have a build for the wetab
[13:44] <popey> filmee24: but that's an x86 tablet?
[13:44] <filmee24> yes
[13:44] <seb128> jgdx, that's an ItemSelector
[13:45] <seb128> jgdx, but I changed that one in my mps
[13:45] <seb128> jgdx, but using a Title followed by a selector without text:
[13:45] <popey> filmee24: then perhaps you can apt-get install some of the necessary bits from the repo, but no guarantees it'll work. We don't test on x86 tablets yet
[13:45] <popey> filmee24: what GPU is it?
[13:45] <seb128> jgdx, which is a workaround but does the correct result
[13:45] <jgdx> seb128, oh right, excellent. I saw a bunch of those not changed in cellular, so I figured you left them alone.
[13:45] <jgdx> seb128, can I propose a branch against yours fixing those?
[13:46] <filmee24> idk, ubuntu works on it
[13:46] <seb128> jgdx, sure, please do
[13:46] <popey> filmee24: intel atom cpu?
[13:46] <seb128> jgdx, I put up mine to have a deb to test, I was expecting it to miss some cases, I want to give it a round of testing still before proposing for merging
[13:46] <alexabreu> pitti, hey, quick question about language packs ... the name of the .po file corresponding to a project contained in a given lang LC_MESSAGES (thinking oxide for instance), is picked up from the name of the imported .pot file in the project right?
[13:46] <filmee24> i think intel
[13:47] <jgdx> seb128, makes sense.
[13:47] <popey> filmee24: you could certainly try unity8 on it...
[13:48] <pitti> alexabreu: that confuses several unrelated things
[13:48] <alexabreu> pitti, I thought it would :)
[13:48] <pitti> alexabreu: the .pot file should have the exact same name as the project's translation domain
[13:49] <alexabreu> pitti, right ...
[13:49] <pitti> alexabreu: that's not a strict requirement (the build system might spit out different .mo file names during build), but it avoids confusion
[13:50] <pitti> alexabreu: the .po file names are named ll.po or ll_CC.po, i. e. a locale name or just a language code
[13:50] <alexabreu> pitti, yup ...
[13:50] <pitti> alexabreu: and finally, LC_MESSAGES always specifies a complete locale name (like en_US.UTF_8)
[13:52] <filmee24> im installing unity8 now
[13:52] <pitti> alexabreu: finally at runtie, gettext looks up /usr/share/locale/<LC_MESSAGES prefix>/LC_MESSAGES/<domain>.mo
[13:53] <alexabreu> pitti, my question was not entirely clear hence the confusion I guess ... what I mean is that in the current lang packs the oxide mo file has the wrong name, I have the branches that fixes it and wanted to make sure where the name of the ./mo file in the final langpack was coming from
[13:53] <alexabreu> pitti, you answered my question ..
[13:53] <pitti> alexabreu: ok, good :)
[13:54] <alexabreu> pitti, the domain for oxide should be oxide-qt and afaik it is now oxide ... https://code.launchpad.net/~abreu-alexandre/oxide/fix-pt-BR-po-msgid/+merge/239755
[13:54] <filmee24> i did install unity8, so what should i do now to use it?
[13:57] <filmee24> ?
[14:00] <jgdx> seb128, ListItem.Header / the new element. When to use what?
[14:04] <seb128> jgdx, I'm unsure, I don't understand the distinction, I guess "ping mpt to know"
[14:04] <seb128> jgdx, I went for "use the title element when there is a ':' at the end of the label" mostly
[14:04] <mpt> Except that I answer questions but never pings ;-)
[14:05] <jgdx> seb128, good rule
[14:05] <jgdx> mpt, good rule
[14:05] <seb128> :-)
[14:13]  * mpt compares <https://code.launchpad.net/~jonas-drange/ubuntu-system-settings/security-allow-acceptance-of-here-terms-fixes-1375322/+merge/238419> vs. <https://code.launchpad.net/~mterry/ubuntu-system-settings/location-three-options/+merge/239274>
[14:15] <mpt> kemmko, ^ this is wasting a bit of time … We should have a single design and a single implementation of that block, I think (though the bits around them are different in setup vs. System Settings)
[14:16] <mpt> kemmko, this is similar to how the list of Wi-Fi networks appears both in setup and in System Settings
[14:17] <jgdx> mpt, we implemented "radio buttons" in USS as per the spec. https://launchpadlibrarian.net/187010904/location.phone.png
[14:17] <jgdx> mpt, this means HERE without location detection would make no sense. Looks like you could choose that scenario in the wizard design.
[14:18] <mpt> jgdx, in the setup they look like checkboxes but mterry made them behave like radio buttons
[14:18] <mpt> I’m just wiping my phone so I can see the results :-)
[14:18] <mterry> mpt, that was per the design I was given, don't blame me  :)
[14:18] <jgdx> mpt, to get to the wizard quicly do $ phablet-config welcome-wizard --enable
[14:18] <popey> mterry: you dont need to wipe - just "phablet-config welcome-wi....
[14:18] <mterry> mpt, you don't have to wipe your phone to see the wizard
[14:18] <popey> see^ ☻
[14:19] <jgdx> :p
[14:19] <popey> also, sorry mterry ☻
[14:19] <mpt> mterry, I said I reported the bug on the toolkit, you know I’m not blaming you ;-)
[14:19] <mterry> mpt, I know  :)
[14:19] <mpt> kemmko and I are going to nag gventuri until he agrees
[14:20] <jgdx> just make the ubuntu shape rounder
[14:21] <mpt> That is a drawback of rounded checkboxes, yes … They look needlessly similar to radio buttons
[14:22] <jgdx> mpt, why can't both designs use a boolean plus a checkbox? Boolean for location detection, then a sensistive/insensitive checkbox for HERE?
[14:23] <jgdx> s/boolean/switch
[14:24] <mpt> jgdx, that was my initial design. But even if we managed to avoid it here, there are other cases where radio selection makes much more sense.
[14:25] <jgdx> mpt, as in only one click to enable both loc. det. and HERE?
[14:25] <jgdx> yes, radio is a good, conventional design pattern
[14:28] <dobey> it would be nice if the setting actually stuck after reboot, and the indicator didn't disappear when turning the buttons off in the indicator (because it looks like it just crashed)
[14:28] <dobey> then again, i wonder why the location stuff isn't in the radios indicator
[14:30] <mpt> dobey, what’s the “radios indicator”?
[14:30] <jgdx> dobey, former is by design
[14:31] <jgdx> or was at least..
[14:31] <mpt> jgdx, eh? All settings should persist after restart
[14:31] <dobey> mpt: network indicator. and confusing why those settings aren't connected to the airplane mode
[14:32] <jgdx> mpt, indicator disappearing
[14:32] <dobey> since location detecton is a feature of network connectivity, it seems appropriate there
[14:32] <jgdx> seb128, https://code.launchpad.net/~jonas-drange/ubuntu-system-settings/titles-uis-tweaks/+merge/239858
[14:32] <mpt> dobey, ah … Because while engineers may think of location detection as a networking feature, most people would not
[14:33] <mpt> Even Bluetooth isn’t in there, and that’s much more network-y than location is
[14:33] <dobey> bluetooth doesn't depend on a data connection to be functional
[14:33] <dobey> HERE does
[14:35] <dobey> ironically, enabling airplane mode though, does turn off bt and cause that indicator to disappear, while location and GPS are both still enabled, and indicator is still there
[14:35] <mpt> So does automatic time zone detection (clock), or streaming audio (sound)
[14:36] <mpt> That something depends on a data connection isn’t really interesting … The network menu is primarily for “I don’t have Internet/cellular connection and I want to fix it”
[14:37] <tsdgeos> seb128: https://code.launchpad.net/~aacid/ubuntu-system-settings/missingi18n/+merge/239862
[14:37] <tsdgeos> dobey: ↑
[14:38] <kemmko> mpt: mterry it should look similar indeed but I don't think the option selector is a good solution for the WiFi screen in the oobe
[14:39] <mpt> kemmko, is that because the setup should be less “list-y” in general than System Settings?
[14:39] <tsdgeos> damn this is pretty bad
[14:40] <tsdgeos> "<b>%1:</b> %2".arg(i18n.tr("From"))
[14:40] <tsdgeos> we are assuming all languages use : and that structure :/
[14:40] <dobey> tsdgeos: that is indeed awful
[14:41] <dobey> tsdgeos: especially in hebrew or arabic
[14:41] <tsdgeos> yeah
[14:41] <tsdgeos> let me open a bug
[14:41] <tsdgeos> or just fix it...
[14:42] <dobey> tsdgeos: i think you need a bug, and get it identified as critical, and on the list :)
[14:42] <tsdgeos> arg
[14:42] <tsdgeos> dobey: for https://code.launchpad.net/~aacid/ubuntu-system-settings/missingi18n/+merge/239862  too?
[14:43] <dobey> tsdgeos: probably
[14:43] <tsdgeos> arg
[14:43] <kemmko> mpt. yes, the idea was to make it look different but still Ubuntu because in the end users won't see it again
[14:43] <tsdgeos> dobey: ok ^_^
[14:43] <dobey> tsdgeos: i'm not sure how system-settings manages the pot file, but i'd say you should ensure it's updated in the tree with your branch too, when changing strings like that
[14:43] <dobey> or adding new i18n.tr() calls
[14:44] <tsdgeos> dobey: i've been told we just push to it
[14:44] <tsdgeos> after
[14:44] <tsdgeos> the MR
[14:44] <kemmko> mpt:  where you are right though is that a certain recognition from users end should happen, therefor similarity is a good call
[14:44] <tsdgeos> but what do i know in this world of changing things
[14:45] <mpt> kemmko, I just saw the new “Lock security” screen in the setup, and I can see why you don’t want the same widget for Location ;-)
[14:45] <kemmko> hahaha
[14:45] <kemmko> mpt: exactly
[14:46] <kemmko> mpt: we need radio buttons
[14:46] <mpt> As Tufte might put it, the data-ink ratio is a bit low
[14:47] <kemmko> mpt:  mterry did the right thing to implement the checkboxes behave like radio buttons for now, it is an interim solution until we (hopefully) have radio buttons
[14:47] <mpt> yeah
[14:48]  * mpt runs into bug 1379381 again
[15:02] <dobey> mpt: aside from "make things start faster or prevent unlock until dash is started" i'm not sure how one would fix that; and forcing the screen to be locked would seem a bit frustrating
[15:04] <mpt> dobey, Unity already has a system for customizing the splash screen per-app. So I imagine it would be easy to special-case the splash screen of the Dash. I could be wrong.
[15:07] <dobey> mpt: well, it's the splash screen for unity. it used to say "Dash" but i'm not sure adding an icon or changing the name would be particularly helpful to the user experience at that point. as a user my expectation when i unlock the screen, is that i can access my apps
[15:09] <mpt> dobey, naturally. But if we can’t just show the apps instantly, showing just the header (so it looked like a momentarily-empty Dash) would be less distracting.
[15:10] <mpt> Like we do for System Settings, though it would be a little more complicated since the Dash uses a logo in its header.
[15:11] <dobey> oh, huh. how does system settings do that
[15:18] <mpt> dobey, http://developer.ubuntu.com/apps/platform/guides/splash-screens/
[15:18] <bdmurray> asac: that one is waiting to retrace possibly due to a corrupt core dump
[15:18] <bdmurray> pitti: fyi, there is not a backlog for armhf (only i386 and amd64)
[15:19] <pitti> bdmurray: ah thanks, good to know
[15:19] <asac> bdmurray: waiting for a new, potential better core submission?
[15:19] <asac> gotcha
[15:19] <dobey> oh
[15:28] <cwayne> ogra_: so how do we run autopilot tests now that autopilot is removed from the seed?
[15:28] <ogra_> cwayne, like you always did
[15:28] <pitti> phablet-test-run should just install it
[15:29] <ogra_> right
[15:29] <ogra_> it will magically pulled in as dep
[15:29] <pitti> ogra_: related to that, I taught autopkgtest enough now; it happily runs AP tests with AP being uninstalled, and without r/w
[15:29] <ogra_> (it would have before ... just that this wasnt necessary because it was seeded)
[15:29] <ogra_> pitti, yay !!
[15:30] <cwayne> pitti: ooh, im interested in using autopkgtest as well (as i hear that's going to be CI standard soon)
[15:32] <ogra_> cwayne, phablet-test-run will soon be switched
[15:32] <ogra_> so you can just use the default test procedures as documented
[15:32] <ogra_> (it will become a wrapper for autopkgtest ... (indeed you can also use it directly without wrapping if you want))
[15:33] <cwayne> ogra_: right, so I'd just need to add stuff to the click manifest to use it then?
[15:34] <ogra_> Saviq, mterry, do you guys know if the fix for "cant properly type on most left column in the keyboard" is supposed to be fully final ? or are there still bits missing ?
[15:34] <ogra_> my kbd is still very hard to use on the left side
[15:34] <Saviq> ogra_, not there on rtm
[15:34] <Saviq> ogra_, in silo 15
[15:34] <ogra_> ah
[15:34] <ogra_> phew
[15:34]  * ogra_ is happy then
[15:35]  * ogra_ was scared it was supposed to be fixed already
[16:50] <pramod> i tried to install ubuntu touch on my Nokia X mobile
[16:50] <pramod> which is A dual core mobile
[16:51] <pramod> But on using cmd "$ adb devices " it shows "List of devices attached 025d138e2f521413 offline"
[16:59] <barry> stgraber: ping
[17:00] <stgraber> barry: pong
[17:01] <barry> stgraber: hi.  i'm working on the test plan for the phased updates, using phablet.stgraber.org.  i grab your archive-master keys, but then i get an error because i think the image-signing.tar.xz (and possibly other keyrings) have expired timestamps.  can you update and regen the sigs for the ubuntu-touch/test channel, mako?
[17:01] <barry> stgraber: keeping the same phased update values
[17:01] <stgraber> barry: oh, yeah, that server may very well be more than a year old :)
[17:01] <barry> :)
[17:01] <stgraber> barry: I'll re-gen all the keys after lunch+TB meeting
[17:02] <barry> stgraber: awesome, thanks.  i'll be out for a bit soon, but ping me when it's updated and i'll retest this afternoon
[17:17]  * dobey wonders what the deal with ubuntu-touch/vivid-proposed channel is
[17:18] <ogra_> not building yet
[17:19] <Tassadar> dobey: I noticed it too, I'll switch to it on tasemnice once devel(-proposed) starts pointing to it on s-i.u.com
[17:19] <dobey> ogra_: any idea when it will be? it didn't even exist yesterday, but now it does and is empty. and i really need a vivd mako image to test on :)
[17:19] <ogra_> once it works
[17:20] <ogra_> dobey, you are only the 244675th pinging me about it today ... :P
[17:23] <dobey> ogra_: actually i haven't pinged you about it today. you just happeend to appear when i asked. i did ping yesterday though. ;)
[17:24] <ogra_> heh
[17:24] <ogra_> dobey, well, infinity is on it, trying to find out why debootstrap doesnt work on the armhf build machines ... just be patient ... images will pop out as soon as possible
[17:26] <dobey> ogra_: yeah, being as patient as i can. just trying to see visible status that's not just me re-running ubuntu-device-flash constantly and having it fail. and i'm feeling a bit useless at the moment :)
[17:27] <ogra_> but why do you care about vivid ... you need to land in rtm
[17:27] <ogra_> vivid will likely be completely wonky for weeks anyway
[17:27] <davmor2> ogra_: so about ubuntu-touch/vivid-proposed /me only asking to see how many pings count as a ddos on ogra_ ;)
[17:27] <dobey> ogra_: i already landed in rtm. i have to sync it to vivid now.
[17:27] <ogra_> just do it then
[17:27] <davmor2> ogra_: no wonky is 15.10
[17:28] <dobey> ogra_: so just lie and say the tests passed and let ci train sync it anyway? :)
[17:28] <dobey> i don't have a problem with that, but i would like to make sure it doesn't crash on vivid; as it does crash on utopic when built on vivid (possibly due to some change that's in a lower level vivid lib)
[17:29] <dobey> davmor2: wonky wombat ?
[17:30] <davmor2> dobey: that or wobbly weeble :)
[17:30] <dobey> heh
[17:30] <dobey> wittle weevil
[17:34]  * popey pokes davmor2 with a hangout from 30 mins ago.
[17:34] <popey> slacker
[18:18] <kgunn> brendand: hey on bug 1386803, are you saying image #126 is when it started ? or image #126 was good ...then it started
[18:20] <brendand> kgunn, we're not 100% sure yet but i couldn't make #125 crash
[18:21] <brendand> kgunn, nobody has found a reliable test case yet
[18:21] <kgunn> brendand: also, what is the experience exactly ?....screen flashes to black and you get the spinner ? or something else ?
[18:21] <ogra_> kgunn, thats exactly it
[18:21] <dobey> hmm, is it just me or does rtm-proposed #113 have issues with rotation?
[18:22] <brendand> kgunn, usually there is a long hang, followed by the u-s-c spinner
[18:22]  * ogra_ always gets the spinner right after boot/reboot
[18:22] <dobey> 113 mako i guess, since apparently the build numbers are not synced across devices
[18:23] <dobey> ogra_: spinner on boot is just dash taking longer to start and query the few scopes, than it takes you to unlock the screen, i think
[18:24] <ogra_> dobey, you mean after i entered my sim pin it should show me the session and then restart ? ;)
[18:24] <dobey> ogra_: you see the list of apps and *then* you see the spinner?
[18:24] <ogra_> (irt is clearly a crash and many of us see it)
[18:24] <ogra_> yes
[18:25] <dobey> ok, yeah that's a crash
[18:25] <ogra_> i enter my sim pin, then my pin about 20sec later with the session running the whole thing crashes
[18:25] <ogra_> others seem to catch it differently but nearly everyone i talked to today has seen it once
[18:26] <dobey> if i unlock the phone as soon as possible after reboot, i get the spinner, but it's because the dash is still starting, not because of a crash
[18:26] <ogra_> well, then it also says "Scopes" above the spinner
[18:26] <ogra_> (or at least should say)
[18:27] <dobey> when i tried to flash 14.09 instead of 14.09-proposed though, on my n5, the dash was crashing constantly; so i flashed to 14.09-proposed instead
[18:27] <ogra_> well, it wasnt crashing it was "lifecycle managed" ;)
[18:27] <dobey> ogra_: yeah, it does say "Scopes" there. when i've seen the dash crash before, it did as well. but anyway
[18:27] <ogra_> (with a way to high oom score ... just like any app)
[18:28] <dobey> ogra_: lifecycle management was causing apport to keep collecting crashes?
[18:29] <ogra_> dobey, no, but restarting the dash all the time
[18:29] <ogra_> dash had the same score as apps ... and was SIGKILLed
[18:29] <dobey> ogra_: yeah, for me apport kept getting started whenever the dash crashed. so was definitely crashing (at least on my n5 on 14.09) :)
[18:29] <ogra_> today the score is a lot woer but still not 100% perfect ... next iteration of the fix is supposed to land soon though
[18:35] <ogra_> kgunn, fyi, i seem to have mediascanner and media-hub crashing alongside unity8 (according to /var/crash timestamps) not sure thats any valuable as a hint
[18:35] <kgunn> ogra_: yeah, for sure....looking at commits #126 fwd
[18:35] <kgunn> seems media hub might be the suspicion
[18:35] <kgunn> no unity8 change in there
[18:36] <ogra_> well, we were suspecting the hud dropping
[18:36] <ogra_> since that pulled so many unseeded additional packages
[18:36] <ogra_> but according to unity8 devs nothing of these packages should be used by it
[18:42] <kgunn> ogra_: i've been testing with version 133 today...quite a bit, and haven't seen it....
[18:42] <ogra_> i have had it at least three times
[18:42] <kgunn> ogra_: what are your steps ?
[18:42] <ogra_> and i actually did a fresh bootstrap today
[18:43] <kgunn> mmm
[18:43] <ogra_> well, i did a bootstrap, went through the wizard ... punched in my sim pin ... then my pin... then opened system settings and got the spinner
[18:43] <ogra_> so i thought i better reboot ...
[18:44] <ogra_> did that  ... spinner after pin again ... then it stopped doing that
[18:44] <ogra_> at some point a webapp hung ... spinner again ...
[18:44] <ogra_> thats the tree cases i had
[18:44] <ogra_> i know popey, davmor2 and brendand saw it more often than me
[18:45] <kgunn> popey: davmor2 brendand ....was it at a similar moment ? ^
[18:47] <davmor2> kgunn: I have it all over the place, so notify osd pops up crash, open and app crash, create an account crash, close and app crash, unlock the sim before you unlock the phone crash
[18:47] <brendand> kgunn, most commonly for me it's when i unlock the second of my two locked sims
[18:47] <brendand> kgunn, but it happens in a lot of places
[18:47] <kgunn> davmor2: curious if you --bootstrap 'd
[18:47] <davmor2> kgunn: --wipes
[18:48]  * kgunn still wonders if the delta between --wipe & --bootstrap is documented :)
[18:48] <davmor2> kgunn: no idea
[18:49] <pmcgowan> ogra_, do you often see adb not work to krillin, seems the case after ever update/reboot
[18:49] <kgunn> pmcgowan: i've seen that alot myself
[18:49] <ogra_> pmcgowan, nope, always works fine for me ...
[18:49] <davmor2> kgunn: the worst one by far was when I got back to the uk my wife called me to see how I was getting home from the airport and the popup for the call crashed the phone so I couldn't answer it
[18:50] <kgunn> davmor2: mmm, do you agree that #126 is the stinker ?
[18:50] <ogra_> pmcgowan, but as i said above i did a fresh bootstrap of my krillin today for the first time since re-partitioning ... lest see how it goes after my foorst OTA
[18:50] <kgunn> pre 126 seemed fine?
[18:50] <ogra_> *first
[18:51] <davmor2> kgunn: whatever was out on Saturday, Friday seemed fine I was testing on it all day
[18:51] <pmcgowan> ogra_, ok, pretty consistent for me for some time, I should log a bug finally
[18:51] <pmcgowan> ogra_, which package?
[18:51] <ogra_> pmcgowan, no idea, android-tools perhaps ...
[18:51] <kgunn> davmor2: this is the one of suspicion...
[18:51] <kgunn> http://people.canonical.com/~lzemczak/landing-team/ubuntu-rtm/126.commitlog
[18:52] <kgunn> not sure if you can tell whether or not you were on that?
[18:52] <ogra_> pmcgowan, so you mean adb is offline after the session is up on screen ?
[18:52] <pmcgowan> ogra_, yes
[18:52] <ogra_> (before session is expected behavior)
[18:52] <pmcgowan> ogra_, after I log in to phone
[18:52] <kgunn> davmor2: so brendan kind of thinks that's it based on testing...i thikn that's it based on contents
[18:52] <pmcgowan> ogra_, I need to reboot then it works
[18:52] <ogra_> strange
[18:52] <ogra_> and you are sure thats not the PC side ?
[18:52] <pmcgowan> seems after an update only
[18:52]  * ogra_ has never seen such issues 
[18:53] <pmcgowan> I just reboot the phone
[18:53] <ogra_> i do that plenty ... no issues here
[18:53] <pmcgowan> I have tried unplug/replug etc when in that state and doesnt work
[18:53] <davmor2> kgunn: yeah he has been looking into it I think so I would go with that, but it seems odd that it didn't start crashing a lot till saturday
[18:54] <ogra_> kgunn, this is my main phone ... i dont run tests on it and see the issue a lot ...
[18:54] <ogra_> i guess testing simply triggers it more easily
[18:54] <davmor2> kgunn: I'm wondering if this was the initial trigger and something else made it worse
[18:54] <kgunn> ogra_: sure, no prob...not saying it's not witnessed
[18:54] <kgunn> just trying to discern best info
[18:55] <kgunn> davmor2: so you're saying you flashed friday or sat...then haven't updated....and suddenly today it started acting up ?
[18:55] <kgunn> pmcgowan: don't forget on host "adb kill-server"
[18:55] <john-mcaleely> kgunn, so we (well, joc, but he's away) saw it a lot during our PES QA run yesterday/today
[18:56] <john-mcaleely> kgunn, none of that is with test harnesses - just manual use of the phone UI
[18:56] <kgunn> john-mcaleely: ack
[18:56] <davmor2> kgunn: no it started playing up for me a lot on saturday after upgrading to the revert for apt which broke installing apps
[18:56] <pmcgowan> kgunn, I tried to add silo 1 and it complains about a path to a vivid ppa
[18:56] <davmor2> kgunn: up until then it was working okay with occasional glitches
[18:57] <john-mcaleely> kgunn, as another data point, he would have exclusively used r128
[18:57] <pmcgowan> mhy did that heppen
[18:57] <pmcgowan> bah
[18:57] <ogra_> must be the jetlag
[18:57] <pmcgowan> ogra_, I added a silo ppa and it added it as vivid?
[18:58] <ogra_> pmcgowan, did you use citrain for that ? (the script from phablet-tools-citrain)
[18:58] <pmcgowan> no
[18:58] <pmcgowan> just add-apt-repo
[18:58] <ogra_> well, if you dont, you need to use the right url with "ubuntu-rtm" in it
[18:58] <davmor2> kgunn: okay so 126 looks like it might be this build http://people.canonical.com/~ogra/touch-image-stats/rtm/20141025.changes and the 25 was saturday so that sounds correct
[18:58] <pmcgowan> ogra_, ok but why? I am on rtm
[18:59] <pmcgowan> oh
[18:59] <kgunn> thanks for the cross check davmor2 & john-mcaleely
[18:59] <pmcgowan> silo is not rtm
[18:59] <ogra_> ah
[18:59] <pmcgowan> not even sure how to do this
[18:59] <kgunn> looking more and more like media hub
[18:59] <john-mcaleely> you're welcome kgunn
[18:59] <davmor2> kgunn: so yes 126 is most likely the cause I just thought that 126 landed friday not saturday :)
[19:00] <ogra_> pmcgowan, by hand ... which means adding an /etc/apt/sources.list.d/ file and manually adding the key ... and even then deps might fall over etc
[19:00] <ogra_> pmcgowan, rtm is a derivative ... thats a bit like adding a debian jessie archive to your utopic install
[19:01] <ogra_> might work, but can also break in heavy ways
[19:02] <pmcgowan> ogra_, yeah I am backing away, was trying to help oh well
[19:03] <kurt___> should I have installed the SDK with a PPA and not the app store?
[19:03] <ogra_> mixing distros is a quite advanced task :)  not impossible though
[19:03] <ogra_> kurt___, i think thats what the documentation says, yes
[19:04] <kurt___> ogra, thanks!
[19:04] <ogra_> (else you will be on an old SDK, the PPA constantly moves forward, releases do not)
[19:04] <AlbertA> so what do the crashes look like? is there a stacktracetop somewhere?
[19:05] <ogra_> AlbertA, i think asac had a link to a traceback on errors.u.c for his
[19:07] <AlbertA> ogra_: is it the mutex lock assert?
[19:08] <ogra_> oh, i dont know
[19:09] <ogra_> i had two on my own here though ... 3f6b473c-5e83-11e4-a8bb-fa163e373683 and 6a680838-5e85-11e4-9625-fa163e339c81
[19:09] <kgunn> asac: so AlbertA had a good point, that likely there's a audio service create/destroy for every notification...
[19:09] <ogra_> they werent processed this morning when we checked
[19:09] <kgunn> and that's what we're using for all the prompting....that seems to be a common thread in what the guys are seeing too...
[19:09] <kgunn> crash just as their being prompted for something
[19:09] <ogra_> https://errors.ubuntu.com/oops/3f6b473c-5e83-11e4-a8bb-fa163e373683
[19:10] <ogra_> yeah, looks like muutex_lock
[19:10] <ogra_> -u
[19:10] <ogra_> https://errors.ubuntu.com/oops/6a680838-5e85-11e4-9625-fa163e339c81
[19:10] <AlbertA> ogra_: ok that should be addressed by the dbus-cpp branch in line 57 in the silo....
[19:10] <ogra_> the medis-hub one
[19:10] <kgunn> yeah...last line on the report is mutex lock
[19:11] <kgunn> AlbertA: i take it that's b/c there's some racyness going on wrt previous dead obj on the bus ?
[19:12] <ogra_> it is because it is dbus-cpp
[19:12] <ogra_> :P
[19:12] <kgunn> lol
[19:12] <kgunn> man harsh
[19:12] <AlbertA> kgunn: yeah there could be accesses to dead objects which is fixed in the dbus-cpp branches listed in line 57
[19:12] <ogra_> kgunn, common meme among all devs though
[19:13] <ogra_> just say dbus-cpp in a room full of ubuntu touch devs and you will see them running for a pub ... to get really drunk
[19:15] <AlbertA> so it kind of makes sense...
[19:15] <ogra_> getting drunk ?
[19:15] <ogra_> yeah, surely does
[19:15] <ogra_> :)
[19:15] <AlbertA> the fix I added friday let's the client player instances receive EOS...so they end up destroying the player instances
[19:16] <AlbertA> so the probability of hitting the dead object access bug increases
[19:16] <AlbertA> just speculating....
[19:42] <hardtail> anyone install ubuntu on an asus transformerbook t100 can help me with install please/
[19:44] <dobey> hardtail: are you trying to install the phone/tablet image on it?
[19:45] <hardtail> @dobey I am trying to install the desktop version but I have been having issues for 3 days now
[19:46] <dobey> hardtail: you would be better off asking in #ubuntu this channel is about the development of the phone/tablet interface
[19:47] <hardtail> @dobey been out of luck in there for days...i guess i will try again...is it possible to get a tablet image though?
[19:48] <dobey> hardtail: i have no idea what you can install on that hardware. but i suspect not many people have one.
[19:49] <hardtail> dobey well thanks..ill see what i can do
[19:57] <barry> stgraber: hi.  back now.  any update on test server?
[20:02] <stgraber> barry: just finished resetting the whole server, importing an image now
[20:02] <barry> stgraber: cool, thanks
[20:05] <stgraber> barry: try now
[20:06] <stgraber> barry: note that the channel contains a single image at the moment since I reset the server. If that's a problem, I can probably figure out a way to get you a second image in there
[20:24] <barry> stgraber: nope, it's okay as long as there's a phase
[20:51] <hardtail> anyone have an asus t100
[20:59] <asac> AlbertA: dunno, is garbled too much i think: https://errors.ubuntu.com/oops/47162672-5e98-11e4-a34f-fa163e22e467
[20:59] <hardtail> does anyone know why this returns an error? linux (hd2,gpt5)/boot/vmlinuz-3.13-xxxx root=/dev/mmcblk0p5 video=VGA-1:1368x768e reboot=pci,force
[21:03] <dobey> hardtail: because the screen is 1366 pixels wide, not 1368 maybe?
[21:03] <dobey> though i don't know what error you are getting
[21:05] <hardtail> dobey the error I am getting is error: missing ')' symbol
[21:15] <dobey> hardtail: oh ok. anyway, #ubuntu is the right channel to ask general support questions about ubuntu. please ask in there. #ubuntu-kernel might be able to help you to, as it seems you might be having kernel issues with that machine