[00:26] <augrox> I'm dieing to know. Will Ubuntu touch has proper windowed multitasking? Or will it be only for media consumption. Like all the tablets currently on the market?
[00:26] <augrox> have*
[01:08] <ataranlen> Good evening everyone. I did apt-get update, then apt-get upgrade on my nexus 7, and now when it boots it only shows a black screen.
[01:09] <ataranlen> any suggestions?
[01:12] <ataranlen> Alright, let me take a step back. I tried to do an update because my "Settings" app wasn't working. About the only option that worked from it was the cellular one.
[01:22] <popey> ataranlen: most of the settings app isn't finished yet, I'd re-flash the device
[01:23] <ataranlen> Alright, So is there an alternative way to get blutooth devices connected?
[01:24] <ataranlen> Namely a blutooth keyboard :)
[01:25] <popey> ataranlen: maybe via command line tools, like hcitool
[01:25] <popey> ataranlen: not tried myself, don't even know if bt is supported on the n7 yet..
[01:26] <popey> http://bit.ly/18kIrhM suggests it's work in progress
[01:26] <ataranlen> alright, thanks :)
[01:27] <ataranlen> Thankfully I'm using MultiRom and reflashing is easy
[02:14] <_rogue_>  HexChat: 2.9.5 ** OS: Linux 3.2.0-49-generic x86_64 ** Distro: Ubuntu "precise" 12.04 ** CPU: 4 x AMD Phenom(tm) 9950 Quad-Core Processor (AuthenticAMD) @ 2.61GHz ** RAM: Physical: 7.8GB, 75.8% free ** Disk: Total: 76.9GB, 76.0% free ** VGA: Advanced Micro Devices [AMD] nee ATI RV730XT [Radeon HD 4670] ** Sound: HDA-Intel - HDA ATI SB1: HDA-Intel - HDA ATI HDMI ** Etherne
[02:14] <_rogue_> t: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller ** Uptime: 4h 45m 4s **
[02:40] <RobbyF> Did i read some where that change logs might be coming this week?
[03:09] <AskUbuntu> my touchpad and keyboard in labptop is notworking in ubuntu 13.04 | http://askubuntu.com/q/324677
[03:43] <acdxz06> is there a default root pass after installing ubuntu touch on nexus 4 ?
[03:44] <acdxz06> nvm
[06:31] <not_found> clever redirect from ubuntu-edge to here :)
[06:49] <dholbach> good morning
[06:49] <not_found> o/
[06:53] <not_found> I am so hyped about Ubuntu Edge that I even installed the Ubuntu Touch SDK and I'm not a dev or a programmer :p
[06:59] <oSoMoN> good morning
[07:45] <spikey> Hi there
[07:46] <spikey> im wondering when this awesome ubuntu release wil be ported to the galaxy s4 i9505 or is it already possible ?
[07:51] <spikey> anyone ?
[07:57] <sil2100> spikey: hi, sadly I don't know anything about that - as it's not an official platform, it's all up to users to get this running there
[07:59] <spikey> Alright
[07:59] <spikey> what do you mean by not an official platform ?
[08:04] <deiu> spikey, https://wiki.ubuntu.com/Touch/Devices
[08:07] <wilee-nilee> spikey, http://forum.xda-developers.com/showthread.php?t=2337903
[08:08] <spikey> Thnks for the link deiu, i had already looked there and not see it there
[08:33] <gema> ogra_: what's up with yesterday's images?
[08:33] <gema> ogra_: any big fixes landing on the images today?
[08:33] <ogra_> gema, they work fine on my devices here
[08:33] <gema> ogra_: what devices do you have?
[08:33] <ogra_> not that i know of
[08:33] <ogra_> maguro and grouper
[08:34] <gema> and 25.1 works well for you?
[08:34] <ogra_> but i  know pwoplw in #phablet also used mako and Saviq has installed it on manta yesterda
[08:34] <ogra_> y
[08:34] <gema> ogra_: plars and omer were reporting failures and random crashes of apps that they could reproduce on their devices
[08:34] <ogra_> *people
[08:35] <ogra_> i see that unity8 is taking up about 30% CPU here .... but thats not affecting the UI feeling for me ... (definitely should eb fixed indeeed)
[08:35] <ogra_> and i saw some odd behavior of the OSK in the terminal on maguro
[08:35] <ogra_> beyond that no issues here
[08:36] <gema> ogra_: say bug 1205115
[08:36] <ogra_> ah, havent tried starting stuff from the cmdline, one sec
[08:36] <gema> ack
[08:37] <ogra_> works on grouper
[08:37]  * ogra_ plugs the cable over
[08:38] <ogra_> confirmed
[08:38] <gema> what is confirmed? maguro and manta seemed to be suffering of it
[08:41] <fast> does calling / sms work in galaxy s2 ubuntu touch
[08:41] <gema> fast: I don't think we have supported images for that device
[08:41] <fast> gema: you do
[08:41] <ogra_> Saviq, so that new unity .... doe it do anything new the former one didnt ?
[08:42] <gema> fast: ack, then I don't know if that works, we are not testing those :)
[08:42] <ogra_> fast, no, but there is a commmunity port
[08:42] <fast> https://wiki.ubuntu.com/Touch/Devices/i9100
[08:42] <Saviq> ogra_, http://bazaar.launchpad.net/~unity-team/unity8/trunk/revision/131/debian/changelog :P
[08:42] <ogra_> fast, you should talk to the porter, there should be a link on the device wikipage to an xda thread
[08:42] <fast> ogra_: whats a port?
[08:43] <Saviq> ogra_, so yeah, you can install scopes on devices
[08:43] <gema> fast: a new version somebody is maintaining
[08:43] <Saviq> ogra_, and they will display stuff in a better way than it did before
[08:43] <ogra_> fast, if someone ports the code to a new device we call that a port :)
[08:43] <Saviq> ogra_, indicators should be faster
[08:43] <ogra_> Saviq, well, i'm more intrested if the new unity could cause bug 1205115
[08:43] <Saviq> ogra_, that it
[08:44] <ogra_> i.e. do you register with something we could be missing to set on user login etc
[08:44] <rickspencer3> Saviq, should that bu be assigned to you?
[08:44] <rickspencer3> It would be nice if someone claimed it in lp so folks knew it was being addressed ;)
[08:44] <ogra_> Saviq, i also see a lot higher cpu consumption
[08:45] <fast> ogra_: is it this http://goo.im/devs/MaxWallstedt/ubuntu-touch-i9100
[08:45] <ogra_> currently top shows 52% CPU and 21% ram for the unity8 process
[08:46] <ogra_> fast, talk to the porter on xda ... nobody here works on the S2 port
[08:47] <ogra_> Saviq, do you have a maguro ? i definitely dont see that resource consumption on my grouper
[08:47] <ogra_> seems to only happen on the gnex
[08:48] <Saviq> ogra_, yeah, got a maguro and works fine
[08:48] <ogra_> thats strange
[08:48] <Saviq> ogra_, https://bugs.launchpad.net/unity8/+bug/1201116
[08:48] <fast> ogra_: i think i found it http://forum.xda-developers.com/showthread.php?t=2165568
[08:48] <Saviq> ogra_, but we do have this issue sometimes
[08:50] <deiu> Does anyone know if work has begun on mobile data for mako?
[08:50] <ogra_> Saviq, it is constantly there, my phone is locked atm with the above values
[08:50] <ogra_> deiu, thats there since weeks
[08:50] <deiu> hmm, someone should update the wiki page then :)
[08:50] <deiu> Thanks!
[08:50] <Saviq> ogra_, yeah, when it happens it's constant
[08:51] <ogra_> i also rebooted several times already
[08:51] <Saviq> ogra_, restarting unity8 generally helps
[08:51] <deiu> (I mean the google docs)
[08:51] <ogra_> it persists
[08:51] <fast> ogra_: calls don't work yet though
[08:52] <dlan> anyone know is it possible to have a HDMI connection with nexus-4 ? so I can try desktop ui?
[08:52] <ogra_> Saviq, ah, confirmed ...
[08:52] <ogra_> dlan, there is no desktop UI yet ... thats 14.04 stuff
[08:53] <ogra_> for 13.10 we focus on the phone only
[08:53] <dlan> ogra_: oh, I thought we can switch from phone ui to desktop ui
[08:54] <ogra_> yes you will, in 14.04 (was never announced differently)
[08:54] <dlan> so, is there any pre-install image for the version 14.04
[08:54] <ogra_> no, we start working on the 14.04 version after we released the 13.10 version (obviously)
[08:54] <dlan> ogra_: so you mean that 14.04 is not ready? haven't start?
[08:55] <ogra_> we need a solid phone OS before we cn even think about working on the convergence
[08:55] <gema> dlan: we will start that one in october more or less
[08:55] <dlan> gema: thanks
[08:55] <asac> ogra_: powerd under control?
[08:56] <ogra_> asac, dunno, i have lost my backlog (my bip server crashed over night) so i dont know how it turned out
[08:57] <asac> ogra_: can we check what changed on the images to narrow down?
[08:57] <asac> just would like to find an owner for this bug... if we could figure what the prob is that would be cool
[08:57] <ogra_> asac, well, we know the powerd issue is self induced by some changes  ... but i dont know if sforshee nailed it down
[08:58] <asac> ogra_: can you get it working by backing out?
[08:58] <asac> e.g. going back to previous powerd?
[08:58] <ogra_> will try ... let me confirm something for tvoss_ first
[08:58] <JamesTait> Good morning all, happy Friday and happy One Voice Day! :-D
[08:59] <asac> JamesTait: welcome!
[09:00] <asac> sforshee: can you confirm that bug 1205115 is a regression from powerd changes?
[09:00] <asac> e.g. if yuou go back to previous versionms its gone?
[09:01] <deus_> hi all
[09:02] <deus_> any news for chinese tablets (Copy of GoClever A105) release of ubuntu touch?
[09:04] <ogra_> deus_, feel free to port it :)
[09:05] <ogra_> it depends on someone from the community porting it :)
[09:05] <deus_> xD I wish I could XD
[09:06] <deus_> I dont know how to get the drivers for my device
[09:06] <deus_> and bake a custom rom
[09:08] <ogra_> asac, still there with the previous version ... must be something else
[09:09] <asac> ogra_: unity8? can you go back to previous there?
[09:09] <ogra_> bah, and androids sensorservice is acting up again
[09:09] <deiu> ogra_, I just flashed ubuntu on my Nexus4 and I can't seem to be able to get the cellular data connection :S
[09:10] <ogra_> deiu, it should just come up by default
[09:10] <deiu> actually, it didn't even find the carrier
[09:10] <ogra_> asac, not sure, if i can find a deb i surely can :) (ppas usually wipe the former build, need to dig)
[09:10] <asac> ogra_: Saviq should know
[09:10] <asac> he said they are prepped for the case
[09:10] <ogra_> deiu, does your SIM have a PIN ?
[09:11] <deiu> yes
[09:11] <deiu> weird, it didn't ask me for it
[09:11] <ogra_> deiu, well, then you need to unlock it
[09:11] <deiu> wasn't it supposed to ask for the PIN after finishing booting?
[09:11] <ogra_> there is no UI for that ... (and i dont know the runes for doing it from cmdline, i fear you need to google)
[09:11] <ogra_> (or dig the mailing list archives)
[09:12] <deiu> Thanks
[09:12] <ogra_> asac, i doubt it is unity8 ... my phone is now in a completely broken state due to the sensorservice not starting on the android side
[09:13] <ogra_> asac, something accesses the sensors before the service is started, so it cant attach anymore ... i had that yesterday and was assuming a bad flashing since nobody else could reproduce it
[09:13] <Saviq> asac, we'll just revert if we see breakage caused by unity8 - there's no downgrading in dpkg world...
[09:13] <asac> Saviq: yeah i know. we have to try though locally
[09:13] <asac> Saviq: so would be easier if we could get the old packages for ogra to try and confirm
[09:13] <ogra_> asac, it even shows up if i reboot with the complete session disabled
[09:14] <ogra_> it is not realted to any UI bits
[09:14] <asac> maybe its not unity after all :)
[09:14] <Saviq> asac, I can't see how unity8 could cause that
[09:14] <seb128> deiu, https://lists.launchpad.net/ubuntu-phone/msg02776.html
[09:14] <ogra_> asac, exactly
[09:14] <ogra_> something started accesssing sensors before the contsainer is up ... sensorservice cant start because the sensor is blocked
[09:14] <asac> Saviq: thats debugging and guessing. the only way we can systematically find out what causes this is to try backing out
[09:14] <asac> ogra_: can you conpare the package manifest?
[09:15] <asac> lets be smart about our guesses
[09:15] <Saviq> asac, yeah I know
[09:15] <ogra_> asac, i did yesterday already ... i didnt see that behavior with 25 but see it with 25.1 ... thats a pertty narrow window (6h or so)
[09:15] <asac> ogra_: so whats the package difff?
[09:15] <asac> what changed?
[09:16] <ogra_> but the changes ML doesnt have anything that looks suspicious
[09:16] <asac> between 25 and 25.1
[09:16] <asac> ogra_: lets see the full list
[09:17] <deiu> seb128, thanks
[09:17] <seb128> deiu, you're welcome
[09:18] <ogra_> http://paste.ubuntu.com/5914158/
[09:19] <deiu> seb128, do I need to install the ofono-scripts package on the phone?
[09:19] <ogra_> the only non UI bit is qtdeclarative5-ubuntu-ui-toolkit-plugin
[09:19] <asac> ogra_: can you go down one by one systematiically until you have it?
[09:20] <asac> starting with whatever you feel is most likely :)
[09:20] <deiu> hmm, I can't seem to get the keyboard to show again in the terminal application
[09:20] <hurdman> hello
[09:20] <ogra_> asac, nothing from that list ... thats the point
[09:20] <hurdman> Wwill the futur ubuntu edge phone be open hardware ?
[09:20] <asac> if we end up having all the same and we still have the issue we have to go back to drawingboard :)
[09:20] <asac> ogra_: have you tried?
[09:20] <asac> ogra_: go one by one
[09:20] <asac> if previous image does work
[09:20] <asac> and this one doesnt
[09:20] <ogra_> asac, i checked the lxc and initrd changes from stgraber already ... all the rest cant affect it (since it happens even with the session not started)
[09:20] <asac> that its either that
[09:21] <asac> or something else
[09:21] <asac> ogra_: have you backed stuff out?
[09:21] <asac> you looked with your eyes right?
[09:21] <tvoss_> ogra_, a lot of apps got upgraded in one go .. why is that?
[09:21] <ogra_> asac, i disabled every upstart job except the container
[09:21] <ogra_> asac, *nothing* started, but the issue poersists
[09:21] <asac> ogra_: just downgrade the package ... is that not possible?
[09:22] <ogra_> asac, i wont invest time into that, the apps cant influence it ... i have exactly 20 processes running ... 16 of them lxc container nothing else started and it still happens
[09:23] <ogra_> there is something fundamental broken that cant come from these packages
[09:23] <asac> so you say its guaranteed that the changes in the image are not the reason?
[09:23] <ogra_> i'm pretty sure, yes
[09:23] <asac> remember that if we now end up finding that it was in those images anyway
[09:23] <asac> we waste lots of time
[09:23] <asac> not just trying this quickly first
[09:23] <ogra_> how would any of the apps influence it if they dont run ?
[09:23] <asac> ogra_: what other sources could be to blame?
[09:24] <ogra_> or any pf the framework
[09:24] <asac> ogra_: i dont know. currently all i see is thats the only source of changes
[09:24] <ogra_> *of
[09:24] <asac> so either we had that issue before, or its becuse of those packages or we have other sources of noise
[09:24] <asac> that i would surely like to identify and eliminate :)
[09:24] <tvoss_> tmoenicke, ping
[09:25] <ogra_> asac, it is some process that accesses a sensor ... before the container starts
[09:25] <asac> ogra_: so first. have you gone back and tried 25 image for real?
[09:25] <asac> e.g. are we 100% sure we didnt have the issue there?
[09:25] <ogra_> i just cant identify which
[09:25] <asac> lxc-android-config?
[09:25] <asac> how about going back with that?
[09:26] <ogra_> http://paste.ubuntu.com/5914181/
[09:26] <ogra_> logcat
[09:26] <ogra_> if i use android-chroot ... manually start the sensors service, all is fine
[09:26] <asac> ogra_: you are trying to undersatndt he problem rather than systematically figuring what the problem caused and throwing it out :)
[09:26] <asac> thats not scaling
[09:29] <ogra_> the point is that the bug happens before the container is starting ... (which iis like the third thing starting after init)n  what accesses the sensor must start before the container
[09:29] <ogra_> nothing on this list can do that
[09:30]  * ogra_ shecks what these packages ship 
[09:32] <deiu> what is the phablet password for sudo?
[09:32] <sil2100> Kaleo: hi!
[09:32] <sil2100> Kaleo: https://bugs.launchpad.net/ubuntu-ui-toolkit/+bug/1205259
[09:32] <sil2100> Kaleo: FTBFS we get
[09:35] <sil2100> bzoltan: ping! Hi!
[09:35] <sil2100> bzoltan: maybe you could help out ^ ?
[09:43] <ogra_> asac, logcat afer recursively purging ubuntu-touch (which includes all apps on the list and unity8) http://paste.ubuntu.com/5914217/
[09:43] <ogra_> asac, it has nothing to do with the changed packages
[09:43] <ogra_> (i wish i knew with *what* it has to do)
[09:44] <ogra_> it is definitely not solvable through backing out a package
[09:44] <ogra_> there is some other fundamental flaw
[09:45] <ogra_> asac, it must b something unpackaged on the android side ...
[09:46] <ogra_> asac, either hybris  or platform-api
[09:46]  * ogra_ will dig through the changelogs after a break
[09:52] <tvoss> ogra_, could you give me the diff from 24 to 25.1?
[09:53] <bartek> hi
[09:53] <bartek> are there new instructions for porting Ubuntu Touch using newest "flipped Ubuntu Touch Images"?
[09:55] <w-flo> bartek, there's only this WIP afaik, maybe it helps you: https://wiki.ubuntu.com/Touch/PortingFlippedInProgress
[09:57] <seb128> stgraber, hey, did you stampfile change get merged (what's the right project/vcs for that code, I just saw your pastebin the other day)
[09:57] <stgraber> seb128: yep, it's there now
[09:57] <ogra_> tvoss, http://paste.ubuntu.com/5914258/
[09:57] <stgraber> seb128: http://phablet.ubuntu.com/gitweb?p=CyanogenMod/android_bootable_recovery.git;a=shortlog;h=refs/heads/phablet-saucy
[09:58] <seb128> stgraber, thanks
[09:58] <tvoss> ogra_, thx
[09:58] <bartek> w-flo, thanks
[09:58] <w-flo> bartek, it won't help you. I guess. Just looked at what's changed in that wiki article, and the important bits are still missing
[09:58] <bartek> yeah, I am reading it
[09:59] <ogra_> tvoss, i'd blame apparmor for your issue
[09:59] <ogra_> (sadly that doesnt help mine :( )
[09:59] <tvoss> ogra_, hmmm ...
[09:59] <bartek> but I will visit it regularly, I assume one day the guide will be updated :>
[10:00] <w-flo> bartek, me too. make sure you have some ~2mb free space on your boot partition though :D
[10:00] <ogra_> tvoss, do you know of anything that would access the proximity sensor on boot (powerd and all of ubuntu-touch's deps  are already purged)
[10:02] <bartek> btw. I really wonder how somebody ported it for Galaxy SII :>>
[10:03] <ogra_> bartek, its not that hard if there is a cyanogenmod port already
[10:03] <ogra_> oh my !
[10:04] <ogra_> asac, fond the issue with the sensorservice
[10:04]  * ogra_ sighs ... i though cyphermox  had tested this
[10:05] <john-mcaleely> cjwatson, ping
[10:07] <john-mcaleely> lool, ping
[10:07] <ogra_> rsalveti, so my non starting sensorservice returned .this morning .. even on the 25.1 image ... seems mounting /factory causes it :( .... there goes our bluetooth support :(
[10:10] <ogra_> yup, and it also fixes the app starting problem
[10:10] <ogra_> Saviq, tvoss  ^^^
[10:10]  * ogra_ reboots and re-tests a few times to make sure
[10:14] <ogra_> yup, 10 reboots and it works reliably
[10:14] <Saviq> ogra_, oh cool
[10:14] <ogra_> Saviq, well, not so cool
[10:14] <ogra_> since that means we wont have bluetooth
[10:15] <Saviq> ogra_, well, cool that you found the reason
[10:15] <ogra_> mounting /factoy is essenetial to have BT working
[10:15] <ogra_> yeah, well, i dug half into it last night with rsalveti already ... but we were both guessing it was a bad flash that caused it
[10:16] <ogra_> s/flash/flashing/
[10:16]  * ogra_ prepares a fix
[10:17] <fast> the hardware buttons like menu isn't working for galaxy s2
[10:20] <ogra_> fast, ubuntu touch has no use for HW buttons
[10:20] <ogra_> Saviq, gema, it would be nice if someone could confirm the fix before i upload it
[10:20] <fast> ogra: oh, then how do you turn it off
[10:21] <Saviq> ogra_, otp
[10:21] <ogra_> fast, through a shutdown menu that doesnt exist yet (or via adb using shutdown)
[10:21] <cjwatson> john-mcaleely: yes?
[10:23] <w-flo> fast, I can also initiate the shutdown sequence by long-pressing the power button (2-3 secs), not sure if that is a cyanogenmod feature specific to my phone..
[10:23] <fast> wflo: does calling work in the S2?
[10:23] <w-flo> fast, not sure, my phone is a Desire Z
[10:24] <fast> w-flo: does it work for u
[10:24] <john-mcaleely> cjwatson, I believe a click package is defined to contain both an apps read-only dependencies, and any writeable data I creates, all in one filesystem tree
[10:24] <w-flo> fast, not sure, I don't have a SIM card in that old phone :D
[10:24] <john-mcaleely> cjwatson, or am I mistake at the start of my assumptions?
[10:26] <cjwatson> john-mcaleely: Sort of
[10:26] <cjwatson> john-mcaleely: At present, Click packages effectively depend on the framework they declare in their manifest, and are not allowed other dependencies; so if they need other misc dependencies then it's true that they need to ship them themselves
[10:27] <cjwatson> john-mcaleely: However, from the point of view of the app, its unpacked filesystem tree is read-only.  They must write data elsewhere, probably in the user's home directory somewhere
[10:28] <john-mcaleely> ok. is the place they write data to constrained in any way? (ie, if it's user-writeable, an app can write to it?)
[10:30] <deiu> ogra_, I got voice to work but I still can't connect to cellular data
[10:30] <cjwatson> john-mcaleely: Apps will run under AppArmor confinement.  I don't know the details, but hopefully https://wiki.ubuntu.com/SecurityTeam/Specifications/ApplicationConfinement/Manifest and maybe https://wiki.ubuntu.com/SecurityTeam/Specifications/ApplicationConfinement will help
[10:30] <john-mcaleely> aha. thanks!
[10:30] <fast> w-flo: is there an app store or something
[10:30] <w-flo> fast, not yet
[10:31] <deiu> Can't connect to protected WiFi networks either
[10:33] <ogra_> davmor2, can you confirm the behavior in bug 1205115 with 25,1 and could you also try if the suggested fix changes it for you ?
[10:34] <ogra_> (just might be a coincidence that it fixes it for me)
[10:34] <ogra_> *might just be
[10:37] <davmor2> ogra_: The camera app seems to be running fine here.  Let me try it with his specific command line call
[10:37] <ogra_> davmor2, well, if you started it from the UI already, please reboot first
[10:37] <ogra_> to make sure you are in a virgin state
[10:38] <ogra_> then try the cmdline (unlock the phone but dont start anything from UI)
[10:38] <ogra_> then comment the line in fstab, reboot and try again
[10:39] <davmor2> ogra_: oh by the way after a fresh flash on grouper the camera works till you take a photo then it locks up and never works again :D
[10:39] <ogra_> davmor2, i guess gusch would like to know about that :)
[10:39] <ogra_> he made it work :)
[10:41] <davmor2> gusch: good work my man,  there are a couple of issue I'll write up some bugs for it if I get chance but it is at least a step in the right direction :)
[10:41] <ogra_> if we now get media playback and sound it shoudl eb perfect :)
[10:41] <ogra_> *be
[10:41] <lool> john-mcaleely: pong
[10:42] <davmor2> ogra_: I thought the reason the media playback died was because of the sound :D
[10:42] <ogra_> probably
[10:42] <ogra_> :)
[10:42] <gusch> davmor2: grouper is the N7, right?
[10:42] <ogra_> yeah
[10:43] <davmor2> gusch: yep
[10:43] <gusch> davmor2: yea - I heard there a some problems - maybe some of my recent fixes will help - but I don't have the N7, so I can't investigate into that ...
[10:43] <davmor2> ogra_: meh should I be worried by the black screen I am getting on reboot
[10:43] <mardy> Laney: hi! I saw your branch, but I still think that just using QCoreApplication::arguments() is easier and most Qt developers will be more familiar with that
[10:44] <ogra_> davmor2, you mean it doesnt start anymore ?
[10:44] <davmor2> ogra_: this is my maguro on 25.1
[10:44] <ogra_> awesome :)
[10:44] <mardy> Laney: I'll fix the segfault in my branch
[10:44] <ogra_> so you hit the same bug as mine :)
[10:45] <ogra_> but that makes it hard to reproduce the other one indeed
[10:45] <Laney> mardy: Fine. I still think it's better to use a proper parser until Qt gets one but I don't want to argue about it too much.
[10:45] <ogra_> so let me file a separate bug for the non-start :)
[10:46] <davmor2> ogra_: it also means I'm without a phone so lets really hope there isn't a phone call from the hospital with regard the mother-in-law tum-ti-tum-ti-tum.......ooops
[10:47] <ogra_> davmor2, heh, just comment the /factory line in fstab and reboot
[10:47] <ogra_> that will fix it
[10:47] <davmor2> ogra_: hahaha
[10:51] <davmor2> ogra_: Yay and it's back end of panic
[10:51] <ogra_> davmor2, bug 1205285
[10:52] <davmor2> ogra_: and confirmed
[10:53] <ogra_> davmor2, the bad thing is that i would really like to know if the app starting is related or not
[10:54] <ogra_> but once it started booting to a black screen with /factory mounted it always seems to do that once the mount is enabled again
[10:54] <ogra_> its also funny that it doesnt do that from the first boot on
[10:55] <ogra_> fix uploaded
[10:56] <ogra_> asac, i'll trigger a new image once thats in
[11:02] <ogra_> davmor2, oh, try adding ro, to the fstab line
[11:02] <ogra_> seems that helps here
[11:02] <ogra_> (and also makes the apps from cdmline work)
[11:03] <ogra_> yeah, seems mounting it readonly works
[11:03]  * ogra_ prepares anothe upload 
[11:08] <davmor2> ogra_: confirmed ro added and # removed and it boots :)  the camera still works fine though
[11:08] <ogra_> yeah
[11:09] <ogra_> i wonder if the rild issues awe saw the last days are related
[11:09] <w-flo> ogra_, sorry to bug you again.. :) the touch initramfs script can't find my data partition. it's called /dev/mmcblk0p26 according to /proc/emmc.. I'm not good at shell scripting, but I think the code looks for a /dev/UDA etc. device?
[11:11] <ogra_> w-flo, try to find a "by-name" directory underneath /dev/block (might be a few levels deeper than that) and in there take a look at the names ... i'm pretty sure there are partition labels
[11:12] <w-flo> ah, that's what that find does. thanks for the hint :)
[11:12] <ogra_> sadly there is no find commmand in the android build to make that easy
[11:12] <ogra_> and you wont see the android /dev from ubuntu
[11:12] <ogra_> if you found the by-name dir, pastebit its content ... i can add the right name to the script then
[11:13] <w-flo> mh, it's a little strange. just a second
[11:13] <ogra_> if there are *really* no labels, you might need to wait until i find the time to fixx bug 1199084
[11:13] <w-flo> http://pastebin.ubuntu.com/5914485/ ogra_
[11:14] <w-flo> ogra_, I'll just hardcode the correct partition for the time being
[11:14] <ogra_> yeah
[11:14] <ogra_> wow, that looks bad
[11:14] <w-flo> I didn't even know you could have ":" in a file name
[11:14] <w-flo> thanks :)
[11:15] <ogra_> sure, you can evven have special chars and spaces
[11:15] <ogra_> though where do you have a : in the filename
[11:15] <w-flo> I use spaces all the time.. and Umlaute.. ":" just seems *too* special :D
[11:15] <ogra_> oh, i see
[11:15] <ogra_> sorry
[11:15] <w-flo> yeah, the link names
[11:16] <ogra_> right
[11:16] <ogra_> yeah they are just translated from the major/minor device names
[11:18] <cjwatson> You can; it's not necessarily a good idea since it can be confusing with things like scp
[11:19] <cjwatson> For most purposes : is less special than space
[11:24] <ogra_> cjwatson, well, tell that to google (or the vendor that designed that android fork)
[11:25]  * ogra_ gave up having *any* expectations to sanity of android ports 
[11:27] <ogra_> i wouldnt be surprised to find device names containing @ or some such one day
[11:27] <w-flo> they don't want to make the lifes of third-party developers too easy after all ;)
[11:28] <StayGreen> Hey i got a question... :)
[11:29] <StayGreen> aaam i think im still too silly too find the download link of the newest ubuntu touch dev preview...
[11:29] <mardy> Laney: I updated the MP
[11:30] <StayGreen> aaam i think im still too silly too find the download link of the newest ubuntu touch dev preview
[11:30] <StayGreen> can someone give me the link?
[11:30] <Laney> k
[11:35] <ogra_> Stskeeps, just use phablet-flash, it will do teh right thing
[11:35] <ogra_> err
[11:35] <ogra_> sorry, didnt notice he was gone already
[11:35] <Stskeeps> no problem
[11:39] <deiu> Right...so I've put up a short guide about PIN protected SIMs: http://fcns.eu/2013/07/26/ubuntu-touch-unlock-change-reset-pin
[11:40] <ogra_> deiu, ofono-scripts is preinstalled
[11:40] <deiu> oh?
[11:40] <deiu> but it's probably not in the PATH
[11:40] <ogra_> root@ubuntu-phablet:/# dpkg -l|grep ofono-scripts
[11:40] <ogra_> ii  ofono-scripts                                        1.12phablet9                                    armhf        Mobile telephony stack (test and maintenance script files)
[11:40] <ogra_> no, its not in path
[11:40] <deiu> I see, that's why I got confused
[11:41] <ogra_> we will link individual scripts into path with one of the next uploads
[11:41] <ogra_> was already discussed :)
[11:42] <deiu> cool!
[11:42] <deiu> my phone seems to heat up quite substantially
[11:43] <ogra_> what device iis that ?
[11:43] <deiu> Nexus 4
[11:43] <ogra_> hmm well, check the processlist and top
[11:43] <ogra_> see if something consumes a lot of resources
[11:49] <seb128> mardy, you should just give up and use getopt, would make Laney happier it seems :p
[11:50] <Laney> I've made that clear :P
[11:50] <asac> ogra_: once what is in?
[11:50] <seb128> mardy, he even pushed working code to copy ;-)
[11:50] <ogra_> asac, the fix
[11:50] <asac> ogra_: what was the problem? how did we identify it?
[11:51] <ogra_> it was the /factory mount that we enabled for bluetooth support
[11:51] <Laney> I did however go into that MP expecting to approve it
[11:51] <mardy> Laney, seb128: honestly, if it were my own SW, I wouldn't even fix that :-)
[11:51] <asac> ogra_: where was that change manifested?
[11:51] <asac> ogra_: which package carries that?
[11:51] <ogra_> and i identified it by removing all packages until i only had the container left
[11:51] <mardy> Laney: so, I'm still in time to fix it?
[11:51] <seb128> mardy, just use Laney's getopt version and we can all move on ;-)
[11:51] <ogra_> asac, lxc-android-config creates fstab on first boot
[11:52] <asac> ogra_: i mean: we had the package diff. which package had the regression?
[11:52] <Laney> I don't know of any other bugs atm
[11:52] <asac> ah so it was lxc-android-config
[11:52] <asac> so we would have been able to identify
[11:52] <asac> and revert that
[11:52] <Laney> other than --option=foo=bar not working which is annoying but not essential
[11:52] <asac> without understanding the fix
[11:52] <asac> thats good
[11:52] <asac> didrocks_busy: are you there?
[11:53] <didrocks_busy> asac: I'm here
[11:53] <didrocks_busy> asac: but working on lool's priority
[11:53] <asac> didrocks_busy: wth is lool's priority?
[11:53] <didrocks_busy> asac: the UI for system update
[11:53] <mardy> Laney: I don't care too much either, I just think that the Q-only version is easier
[11:53] <ogra_> asac, the issue is that the problems didnt show up all the time, only for some boots ...  it didnt show up on wed.'s image even though the bug was there already
[11:53] <mardy> Laney: if you are not already familiar with getopt, of course
[11:53] <mardy> (which I'm not)
[11:54] <mardy> Laney: I pushed a new commit, you decide :-)
[11:54] <asac> ogra_: aha... so again we relied on intuition, rather than systematic approach to narrow dow
[11:54] <asac> n
[11:54] <ogra_> asac, and as i said rolling back between 25 and 25.1 wouldnt have gained us anything with such a heisenbug
[11:54] <Laney> mardy: well, it should be easy to follow the pattern to add new options if needed
[11:54] <ogra_> since it wasnt stable showing/non-showing
[11:54] <asac> ogra_: so if you have automation, how can identify such things earlier?
[11:54] <asac> just run 10 times?
[11:55] <ogra_> asac, had i followe dyour suggestion i would still roll back individual app packages
[11:55] <ogra_> not intuition, experience
[11:55] <asac> or have a 100 reboot test?
[11:55] <ogra_> if the container misbehaves even if the session doesnt run it cant be an app
[11:55] <asac> ogra_: thats simialr in the respect of not giving us a guaranteed time to identification and elimination
[11:55] <asac> (experience, etc.)
[11:55] <asac> ogra_: so would we have found it with a test that reboots the system 20 times
[11:56] <asac> more easily?
[11:56] <asac> more often?
[11:56] <ogra_> well, but some clear indicators can save you a lot of debugging work
[11:56] <asac> debugging is the act of a human looking closer at an issue
[11:56] <ogra_> asac, no idea, davmor2 hit it after a few reboots, dunno how many he did
[11:56] <ogra_> my maguro did for some flashes hiot it immediately
[11:56] <ogra_> for others only after like 20 reboots
[11:57] <asac> nice
[11:57] <ogra_> yeah
[11:57] <asac> ogra_: so can we please work with QA team that we get a test that just reboots and checks that an app starts properly
[11:57] <asac> 20 times?
[11:57] <davmor2> ogra_: only 2 reboots
[11:57] <ogra_> hmm, not sure 20 is sufficient ... i wuld go for more
[11:57] <ogra_> 50-100
[11:57] <asac> ogra_: well, reasonably more than 1
[11:58] <ogra_> but that will eat a lot extra testing time
[11:58] <asac> lets start with 10 or so for premerge testing
[11:58] <ogra_> ok
[11:58] <ogra_> premerge ?
[11:58] <asac> like continuous stress and testing doesnt work
[11:58] <ogra_> so you want that in CI >
[11:58] <ogra_> ?
[11:58] <asac> ogra_: at want this at every stage right now
[11:58] <asac> currently our image testing is kind of premerge testing as well as we use it to gate
[11:58] <asac> :)
[11:59] <ogra_> asac, the big prob with that bug is btw that you wont notice it from cmdline
[11:59] <asac> anyway...  having the test will allow us to put it wherever it makes sense
[11:59] <ogra_> if you dont see the screen it looks like everything is fine
[11:59] <ogra_> all processes were up
[11:59] <asac> ogra_: well, we reboot stystem and start app and run basic autopilots too see that it works
[11:59] <ogra_> right
[11:59] <asac> ogra_: you could use autopilot to drive the app that didnt start?
[11:59] <ogra_> and we catched that issue even with yesterdays tests
[12:00] <ogra_> it is just that nobody could explain the symptoms
[12:00] <ogra_> (and indeed nobody looked at the screen)
[12:00] <asac> yeah. proofs the point that we are on track
[12:00] <asac> that we just need to be more strict about the idea of "stop the factory line if something odd, unexplainable is observed"
[12:00] <ogra_> right, but we didnt have a chance to actually find whats wrong through testing
[12:00] <asac> so we dont build more stuff and more noise on top
[12:01] <asac> ogra_: so we saw issues on yesterdays dashboard?
[12:01] <asac> then its all fine
[12:01] <ogra_> and everybody was still on the wrong track this morning
[12:01] <ogra_> (including me)
[12:01] <ogra_> we saw it on yesterdays tests, yeah
[12:01] <asac> we would have catched it if we would explicitely move our images back and forward one step at a time and dont continue to move if there is a problem
[12:01] <asac> thats all i want :)
[12:02] <deiu> is there a bug affecting the keyboard? it doesn't show in most cases
[12:02] <ogra_> asac, i had the bug last night and debugged it heavily with rsalveti ... neither of us got the connection to the tests, since only my device seemed to misbehave
[12:02] <ogra_> (i even thourgh my flash was worn out)
[12:02] <asac> right
[12:02] <ogra_> i only got on the right track when it showed up again after a fresh flash this morning ... and even that was a matter of luck
[12:03] <ogra_> i think we need to get more effective with nailing down such issues ...  just not sure how
[12:03] <asac> right. one thing is to stop accept issues we see
[12:03] <asac> hold the factory line
[12:03] <asac> investigate, fix
[12:03] <asac> continue
[12:04] <asac> at brest we can can hold factory line; identify change, back that out, continue factory line, spin off folks to fix the issue
[12:04] <asac> nd bring back the fixed code
[12:04] <asac> ogra_: you remember the lean training we had at some point?
[12:04] <ogra_> yeah, indeed
[12:04] <asac> and how they talked how aviation industry does that ... while NASA didnt :)
[12:04] <ogra_> ubuntu toyotaphone
[12:04] <asac> and how the stats looked :)
[12:05] <asac> like 1/3 of the NASA shuttles exploded
[12:05] <asac> while airlines could carry billions of man miles without a crash :)
[12:05] <asac> hehe
[12:05] <ogra_> new image build running
[12:05] <asac> nice
[12:05] <ogra_> should be there in 1h
[12:06] <asac> ogra_: so yesterday i tried to probe how long it took to get a merge commit in until we see the effect on the images
[12:06] <asac> i dropped out after 15 hours
[12:06] <asac> :)
[12:06] <ogra_> heh
[12:06] <asac> with no results on dashboard yet
[12:06] <asac> ogra_: can you try to note down the time you wait from the merge request
[12:06] <ogra_> yeah, thast what i complain about ...
[12:06] <asac> tot he dashboard results?
[12:06] <ogra_> :)
[12:06] <asac> for a few things so we get real numbers?
[12:06] <ogra_> i rarely touch stuff that needs MPs
[12:06] <asac> but when you do, do it :)
[12:07] <asac> you can also note the time for the "avoid MP road"
[12:07] <ogra_> from upload to archive it takes 1.5h for a fast package upload ... plus 1h image build time
[12:07] <asac> that you do when uploading to archive
[12:07] <asac> ogra_: time from commit to dashboard results
[12:07] <asac> is what is important
[12:07] <ogra_> so around 3h with some delays between the steps
[12:07] <asac> so you commit through MP or through upload to proopsed
[12:07] <asac> i guess
[12:07] <asac> ogra_: get some samples noted down
[12:07] <ogra_> oh, yeah, dashboard adds up
[12:07] <asac> its nice to have real empirical data
[12:08] <ogra_> but i dont think we can measure that until it really restarts the tests automatically
[12:08] <asac> rather than claiming and everybody then said that we didnt measure right :)
[12:08] <asac> ogra_: we can
[12:08] <asac> ogra_: its thre reality
[12:08] <asac> we want to know what is the time now
[12:08] <ogra_> asac, well, there are human delays in that
[12:08] <asac> inclduing mess at any stage
[12:08] <asac> and human delays
[12:08] <asac> etc.
[12:08] <ogra_> ok
[12:08] <asac> ogra_: thats fine. thats all part of the time it takes in reality
[12:08] <ogra_> well, i can do it for my current build for sure
[12:09] <asac> do it for whenever ou do a change. just a simple spreadsheet.
[12:09] <ogra_> CI adds a lot prefix time that i dont have with a deb source package though
[12:09] <ogra_> and indeed i have the advantage of being able to drive the live builder off schedule
[12:10] <ogra_> if you would add the cron delay that would be adding half a day or so
[12:10] <ogra_> (for live builds)
[12:14] <deiu> unity8 seems to eat a lot of CPU (~35-40%),  with a load average around 3.00
[12:19] <asac> ogra_: its ok to measure with you guiding stuff manually through the system ... maybe also record cases where you dont do that
[12:20] <asac> for comparison
[12:20] <ogra_> yep
[12:20] <ogra_> will do
[12:30] <lool> asac: finishing the OS update UI (just a button to trigger the OS updates)
[12:30] <ogra_> sounds highly complex :)
[12:30] <lool> asac: didrocks is starting on this today as seb128 and him are the only two able to develop this speedily (the original plan had barry pinned down for this until a couple of days ago, but it's just too long to learn QML Settings panel that it wasn't worth it here)
[12:31] <seb128> lool, asac: didrocks had the backend mostly done at lunch time, we should be fine to land a working version, integrated to system settings, in the afternoon
[12:31] <lool> cool
[12:31] <ogra_> lool, without MIr+lightdm we wont be able to switch to the new images ....
[12:32] <lool> ogra_: hmm I'm not sure I see the link between the two
[12:32] <asac> seb128: ogra_: please coordinate the landing in our real images
[12:32]  * ogra_ doesnt see why there is that hurry
[12:32] <asac> we currently have not a working image
[12:32] <asac> that ran through dashboard
[12:32] <asac> i would prefer to see that fixed before shoveling this cool thing in
[12:32] <asac> but i guess we dont talk about image landing anyway?
[12:33] <lool> it does not need to be in the /current image; /pending will be picked up
[12:33] <ogra_> lool, click needs logind session registeration (as does NM and bluetooth) ... on non readonly systems we can hack around that ... for the readonly setup we need lightdm to register the session (and drop all the hacks we have in the apps currently)
[12:33] <seb128> same for system settings
[12:34] <seb128> setting stuff like the tz doesn't work on the touch image because polkit is broken
[12:34] <ogra_> lool, so we cant switch before we have proper session mgmt
[12:34] <ogra_> or any other way of registering a session properly with logind
[12:34] <seb128> oh, on the topic, I hope the upgrade service doesn't rely on polkit
[12:34] <seb128> otherwise it's not going to work on the device either
[12:35] <ogra_> it very likely does i'd guess
[12:35] <lool> ogra_: OMG, so OS updates linked to Click linked to lightdm -- this is getting really bad
[12:35] <ogra_> lool, yeah
[12:35] <ogra_> we live on top of a ton of hacks currently
[12:36] <seb128> lool, well, there is no technical reason we need lightdm to solve that, we just need a properly registered session that is seen as a front/active one by logind so the user gets the credential associated with local sessions
[12:36] <seb128> lool, lightdm solves that for us
[12:36] <seb128> but we can probably solve it without lightdm as well
[12:36] <ogra_> lool, the prder must be Mir+lightdm+new-unity ... then system images, then the partitioning stuff to drop loop images again
[12:36] <ogra_> *order
[12:37] <ogra_> else we will have to add new hacks to make stuff work ... waste of time imho
[12:41] <lool> ogra_: it depends how long it takes to land the other things
[12:41] <ogra_> we already have Mir images
[12:41] <lool> ogra_: if it's a couple of dyas or a couple of months, it's not the same story
[12:41] <ogra_> (on jenkins)
[12:41] <ogra_> i dont know how long lightdm addition will take
[12:42] <ogra_> (they only replace SF with Mir yet, no lightdm on them)
[12:42] <ogra_> robert_ancell should be able to tell you
[12:45] <deiu> is manage-address-books.py gone from the latest builds?
[12:46] <ogra_> since a while already i think
[12:46] <deiu> any alternatives to importing contacts?
[12:46] <ogra_> we suck at keeping the wiki up tp date
[12:46] <ogra_> yeah, there was a blogpost from sergiusens
[12:47] <deiu> I don't have the blog url :(
[12:47] <ogra_> me neither, just digging here
[12:47] <deiu> btw, mobile data is not working on Nexus 4
[12:48] <ogra_> http://sergiusens.github.io/
[12:48] <ogra_> there is a howto for google contacts
[12:48] <deiu> that's no longer supported by google
[12:49] <deiu> SyncML that is
[12:49] <deiu> the decision is a couple of months old
[12:49] <ogra_> well, thats all i know for importing contacts...
[13:03] <sergiusens> deiu: ogra_ as far as I know syncevolution doesn't use syncml only
[13:05] <deiu> sergiusens, [ERROR] error code from SyncEvolution fatal error (local, status 10500): addressbook: unable to access databases registry
[13:05] <deiu> when doing syncevolution --sync refresh-from-server Google_Contacts addressbook
[13:06] <user82> deiu, related to googles issues?
[13:06] <deiu> yes
[13:06] <user82> this one.. http://productforums.google.com/forum/m/#!topic/mobile/p1TF2uOlF0A
[13:06] <user82> annoying
[13:10] <ogra_> gema, so there is a 26.1 image now and i see the app tests didnt run on the 26 image ... can we just skip 26 and move on (and kill if there is anything left from 26)
[13:11] <ogra_> plars, ^^^
[13:22] <barry> didrocks_busy: just wanted to let you know i'm around now to answer any questions.  sent you an email reply
[13:23] <didrocks_busy> barry: hey, thanks! I noted multiples things:
[13:24] <didrocks_busy> barry: first, I think all the "checkUpdate… getUpdate…" should let a delay before sending the signal
[13:24] <didrocks_busy> barry: to mock the latency + download time
[13:24] <gema> psivaa: ^^
[13:24] <didrocks_busy> (as told on the bug, I think 5s is enough)
[13:24] <gema> psivaa: can we move to 26.1?
[13:25] <barry> didrocks_busy: ah, i missed that.  will add
[13:25] <didrocks_busy> barry: second thing, I don't see any cancel signal triggered when I call (Cancel()) until I call then readyToReboot()
[13:25] <psivaa> gema: we are now flashing with 26.1
[13:25] <ogra_> psivaa, thanks !
[13:25] <gema> psivaa: excellent, ahead of me, thanks
[13:25] <psivaa> lol
[13:25] <ogra_> just doesnt make sense to waste time on 26
[13:25] <gema> ogra_: indeed
[13:25] <barry> didrocks_busy: right.  canceling doesn't actually do anything until the next .GetUpdate() or .Reboot() call
[13:27] <didrocks_busy> barry: that's not handy TBH
[13:27] <didrocks_busy> barry: can't we have the signal triggered as a callback for cancelling?
[13:29] <barry> didrocks_busy: in that case it would just be an acknowledgment that the Cancel method was called.  what should happen at the next .GetUpdate() or .Reboot() then?  should it silently cancel the operation?  should it send out another Canceled signal?  what would make the most sense for the u/i?
[13:29] <sergiusens> sbeattie: jdstrand hey guys, are you aware of this http://pastebin.ubuntu.com/5914837/ ? It's from a dist-upgrade
[13:29] <didrocks_busy> barry: no signal would make sense IMHO
[13:29] <didrocks_busy> should just do nothing
[13:30] <didrocks_busy> barry: last item is that checkUpdateAvailable(), as we discuss, doesn't retrigger a check, I think it should. So that even after a Cancel() or Failed, we can restart/retry :)
[13:30] <barry> didrocks_busy: so: when .Cancel() is called, send a Canceled signal.  then silently no-op future .GetUpdate() and .Reboot() calls?
[13:30] <jdstrand> sergiusens: yes, I just uploaded click-apparmor 0.0.5 with sbeattie's changes to address that
[13:30] <didrocks_busy> barry: right, until checkUpdateAvailable()
[13:30] <didrocks_busy> barry: which should reset the state basically
[13:31] <didrocks_busy> wdyt?
[13:31] <barry> didrocks_busy: i have to think about that one ;).  resetting the state without restarting the process may be difficult, but let me study and poke at things to see if it's possible
[13:32] <didrocks_busy> barry: ok, because I have no way to restart after a failure :p
[13:32] <jdstrand> sergiusens: if you apt-get update and apt-get sit-upgrade again, it should work
[13:32] <didrocks_busy> barry: or just have to wait 2min
[13:32] <didrocks_busy> this is kind of annoying ;)
[13:32] <didrocks_busy> (even for testing)
[13:32] <jdstrand> s/sit-upgrade/dist-upgrade/
[13:32] <jdstrand> https://launchpad.net/ubuntu/+source/click-apparmor/0.0.5
[13:33] <barry> didrocks_busy: did you see my comment about .Reset()?
[13:33] <barry> (and about .Exit()?)
[13:33] <jdstrand> sergiusens: fcan you let me know if it works for you?
[13:34] <barry> didrocks_busy: .Reset() is only a --testing method, but i could add .Exit() and promote it to a "live" setting.  then dbus activation would automatically restart the process with new state
[13:34] <barry> (without waiting for the 2m timeout)
[13:36] <didrocks_busy> barry: I don't see a .Exit()
[13:36] <sergiusens> jdstrand: ack, will try that in a bit
[13:36] <didrocks_busy> barry: but good for .Reset()! I'll do that in case of cancel or failure then
[13:36] <didrocks_busy> barry: or just tell me if you have .Exit…
[13:37] <didrocks_busy> barry: so timeout + changing the Cancel behavior + Exit()?
[13:37] <didrocks_busy> sorry timeout -> delay on all checkUpdateAvailable() and GetUpdate() to deliver their signal?
[13:37] <barry> didrocks_busy: right, i mentioned the phantom .Exit() in my email, but i can certainly add it
[13:37] <didrocks_busy> barry: keep me posted, I'm mostly done on the UI side right now
[13:37] <barry> didrocks_busy: i would much rather add .Exit() than try to reset state at this point :)
[13:38] <barry> i think these changes would not take long.  can you run things from the bzr trunk, or do you want me to just upload the changes?  (i'd love it if you tested locally before upload)
[13:38] <barry> didrocks_busy: ^^
[13:39] <barry> didrocks_busy: oh, and do you want .Exit() for the production version, or just for --testing?
[13:39] <didrocks_busy> barry: production please
[13:39] <barry> didrocks_busy: +1
[13:40] <didrocks_busy> thanks barry ;)
[13:40] <didrocks_busy> barry: just tell me, I'll run that locally
[13:40] <barry> didrocks_busy: sounds good.  will ping you asap
[13:40] <didrocks_busy> barry: btw, thanks for the small hunting this morning, I had to dive a little bit to see I needed the -dev package (your -dev package in the description is wrong as well btw :p)
[13:40] <didrocks_busy> barry: thanks! ;)
[13:41] <barry> didrocks_busy: oops ;)  i'll fix the description in the package branch for next upload.  thanks for the great feedback
[13:41] <ogra_> didrocks_busy, are you particulary more busy than other days that you carry this tail on your nick ?
[13:41] <ogra_> :)
[13:43] <didrocks_busy> ogra_: just a little bit (I overflow this time :p), seems everyone wants to get things for IoM…
[13:44] <ogra_> heh, yeah
[13:44] <w-flo> yay, my initramfs works now, according to a log file control reaches the exec run-init call :) now I need to figure out why the phone bootloops.. sigh
[13:45] <ogra_> w-flo, most likely missinf console options ... init needs an actual device to attach to
[13:45] <ogra_> compare your kernel config with one of the nexus ones
[13:51] <cyphermox> tvoss_: ping?
[13:53] <tvoss_> cyphermox, pong, sorry, restarting constantly
[13:53] <cyphermox> tvoss_: sure. I saw we have a lp:mtp branch. how would I go about using that?
[13:58] <tvoss_> cyphermox, the package installs an example mtp server
[13:58] <tvoss_> cyphermox, if you run that server on the phone, and connect via usb to the desktop, you should see an image folder with ten items
[13:58] <tvoss_> cyphermox, those are just dummy items
[13:59] <cyphermox> ok
[13:59] <cyphermox> but good then if we have at least example stuff, thanks!
[14:00] <cyphermox> tvoss_: is anyone working on / planning to / making a proper actual mtp server app with this to server iamges and music and such?
[14:00] <tvoss_> cyphermox, yup, that will be integrated with lp:content-hub
[14:00] <tvoss_> cyphermox, that's planned at least, I haven't started working on it
[14:01] <cyphermox> tvoss_: ok, you'd be the one doing that?
[14:01] <tvoss_> cyphermox, any help appreciated. The first step would be to write a proper MtpDatabase implementation actually touching the filesystem
[14:01] <cyphermox> tvoss_: do you have a rough plan as to when you'll be working on it?
[14:01] <ogra_> tvoss_, note that you will likely have to implement protocol switching support for the android gadget to have it fully working
[14:02] <tvoss_> ogra_, aware of that :)
[14:02] <ogra_> mtp support is currently completely removed
[14:02] <tvoss_> cyphermox, given my current workload: 2014 ;)
[14:02] <tvoss_> cyphermox, why do you ask?
[14:02] <cyphermox> tvoss_: haha :)
[14:03] <cyphermox> tvoss_: because my name was at mtp for the monthly plans and such, and tbh I kind of ignored it a whole lot more than I should have
[14:03] <cyphermox> I was asked how that was going, and I didn't know there was lp:mtp
[14:03] <cyphermox> so, very happy to see it's much less bad that I expected
[14:04] <tvoss_> cyphermox, happy to hand over tbh ;)
[14:04] <tvoss_> it really comes down to implementing MtpDatabase to access the filesystem
[14:04] <tvoss_> that would be the first step
[14:04] <cyphermox> tvoss_: ahah, not sure if I can start to complete that now but yeah, perhaps
[14:05] <cyphermox> tvoss_: can we discuss it in a hangout on, say, August 5? today I'll still be working on bluetooth, and I'm on vacation next week
[14:05] <tvoss_> cyphermox, ack
[14:05] <tvoss_> ack, works for me
[14:05] <cyphermox> tvoss_: awesome
[14:05] <tvoss_> cyphermox, please add it to my calendar though
[14:05] <cyphermox> sure
[14:05] <cyphermox> what time is best? any free?
[14:06] <cyphermox> for example, around 14 UTC?
[14:12] <cyphermox> tvoss_: you should have an invite
[14:12] <tvoss_> cyphermox, thx
[14:12] <cyphermox> thx
[14:13] <lool> barry: didrocks just finished https://code.launchpad.net/~didrocks/ubuntu-system-settings/ignore-local-settings/+merge/177150 !  but not tested against real daemon (only mock); he mentioned some update stuff was missing
[14:14] <barry> lool: there are a few dbus api changes we just discussed. i'm working on getting those in now
[14:30] <davism> Im having issues with my install of ubuntu touch
[14:31] <davism> after following the instrutions my device has gone into  CWM-based Recovery v6.0.2.8
[14:31] <davism> I am unsure which otions on it to use please someone help
[14:31] <davism> imon a nexus 7 btw
[14:40] <cyphermox> davism: it is supposed to go in recovery for part of the installation. what does phablet-flash say when you ran it? did it complete successfully?
[14:40] <davism> yes
[14:40] <davism> was complete sucessfully
[14:41] <cyphermox> saying that the phone will reboot?
[14:41] <davism> when it reboots the tablet just shows a google logo and stays on that
[14:41] <sil2100> bzoltan1: argh!
[14:41] <sil2100> bzoltan1: curse you SDK people!
[14:41] <ikercv> hi all
[14:42] <sil2100> bzoltan1: how could you change the python package name without informing us!
[14:42] <cyphermox> davism: perhaps just try to run phablet-flash -b again
[14:42] <ikercv> does anyone know where can I find some info about how to add contacts from a vcard file or other format=
[14:42] <davism> I tried but i cant get on android so it wont do it
[14:43] <cyphermox> davism: reboot into the recovery then run: phablet-flash -b -d grouper
[14:43] <cyphermox> that should automatically reboot it in bootloader and reflash
[14:43] <cyphermox> presuming it's a nexus 7, of course. if not, you don't want to write "grouper" there
[14:44] <davism> yes it is a nexus 7 its doing something now give me a sec
[14:45] <davism> says reinstalled and then it went to recovery shall i click reboot system now?
[14:45] <cyphermox> no
[14:46] <cyphermox> the system is supposed to reboot by itself
[14:46] <cyphermox> if it doesn't , something is not working right
[14:46] <davism> it says autodeply.zip not found :?
[14:47] <davism> sorry to be a pain
[14:47] <diwic> davism,  autodeploy not autodeply ?
[14:47] <sergiusens> davism: shouldn't matter
[14:48] <sergiusens> oh, wait, if you did -b it does matter
[14:48] <davism> yes autodeploy.zip
[14:48] <sergiusens> davism: pastbin full output of phablet-flash?
[14:49] <cyphermox> could be an out of date phablet-flash and possibly not putting the file in the right place
[14:50] <davism> right its rebooted its self just on a loading screen witha  droid on it
[14:51] <sergiusens> davism: don't touch the device while phablet-flash is doing it's thing
[14:52] <sergiusens> still need that full output
[14:52] <davism> not doing
[14:53] <davism> gettin! thankyou guys working perfectly
[15:14] <alcides> Ubutun Edged Goal: 20.4192%
[15:18] <ogra_> alcides, ++
[15:20] <alcides> ogra_ got one to yourself?
[15:21] <ogra_> well, "got" as much as getting can go here :)
[15:21] <ogra_> i paid for one :)
[15:21] <ogra_> and lend someone else the money for his
[15:22] <bzoltan> sil2100:  what package name?
[15:22] <alcides> ogra_ lend me some money too
[15:22] <alcides> XD
[15:22] <ogra_> haha
[15:22] <ogra_> i'm not mark :)
[15:23] <alcides> XD
[15:24] <ogra_> lool, i just hear that lightdm work is already moving fast and should be ready soon
[15:24] <ogra_> lool, seems like early next week we'll have something
[15:25] <bzoltan> ping sil2100
[15:25] <alcides> lovely
[15:29] <lool> ogra_: awesome
[15:30] <ogra_> lool, but we still have to wait for Mir in the archive
[15:30] <ogra_> (which is to happen "soon" since a week or two)
[15:30] <barry> didrocks_busy: i just pushed updates to my trunk branch for all the changes we discussed.  can you run it from trunk, or do you want me to create a local package that you can install and test?
[15:32] <didrocks_busy> barry: is there any PYTHONPATH trick or should I just run the daemon?
[15:33] <barry> didrocks_busy: best to create a python3 virtualenv, install it and run it from there, e.g.:
[15:33] <barry> virtualenv -p python3 /tmp/py33
[15:33] <barry> source /tmp/py33/bin/activate
[15:33] <barry> python setup.py install
[15:33] <didrocks_busy> barry: urgh, ok, packaging is in trunk? ;)
[15:34] <barry> system-image-dbus -C <your-ini-file> -vv --testing=<mode>
[15:34] <ogra_> asac, YAY !!! http://reports.qa.ubuntu.com/smokeng/saucy/image/3193/
[15:34] <barry> didrocks_busy: packaging is a separate branch.  it's easy for me to build a source and/or binary package for you if you want
[15:34] <asac> ogra_: is that what i think it is?
[15:34]  * asac uses mouse
[15:34] <ogra_> asac, it is, mako is still running though
[15:34] <didrocks_busy> barry: yeah, that would speed me up, thanks!
[15:35] <barry> didrocks_busy: will do
[15:35] <asac> ogra_: nice... thts with unity8? sdk and security are missing :/
[15:35] <ogra_> asac, one test failing, 99.0% coverage and green
[15:35] <asac> can you get those results so i can send out hugs?
[15:35] <didrocks_busy> barry: thanks!
[15:35] <ogra_> i think they will just run
[15:35] <rickspencer3> asac, hugs? 99 < 100, no?
[15:35] <rickspencer3> j/k
[15:35] <ogra_> plars, ^^^ does that need manual poking ?

