[00:18] <cwayne> thomi, so something like this? https://code.launchpad.net/~cwayne18/address-book-app/autopilot-upstart/+merge/212747
[00:20] <thomi> cwayne: yup, that looks good. Not sure what else was in 'self.ARGS', and if you need that in upstart-land
[00:20] <thomi> but that's the right idea
[00:20] <thomi> I gotta go to lunch, but ping me if you need anything else
[00:20] <cwayne> all that was in there was --desktop-file-hint
[01:19] <solock> hello
[02:06] <lotuspsychje> whats the progress of ubuntu touch on tablets? any stable yet?
[02:09] <lotuspsychje> oh nvm i found this: http://www.omgubuntu.co.uk/2014/03/ubuntu-tablets-coming-year
[02:15] <luxixsd> 这里可以说汉语吗？
[02:16] <luxixsd> 我想知道手机安装ubuntu系统方法
[03:20] <adh0c> Hey, does anyone know why the Nexus 7 (WIFI 2012 - grouper) has been deprecated?
[03:21] <adh0c> At the time, Ubuntu touch was about half the reason I got the tablet in the first place. :-(
[04:01] <nhaines> adh0c: Because it's a different chipset, whereas the 2013 Nexus 7 has the same chipset as Nexus 4, I believe.
[04:02] <nhaines> adh0c: the goal is just to get the OS ready so that devices can ship and OEMs can pay for hardware enablement.  Nexus support is only around until devices are out.
[04:13] <adh0c> nhaines: That would make sense.  Guess I'm stuck with boring old android.
[04:27] <nhaines> adh0c: afraid so. :(
[05:14] <Mirv> davmor2: nope
[07:34] <tvoss> w00t, good morning
[07:35] <w00t> the only good morning is a dead one ;)
[07:36] <tvoss> that sets the stage ;)
[08:05] <zenpit> ho
[08:05] <zenpit> howdy*
[08:05] <zenpit> anyone on?
[08:06] <zenpit> I have a quick ? on how to set up mobile networks. Very new to ubuntu, and only dabbled with linux for 3 years (Mint 12 to Fedora 17-19)
[08:08] <zenpit> :p
[08:10] <zenpit> hey guys
[08:10] <zenpit> yall manage to get the network running for carriers on touch?
[08:12] <zenpit> howdy
[08:58] <dholbach> good morning
[09:07] <JamesTait> Good morning all!  Happy Purple Day! :-D
[10:05] <davmor2> Saviq: I have a general bug against scopes what package do I target?
[10:06] <Saviq> davmor2, what do you mean "general"? :)
[10:06] <Saviq> davmor2, probably unity8, and we'll reassign as needed
[10:07] <davmor2> Saviq: it effect all scopes
[10:07] <Saviq> davmor2, could mean you want unity-scopes-api, too
[10:07] <Saviq> davmor2, that's the scope-facing API
[10:08] <davmor2> Saviq: with the new scopes scroll up the page till the header disappears, then pull it back down, then on the header select a new scope
[10:08] <davmor2> Saviq: when the header says you are on the new scope scroll back up and the icons run into the header as a secondary bug
[10:10] <Saviq> davmor2, that's UI - unity8
[10:10] <Saviq> davmor2, all UI bugs are unity8
[10:10] <davmor2> Saviq: great thanks
[10:36] <Saviq> davmor2, see comment on bug #1297770
[10:37] <Saviq> davmor2, we really don't want to touch the header unless the issue is really bad
[10:37] <Saviq> since we'll be replacing the header whole
[11:04] <davmor2> Saviq: do you know when that work is likely to land?
[11:09] <Saviq> davmor2, hopefully within a few weeks - if not, we'll spend some time fixing them with the old header then
[11:11] <davmor2> didrocks: ^  so scope swipe side to side still works just the header that is broken.  Hence saying I wouldn't block on it.  Also it seems pretty pointless work if it is going away anyway  but I'm not sure how to address it.  We can make a comment on the bug I guess
[11:13] <didrocks> davmor2: needs to be discussed and approved by QA + management
[11:13] <didrocks> davmor2: I won't give advice on promotion or not seeing the latest feedback :)
[11:13] <davmor2> didrocks: that's fine I'll pass it up my line then
[11:24] <sergiusens> Mirv, can you take a look at https://code.launchpad.net/~sergiusens/phablet-extras/qtbase-opensource-src-gles/+merge/211808 ?
[11:32] <davmor2> Saviq: So I'll let jfunk know in a bit and comment on the bug.
[11:36] <Saviq> davmor2, ok
[11:48] <dpm> hi ogra_, we're adding a scopes template project to the SDK, which will require new dependencies to be installed: libunity-scopes-dev unity-scope-tool - after a discussion with bzoltan it seems we could add them to the seeds or to the qt creator plugin, but you'd be the best person to ask for advice. So what do you recommend we should do to ensure these dependencies are installed for Qt Creator to work properly with the new scopes template?
[11:49] <ogra_> dpm, is it needed at runtime ?
[11:50] <dpm> ogra_, libunity-scopes-dev is needed at build time to actually build the scope, and unity-scope-tool is needed at run time to run the scope from Qt Creator
[11:51] <ogra_> dpm, libunity-scopes-dev should go into sdk-libs-dev in the seed then (and if it has a runtime equivalent this needs to go to sdk-libs), unity-scope-tool sounds like it should be a dep of the SDK itself
[11:52] <dpm> thanks ogra_
[11:53] <dpm> pstolowski, bzoltan ^
[11:53] <ogra_> (runtime would likely be libunity-scopes0 by the looks of it)
[11:54] <dpm> I'm guessing libunity-scopes0 is already installed so that scopes can work at all
[11:55] <ogra_> though a dep perhaps ... it is not seeded atm
[11:55] <ogra_> yeah, comes in via unity-scope-scopes
[11:56] <dpm> ok, cool
[11:56] <ogra_> so only the -dev side needs seeding
[11:56] <dpm> sounds good
[11:58] <ogra_> dpm, seeds changed, i'll take care for the meta upload
[11:59] <pstolowski> dpm, ogra_ looks sensible, thanks
[12:02] <dpm> ogra_, to make sure I get it right: you're adding it to the desktop seeds so that Qt Creator has those dependencies installed, but not to the touch image, correct?
[12:03] <ogra_> dpm, i'm adding it to ubuntu-touch-sdk-dev
[12:03] <ogra_> (which i assume the SDK depends on) ... i.e. to our API framework
[12:04] <dpm> thanks ogra_. pstolowski, bzoltan, could you comment on that, to make sure we've got them in the right place? ^
[12:05] <ogra_> ah, sorry, the binary is only called: ubuntu-sdk-libs-dev
[12:05] <ogra_> no touch in the name :)
[12:05] <dpm> ah, ok
[12:06] <ogra_> on any case the meta package is ready for upload here ... i'll upload once i get confirmation
[12:10] <dpm> thanks ogra_, we'll come back to you as soon as I can get hold of the sdk guys
[12:10] <ogra_> yep
[12:11] <ogra_> no hurry
[12:11] <t1mp> dpm: the sdk guys are now all in a meeting
[12:11] <dpm> ok, thanks t1mp :)
[12:11] <dpm> I'll bug you when you're done :)
[12:18] <dpm> marcustomlinson, re: bug 1297397 I was helping kyleN trying to reproduce it, but to answer the questions in the comments, it seems that he had up-to-date packages. I'm not sure if the Author= think would be the cause for the missing symbol error. Do you have any ideas?
[12:21] <tonikasch> hi, any help with porting guide?
[12:22] <marcustomlinson> dpm: the author field is not the only problem but it is one of them. The missing symbol I'm pretty sure is due to linking against an older lib.
[12:24] <dpm> marcustomlinson, yeah, it seems the symbol comes from libzmq3, but he had the latest version installed
[12:28] <tonikasch> hi! using https://wiki.ubuntu.com/Touch/AndroidDevel   "Removals"... do you know how to make this error go away? *** ubuntu/libhybris/compat/media: MODULE.TARGET.EXECUTABLES.codec already defined by frameworks/av/cmds/stagefright.
[12:30] <marcustomlinson> dpm: you mean libzmqpp3?
[12:33] <dpm> marcustomlinson, yes, sorry, the C++ bindings, so libzmqpp3
[12:34]  * ogra_ wonders if people that name libs *ever* try to promounce what they name their libs :P
[12:51] <seb128> Mirv, seems like https://launchpad.net/ubuntu/+source/qtdeclarative-opensource-src/5.2.1-3ubuntu11 has regressions
[12:52] <seb128> Mirv, e.u.c has reports starting with that version, see https://errors.ubuntu.com/problem/85c403c4a05cd32a48a73b226340850faa45e785
[12:52] <seb128> in fact those seem to hit an abort in libqubuntumirclient.so
[12:53] <seb128> so maybe it's qtubuntu that has a regression ... but that didn't change recently
[12:57] <Mirv> tsdgeos: Saviq: ^ were there some new crashes recently? can you think if those patches in ubuntu11 could cause some problems? there are the V4 patches that replaced the abandoned x86 register fix, and then Don-t-crash-on-Runtime-getQmlImportedScripts.patch and Fix-global-object-handling-in-worker-script-JS-files.patch
[12:58] <Mirv> seb128: in the image results there doesn't seem to be a bump in crashes when that qtdeclarative went in
[12:58] <Mirv> but there are some untraced crashes otherwise with qt 5.2
[12:58] <seb128> Mirv, well look at the non debug bt in e.g https://errors.ubuntu.com/oops/3f8e7c0c-b4d3-11e3-90de-fa163e707a72
[12:58] <seb128> #4 0xb3e0d94c in ?? () from /usr/lib/arm-linux-gnueabihf/qt5/plugins/platforms/libqubuntumirclient.so
[12:59] <seb128> that hits an abort()
[12:59] <seb128> so maybe a change in qtubuntu or mir (though those didn't change recently)
[12:59] <seb128> issues started yesterday
[13:05] <Mirv> none of the 5 images with the ubuntu11 have a qmlscene .crash file in the image dashboard, just unity8 etc crashes. it would be useful to get a traceable crash.
[13:05] <seb128> it would
[13:05] <seb128> those might come from a silo somebody is tested
[13:05] <seb128> e.u.c could be better at providing those infos
[13:05] <seb128> is qtubuntu or mir in a silo?
[13:06] <Mirv> I guess the 3 V4 patches all should only affect x86, and the other two patches were fixes for bug #1294181 and bug #1294019
[13:06] <Mirv> qtubuntu is in the right edge preparation silo
[13:06] <seb128> well, it's unsure it's qtdeclarative, reports goes there because it's qmlscene which hits the bug
[13:06] <seb128> ok
[13:06] <Mirv> and mir in the greeter silo
[13:06] <seb128> so my bet would be that it's a bug in one of those silos
[13:07] <Mirv> that would explain not seeing it in the image results
[13:08] <seb128> is the right edge silo owned by Saviq?
[13:08] <seb128> Saviq, ^
[13:09] <Mirv> yes, as is the greeter one
[13:13] <hedz09> ogra_: I built the 3.2 kernel with sgx, it seems to boot fine but the kernel doesn't support the LCD :(. Is there any other way to display the UI to see if it is working?
[13:13] <ogra_> hedz09, i dont know of any other than actually having a screen
[13:16] <cwayne> zsombi, hiya, any idea why the ubuntuuitoolkit autopilot tests are getting stuck at: 08:29:48.917 DEBUG dbus:432 - Selecting objects of any type with attributes: {'objectName': 'testListElement5'}
[13:16] <cwayne> 08:29:49.482 INFO logging:45 - QQuickListView: _show_more_elements_below. Arguments (). Keyword arguments: {}.
[13:16] <cwayne> 08:29:49.639 DEBUG _uinput:546 - Dragging from 432,413 to 432,100
[13:16] <cwayne> for 5 hours?
[13:17] <ogra_> must be many objects :)
[13:18] <cwayne> but it also only happens on the touch_custom suite, which shows up as never finishing :(
[13:23] <zsombi> cwayne: no idea....
[13:25] <cwayne> zsombi, damn.  i logged a bug here: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1297846 for it, this is kinda blocking the customized image testing
[13:26] <Saviq> Mirv, seb128, still not sure you need me for anything :)
[13:26] <seb128> Saviq, those reports might be an abort in the edge ppa, so it's a fyi
[13:26] <zsombi> cwayne: if it only happens with the customized image, I'd need more input to reproduce it
[13:26] <Saviq> seb128, which reports?
[13:26] <seb128> Saviq, it's an issue with qtubuntu that started somewhere yesterday, we didn't have archive uploads
[13:27] <seb128> Saviq, read backlog?
[13:27] <Saviq> seb128, yeah, but didn't see what this related to...
[13:27] <seb128> Saviq, the urls I gave to Mirv 35 minutes ago
[13:27] <cwayne> zsombi, sure, what input would be helpful?
[13:27] <Saviq> seb128, /me reads further up
[13:27] <seb128> Saviq, https://errors.ubuntu.com/problem/85c403c4a05cd32a48a73b226340850faa45e785
[13:27] <cwayne> just steps to reproduce? it's been hard for me to repro locally, but happens in the dashboard 100% of the time
[13:27] <Saviq> Mirv, no, no new crashes that could be caused by v4 afaict, we have three distinct ones we're looking into, one we can't reproduce, another is fixed by thumbnailer going into UITK, one more on exit, so not critical
[13:27] <zsombi> cwayne: like what is the custom stuff you are using, so I can set teh same env
[13:27] <seb128> Saviq, click on individual reports are the bottom of the page, those have non debug bts but they hit an abort in libqubuntumirclient.so
[13:28] <cwayne> zsombi, ubuntu-device-flash --channel devel-proposed-customized has it all
[13:28] <zsombi> cwayne: would you mind to add this to the bug?
[13:28] <Saviq> seb128, mhm
[13:28] <cwayne> not at all, i'll add as much info as i can get
[13:28] <seb128> Saviq, since that started yesterday and neither qtubuntu or mir changed in the archive, I guess it might be reports from testers of a silo
[13:28] <Saviq> seb128, could be, yeah
[13:29] <zsombi> cwayne: also, would be nice to know what this image contain that is custom: theme? where's that located? what else?
[13:29] <Saviq> shame we don't get that info in errors :|
[13:29] <seb128> indeed :/
[13:29] <seb128> it's qmlscene which hits the error
[13:29] <seb128> so we get depends info from that one
[13:29] <seb128> but it's not very useful there
[13:29] <seb128> we might want to add some apport hook to collect more infos for qmlscene issues
[13:30] <seb128> like we could always include ppa in use versions, or versions of other things in the stack
[13:30] <seb128> like qtubuntu or mir
[13:30] <cwayne> zsombi, the theme AIUI should be the only thing that would affect this.. just added a bunch of info to the bug
[13:32] <hedz09> ogra_: hmm, no vnc server I guess?
[13:32] <zsombi> cwayne: awesome! thx!
[13:32] <ogra_> hedz09, heh, nope, Mir is still pretty young, no fancy third party apps that support it yet
[13:33] <cwayne> zsombi, np, please let me know if there's anything else I could add, i've been trying to figure this guy out for awhile now :)
[13:33] <ogra_> hedz09, we just only got screenshooting support :)
[13:33] <zsombi> cwayne: I hope I'll be able to repro on the device :)
[13:33] <zsombi> cwayne: it could be that there was some style element the AP is trying to look after...
[13:35] <cwayne> zsombi, i hope you're able to reproduce too :)
[13:42] <kyleN> hey marcustomlinson. Thanks for looking at bug https://bugs.launchpad.net/unity-scopes-api/+bug/1297397. As you can see the undefined symbol happens when running unity-scope-tool even without a scope (no .ini file as arg).
[13:42] <hedz09> ogra_: ahh :).
[13:52] <tsdgeos> Mirv: can't really say tbh
[14:02] <cwayne> zsombi, i think i reproduced here
[14:02] <cwayne> im not seeing the same output though, but it appears hung
[14:09] <cwayne> yep, definitely got it frozen here
[14:11] <sergiusens> slangasek, can you take a look at https://code.launchpad.net/~sergiusens/phablet-extras/qtbase-opensource-src-gles/+merge/211808 when you have a minute? Need to know if this is the right direction
[14:11] <cwayne> zsombi, ^ any logs, debugging I can add to the bug since i've got it int his state
[14:11] <tsdgeos> Mirv: i ran crypto.js in the phone that is the problem that was because of the register thing and works fine
[14:12] <tsdgeos> so may be or may not, but at least is not the exact problem we had
[14:16] <Mirv> tsdgeos: sounds good
[14:16] <zsombi> cwayne: add whatever you get
[14:20] <cwayne> zsombi, nothing useful that i can see.. just dpkg-architecture: warning: couldn't determine gcc system type, falling back to default (native compilation) a bunch
[14:20] <zsombi> cwayne: that's irrelevant
[14:20] <cwayne> yeah, that's what i figured
[14:20] <cwayne> but that's all that i see in stdout
[14:20] <cwayne> unless there's some logfile it dumps somewhere
[14:36] <rickspencer3> hey all, is there a way for me to take a screenshot using adb these days?
[14:36] <seb128> rickspencer3, https://lists.launchpad.net/ubuntu-phone/msg06853.html
[14:36] <rickspencer3> thanks seb128
[14:36] <seb128> yw
[14:37] <rickspencer3> wow
[14:37] <rickspencer3> that looks complicated lol
[14:37] <ogra_> time to get that merged into phablet-screenshot i guess
[14:37] <nijo> is there any way i can be a part of ubuntu touch dev team??
[14:37]  * ogra_ saw seb128 pasting this twiice already today
[14:37] <rickspencer3> thanks to ogra_ for making it simple :)
[14:37] <ogra_> :)
[14:37] <rickspencer3> I was wondering why seb128 had it so easy at hand
[14:38] <seb128> ogra_, yeah, people keep asking about it :p
[14:38] <ogra_> right
[14:40] <rickspencer3> nice one ogra, works great
[14:40] <ogra_> enjoy
[14:40] <ogra_> next stop ... videos :)
[14:46] <sergiusens> rickspencer3, there's an MR from someone which I acked and ogra_ seems to as well; but not sure about the contributor agreement and all that stuff
[14:46] <ogra_> sergiusens, nope, i set it to "needs work"
[14:46] <sergiusens> I think we decided phablet-tools was free for all, but need to confirm
[14:46] <ogra_> asking to get the hardcoded resolutions ripped out first
[14:46] <sergiusens> ogra_, oh, did you see the updates though? it has
[14:46] <ogra_> but i think i'll just prepare another MP that does this
[14:46] <rickspencer3> sergiusens, ogra_ you are asking if phablet tools falls under the contributor agreement?
[14:46] <sergiusens> rickspencer3, yes
[14:47] <ogra_> sergiusens, ah, no, i didnt see code updates :)
[14:47]  * ogra_ goes checking
[14:47] <rickspencer3> sergiusens, I don't think it does, pmcgowan ^ do you know? is it listed on the wiki?
[14:48] <ogra_> it is a bunch of scripts ... i wouldnt put it under the agreement ... but IANAL :)
[14:49] <ogra_> sergiusens, ok, one issue with manta in that code change ...
[14:49] <sergiusens> ogra_, put that in the MR :-)
[14:49] <ogra_> yeah
[14:50] <pmcgowan> rickspencer3, we do not have it listed, but that was not an explicit decision afaik
[14:51] <rickspencer3> pmcgowan okay
[14:51] <rickspencer3> I think that we probably won't list it, but let me follow up
[14:52] <pmcgowan> seems fine either way
[14:52] <pmcgowan> just scripts as ogra says, and a little Go?
[14:52] <ogra_> i dont think there is go in phablet-tools
[14:52] <ogra_> shell and python
[14:56] <pmcgowan> sergiusens, when I do adb devices -l on a Flo it tells me the following:
[14:56] <pmcgowan> 05f10a69               device usb:2-1.2 product:occam model:Nexus_4 device:mako
[14:56] <pmcgowan> is that expected?
[14:57] <ogra_> pmcgowan, totally not
[14:57] <ogra_> is that fully booted into a working system ?
[14:57] <pmcgowan> yes
[14:57] <sergiusens> ogra_, didn't you already log a bug for that?
[14:57] <ogra_> and there is definitely nowhere a mako attached to that machine
[14:57] <pmcgowan> nope
[14:57] <pmcgowan> and nope
[14:58] <pmcgowan> yes its fully booted and there is no mako attached
[14:58] <ogra_> sergiusens, no, it should not happen anymore except from initrd where we have it hardcoded
[14:58] <pmcgowan> rick saw the same
[14:58] <pmcgowan> I have build 237 here
[14:58] <pmcgowan> should update this thing
[14:58] <ogra_> the gadget setup happens completely from the android side now
[14:58] <ogra_> which means it should use the values from there
[14:58] <sergiusens> pmcgowan, you are missing out on the new scopes; they look really nice.... and useful!
[14:59] <ogra_> so on flo it should also say flo
[14:59] <pmcgowan> ogra_, but rickspencer3 saw it with latest promoted
[14:59] <quebre> hello all
[14:59] <quebre> i have question
[14:59] <quebre> https://wiki.ubuntu.com/Touch/Building
[14:59] <ogra_> pmcgowan, yeah
[14:59] <ogra_> ogra@styx:~$ adb devices -l
[14:59] <ogra_> List of devices attached
[14:59] <ogra_> 07b2f660               device usb:3-1 product:occam model:Nexus_4 device:mako
[14:59] <ogra_> me too
[14:59] <pmcgowan> huh
[14:59] <quebre> do i need to have bootloader unlocked in order to start building ?
[15:01] <sergiusens> quebre, not for building; just for installing
[15:01] <quebre> sergiusens: i have Samsung tab 3 SM-T210 - i think it have locked bootloader - if it is locked, can i unlock it ?
[15:02] <sergiusens> quebre, not sure how that one works, if it uses fastboot, yes; don't think there's a concept of locks for other devices
[15:03] <quebre> sergiusens: hmm, how can i check if the bootloader is locked ? and how to check if it uses fastboot ? sorry if questions are lame but i'm complete noob, just started learning this stuff..
[15:03] <sergiusens> quebre, I really don't now the specs of your device; can you google around a bit?
[15:03] <quebre> ok
[15:04] <quebre> sergiusens: in specification it should say whether it uses fastboot right ?
[15:04] <sergiusens> yes
[15:04] <sergiusens> well, not sure
[15:04] <sergiusens> quebre, just figure out how to get a custom recovery
[15:05] <pmcgowan> ogra_, any idea what the issue is?
[15:05] <ogra_> pmcgowan, not without digging
[15:05] <ogra_> we dont set anything for the device on the ubuntu side anymore ... at least we shouldnt, i have to check if i have overseen anything
[15:06] <quebre> sergiusens: you meant recovery from the TWRP program ?
[15:06] <quebre> sergiusens: i have TWRP installed on that rooted tablet..
[15:06] <ogra_> on the ubuntu side we only start adbd now when the property is set in android, we dont put any additional configuration in
[15:07] <sergiusens> quebre, yeah; then you should be fine, we use a different recovery, but if you can install the built recovery, you should be fine
[15:07] <quebre> sergiusens: built in recovery ?...
[15:07] <quebre> ;/
[15:07] <ogra_> pmcgowan, i assume it properly says Nexus7 in nautilus and other places ?
[15:08] <pmcgowan> ogra_, yes
[15:08] <sergiusens> quebre, after you do the portig, you will have a recovery.img
[15:08]  * ogra_ will check after the meeting he is in ... had to move to another machine
[15:12] <slangasek> sergiusens: https://code.launchpad.net/~sergiusens/phablet-extras/qtbase-opensource-src-gles/+merge/211808> I'm surprised you need to build separate gles versions of the database packages (libqt5-sql5-{mysql,odbc,sqlite,...}) ?  Surely these binaries are unaffected by the GL/GLES ABI, and we should have only one version of these in the archive
[15:13] <slangasek> sergiusens: likewise a number of the other binaries listed there
[15:15] <sergiusens> slangasek, I'm just building them, but don't plan to use them to avoid to a big delta in the packaging; should be easy to remove though
[15:15] <slangasek> sergiusens: I don't want them in the archive at all :)
[15:16] <sergiusens> slangasek, I'll remove that then ;) is the rest ok though?
[15:16] <slangasek> sergiusens: as far as I can see
[15:16] <sergiusens> great
[15:29] <rickspencer3> mhall119, is that click package validator available in QtCreator today?
[15:30] <popey> rickspencer3: been in there for a while
[15:30] <rickspencer3> popey, how do I get to it?
[15:30] <popey> packaging button on left
[15:30] <rickspencer3> popey, right, so I get hte packaging form, but I don't see the validation
[15:30] <popey> sorry, publish button
[15:30] <ogra_> slangasek, probably the databases work faster if they have hardware acceleration support :)
[15:31] <popey> rickspencer3: qtc 3.0.1?
[15:31] <rickspencer3> popey, I did a dist-upgrade this morning, so should have the latest, right?
[15:32] <rickspencer3> fwiw, the plugins dialog says the plugin is 3.0.1
[15:32] <popey> rickspencer3: hmm, i last tested it some weeks back..
[15:32] <popey> rickspencer3: do you have click-reviewers-tools installed?
[15:33] <rickspencer3> popey, nope
[15:33] <rickspencer3> shall install that package?
[15:33] <popey> yes
[15:33] <popey> you need that
[15:33] <slangasek> ogra_: I'm sure it's possible to write stored procedures in GL
[15:33] <rickspencer3> now restart QtCreator, I guess?
[15:34] <ogra_> mterry, nice new animation for the bootsplash !
[15:34] <mterry> ogra_, you like it?  Nice.  MacSlow is working on a tweak that makes it a spinning logo instead of just a busy spinner  :)
[15:34] <rickspencer3> nice!
[15:35] <mhall119> bzoltan: click-reviewers-tools really should be a recommends on the ubuntu sdk metapackage
[15:35] <ogra_> i like the current one though ... but yeah, spinning logo will be nice as well
[15:35] <popey> rickspencer3: ya
[15:35] <rickspencer3> ok
[15:35] <bzoltan> mhall119:  it is afaik
[15:35] <MacSlow> ogra_, newer bling soon :)
[15:35] <rickspencer3> now time to try the new scanner, etc... :)
[15:35] <ogra_> MacSlow, cant wait !"
[15:35] <popey> its very neat
[15:36] <MacSlow> maybe I can manage to sneak in cloth anim ;)
[15:37] <mhall119> bzoltan: ah, so probably just rickspencer3 needed to apt-get install --fix-policy to make it add that
[15:39] <popey> mhall119: heh, just ran that and pulled in a bunch more packages
[15:39] <ogra_> mterry, hrm, looking at a bootchart of the split greeter atm, is iot really necessary to start *all* indicators in the lightdm session ?
[15:39] <mterry> ogra_, which ones aren't used?
[15:39] <ogra_> even multiple times
[15:40] <mterry> multiple times?  that sounds like a bug
[15:40] <ogra_> mterry, yeah, its only three indicators, but they start 6 times each ... i mistook that for 18 indicators :P
[15:41] <mterry> ogra_, start 6 times!?
[15:41] <mterry> ogra_, I did not notice that
[15:42] <mterry> ogra_, hmm I bet they are starting before unity8 is up.  I'll play with that
[15:42] <ogra_> mterry, http://people.canonical.com/~ogra/greeter-bootchart.png
[15:43] <mterry> ogra_, neat thanks
[15:43] <ogra_> -datetime only starts twice
[15:44] <mterry> good ol' datetime
[15:44] <ogra_> but -power and -location seems to be in a loop
[15:44] <ogra_> maliit-server starts twice too
[15:45] <ogra_> hmm ... and the greeter itself seems to also start several times
[15:48] <ogra_> ah no the first two seem to be some script the text is cropped after greeter-
[15:52] <seb128> dbarth, oSoMoN: seems like the 03-19 webbrowser-app updated started hitting errors, see https://errors.ubuntu.com/problem/3b4bb118a9479a6dd49d5fe57af9934f7f331ee4
[15:52] <seb128> hum, those are issues from qtubuntumir.so as well though
[15:53] <seb128> could be the same issue I pointed Saviq at earlier
[15:53] <seb128> Saviq, ^
[15:58] <ogra_> pmcgowan, aha .... ! i think that wrong naming is  PC side, the udev rules for adb dont know about flo
[15:58] <pmcgowan> I wondered
[15:58] <Saviq> seb128, it's unlikely that silo 015 has anything to do with that, though...
[15:59] <davmor2> popey: pffff rickspencer3 had my hopes raised then I thought that app was call dbiscuit :D
[15:59] <popey> gets me every time too
[15:59] <seb128> Saviq, right...
[15:59] <Saviq> seb128, there's only removal of sflinger support in that silo
[15:59] <Saviq> seb128, doesn't actually touch any existing code
[16:00] <seb128> Saviq, yeah, likely something else then...
[16:00] <pmcgowan> ogra_, which files is that?
[16:00] <seb128> Saviq, shame we don't have a debug bt and versions info
[16:00] <ogra_> pmcgowan, /lib/udev/rules.d/70-android-tools-fastboot.rules ... but adding 4ee2 there doesnt change it
[16:00] <Saviq> seb128, yeah, that weird :|
[16:01] <ogra_> pmcgowan, i think there is code involved in adbd too
[16:02] <ogra_> aha
[16:02] <ogra_>     static const char *values[] = {
[16:02] <ogra_>         "occam",
[16:02] <ogra_>         "Nexus 4",
[16:02] <ogra_>         "mako",
[16:02] <ogra_>     };
[16:02] <ogra_> there we go
[16:02] <dbarth> seb128: what's that?
[16:02] <dbarth> ouch
[16:03] <ogra_> pmcgowan, so the bug is in android-tools, adbd has the values hardcode
[16:03] <ogra_> d
[16:03] <pmcgowan> ogra_, I see
[16:09] <ogra_> pmcgowan, rickspencer3, bug 1297927 for reference
[16:09] <rickspencer3> thanks ogra_
[16:16] <pmcgowan> ogra_, you wrote "we hardcode" is that code we modified?
[16:16] <ogra_> yes
[16:17] <ogra_> when we didnt have properties available on the devices we needed to use a hardcoded value else adbd wouldnt start
[16:17] <pmcgowan> ok
[16:18] <ogra_> it is one of these duct tape and string interim hacks that worked so well that it was forgotten :)
[16:19] <dobey> is unity freezing hard for anyone else on image 262? i've as of yet been unable to unlock the screen at boot up, after 4 reboots
[16:19] <ogra_> the prob here is that we still want to be able to start adbd in situations where the property system isnt there ... for porters
[16:19] <ogra_> dobey, works fine here apart from some bugs
[16:20] <ogra_> (teh shell can go unresponsive but the edges still work for example ... thats a known one)
[16:20] <dobey> no, the edges aren't working at all for me
[16:21] <ogra_> right, that sounds like a new one then
[16:21] <dobey> this time for example, the lock screen froze halfway across the screen
[16:21] <dobey> and i can't do anything
[16:21] <ogra_> no issues here
[16:22] <ogra_> do you have a lot of music on the phone or some such ?
[16:22] <dobey> no, and it's not a phone
[16:22] <dobey> it's 2012 n7
[16:22] <dobey> i have nothing on it
[16:22] <ogra_> ah, unsupported HW
[16:22] <dobey> just ubuntu touch and a couple apps i installed
[16:23] <davmor2> dobey: I have 99 issues but that ain't one
[16:23] <ogra_> yeah, thats most likely tegra related
[16:23] <ogra_> we had our reasons to drop it :)
[16:26] <dobey> that's great, but not helping me
[16:29] <ogra_> well, you could file a bug, but i doubt it will be worked on soon
[16:29] <ogra_> most likely Mir
[16:32] <ogra_> dpm, so i still have that meta upload sitting on my desktop ... did bzoltan1 answer your question at some point ?
[16:33] <dpm> ogra_, not yet, just re-pinged him again
[16:33] <ogra_> thx
[16:40] <bzoltan1> ogra_: dpm: sorry, i am commuting right now :) I think it is fine to add that tool to the sdk-dev
[16:41] <dpm> thanks bzoltan1
[16:42] <bzoltan1> dpm: thanks to you :)
[16:44] <ogra_> bzoltan1, great, thanks !
[16:47] <daniele_> HI, I have read info on ubuntutouch here "https://wiki.ubuntu.com/Touch/Install" , I'd like to buy a "Nexus 10 	  manta 	  mantaray 	  Active development " .  anyway I don't know how to be sure to recognize the right model, may it be a "samsung"?? may I search a particular "model name" "model number or code"?? thanks
[16:50] <ogra_> daniele_, there is only one nexus10
[16:51] <daniele_> is it made by samsung?? I found this on amazon http://www.amazon.it/Samsung-Nexus-32GB-Tablet-Computer/dp/B00GZNHHZC/ref=sr_1_8?ie=UTF8&qid=1395850593&sr=8-8&keywords=Nexus+10#productDetails
[16:51] <ogra_> yes
[16:55] <daniele_> there are also these models anyway ,are all of them to be considered as "nexus 10" ??  http://www.amazon.it/Samsung-Google-Nexus-10/dp/B00ABYXNC2/ref=sr_1_2?ie=UTF8&qid=1395850593&sr=8-2&keywords=Nexus+10#productDetails   AND http://www.amazon.it/Samsung-Galaxy-Google-Nexus-16GB/dp/B00AGHO3LO/ref=sr_1_1?ie=UTF8&qid=1395850593&sr=8-1&keywords=Nexus+10#productDetails
[17:17] <davmor2> dobey: I blame you entirely for this https://bugs.launchpad.net/ubuntu/+source/unity-scope-click/+bug/1297965 ;) feel free to spread the blame though :)
[17:21] <popey> davmor2: confirmed
[17:21] <davmor2> popey: \o/ thanks
[17:24] <dobey> davmor2: does it have a different title on the icon, after you install it?
[17:26] <davmor2> dobey: looks like the space has been removed on the installed version
[17:27] <dobey> davmor2: ok, it's a dup
[17:27] <dobey> and totally not my fault :)
[17:28] <cwayne> popey, hey, any idea where shorts app gets it's feeds list from?
[17:30] <davmor2> dobey: I didn't say it was your fault I said I blamed you ;)  But then did add to feel free to spread the blame
[17:31] <davmor2> sil2100: ^
[17:32] <popey> cwayne: how do you mean, the two it gets by default or how it searches for new ones?
[17:32] <cwayne> popey, well, either really
[17:32] <cwayne> mostly the two default though
[17:33] <sil2100> dobey: hi, so you have any idea what is causing the problem?
[17:33] <popey> shorts-app.qml:            DB.addFeed("" , "http://design.canonical.com/feed/")
[17:33] <popey> shorts-app.qml:            DB.addFeed("" , "http://voices.canonical.com/feed/atom/")
[17:33] <popey> shorts-app.qml:            DB.addFeed("" , "http://blog.canonical.com/feed/")
[17:33] <popey> cwayne: it seeds the database on start if empty
[17:34] <dobey> sil2100: the app showing in installed and available both?
[17:34] <cwayne> ah, which db is that?
[17:34] <popey> cwayne: alan@deep-thought:~/.local/share/com.ubuntu.shorts$ ls
[17:34] <popey> Databases  ShortsSettings
[17:34] <davmor2> cwayne: the one you never are allowed access too :P
[17:34] <popey> /.local/share/com.ubuntu.shorts/Databases is where it is for me
[17:35] <cwayne> ah, cool
[17:35] <cwayne> so we could pre-seed that in the custom image then :D
[17:35] <popey> you could
[17:35] <davmor2> cwayne: other people could but you break things so you can't :P
[17:38] <cwayne> davmor2, hah, its not my fault i break things, it's part of my job :)
[17:50] <pmcgowan> hey popey I am still getting errors on OSMtouch app, even with the package seeded
[17:50] <pmcgowan> at least it tries to start now
[17:50] <popey> pmcgowan: interesting.. lemme test here
[17:50] <popey> pmcgowan: which image?
[17:50] <popey> pmcgowan: 262 here
[17:50] <pmcgowan> 262
[17:51] <popey> davmor2: did you file a bug about the scopes and headers being out of sync?
[17:51] <popey> pmcgowan: works here
[17:51] <popey> pmcgowan: http://popey.com/~alan/phablet/device-2014-03-26-175131.png
[17:51] <popey> move to Europe. That'll sort it
[17:51] <pmcgowan> hmm
[17:52] <pmcgowan> popey, I get this in the log http://pastebin.ubuntu.com/7158076/
[17:53] <popey> pmcgowan: I'm on osmtouch 0.1.3, you're on 0.1.2
[17:53] <pmcgowan> popey, aha!
[17:53] <pmcgowan> I just installed it yesterday though
[17:54] <popey> latest version in the store is 0.1.2 - ybon you probably want to push 0.1.3 to the store ☻
[17:54]  * popey goes to do fatherly duties, back later
[17:55] <ybon> popey: sure, I was waiting to a confirm that it works for you
[17:55] <ybon> but now I've updated my phone to 5.2 too, so I will be able to test it myself
[18:01] <popey> ybon: works for me.. http://popey.com/~alan/phablet/device-2014-03-26-175131.png
[18:01] <popey> and http://popey.com/~alan/phablet/device-2014-03-26-175235.png
[18:02] <kalikiana> I'm getting "Failed to locate image 262" with "ubuntu-device-flash --revision r262 --wipe" - does anyone spot the problem?
[18:03] <sergiusens> kalikiana, maybe 262 is not on the server anymore
[18:03] <sergiusens> or wrong channel
[18:03] <sergiusens> --channel devel-proposed
[18:03] <sergiusens> or devel
[18:03] <kalikiana> hmm lemme add that
[18:03] <pmcgowan> devel-proposed
[18:03] <ybon> popey: thanks
[18:03] <kalikiana> yay that's it, thanks!
[18:10] <ybon> popey: pushed a click
[18:10]  * ybon afk for diner
[18:11] <jdstrand> rsalveti: hey, you had a question for me regarding powerd?
[18:15] <rsalveti> jdstrand: yeah, solved already, no worries :-)
[18:16] <rsalveti> but thanks for pinging me back
[18:16] <jdstrand> oh, now that is what I like to hear :)
[18:16] <jdstrand> rsalveti: curious what you implemented
[18:20] <rsalveti> jdstrand: just changed the dbus config file for powerd to export just a few methods and properties for the normal user http://paste.ubuntu.com/7154678/
[18:21] <rsalveti> had to add a separated 'allow' for each interface, as we don't want the user to be able to request a suspend blocker
[18:21] <davmor2> popey: I did
[18:21] <davmor2> popey: however it isn't going to be a blocker as the header is going to change soon
[18:21] <jdstrand> rsalveti: cool
[18:22] <jdstrand> rsalveti: there was some talk last week about really tightening it down. I think what is here is reasonable, but if we want to go farther, we can
[18:29] <rsalveti> jdstrand: yeah, we might want to tune it later on indeed
[18:29] <rsalveti> but as we're moving quite a bit of that to unity8 itself (screen on/off, etc), we can revisit this later
[18:29] <rsalveti> unity8/usc
[18:34] <quebre> sergiusens: hi are you still online maybe ?
[18:34] <popey> ybon: thanks, approved
[18:35] <quebre> sergiusens: https://wiki.ubuntu.com/Touch/Building - you said i don't need to have the device in order to build Ubuntu Touch.. but on the site i see the build process is using the device to build..
[18:35] <quebre> it's confusing
[18:37] <quebre> can someone tell me whether it is possible to build the Ubuntu Touch without having the smartphone/tablet whatever the target is ?
[18:37]  * jdstrand nods
[18:39] <mhall119> quebre: yes
[18:40] <mhall119> quebre: specifically are you interested in building the shell (unity8) or a device image?
[18:42] <kenvandine> is anyone else having ofono problems on mako?
[18:42] <kenvandine> http://paste.ubuntu.com/7158338/
[18:43] <kenvandine> i just noticed my phone isn't connecting to cellular... image 262
[18:44] <kenvandine> awe_, ^^
[18:45] <awe_> kenvandine, that's the first report I've seen
[18:45] <awe_> the NM warnings are harmless ( although I'd love to see that code removed from NM )
[18:45] <awe_> however the SIM status too small, doesn't look very good
[18:45] <kenvandine> i tried the sim in my android phone, worked fine
[18:46] <awe_> kenvandine, we haven't landed anything new at the ofono layer that would cause this
[18:46] <awe_> do you see the problem with the last stable image?
[18:46] <cyphermox> awe_: that code won't get removed; the best I am willing to do is drop the severity to debug
[18:46] <kenvandine> i haven't tried flashing to the stable image
[18:47] <awe_> cyphermox, you can't ifdef it???
[18:47] <kenvandine> i'm also not sure when it last worked...
[18:47] <cyphermox> awe_: that code is required for non-ril modems.
[18:47] <kenvandine> i probably haven't made any calls on it in a couple days
[18:47] <awe_> sigh...
[18:47] <Stskeeps> awe_: totally random question, have you guys ever seen a qcom device just shut down or reboot due to bad RIL interaction?
[18:47] <kenvandine> awe_, any chance it could have anything to do with the multi modem code that landed?
[18:48] <awe_> Stskeeps, I haven't although I know some rilds do behave in that manner
[18:48] <awe_> we've seen the Mtk rild drop it's connection when the radio is powered on for instance
[18:48] <awe_> Stskeeps, but I haven't seen that with any of the qcom rilds
[18:48] <Stskeeps> ok
[18:48] <awe_> which is what mako includes
[18:48] <awe_> kenvandine, possibly
[18:49] <Stskeeps> i made a xperia z reboot at least, we're seeing this in production so idly wondering if modem is to blame
[18:49] <kenvandine> list-modems only lists the one modem though
[18:49] <awe_> kenvandine, however AFAIK, we only landed the telepathy-ofono bits
[18:49] <kenvandine> http://paste.ubuntu.com/7158376/
[18:49] <kenvandine> output of list-modems
[18:49] <kenvandine> i assume powered = 1 is powered on?
[18:49] <awe_> kenvandine, the changes made were infrastructure changes in tp-ofono to support multiple accounts ( which each represent a modem )
[18:49] <awe_> kenvandine, yes
[18:50] <awe_> kenvandine, the we essentially auto-power on ( hence the NM messages ), and the radio power is controlled via the Online property
[18:50] <kenvandine> oh... so i ran online-modem and it brought it online
[18:50] <awe_> ah, and you're not Online
[18:50] <awe_> why?
[18:50] <kenvandine> no idea :)
[18:50] <awe_> and it works?
[18:50] <kenvandine> what could put it offline?
[18:50]  * kenvandine tries
[18:51] <awe_> nothing should right now...
[18:51] <ChickenCutlass> kenvandine: awe_ I think there might be a race with the new multiple account code.
[18:51] <ChickenCutlass> kenvandine: awe_ I know bfiller was seeing something
[18:51] <awe_> boiko, you guys didn't land the tp-onfono code with the auto-online code removed did you?
[18:51] <awe_> ChickenCutlass, there's only one modem on a mako!
[18:51] <awe_> ;D
[18:51] <ChickenCutlass> I know
[18:51] <davmor2> kenvandine: you know that power switch on the side if you press and hold that long enough it will be offline
[18:52] <kenvandine> davmor2, oh?
[18:52] <boiko> awe_: nope, but our latest changes uncovered a bug in ofono-qt that salem_ already has a fix for
[18:52] <awe_> ChickenCutlass, so how could there be a race?
[18:52] <kenvandine> that's annoying
[18:52] <ChickenCutlass> awe_: I am just repeating what I was told
[18:52] <awe_> davmor2, what??
[18:52] <davmor2> kenvandine: I'm teasing it'll turn the phone/tablet/etc off
[18:52] <mhall119> davmor2: too subtle
[18:52] <awe_> davmor2, ;D
[18:52] <kenvandine> haha :)
[18:52] <bfiller> awe_, kenvandine: this is a bug in ofono-qt, salem_ has a fix for it: https://bugs.launchpad.net/bugs/1297586
[18:53] <davmor2> awe_: you have to it would power down the modems
[18:53] <Stskeeps> awe_: also, if you guys didn't see yet: https://github.com/nemomobile/mms-engine (i don't recall your mms approach)
[18:53] <kenvandine> and the dialer won't let me place calls...
[18:53] <kenvandine> bfiller, ah
[18:53] <bfiller> kenvandine: same bug
[18:53] <boiko> kenvandine: mc-tool reconnect ofono/ofono/account0 should do the trick
[18:53] <awe_> kenvandine, mystery solved
[18:53] <awe_> Stskeeps, no I hadn't seen that
[18:53] <bfiller> kenvandine: or pkill telepathy-ofono I think works too
[18:53] <awe_> Stskeeps, guess they decided against using mmsd too
[18:54] <mhall119> popey: have we figured out why Terminal won't launch in the latest stable images?
[18:54] <awe_> Stskeeps, we're using a slightly different architecture that includes DownloadManager, and a new component called Nuntium
[18:54] <Stskeeps> awe_: alright
[18:54] <popey> news to me mhall119
[18:54] <kenvandine> ok, working again :)
[18:54] <mhall119> popey: r250, Terminal won't run
[18:58] <popey> mhall119: launches here
[18:58] <mhall119> popey: on r250?
[18:58] <popey> mhall119: oh, on the stable image..
[18:59] <popey> mhall119: i seem to be able to reliably crash unity by search for "ter"
[18:59] <popey> mhall119: terminal loads fine here
[19:00] <mhall119> aa-exec: ERROR: profile 'com.ubuntu.terminal_terminal_0.5.44' does not exist
[19:00] <mhall119> trying to run it manually
[19:00] <popey> why?
[19:00] <popey> oh
[19:00] <popey> to debug?
[19:00] <mhall119> I just wnat my terminal back
[19:00] <popey> http://popey.com/~alan/phablet/device-2014-03-26-190025.png
[19:00] <popey> look at the debug log in /home/phablet/.cache/upstart ?
[19:00] <mhall119> jdstrand: mdeslaur: any idea what might be wrong?
[19:01] <mhall119> popey: which one?
[19:01] <popey> the terminal one
[19:01] <popey> look for the most recent log, usually holds clues
[19:01] <jdstrand> mhall119: the aa-exec command is clear, the question is why
[19:02] <mhall119> popey: no terminal log there
[19:02] <jdstrand> mhall119: what do 'click list | grep term' tell you as the phablet user?
[19:02] <bfiller> popey: are you still seeing https://bugs.launchpad.net/ubuntu/+source/mediaplayer-app/+bug/1297395? testing it with your artic monkeys vid on image 261 and working fine
[19:02] <mhall119> phablet@ubuntu-phablet:~$ click list |grep term
[19:02] <mhall119> com.ubuntu.terminal	0.5.44
[19:02] <jdstrand> mhall119: what does 'sudo aa-status | grep term' give you?
[19:03] <mhall119> phablet@ubuntu-phablet:~$ sudo aa-status |grep term
[19:03] <mhall119> [sudo] password for phablet:  com.ubuntu.terminal_terminal_0.5.41
[19:03] <mhall119> so...wrong version in the apparmor
[19:03] <jdstrand> ok, I think this is the bug cjwatson has been working on
[19:03] <popey> bfiller: lemme see
[19:03] <mhall119> jdstrand: any way for me to correct it manually so I can use the terminal again?
[19:04] <jdstrand> mhall119: see https://launchpad.net/ubuntu/+source/click/0.4.20
[19:04] <jdstrand> mhall119: I suggest installing that package. I haven't seen the issue myself
[19:05] <mhall119> installing click 0.4.20 or installing the terminal package?
[19:05] <jdstrand> mhall119: I bet you could 'click unregister ...' then 'click register ...' to correct it
[19:06] <mhall119> would click unregister remove it completely if only phablet user has it?
[19:07] <popey> bfiller: not seeing the issue on #262
[19:07] <t1mp> plars: I think I'm calling it wrong tim@ideapad:~/dev/ubuntu-test-cases/touch/scripts$ TESTS=all APPS=all ./run-smoke --no-provision
[19:07] <popey> bfiller: updated bug
[19:07] <bfiller> popey: great, thanks
[19:07] <jdstrand> mhall119: not if it is preinstalled
[19:07] <popey> np
[19:08] <jdstrand> mhall119: I was saying install click 0.4.20
[19:08] <quebre> mhall119: device image..
[19:13] <mhall119> jdstrand: installed click 0.4.20, unregistered terminal from phablet user and re-registered with 0.5.44, but aa-status still show 0.5.41
[19:18] <mhall119> jdstrand: is there a way for me to tell apparmor to update itself to use 0.5.44?
[19:19] <jdstrand> it isn't apparmor
[19:19] <jdstrand> click isn't setting up the symlinks
[19:19] <mhall119> which symlinks is it missing?
[19:19] <mhall119> I'll create them manually if it'll fix things
[19:19] <jdstrand> the one in /var/lib/apparmor/clicks is wrong
[19:20] <sergiusens> mhall119, jdstrand for the apparmor links, cjwatson landed a fix yesterday forcing reproccessing of all packages
[19:21] <mhall119> hmmm, I only have 0.5.29 for terminal in /opt/click.ubuntu.com/
[19:21] <jdstrand> I presume that is 0.4.20 that is in the archive?
[19:21] <mhall119> sergiusens: where does the pre-installed terminal get put?
[19:21] <jdstrand> mhall119: /usr/share/click/preinstalled
[19:22] <jdstrand> mhall119: you are going to want to followup with cjwatson
[19:22] <sergiusens> jdstrand, yes
[19:22] <jdstrand> mhall119: the thing is, if you updated to 0.4.20 and it still isn't right, you fixing your terminal will destroy the evidence he probably needs
[19:23] <mhall119> jdstrand: I'm just creating the symlink, I can remove it later to help debug
[19:23] <mhall119> jdstrand: but I'm leaving on a roadtrip tomorrow morning, and would very much like to have a working terminal while I'm gone
[19:23] <jdstrand> once the symlink is updated, run 'sudo aa-clickhook -f'
[19:24] <jdstrand> mhall119: actually, without -f should be enough
[19:25] <mhall119> ERROR: Could not parse click manifest. Skipping 'com.ubuntu.terminal_0.5.44.json'
[19:25] <mhall119> it doesn't like that file...
[19:26] <mhall119> jdstrand: http://paste.ubuntu.com/7158558/ anything look amiss?
[19:26] <jdstrand> mhall119: that fine. the error is about the click manifest, not the security manifest
[19:27] <jdstrand> mhall119: you need to update the symlinks in /opt/click/.click/users/phablet
[19:28] <jdstrand> mhall119: mind you, I am not recommending this :) fair warning
[19:28] <mhall119> jdstrand: what do I need to do with that symlink? it already points to 0.5.44
[19:28] <jdstrand> I have a basic knowledge of the click database; I could easily miss something
[19:29] <quebre> mhall119: i prepared ubuntu VPS just to build it the device image but i don't know what instructions to follow..
[19:29] <quebre> could you give me few hints ..
[19:29] <mhall119> jdstrand: ah, it's working now!
[19:29] <mhall119> aa-status shows both 0.5.41 and 0.5.44 now
[19:34] <quebre> unless it's not doable ...
[19:39] <mhall119> quebre: it should be, didrocks posted something about it on the ubuntu-phone list a while back IIRC
[19:41] <quebre> im scrolling back thru the chat log but cant find it ;f
[19:45] <mhall119> I cna't find it either,sorry
[19:51] <ivivek> What is the right way to mount /system as rw
[19:51] <ivivek> root@ubuntu-phablet:/# mount -o remount,rw /system
[19:51] <ivivek> mount: cannot remount block device /dev/mmcblk0p8 read-write, is write-protected
[19:51] <ivivek> If I try changing /etc/fstab android does not seem to start inside lxc
[19:52] <ivivek> I only see these processes
[19:52] <ivivek>   475 ?        Ss     0:00 lxc-start -n android -- /init
[19:52] <ivivek>   500 ?        S      0:00  \_ /init
[19:52] <ivivek>   514 ?        S      0:00      \_ /sbin/ueventd
[19:52] <ivivek>   520 ?        S      0:00      \_ /sbin/watchdogd 10 20
[19:52] <ivivek>   522 ?        S      0:00      \_ /sbin/upstart-property-watcher
[19:52] <ivivek>   523 ?        S      0:00      \_ /sbin/healthd
[19:52] <ivivek> if i mount /system rw in fstab
[19:55] <ivivek> @ogra_ can you please help
[19:59] <popey> ivivek: phablet-config writable-image
[20:02] <ivivek> @popey where do I have to run this command
[20:02] <popey> on your ubuntu computer
[20:03] <ivivek> I have built my images from code
[20:04] <ivivek> I am not using automatic download and flash tool
[20:06] <popey> not sure that makes a difference
[20:06] <ivivek> ok...let m try
[20:07] <facundobatista> Hi all
[20:08] <facundobatista> question, do you know how to change the virtual screen resolution for the ubuntu-emulator?
[20:08] <popey> hi, rsalveti may
[20:08] <sergiusens> facundobatista, the resolution is a bit more complicated; pixel density is easy
[20:09] <rsalveti> right, you can easily change the size of it, using the scale option
[20:09] <rsalveti> for resolution I guess it depends on the skin
[20:09] <sergiusens> facundobatista, /usr/share/android/emulator/development/tools/emulator/skins/EDGE/layout has the resolution settings
[20:09] <sergiusens> facundobatista, that said, you can change the skin
[20:10] <sergiusens> ust do --skin WQVGA432
[20:10] <sergiusens> *just
[20:10] <facundobatista> sergiusens, which is the best way for the phone to not be taller than my laptop screen? ;)
[20:11] <sergiusens> facundobatista, --scale 0.7 or lower
[20:11] <facundobatista> sergiusens, the --skin is in the create, or in the run?
[20:11] <sergiusens> facundobatista, in the run
[20:11]  * facundobatista tries scale
[20:12] <facundobatista> sergiusens, --scale did the trick, thanks!
[20:12] <ivivek> @popey I get the following error "subprocess.CalledProcessError: Command '"touch /userdata/.writable_image ; echo ADB_RC=\$?"' returned non-zero exit status 1
[20:12] <ivivek> "
[20:12] <sergiusens> facundobatista, np; now wait 30' :-P
[20:13] <ivivek> looks like it tries to create /userdata/.writable_image but there is no /userdata/ on the device
[20:13] <popey> yes, thats all it does
[20:13] <popey> that should exist
[20:13] <ivivek> there is /data
[20:13] <ivivek> no /userdata
[20:13] <popey> for my nexus 4 /userdata is /dev/mmcblk0p23
[20:14] <ivivek> is this same as the userdata partition od andorid ?
[20:14] <ivivek> /dev/mmcblk0p9 on /data type ext4 (rw,noatime,nodiratime,errors=remount-ro)
[20:15] <ivivek> i see this on my nexus10
[20:17] <rickspencer3> jhodapp, o/
[20:18] <rickspencer3> so, I copied a video onto my flo and tried to play it, but it was slightly slow
[20:18] <jhodapp> rickspencer3, care to share the video with me so I can try?
[20:18] <rickspencer3> jhodapp, here's the info from mplayer:
[20:18] <rickspencer3> http://pastebin.ubuntu.com/7158809/
[20:19] <rickspencer3> jhodapp, never mind, it is going slowly on my desktop too, I think
[20:19] <jhodapp> rickspencer3, that seems to be using a software decoder
[20:19] <rickspencer3> either that, or I took too much cough syrup at lunch time
[20:20] <rickspencer3> jhodapp, right, so I infer that it is in a format that lacks hardware decoding support
[20:20] <jhodapp> rickspencer3, yes indeed
[20:20] <rickspencer3> jhodapp, that info was from my desktop, btw
[20:20] <rsalveti> jhattara: remember it shouldn't play if using software decoder
[20:20] <rsalveti> jhattara: sorry
[20:20] <rsalveti> jhodapp: ^
[20:21] <rsalveti> we only support hw decode and rendering
[20:21] <jhodapp> rsalveti, right
[20:21] <jhodapp> rsalveti, got confused by the debugging output
[20:21] <rickspencer3> jhodapp, do you want me to share the file with you, still?
[20:21] <jhodapp> rickspencer3, sure I'll give it a try
[20:22] <rickspencer3> it's only 73 megs, so must be ultra compressed
[20:22] <rickspencer3> jhodapp, have you seen Rick and Morty before?
[20:22] <jhodapp> rickspencer3, I haven't
[20:22] <rickspencer3> then you are in for a treat :)
[20:22] <rickspencer3> this is the pilot episode
[20:24] <jhodapp> excellent :)
[20:24] <rickspencer3> jhodapp, for the record, this particular copy of the video is of ... let's say ... questionable origins
[20:24] <jhodapp> np
[20:26] <rickspencer3> I suspect, now, that Ubuntu was playing the file just fine, but that the file is ropey :)
[20:30] <pmcgowan> popey, davmor2 I updated several apps via update manager and none would run until after a reboot
[20:31] <rickspencer3> pmcgowan, I got the same effect today, I assumed the applications scope needs to be tweaked
[20:32] <davmor2> pmcgowan: on what image?
[20:37] <barry> sergiusens: any chance we can get this mp into a silo and landed?  it's blocking all other py3 autopilot port branches https://code.launchpad.net/~xnox/phablet-tools/py2-3/+merge/205608
[20:37] <popey> pmcgowan: sounds like the two bugs davmor2 and I filed today
[20:38] <davmor2> I just updated OSMTouch with no issues
[20:38] <sergiusens> barry, welcome to the future; that landed into the archives an hour ago :-)
[20:39] <davmor2> so I wonder if it is related to the installed click having a different name to the Available click package and that is the cause of the problem
[20:39] <sergiusens> barry, https://launchpad.net/ubuntu/+source/phablet-tools
[20:39] <davmor2> pmcgowan: one of the apps that you updated can you see if it is listed in both Available and installed please
[20:40] <barry> sergiusens: no way!  i guess it just takes some time for the mp to get marked, etc.
[20:40] <barry> sergiusens: that's awesome
[20:40] <sergiusens> barry, oh, ther merge-and commit thing may not have been run :-P
[20:42] <barry> sergiusens: my gallery-app and address-book-app mp's are currently failing because of py2/py3, but maybe they just need to be retried?  e.g. https://code.launchpad.net/~barry/gallery-app/py3autopilot/+merge/208055/comments/503378
[20:44] <sergiusens> barry, looks strange... could not import package gallery_app: No module named gallery_app
[20:45] <barry> sergiusens: /var/local/autopilot/setup.log: Python choice: python2
[20:45] <barry>  
[20:45] <barry> that's weird
[20:46] <sergiusens> barry, might want to ping fginther on the setup; they test through the debs on ci
[20:46] <pmcgowan> davmor2, 262, I updated OSMtouch, gallery, and a couple others, neither gallery or osmtouch would start until I rebooted
[20:47] <barry> sergiusens: k, thx
[20:47] <pmcgowan> davmor2, they are only in one category now, but again I rebooted
[20:47] <barry> fginther: can you take a look at https://jenkins.qa.ubuntu.com/job/autopilot-testrunner-otto-trusty/3707/console
[20:47] <barry> fginther: any thoughts on why it's still picking py2 instead of py3?
[20:47] <fginther> barry, looking
[20:48] <barry> fginther: thx.  interestingly, it doesn't look like phablet-tools is getting installed.  if that's the case, then xnox's phablet-test-run support isn't either and i guess at that point it wouldn't auto-select autopilot-py3
[20:49] <fginther> barry, the ci test you pointed to is the desktop test, it is specifically looking for a dependency on python3-autopilot to trigger use of py3
[20:51] <barry> fginther: ah, got it.  i'll add that dep and re-push.  thankx
[20:51] <barry> *thanks
[20:52] <sergiusens> barry, fginther the mako test does fail, and for that you would need the latest test; is this box raring?
[20:52] <fginther> barry, I believe you're still going to run into a failure on the touch device testing
[20:52] <sergiusens> fginther, the latest phablet-tools landed into trusty
[20:52] <fginther> sergiusens, yes it's still raring, the upgrade was wrecked due to usb hub issues
[20:53] <fginther> *sigh*
[20:53] <sergiusens> fginther, you can just download the deb manually from trusty and install into raring I guess
[20:53] <barry> wow, raring still
[20:55] <fginther> sergiusens, hmmm
[20:57] <barry> sergiusens, fginther yeah. the address-book-app branch already dep'd on python3-autopilot and it's touch tests failed too (but just generic-mediumtests-runner-mako and generic-mediumtests-trusty-touch): https://code.launchpad.net/~barry/address-book-app/py3autopilot/+merge/210724/comments/503417
[20:58] <barry> i guess ultimately they're the same tests?
[20:58] <barry> could not import package address_book_app: No module named address_book_app
[20:58] <barry>  (which would make sense if ap py2 was trying to run the tests)
[20:58] <quebre> i try to build ubuntu-touch, i did: phablet-dev-bootstrap ubu-touch
[20:58] <quebre> 4gb of files downloaded
[20:58] <quebre> but what now ?
[20:59] <quebre> i want it for samsung galaxy s4
[21:00] <fginther> barry, I'm working on a solution, hang on
[21:07] <davmor2> pmcgowan: hmm osmtouch works fine here after the update only think I had to do was look it up via search to open it after update
[21:07] <pmcgowan> davmor2, I did not search
[21:07] <pmcgowan> that bug was solved with old scopes, so seems its back
[21:09] <davmor2> pmcgowan: if you search does it open then?
[21:09] <pmcgowan> davmor2, well, they all open now that I restarted
[21:09] <davmor2> ah yeah same result I guess
[21:10] <davmor2> hmmm still can't add an image to a contact :(
[21:10] <fginther> barry, I'm going try an upgrade later tonight (say 4 hours from now). I'll send you an update on how it goes
[21:11] <barry> fginther: sounds great, thanks.
[21:11] <pmcgowan> davmor2, before new scopes landed, the old one was changed to invalidate the entire results, which showed the new apps in the right place, but created a poor experience repainting the entire list
[21:18] <davmor2> pmcgowan: indeed
[23:54] <josharenson> Hi, I just flashed Ubuntu for the first on a Nexus 7 and wi-fi doesn't seem to work. Is there anything I need to do to enable it?
[23:56] <nhaines> josharenson: No, it should just work.
[23:56] <josharenson> ... Disregard, 2 reboots seems to have resolved
[23:56] <josharenson> weird
[23:56] <nhaines> \o/
[23:56] <nhaines> 'sudo phablet-network' on your computer with the tablet attached should push your wi-fi settings over.
[23:57] <josharenson> nhaines: cool, thanks
[23:57] <nhaines> josharenson: just a little timesaving tip. :)