=== juicyjones|away is now known as juicyjones [00:21] rsalveti: sergiusens: https://plus.google.com/u/0/111980561516715514914/posts/gRhx9VNzipu [00:50] is it true that it will be a release candidate by the end of the month? [00:59] andril: no [00:59] andril: the goal is to have something usable enough that those developing and testing it can use it as their daily device OS [00:59] which is quite different from a release candidate [01:00] mhall119: looks interesting [01:00] mhall119: that's what i expected - sounds good to me :) [01:02] i added the touch core apps PPA to my nexus 7 ubuntu touch and installed the coreapps but they don't seem to do anything but bring up a white screen [01:03] how do I go about running these once installed on my nexus 7 ? [01:12] mhall119: side question, can we get icons in standard locations for the icons of the community core apps? [01:17] sergiusens: we can put them anywhere you want [01:18] bcurtiswx: what image version are you running? [01:19] i just did a phablet-flash today [01:19] mhall119, ^^ [01:19] bcurtiswx: hmmm, I had a similar problem a while back, but it was fixed in an update [01:20] is it only the coreapps doing this, or all apps? [01:20] all apps now [01:20] have you tried rebooting? [01:20] i've tried reboot in the shell, it rebooted, no change [01:20] how about apt-get upgrading? [01:21] yeah i did that [01:21] IIRC, it was a HUD API change that needed package updates [01:21] when I had this issue [01:23] mhall119, are you supposed to run them from command line still, or should it work fine using the display ? [01:25] mhall119, http://paste.ubuntu.com/5688936/ [01:35] bcurtiswx: they will run from the Dash (though you may have to search for them) [01:35] I do it all the time on my Nexus 7 [01:35] mhall119, yeah this is weird why they don't run right [01:35] bcurtiswx: try running one from the command line, it might give an informative error message [01:36] mhall119, http://paste.ubuntu.com/5688967/ [01:37] hmm, nothing looks wrong... [02:21] What is the best cell phone to use for Ubuntu Touch? [03:57] hi all.. [03:58] can i ask something bout ubuntu touch for phone? [04:00] mhall119: yes [04:00] mhall119: for saucy Qt 5.0.2 is available in qt5-proper PPA currently, archive uploads hopefully this week still [04:01] Mirv: jono was having some dependency version problems earlier [04:02] mhall119: (ZDmitry was asking) regarding raring, yes SDK PPA also has the packages since our gomobile instructions used to specify only SDK PPA for raring users so it was thought there might be many people who have only that one PPA enabled [04:05] jono: if your problem was on saucy, apt-add-repository ppa:canonical-qt5-edgers/qt5-proper [04:05] Mirv, arn't we getting normal archive uploads this week though? [04:06] jono: yes, that's the plan, I'm still waiting for Saviq (and/or some others) to also 'ack' that it's fine, but I have everything ready for uploads [04:06] Mirv, cool, I will just wait until then, thanks :-) [04:06] using saucy on the device dist-upgrade seems to go fine and everything works with those PPA packages, and all syncs have been done ith Debian [04:09] the dependency problems come from the complex PPA dependencies we have.. images now only use daily-build-next, not qt5-proper PPA. and d-b-n only uses archives and itself. but users, phablet PPA and core-apps PPA use the qt5-proper as build dependencies, so some packages get newer dependencies earlier than others [04:10] but that should be all gone with saucy anyhow soon enough [04:12] Mirv: for reference, Jono was experiencing this installing on his desktop [04:12] not on a device [04:13] mhall119: yeah, on the desktop users are instructed to add the PPA:s, even though on saucy they won't be used probably before October once the automatic landing starts to work [06:25] hi all [06:25] any url on ubuntu touch security? [06:25] i found this one: https://wiki.ubuntu.com/Security/Features [06:25] but not sure if it holds ubuntu touch same as desktop? [06:27] good morning [08:04] Hello [08:04] I'm reading about ubuntu-touch and I wonder if I can install this on my Samsung Galaxy S3? Is this the same device as the Galaxy Nexus? [08:07] !devices [08:07] You can find the full list of devices, official images, community images, and works in progress at https://wiki.ubuntu.com/Touch/Devices [08:07] BezNalogov, ^ [08:09] Thanks [08:52] didrocks: ping [08:53] oSoMoN: pong [08:53] didrocks: I’m working on internationalizing the remaining bits of the webbrowser-app (desktop file, automatic pot generation at build time), and I’ve got a MR that I’d appreciate if someone from the distro team could have a look at [08:54] oSoMoN: oh sure, please send the link, I'll have a look today :) [08:54] didrocks: awesome! here it is: https://code.launchpad.net/~osomon/webbrowser-app/i18n-pot-target/+merge/164937 [08:55] oSoMoN: will probably have a look within the day, trying to get dailies working back first (jenkins issue) [08:55] didrocks: sure [08:56] didrocks: note that it’s not using the standard mechanism because at present intltool doesn’t support custom keywords for pot generation, unfortunately, so I need your opinion on my custom solution [08:56] oSoMoN: ok, I'll tell you :) [08:56] thanks! === Soulflare3_zzz is now known as Soulflare3 [09:08] tmoenicke, ping [09:08] ZDmitry: pong [09:09] tmoenicke, does VKB support additional layouts? [09:09] ZDmitry: yes [09:10] tmoenicke, and what we need to create layout? I mean, which format it has? [09:11] ZDmitry: http://bazaar.launchpad.net/~phablet-team/phablet-extras/maliit-plugins/files/head:/maliit-keyboard/data/languages/ [09:11] there is what we have. they are xml files [09:11] tmoenicke, thanks [09:11] yw [09:11] So I have a non-mainstream Android tablet. Is it still possible for me to use Ubuntu Touch? [09:13] tmoenicke, next question. I just noticed that VKB supports orientation changing. But suddenly, height of keyboard rectangle not changed. Is this mean that this fetaure [09:13] "in progress"? [09:17] tmoenicke, so do I need use width of VKB instead of height in landscape mode for my app? === vrruiz_ is now known as rvr [09:23] ZDmitry: no that is a bug and been fixed, should land soon [09:24] tmoenicke, ok === ckpringle_ is now known as ckpringle [09:33] hello ... can you tell me something about ubuntu touch & ZTE GRAND X IN aka Orange Santa Barbara ??? [09:34] el_silver, probably the devices wikipage can ... [09:34] !devices | el_silver [09:34] el_silver: You can find the full list of devices, official images, community images, and works in progress at https://wiki.ubuntu.com/Touch/Devices [09:35] tmoenicke, and the last one question about extra keys: as I understood from VirtualKeyboardLayout.dtd, currently, VKB supports only modifiers (alt|shift|altshift) and not supports extra keys (such as F1 - F12 keys). Correct? [09:35] hey i wanna join developer group for ubuntu -phone can someone guide me [09:37] thx ... but Grand X IN not listed ... phone have Intel Atom procesor and I would be happy if they started to work on it .... you know tell me where to send the proposal ??? [09:46] hey i wanna join developer group for ubuntu -phone can someone guide me??? [09:48] mayank, https://wiki.ubuntu.com/Touch/CoreApps/DevelopmentGuide [09:49] thanks ZDmitry iwill check it now === dandrader is now known as dandrader|afk [09:54] who do I ask about an error adding an upstream qt bug to a launchpad issue? [09:54] dpm or mhall119 any suggestions? [09:56] kalikiana, you can ask in #launchpad or in #ubuntu-desktop, but basically, you use the "Also affects project" link in the bug, which will then allow you to enter the URL of the upstream bug [10:00] dpm, kalikiana: the Qt bugtracker is not supported by launchpad, see https://bugs.launchpad.net/launchpad/+bug/157488 [10:00] Launchpad bug 157488 in Launchpad itself "Add bugwatch support for the JIRA bugtracker" [High,Triaged] [10:00] thanks seb128, good to know. kalikiana, so I guess it will be just a matter of mentioning the bug in a comment or on the bug description [10:06] dpm, seb128 alrighty, thanks === dandrader|afk is now known as dandrader [10:08] tmoenicke, sorry for annoying. Will VKB support CTRL modifier and FN (F1-F12) keys? [10:25] didrocks: information on how to demangle C++ symbols is added to both debian wiki & daily release (see https://wiki.ubuntu.com/DailyRelease/FAQ#I.27m_exposing_a_new_C.2B-.2B-_symbols_in_my_library.2C_it_seems_that_some_packaging_changes_are_needed.2BICY- ) [10:25] please merge my symbols branches =) [10:26] xnox: I'll have another review later, but not today! :-) Thanks! [10:30] sil2100: Mirv: we got the thing workarounded [10:30] sil2100: Mirv: I'm restarting, without building, all the stacks, little by little [10:30] (as the stuff is already in the ppa) [10:31] didrocks: regarding unity, could you rebuild everything? Or maybe wait for https://code.launchpad.net/~fginther/unity/autopilot_hud_button_label_fixes/+merge/164999 and re-run with rebuilding, since those 2 merges didn't land yesterday [10:31] And without them, the test results will be sucky anyway [10:31] Same for HUD [10:31] sil2100: everything or just unity? [10:32] sil2100: and rebuild HUD? [10:32] sil2100: or rerun HUD with unity results? [10:33] didrocks: well, we would need the latest unity in the PPA so that unity and HUD tests would be fixed [10:33] sil2100: ok, so rebuilding Unity [10:33] and rerunning the HUD tests after Unity [10:33] making sense? [10:33] sil2100: HUD FTBFS on some arch in the ppa [10:33] sil2100: same for some scopes in unity [10:34] sil2100: if it's an arch mismatch, do you mind kicking that in manually in the ppa? (the rebuild) [10:34] sil2100: otherwise the build monitoring will fail [10:34] didrocks: ok, will do that [10:35] sil2100: keep me posted once this is fixed and your unity branch is merged [10:35] sil2100: I'll kick the rebuild [10:35] doing the touch stuff meanwhile [10:48] didrocks: ok, let's hope for the best [10:48] Mirv: I'm crossinger fingers :) [10:48] prepare+build fine [10:49] waiting for powerpc [10:49] then onto autopilots [10:51] Having so many packages can be a bother sometimes ;p [10:52] ooh, we seem to have automatic screen turning offness \o/ === SkavenXXI-[OFF] is now known as SkavenXXI [10:57] sil2100: you think that is a problem you should try the migration of 700 commercial apps from one distro series to another it takes 45minutes to do an apt-get update after :D [11:00] ok, I've "greenified" jenkins [11:00] didrocks: I checked the scopes and hud, rebuilded those, they're building now [11:00] didrocks: unity also failed for powerpc, but I'm not rebuilding that one, since unity will be rebuilt anyway, right? [11:00] sil2100: great! tell me once you have your branch merged and I'll rebuild Unity [11:00] sil2100: exactly :) [11:00] is* [11:01] Mirv: sil2100: so, everything is reran now, but the unity (and the HUD as we want for unity first) stacks [11:02] Still waiting for that one merge [11:03] I'm waiting for sdk build phase to complete [11:03] ok, taking a break, will be back later, the time that the current tests are running… :) === pete-woods is now known as pete-woods-lunch === MacSlow is now known as MacSlow|lunch [11:04] Mirv: hum, it will wait forever, isn't it? [11:04] 2013-05-22 11:02:47,217 INFO current_package: ubuntu-ui-toolkit 0.1.46daily13.05.22ubuntu.unity.next-0ubuntu1 [11:04] 2013-05-22 11:03:05,483 INFO arch: powerpc, status: building [11:04] didrocks: possibly. armhf/i386/amd64 published, powerpc building [11:05] that [11:05] Mirv: well, it can't build on powerpc, can it? [11:05] Mirv: as v8 is not available on it [11:06] which packgage from qt5-edgers contains shaders (libqmlshadersplugin)? [11:06] Mirv: Missing build dependencies: qtdeclarative5-window-plugin [11:06] didrocks: yes, no it can't [11:06] Mirv: can you list all the archs for now in debian/control? [11:06] Mirv: that's linked to a discussion we had yesterday on ubuntu-devel [11:06] didrocks: I can, yes [11:06] Mirv: thanks, meanwhile, I'm using cu2d-skip to tell "ignore powerpc for this run" [11:07] ok [11:08] ZDmitry: in Qt 5 it should be part of the core Qt Quick support.. ie. just import QtQuick 2.0 [11:08] from qtdeclarative5-qtquick2-plugin [11:10] sil2100: QA greened! :) [11:10] sil2100: 3 failures per config, but below the threshold at 3 :) [11:10] Mirv, strange but shaders works fine on desktop and wants work on device. [11:11] \o/ [11:11] FINALLY [11:11] HOLY SHIT [11:11] :D === dholbach_ is now known as dholbach [11:13] sil2100: well, still failures [11:13] sil2100: but we ignored them, will be good to get the QA team fixing them (and reproducing them first :p) [11:15] Mirv, fix: shaders don't wants work on device [11:16] sil2100: did you look at the issues before rebuilding? [11:16] Mirv, is there some difference for qml shaders on device? [11:16] sil2100: seems libunity7 is really failing (due to a flacky tests) [11:16] stgraber, no go for me with your tarball on maguro :/ [11:16] sil2100: you should maybe bring pawel into that one :) [11:17] didrocks: yes, I saw, it's a known issue with libunity on armhf [11:17] didrocks: we were trying to fix that last week even [11:18] stgraber, and lxc-console doesnt seem to work [11:18] didrocks: panda boards are really slow, so sometimes the timeout (even though we increased it) is still not enough ;/ [11:18] so i cant really enter it [11:18] sil2100: ok, what's the deal then on that one? :) [11:22] ZDmitry: hmm, there shouldn't be, but I'm not really an expert. it's of course EGL/GLES, but that should be all transparent. [11:22] loicm: do you know if there's anything specific preventing use of shaders in apps currently? [11:23] didrocks: I'll poke Paweł about that again ;) Maybe he and Michal might find a better way of fixing it [11:23] sil2100: ok, so even with rebuilding Unity, the stack will stack red :) [11:24] didrocks: but it's not happening always ;) [11:24] didrocks: it's failing only from time to time, we just need to watch and rebuild ;p [11:24] Mirv: no, it should just work [11:25] sil2100: ok, please rebuild then :) [11:25] Stupid pandas ;p [11:26] Rebuilding [11:26] loicm: ok, thanks [11:26] btw. my merge is still building [11:27] Mirv, loicm: thanks. Seems problem in something other than plugin. === chriadam is now known as chriadam|away [11:29] ZDmitry: yeah, I just tested out of interest that http://qt-project.org/doc/qt-5.0/qtquick/qml-qtquick2-shadereffect.html example works on my device [11:33] And what about Circle Menu in the terminal app on device? In this video shaders works (on desktop), but on mine Galaxy Nexus is not works. [11:34] Mirv, forgot link https://www.youtube.com/watch?feature=player_embedded&v=QVn0af2_ACQ [11:35] Mirv, so I did something wrong? http://bazaar.launchpad.net/~ubuntu-terminal-dev/ubuntu-terminal-app/trunk/view/head:/extraPanel/CircleMenu.qml === gusch is now known as gusch|away [11:49] ZDmitry: I'm not familiar with that one. mhall119 might know about whether the circle menu should be working on device [11:49] hi [11:49] Mirv, thanks. [11:49] Please help to deal with porting Ubuntu Touch on Samsung Infuse! === dandrader is now known as dandrader|lunch [11:58] Please help to deal with porting Ubuntu Touch on Samsung Infuse! === greyback is now known as greyback|lunch === MacSlow|lunch is now known as MacSlow [12:13] rsalveti: do you know if we have x86 images of utouch? (thinking maybe people already ran something like that in say VirtualBox) [12:15] Kaleo, we dont [12:15] would need an android x86 port [12:16] ogra_: it exists right? [12:16] not as ubuntu touch port, not for CM 10.1 [12:16] ogra_: ok [12:16] but yes, theoretically it does === pete-woods-lunch is now known as pete-woods [12:20] rsalveti, http://paste.ubuntu.com/5690128/ ... thats what i get trying stgraber 's lxc on maguro ... sf dies [12:20] i sadly seem to have no way to even enter the container to strace or anything :( === _salem is now known as salem_ [12:30] ah === dandrader|lunch is now known as dandrader === greyback|lunch is now known as greyback === dpm_ is now known as dpm-uow === dpm is now known as dpm-laptop === dpm-uow is now known as dpm [12:51] Mirv: UTAH failed for sdk, I'm relaunching it FYI [12:52] Mirv: have you merge the arch fix? what should I rebuild? [12:52] kenvandine: I'm forcing the publication of the media stack [12:52] (all tests passed \o/) [12:52] blocked because of the sdk stack === gusch|away is now known as gusc [12:55] didrocks, cool, thanks [12:55] * ogra_ sighs [12:55] kenvandine: can you take care of the webapps one? I think you saw it's on manual publishing for packaging changes : [12:55] :) [12:55] kenvandine: we had a jenkins issue this morning, that's why I rebuilt everything [12:55] i haven't looked yet, but i will [12:55] thx! [12:55] yesterday prepare was breaking for everything === juicyjones|away is now known as juicyjones [12:56] kenvandine: yeah, that my "this morning" [12:56] trying to file a file named .xml [12:56] :-D [12:56] cool [12:56] i was waiting to ask you about it :) [12:56] kenvandine: we played a fun game with jibel, ask him :) [12:56] glad it's moving along [12:56] kenvandine: right now, didn't find the root cause, we deployed a workaround [12:56] ok [12:56] (basically an environment variable is set at jenkins startup) [12:56] * kenvandine goes to shower first... bbiab [12:56] kenvandine: ttyl :) [12:57] didrocks: the merge is still pending, did the proposal. and it was because of a new binary package added while the rest already had armhf i386 amd64 listed [12:57] Mirv: pending for review or for merging? [12:57] I'll ping someone to merge it [12:57] Mirv: I can approve it if needed, as it's a pure and trivial packaging change [12:57] didrocks: https://code.launchpad.net/~timo-jyrinki/ubuntu-ui-toolkit/qmlrunner_archs_amd64i386armhf/+merge/165082 [12:58] Mirv: approved [12:58] Mirv: I'll relaunch the stack as soon as it's merged [12:58] didrocks: thanks [12:58] yw === hikiko is now known as hikiko_lunch [13:13] Kaleo: hey, do you know of an easy way to access the i18n object from javascript files? [13:18] sergiusens, http://paste.ubuntu.com/5690128/ [13:19] ogra_: dumb question, but do you have the egl drivers in /system/lib/(?egl?) ? [13:20] i shouldm didnt change them [13:20] * ogra_ checks [13:20] oot@android:/ # ls /system/lib/egl/ [13:20] egl.cfg libGLES_android.so [13:20] hmm [13:20] ah, the rest is in /vendor [13:21] root@android:/ # cat /system/lib/egl/egl.cfg [13:21] 0 0 POWERVR_SGX540_120 [13:21] looks fine too [13:21] what about gralloc? E/SurfaceFlinger( 579): hwcomposer module not found [13:21] where would that live ? [13:22] the system partition is originally from our image without any modificatio [13:22] n [13:22] boiko: hmmm [13:22] same for vendor [13:22] boiko: if you js file is not a stateless library [13:22] boiko: you should have access to it I think [13:23] Kaleo: it is a stateless library [13:24] ogra_: I'm around now [13:24] ogra_: /system/lib/hw/gralloc.default.so but it's not specific to hw iirc [13:24] yep, its there [13:24] stgraber, any idea how i can get a console inside the container ? [13:25] lxc-console stays quiet [13:25] ogra_: I don't see this in your log: D/libEGL ( 127): loaded /vendor/lib/egl/libEGL_POWERVR_SGX540_120.so [13:25] * ogra_ ponders to reflash /system from scratch [13:26] sergiusens, yeah, weird, isnt it [13:26] ogra_: I got that way back when I forgot to add the binary drivers [13:27] well i didnt touch /system at all [13:27] zsombi: any idea? 15:13 < boiko> Kaleo: hey, do you know of an easy way to access the i18n object from javascript files? [13:27] only untarred stgraber's lxc tarball [13:27] which only contains /data/ubuntu with modifications [13:27] Hi all, I was wondering if anyone had any ideas how to shut off MTP after flashing to ubuntu touch? I am trying to issue my device commands but it keeps trying/failing an mtp connection in ubuntu 13.04... [13:28] nethfel: if you have the latest bits flashed you shouldn't be seeing those messages [13:28] ogra_: Android appears to scrap the /dev/ttyX devices that LXC creates and doesn't actually start getty against those anyway so no console for us sadly [13:28] Kaleo: the only solution I could come up with was to pass the i18n object as the argument of the functions I'm using [13:28] stgraber, hmm thats bad for debugging [13:28] ogra_: so how far did you get, do you have the LXC container starting and then a bunch of processes showing up in there at least? [13:29] yeah, all runs fine [13:29] except surfaceflinger [13:29] which restarts in a loop [13:29] boiko: there is a way [13:30] let me flash a fresh /system [13:30] not that i belive that changes anything though [13:32] Sergiusens: I had initially setup the tablet following the instructions on the wiki back on around the 6th of May. When I went back to attempt to activate SSH, I connected the tablet to my laptop and 13.04 kept having a hissy fit about unable to access MTP device and it would seem to reset the connection to the device whenever 13.04 complained. [13:32] i wonder what happens if we re-enable adbd in the container and drop it from ubuntu [13:33] (I only referenced the date of install incase there have been some updates since then that I might not have yet) [13:35] nethfel: you may want to remove the persistent usb settings which may be set to [adb,mtp] to only adb ... It would be better if you flash the latest image though with the latest tools [13:35] nethfel: yeah, the mtp removal and adb only thing was from 2 weeks ago [13:36] ogra_: well, I'd expect we'd get adb access to the android container. I actually meant to try that here as I've now got ssh access to the Ubuntu side so don't need adb anymore [13:36] yeah [13:36] * ogra_ dds a new /system now [13:38] "My cat told me that he's working on a new OS too. But it won't be compatible with touchscreen devices because his OS is going to require the presence of a mouse" [13:39] Serguisens : I'll definitely re-flash and try again (that first week I got the tablet I kinda went back and forth between android and ubuntu a few times in those first couple days) - now for a stupid question - where might I adjust the persistent USB settings? [13:39] uh, oh [13:39] nethfel: if you mess up, you loose your adb connection [13:39] sergiusens, i cant just dd the img file ? [13:39] seems i lost my filesystem on /system now [13:40] sergiusens: is it a setting on the tablet itself? [13:40] nethfel: android property... do adb shell getprop|grep persist [13:40] ogra_: how did that happen? === hikiko_lunch is now known as hikiko [13:41] sergiusens, i dd'ed the img file to the partition [13:41] ogra_: ah, innovator :-P [13:41] now it tells me it cant find a filesystem [13:41] sergiusens: hmm, is there a way to do it temporarily so if I do screw it up I can get it back? [13:42] * ogra_ flashes via fastboot then [13:42] stgraber@castiana:~$ adb shell [13:42] shell@android:/ $ [13:42] ogra_: ^ so yeah, we can run adbd in the Android container [13:42] nethfel: yeah, change it in the non persist option [13:43] ogra_: (make sure the adbd service is in replace/init.rc and comment the rm line in pre-mount.sh, disable the Ubuntu adbd upstart job and reboot) [13:43] yeah [13:43] for now i cant get my phone to mount /system automatically anymore [13:44] weird [13:44] sergiusens: ok, now you mention this is an android property, but I am able to set it after installing touch? [13:47] root@android:/ # lxc-start -n android -d [13:47] lxc-start: no configuration file for '/sbin/init' (may crash the host) [13:47] hmpf [13:48] err [13:48] root@android:/ # ls /var/lib/lxc/ [13:48] root@android:/ # [13:48] sigh [13:50] so i can start over completely ... fun [13:55] rsalveti, ping [14:02] boiko: so now that all the tp stuff is in... are you going to use it with the phone-app? [14:03] oha ! [14:03] ogra_: working any better? [14:04] stgraber, heh, nope, but i think i found the issue [14:04] the initrd ships a /vendor [14:04] while the init.rc wants to create a szmlink called /vendor [14:04] *sym [14:06] ogra_: ah, are you using the init.rc I put in the tarball instead of a patched copy of yours? [14:07] nope [14:07] mkdir -p $LXC_ROOTFS_PATH/data $LXC_ROOTFS_PATH/system $LXC_ROOTFS_PATH/vendor [14:07] thats my issue i think [14:07] you create the dir before init.rc can add the symlink [14:07] in the pre-mount.sh [14:07] ogra_: oops ;) [14:08] removed it ... lets see [14:08] ogra_: ah yeah, I actually fixed that here (needed it to make wlan working) [14:08] hmm no sf [14:10] http://paste.ubuntu.com/5690429/ [14:11] sigh [14:11] 347 - 368 is the interesting part [14:11] the bad address doesn't tell us a whole lot though... [14:11] sergiusens: actually it should just work, not sure if the build is picking telepathy-ofono2 or telepathy-ofono (as they both provide telepathy-ofono which is what phone-app requires) [14:12] boiko: hmmm... ok... let [14:12] 's find out [14:12] boiko: the new build would've picked them up, going to check the manifest [14:13] ogra_: anything in dmesg by any chance? [14:13] boiko: it's picking up telepathy-ofono [14:14] stgraber, lost of pvr errors [14:14] sergiusens: so, telepathy-ofono2 has a Replaces and a Provides: telepathy-ofono, maybe the version needs some tweaking? [14:14] salem_: ^ [14:15] [ 8.470062] PVR_K:(Error): BridgedDispatchKM: Driver initialisation not completed yet. [4807, /home/ubuntu/jenkins/workspace/ubuntu-touch-image/kernel/samsung/tuna/drivers/gpu/pvr/bridged_pvr_bridge.c] [14:16] boiko: I don't see the dep for telepathy-ofono2 in debian/control for the phone-app === juicyjones is now known as juicyjones|away [14:16] ogra_: hmm... and when you were playing with just a chroot, did you manage to get SF to run? (wondering whether we're missing some kind of init bits for your hardware) [14:16] no [14:17] sf never ran with the flipped container [14:17] boiko, sergiusens I thought it should pick-up telepathy-ofono2 as we are replacing telepathy-ofono. [14:17] ogra_: you may want to check: ls /proc/$(lxc-info -n android -p | awk '{print $2}')/root [14:17] ogra_: that should show you the root of the container as it sees it from inside, that way you can check that everything is mounted as expected [14:18] ogra_: though if everything else starts, it should... might be worth triple-checking vendor and firmware though [14:18] yeas, i used it to chroot before [14:19] its all there [14:19] salem_: so telepathy-ofono2 Provides: telepathy-ofono ? [14:19] sergiusens, yes [14:19] (well, vendor, system and data are) [14:20] dev looks fine too [14:20] as does /proc [14:21] ogra_: btw, your problem looks like http://forum.xda-developers.com/showthread.php?t=1403601 haven't found anything relevant in there yet though [14:21] hmmmm qmlplugindump segfaults in u1db arm builds according to https://launchpadlibrarian.net/139782886/buildlog_ubuntu-raring-armhf.u1db-qt_0.1.5bzr90raring0_FAILEDTOBUILD.txt.gz I wonder how to investigate that [14:21] ogra_: apparently that guy was missing some blobs (https://developers.google.com/android/nexus/drivers#maguro) [14:22] well, if i flip the container back it works fine [14:22] and the kernel is identical right? [14:22] its no like my /system is modified in any way [14:22] kernel yes, initrd indeed not [14:30] rsalveti, any idea ? [14:30] rsalveti, http://paste.ubuntu.com/5690429/ ... [14:31] i dont really get why sf tries to start so early ... it didnt do that ever before === ckpringle_ is now known as ckpringle === dandrader is now known as dandrader|afk [14:38] pmcgowan: do we have a roadmap for making the Launcher customizable? === francisco is now known as Guest25788 [14:40] mhall119, in what sense? [14:41] being able to add/remove/reorder the launcher icons [14:41] I expect once unity 8 hits the build [14:42] mhall119, Saviq would know for sure [14:42] ah, and when will that be? [14:42] any minute ;) [14:42] so will the daily device images get daily builds of Unity 8? [14:43] right [14:44] aha ! [14:44] so somehow init.tuna.rc isnt properlz executed on boot [14:45] i have qml-phone-shell up [14:45] finallu [14:45] *finally [14:46] stgraber, does getprop work for you inside the container ? [14:49] ogra_: getprop returns a whole bunch of thing, yes [14:49]