[15:36]  * ogra_ pokes rickspencer3 in the belly with a pointy finger
[15:36] <rickspencer3> (pretty impressive, actually_
[15:36] <plars> ogra_: sdk and security? I can run them manually, I was told that asac asked for them to be disabled last week
[15:36] <asac> rickspencer3: waiting for final results. the big hugs will go to unity8 team - they really did a flawless landing
[15:37] <asac> rickspencer3: turned on, green right away
[15:37] <ogra_> plars, well, he just asked for running them again :)
[15:37] <rickspencer3> asac, yeah, that's what it sounds like
[15:37] <asac> rickspencer3: so guess the other apps dont get more time to rest :)
[15:37] <asac> no reason to not add the rest of what we have next week
[15:37] <rickspencer3> go go go!
[15:37] <asac> let me wait for all results coming together
[15:37] <plars> ogra_: they are running now
[15:38] <ogra_> thanx
[15:38] <tsdgeos> any sdk guy around?
[15:38] <tsdgeos> Kaleo: ?
[15:38] <Saviq> tmoenicke, that sound related http://paste.ubuntu.com/5915197/ ?
[15:39] <sil2100> bzoltan: it's fixed already ;)
[15:40] <sil2100> bzoltan: the python package name has changed from UbuntuUiToolkit to ubuntuuitoolkit
[15:40] <sil2100> bzoltan: and the stack wasn't redeployed after modification, so it was failing ;)
[15:40] <sil2100> bzoltan: but it's all cool now
[15:41] <tmoenicke> Saviq: yep, where did that happen?
[15:42] <Saviq> tsdgeos, ↑
[15:42] <tsdgeos> tmoenicke: i'm just running the shell
[15:42] <tsdgeos> as of now
[15:42] <tsdgeos> and get that
[15:42] <tsdgeos> 99% of the runs
[15:42] <tsdgeos> tmoenicke: on the desktop
[15:44] <tmoenicke> tsdgeos: does it crash or is it just the log?
[15:44] <tsdgeos> tmoenicke: crashes
[15:44] <tsdgeos> that's the gdb backtrace
[15:44] <heath> i purchased the nexus4 so that i could run ubuntu on it
[15:45] <heath> i was able to live with the phone for 3 months before it slipped off a surface all of its own accord and broke itself
[15:45] <heath> to developers of the ubuntu edge hardware: please don't make it slippery
[15:45] <heath> ty
[15:45] <heath> that is all
[15:45] <ogra_> heath, it doesnt have a glass back
[15:46] <heath> \o/
[15:46] <ogra_> it might indeed slip of you put it on its face
[15:46] <heath> that's not a problem
[15:46] <ogra_> :)
[15:46] <heath> it's always placed on its back
[15:47] <heath> also... give me insurance!
[15:47] <j3r1ch0> hi there, anybody seen phablet-flash stall during downloading?
[15:47] <tmoenicke> Kaleo: ping
[15:47] <lool> heath: it will be so hard it wont break  ;-)
[15:47] <heath> :P
[15:48] <wilee-nilee> heath, Gravity a new concept for you. ;)
[15:48] <barry> didrocks_busy: http://barry.warsaw.us/debian/system-image-cli_0.9.1-0ubuntu1_all.deb
[15:49] <barry> didrocks_busy: http://barry.warsaw.us/debian/system-image-common_0.9.1-0ubuntu1_all.deb
[15:49] <barry> didrocks_busy: http://barry.warsaw.us/debian/system-image-dbus_0.9.1-0ubuntu1_all.deb
[15:49] <barry> didrocks_busy: http://barry.warsaw.us/debian/system-image-dev_0.9.1-0ubuntu1_all.deb
[15:49] <barry> didrocks_busy: it's lunch time here, but i'll still around for a few minutes to let you check those out
[15:50] <didrocks_busy> barry: thanks! grabbing those!
[15:52] <didrocks_busy> barry: so, just to confirm, if I cancel an update, I need then to exit() right?
[15:52] <didrocks_busy> (thanks for the timeouts, working well)
[15:53] <Saviq> kgunn, asac http://reports.qa.ubuntu.com/smokeng/saucy/image/3193/unity8-autopilot/
[15:53] <barry> didrocks_busy: yep
[15:53] <Saviq> olli_, http://reports.qa.ubuntu.com/smokeng/saucy/image/3193/unity8-autopilot/
[15:53] <asac> Saviq: i planned to send big hugs  once we have all results :)
[15:53] <Saviq> asac, :)
[15:53] <asac> but i can already give you a big hug here :)
[15:53] <barry> didrocks_busy: i'll file a bug about possibly resetting state and not requiring exit, but i think this close to the demo, that's too risky of a change to make
[15:53]  * asac hugs Saviq 
[15:53] <asac> flawless landing!!
[15:53] <asac> thanks so much
[15:53] <ogra_> ++
[15:53] <asac> "you know what to do" :)
[15:53] <kgunn> Saviq: thanks for being green
[15:54] <ogra_> Saviq rocks !!
[15:54] <didrocks_busy> barry: agreed
[15:54] <olli_> yay Saviq!
[15:54] <didrocks_busy> barry: thanks!
[15:54] <olli_> once again
[15:54] <Saviq> asac, let's wait for manta... I'm worried we hit the crasher
[15:54] <ogra_> manta doesnt look good all over
[15:54]  * kgunn wonders how to take back a hug?
[15:54] <ogra_> plars, looks like mako might like to have the webbrowser test re-run
[15:55] <ax562> anyone getting that ubunt phone?
[15:55] <didrocks_busy> barry: you are going to update that today as 0.9.1?
[15:55] <plars> ogra_: yes, I was just looking at that, we got a lot of slowpath warnings from the kernel while that one ran
[15:55] <ogra_> seems to be stuck since a while (or the dashboard is chating me)
[15:55] <didrocks_busy> barry: I can dep on that version reliably? ;)
[15:55] <plars> ogra_: and it took *way* too long
[15:55] <ogra_> yeah
[15:55] <barry> didrocks_busy: as soon as you give me the thumbs up, i'll release and upload 0.9.1
[15:55] <plars> ogra_: did you look at the console log?
[15:55] <plars> ogra_: what would cause that?
[15:55] <rickspencer3> that's a lot of green
[15:56] <ogra_> ax562, you mean the Edge ? ... many in here, yes
[15:56] <ogra_> plars, i saw some python tracebacks , but i only glanced over it
[15:56] <ax562> yeah...couldln't remember the name
[15:56] <ax562> looks promising
[15:57] <ax562> what are the chances it actually goes into production though?
[15:57] <plars> ogra_: Jul 26 14:38:03 ubuntu-phablet kernel: [  688.728154] WARNING: at /build/buildd/linux-mako-3.4.0/net/wireless/scan.c:590
[15:57] <ogra_> hmm
[15:57] <asac> Saviq: only mako and maguro are governed by martial laws right now :)
[15:57] <asac> so dont worry too much
[15:57] <didrocks_busy> barry: +1, working fine!
[15:57] <ogra_> plars, thats only a warning though
[15:57] <didrocks_busy> barry: enjoy your lunch :)
[15:57] <barry> didrocks_busy: LP: #1205398
[15:57] <plars> ogra_: yeah, we got a lot of them though, and it seemed to be taking an unusually long time to run
[15:58] <barry> didrocks_busy: awesome! thanks for testing it.  i will release and upload now
[15:58] <ogra_> plars, file a kernel bug so they can take a look at it
[16:02] <plars> ogra_: do we have a different kernel project for touch? or is it still just linux?
[16:02] <ogra_> linux-mako
[16:02] <ogra_> (linux-$subarch for all the devices)
[16:02] <ax562> ogra_, do you think the edge will ever hit production though?
[16:03] <ogra_> ax562, if enough people fund it (spread the word !)
[16:03] <ax562> hahaha
[16:04] <wilee-nilee> ogra_, So is the actual release of the edge on a phone is completely dependent on that fund raising?
[16:05] <ogra_> wilee-nilee, yes, it will only happen if the funding goal is reached
[16:05] <plars> manta seems to be getting a lot of failures
[16:05] <wilee-nilee> ogra_, Well I guess I will have to donate. ;)
[16:05] <ogra_> ++
[16:05] <ogra_> you definitely should if you want to see it happpen
[16:06] <ogra_> and tell your friends .. .. and their friends ... and people in the subway ... etc etc :)
[16:06] <ax562> I'm basically running something similar to the edge already
[16:06] <ogra_> heh, i doubt that :)
[16:06] <wilee-nilee> ogra_, The cross os use as a plugin to the desktop is rather unusual as far as I know, that makes it a interesting setup.
[16:07] <ax562> ogra_, you thinking if it does go to production they will use the x86 atom?
[16:07] <ogra_> yeah, tahts the big thing about the edge
[16:07] <ogra_> its actually a PC in your pocket
[16:07] <ogra_> even from its HW specs
[16:08] <ogra_> ax562, whatever gets the best performance buy the time production starts
[16:08] <ogra_> i would put my money on some octacore ARM ...
[16:08] <ax562> I am though, I run android and ubuntu 10.10 simultaneously on my lapdock
[16:08] <ogra_> sure
[16:09] <ogra_> thats not the same :)
[16:09] <ogra_> the android with UfA is an extra ...
[16:09] <ax562> what's the difference..lol
[16:09] <barry> didrocks_busy: 0.9.1 uploaded
[16:09] <ogra_> the big thing is the Ubuntu Touch turning into a desktop bit ...
[16:09] <ogra_> which doesnt involve android
[16:10] <ax562> ARM would have less out of the box support for ubuntu pc apps imho
[16:10] <ogra_> but gives you true convergence ... running the exact same OS in docked and undocked mode
[16:10] <ogra_> nearly all of the ubuntu archive is available on ARM
[16:11] <Kaleo> troyready: pong
[16:11] <ogra_> 95% or so i'd say ... some exotic things like free pascal arent
[16:11] <ax562> not all
[16:11] <didrocks_busy> barry: thanks!
[16:11] <ax562> i would say more like 75%
[16:11] <ogra_> nah, its a lot more
[16:11] <ogra_> what are you missing specifically ?
[16:11] <ax562> and that is more of a tradeoff similar app kind of thing
[16:12] <ax562> graphic apps and sound
[16:12] <ogra_> ??
[16:13] <ax562> games of course
[16:13] <ogra_> which graphc apps ... and my Ubuntu touch phone as well as my ubuntu chromebook desktop definitely has sound
[16:13] <ax562> off the top gimp shop
[16:13] <ogra_> and all sound apps i needed to date are available on ubuntu ARM
[16:13] <ax562> some music player apps
[16:13] <ogra_> which ones ...
[16:14] <ogra_> if you find any, please file a bug and we can fix it
[16:14] <ogra_> (apps that work on x86 but not on arm)
[16:14] <ax562> Not sure, I haven't messed with apt-get synaptic in quite a while
[16:15] <ogra_> on a recent ubuntu install there shouldnt be much missing ... its really only exotic stuff
[16:15] <ogra_> we worked pretty hard over the last cycles to have everything ported properly
[16:15] <ogra_> i.d say from 12.04 on there shouldnt be much missing anymore
[16:15] <ax562> It might be my version of ubuntu 10.10
[16:15] <ax562> cant upgrade
[16:16] <ogra_> ah, well, that were early days of ubuntu arm
[16:16] <ogra_> we only started with 9.04
[16:16] <ogra_> 10.10 was just three releases in ... for arm
[16:16] <ax562> but i love my setup and the edge makes my mouth water
[16:17] <ax562> yeah I wish I could upgrade
[16:17] <ogra_> 11.04 would be the first release that i'd actually have recommended to people
[16:17] <ax562> locked bootloader and proprietary drivers
[16:17] <w-flo> ogra_, thanks for the console cmdline hint! I've added console=tty to the cmdline (I don't have /dev/tty1 or similar, only /dev/tty), but it still fails =( I even tried adding "-c /dev/tty" to run-init. Can I somehow look at the init/run-init output? when calling it manually upstart complains about "/com/ubuntu/upstart: Connection refused", probably since it's not PID1.
[16:18] <ogra_> for arm desktop stuff
[16:18] <ax562> That's what my pc is running
[16:18] <ax562> x86 though
[16:18] <ogra_> well, you should upgrade ... thats EOL since quite a while
[16:18] <ogra_> w-flo, i didnt mean the kernel cmdline, but ratherthe kernel config
[16:19] <w-flo> whoops. okay. %)
[16:19] <ogra_> check that you have bits like signalfd, inotify, hw_console etc etc
[16:20] <ogra_> best is to compare the non HW specific options in your config with one of the nexus kernels
[16:21] <ax562> I mean I have mostly everything I want though
[16:21] <ogra_> ax562, well, i wouldnt do online banking with an EOL distro :)
[16:21] <ax562> haha
[16:22] <ax562> I really don't go into ubuntu that much
[16:22] <ax562> on pc anyways
[16:22] <ax562> only if I need to get down to some nitty gritty
[16:22] <ogra_> heh, i wouldnt do online banking with any supported windows version either ... but thats just me
[16:22] <ax562> I manually flashed my phones partitions this week though lol
[16:23] <ax562> haha
[16:23] <w-flo> so apparently I'm missing HW_CONSOLE. *enables that* :)
[16:23] <ax562> mbm really hooked people up with adding apt-get back into 10.10 on the moto's
[16:23] <ogra_> thats a good first step
[16:24] <ax562> but the onlly thing is I have to stay on gb or else I lose ubuntu :(
[16:24] <ogra_> w-flo, crossing fingers that this already helps :)
[16:26] <ogra_> asac, so now you can give out the rest of your hugs ... at least for maguro
[16:26] <ogra_> mako is still busy but no failures yet
[16:35] <ax562> locked bootloader :(
[16:35] <ax562> how is ubutu-touch coming along anyways...ubuntu os?
[16:35] <ogra_> it comes along ... you can make calls, send messages, surf the web etc
[16:35] <ogra_> still a lot of work ahead until 13.10
[16:35] <ax562> what happens in 13.10?
[16:35] <roman2861> How about Mir in UT? When it will be integrated?
[16:35] <ogra_> roman2861, the next weeks ...
[16:35] <ogra_> ax562, the release of ubuntu touch
[16:35] <ax562> oh shit really.  I hadn't heard.  That's coming up soon.
[16:38] <w-flo> ogra_, so it doesn't work with the new kernel config... too bad we can't see the init output. I've tried redirecting it to some place on rootmnt, but it seems like the phone reboots before anything is successfully written to flash..
[16:39] <ogra_> right, init breakage is hard to debug
[16:39] <ax562> alright ladies and gentlemen.  I'm off.  I might be back in here in a while.  talk to you all later.
[16:39] <w-flo> I will take a break from this now, thanks a lot for your continued help :)
[16:39] <ogra_> you can check /proc/last_kmsg from recovery mode
[16:40] <ogra_> but that wont reveal much either
[16:40] <w-flo> oh, like when the init script spawns adbd?
[16:40] <w-flo> (how do I enter recovery mode?)
[16:40] <ogra_> dunno, thats specific to your device
[16:40] <w-flo> ah... *that* recovery. lol
[16:40] <ogra_> usually by pressing both volume buttons when booting or so
[16:42] <ogra_> plars, is mako really stubborn today ? browser test passed since a while
[16:42] <ogra_> i dont see it moving further
[16:42] <ogra_> (or am i to impatient)
[16:43] <plars> ogra_: yeah, it got stuck for some reason, I'm running the rest now
[16:43] <plars> ogra_: they will show up on http://reports.qa.ubuntu.com/smokeng/saucy/image/3194/ soon
[16:43] <ogra_> thanks !
[16:44] <plars> camera will be in the update due to happen in 1 min. maybe friends if it finishes in time, the others should be in the next 15 min slot
[16:45] <ogra_> great
[16:45]  * ogra_ will do something weekendish then ... and return later 
[16:46] <davmor2> ogra_: how are today's images by the way?
[16:47] <ogra_> davmor2, great
[16:47]  * davmor2 thanks ogra_ and goes and grabs them
[16:53] <bzoltan> sil2100: ohh, the autopilot one ... well, it was not the SDK team's change :) the change came from QA.. more precisely from elopio
[16:54]  * bzoltan gently tosses elopio under the bus :)
[16:55] <sil2100> ;D
[16:59] <elopio> sil2100: did the change cause you troubles? I though that package was just being used on ubuntu-ui-toolkit.
[17:03] <doanac> anyone else seeing system-image.ubuntu.com is down?
[17:03] <sil2100> elopio: hi! Ah, we're using it for our daily-release integration testing
[17:04] <sil2100> elopio: so the change just made it not find the python test package, as we were looking for the old one - but it was quickly noticed, no problem :)
[17:04] <elopio> sil2100: I think I'm done with the big changes there, but if I feel adventurous again I'll ping you.
[17:05] <sil2100> elopio: thanks :) Grately welcome
[17:05] <sil2100> *greatly
[17:13] <ogra_> plars, mako looks perfect. can we have sdk and security too for it ?
[17:14] <plars> ogra_: absolutely, I'm just waiting on share_app to finish, then I'll kick those off
[17:14] <ogra_> yay, thanks
[17:15] <ogra_> asac, so looks like we made it ...
[17:15] <plars> ogra_: they are not very exciting tests btw (sdk and security)
[17:15] <ogra_> yeah
[17:15] <ogra_> and not likely to fail either
[17:15] <alcides> Ubutun Edged Goal: 20.58%
[17:15] <plars> nice
[17:16]  * ogra_ waits for 7mio before partying again :)
[17:16] <jdstrand> hey
[17:16] <plars> yeah, we'll hit the expected slowdown for a bit most likely, but I'm pretty impressed it got to 20% this soon, I was expecting more like 10% in the first days, then lingering until about a week before it ended
[17:16] <jdstrand> I consider the security tests to be very exciting :)
[17:17] <plars> jdstrand: no offense intended, the security tests do check some things at least :)
[17:17] <plars> jdstrand: the sdk one is just an apt-cache policy check at the moment though
[17:17] <ogra_> jdstrand, indeed and they make us feel safer !
[17:17] <jdstrand> plars: no offense taken, I was just teasing :)
[17:17] <jdstrand> ogra_: \o/
[17:17] <ogra_> :)
[17:18] <asac> ogra_: nicely ... sdk+security still on mako
[17:18] <asac> gogogo :)
[17:18] <ogra_> asac, yeah, they wont fail
[17:18] <ogra_> never did
[17:18] <plars> jdstrand: mostly I was just making sure he knew that at this point, they are extremely unlikely to fail
[17:18] <ogra_> manta will definitely need some love
[17:18] <asac> ogra_: so they run last ? e.g. a few days back there was a problem if they didnt show up :)
[17:18] <asac> could be that its not at the end
[17:18] <ogra_> but then we are really lacking devices
[17:19] <ogra_> asac, you asked for them to be disabled
[17:19] <ogra_> so they were now run manually by plars
[17:19] <asac> really?
[17:19] <ogra_> yes
[17:19] <asac> guess they should still be run on any image :)
[17:19] <plars> ogra_: well, we have some jenkins madness we are fighting on that end, I'm working on restructuring the jobs
[17:19] <ogra_> you wanted to just have the app tests run when they looked really bad
[17:20] <asac> i leave it to plars etc. to decide when we can run the automatically again
[17:20] <ogra_> and never reverted that order :)
[17:20] <plars> asac: I'm hoping to turn it on again over the weekend, or Monday at latest. With some improvements to speed as well I think
[17:20] <asac> for now they should jst be there at some point
[17:20] <plars> and lock safety
[17:20] <asac> cool :)
[17:20] <asac> plars: you think ou can get sdk/security for mako still for the .1 images today?
[17:20]  * ogra_ really wants to release a new /current image for the weekend
[17:20] <plars> asac: they are running right now
[17:21] <asac> the rest i dont care :)
[17:21] <asac> coolio
[17:21] <plars> what about the camera failure? did it get an exception?
[17:21] <ogra_> asac, am i ok with making that image /current ?
[17:21] <asac> plars: the 1 camera failure i am willing to look over once we see mako completing
[17:21] <ogra_> plars, we'll just pretend there was dirt on the lens so it couldnt focus :)
[17:21] <asac> but not for much longer
[17:21] <asac> :)
[17:22]  * plars tests calling locally, since that's not covered
[17:22] <ogra_> yeah, we need tests for 3G, calls, SMS and so on at some point
[17:23] <plars> ogra_: I have mako installed right here, I can spot check them at least
[17:23] <ogra_> yeah
[17:23] <plars> argh, --pending
[17:23] <ogra_> heh
[17:23] <plars> ok, I *will* have it installed soon
[17:23] <plars> :)
[17:24] <plars> at least I have a good habit of always checking the image I'm running even if I haven't yet got it through my head that I have to do --pending everytime yet :)
[17:24] <ogra_> yeah, i usually also flash them once cdimage spits them out
[17:25] <ogra_> but only do some rudimentary click around tests ... if apps start and i can browse its fine
[17:25] <plars> ogra_: that's a good plan, I should probably just leave it connected to my server here and have jenkins set up locally to look for the new image and flash it about the time I'm waking up in the morning
[17:28] <user82> is someone with a nexus 4 and android 4.3 round?
[17:43] <plars> argh, security barely missed the window, but it passed. mako should be complete on the dashboard in the next update in 2 min
[17:50] <ogra_> and so it is !
[17:51] <ogra_> YAY !!!
[17:51]  * ogra_ dances
[17:51] <ogra_> asac, so if you dont mind i'lll mark this one as current now
[18:01] <asac> ogra_: yeah do that
[18:03]  * ogra_ does so 
[18:05] <ogra_> DONE
[18:05] <ogra_> ah, that feels good :)
[18:06] <Tassadar_> ogra_: I'm probably like thousandth person who asks this, but will you make touch images also for the new N7?
[18:07] <ogra_> Tassadar_, not officially i fear
[18:07] <ogra_> but making it work wont be to hard
[18:08] <Tassadar_> I suppose, but nobody else will provide daily builds I'm afraid :)
[18:09] <ogra_> well, we have a ton of the old n7's across the teams
[18:09] <sergiusens> Tassadar_: if someone does the port, provides the patches, we can unofficially setup a weekly build
[18:09] <ogra_> i dont think we will invest more money just to support a newer model
[18:09] <ogra_> yeah, the driver situation wont differ from the other nexii :)
[18:10] <genii> Heh, nexii
[18:10] <ogra_> :)
[18:11] <Tassadar_> sergiusens: that seems wonderful, unfortunatelly I don't have the device. If nobody else does it by the time I have it though, I probably will
[18:14]  * ogra_ invested all his spare money into Ubuntu Edges
[18:14] <ogra_> no tablet for me the next time
[18:28] <rsalveti> ogra_: all green?
[18:29] <rsalveti> ogra_: for mako and maguro at least, good stuff
[18:29] <ogra_> yeah, that was the requirement
[18:30] <user82> ogra_, if i may ask: what did you manage to get done?
[18:31] <ogra_> user82, http://reports.qa.ubuntu.com/smokeng/saucy/
[18:31] <ogra_> our image smoke tests all finish fo rteh nexus phones now
[18:32] <user82> waht do those tests include?
[18:32] <ogra_> wasnt just my doing though
[18:32] <ogra_> read them
[18:32] <ogra_> there are logs, you can see exaclty what they do
[18:32] <user82> allright thx
[18:49] <asac> rsalveti: so where is manta :)?
[18:49] <asac> fail
[18:49] <asac> lol
[18:50] <asac> unbearable that even grouper is better :-P
[18:50] <asac> wonder how that could happen
[18:55] <rsalveti> asac: manta is faster, easier to get races
[18:56] <asac> rsalveti: lets slow it down :) ... we dont measure performance on dashboard yet :)
[18:56] <rsalveti> asac: haha, right
[18:56] <asac> feels a bit like an excuse to avoid discussion :)
[18:56] <asac> but ok
[18:56] <asac> i will just file it that way for now
[18:56] <Kimano> I would like to find the touch image to install to the SOny Xperia Z Tablet
[18:56] <rsalveti> well, we're working on the real fix as we speak
[18:57] <asac> rsalveti: whats the real fix?
[18:57] <asac> (for managers)
[18:57] <Kimano> I understand the Xperia T Image might be compatible
[18:57] <rsalveti> asac: android-upstart bridge, so we can get all the android events in the upstart jobs
[18:57] <rsalveti> like once a service is fully up and such
[18:57] <asac> ic
[18:58] <asac> sounds reasonable
[18:58] <asac> ensure its not done multithreaded please :)
[19:12] <asac> rsalveti: ogra_: ogasawara: ChickenCutlass: check mail
[19:12] <asac> convergence matrix
[19:12] <asac> thx!
[19:12] <asac> i think ogasawara might be off the hook if ChickenCutlass does it
[19:12] <asac> bye
[19:14] <rsalveti> asac: sure
[19:15] <mterry> Do today's 20130726.1 images work for anyone else on a nexus4?  After flashing, I just get the google logo on bootup
[19:16] <ChickenCutlass> asac, I see it
[19:18] <asac> mterry: really?
[19:18] <asac> L)
[19:19] <asac> mterry: dashboard was saying green :)
[19:19] <asac> mterry: please find someone to backup your claim
[19:19] <asac> that would be interesting
[19:19] <asac> (or triple check)
[19:24] <mterry> asac, hrm
[19:24] <mterry> asac, am flashing my nexus7 in meantime
[19:24] <asac> mterry: http://reports.qa.ubuntu.com/smokeng/saucy/image/3194/
[19:24] <asac> thats the run
[19:24] <asac> mterry: yuou could try to follow the links down to the jenkins job
[19:25] <mterry> asac, it's possible I got my nexus4 in a weird state too
[19:25] <asac> and find fromt here the "upstream" job that flashes and boots the image
[19:25] <asac> if that shows it really installs todays image :) ... then its likely that the image really booted and was able to run UI tests
[19:25] <mterry> should probably try total reset
[19:25] <asac> (which doesnt mean there is anything to see on the screen of course)
[19:25] <ChickenCutlass> mterry, works fine on my nexus 4
[19:26] <asac> i think one can really see that the media-info on the device running is what one would expect: https://jenkins.qa.ubuntu.com/job/saucy-touch-mako-smoke-phone-app-autopilot/25/consoleFull
[19:27] <asac> whether that means the device booted that I cannot see in that log though, but i guess its likely
[19:41] <mhall119> ogra_: so the N7's camera stops working after trying to take a picture
[19:41] <mhall119> killing and re-starting the camera app leaves no image preview, just like it had before the camera was working at all
[20:26] <plars> I have a small script in the test automation that is basically doing timeout 60s wait-for-network, but it's getting stuck sometimes
[20:26] <plars> currently, it's been running for 20m, and failed to timeout
[20:26] <plars> rsalveti: have you seen anything like this? doanac was theorizing that it could be because the device was idle long enough to go to sleep, then the timeout never fired?
[20:30] <rsalveti> plars: hm, could be
[20:30] <rsalveti> never had such issue though
[20:30] <plars> rsalveti: seems to work sometimes, other times not. currently about 50%
[20:31] <rsalveti> can you open strace/gdb against the pid to see what it's doing in there?
[20:31] <rsalveti> brb
[20:32] <plars> rsalveti: network isn't up, so I don't have a way to get strace
[20:33] <plars> rsalveti: the wait for network script is just doing a ping -c1 in a loop
[20:36] <plars> rsalveti: I think I see the problem, that script is trapping TERM and INT
[20:53] <rsalveti> plars: right
[21:01] <mhall119> rsalveti: ogra_: is there a way to get the IMEI number off my N4?
[21:01] <rsalveti> mhall119: if you put a sim card, the system settings should get that to you
[21:01] <rsalveti> mhall119: I still need to fix it to make it work without sim card
[21:01] <mhall119> ok
[21:22] <user82> mhall119, take the box it was delivered in :p
[21:25] <w-flo> omg, my device just booted with flipped containers! :D finally, a usable shell. now I need to figure out why unity is not up, but I guess that's doable.
[21:25]  * w-flo hugs ogra_ 
[21:28] <w-flo> oh and by the way, you were absolutely correct. I / the defconfig created by the inofficial cyanogen port for my device maintainer was missing some console features (*VT* configs)
[23:55] <urmysony> Hi Guys