=== xiambax_ is now known as xiambax === fmasi is now known as Guest93311 === yofel_ is now known as yofel === andrew__ is now known as ajbrandt1 [02:10] good evening [02:32] Anyone have info on music playing in background? [03:20] popey: fwiw, the QT_QPA_PLATFORM setting traces back to /etc/profile.d/qpa_plugin.sh, which sets either QT_QPA_PLATFORM=ubuntumirclient or QT_QPA_PLATFORM=ubuntu, depending on whether MIR_SOCKET is set in the environment... which it obviously won't be when connecting over adb. So that seems to be a regression in ubuntu-touch-session. [03:22] ogra_: ^^ ubuntu-touch-session 0.88 breaks at least some autopilot use cases over adb; how was this tested before upload? [03:22] ogra_: i.e., nothing sets $MIR_SOCKET, so the shell environment gets set up wrong over adb [05:07] http://www.omgubuntu.co.uk/2014/01/several-ubuntu-phones-release-2014 [05:07] lets hope they come fast [06:12] so, nexus 7 (2012), i installed touch on it using the manual instructions on https://wiki.ubuntu.com/Touch/Install and it boots past google logo but sits on a black screen [06:12] how far back should i go to find one that works [06:12] ? === karni is now known as Guest86298 === dk_ is now known as dk === Zic is now known as Guest56028 [09:12] hi folks [09:12] i try to get the source on my box [09:12] for dev a rom [09:12] i am having prob with the repo sync [09:12] when i run [09:12] phablet-dev-bootstrap code/ [09:13] it stopp [09:13] i gonna dig [09:20] solved [09:20] just been stupid [09:39] slangasek, yes, on all devices with SF and Mir i wonder why they worked then (the landing took 8 weeks for this, but i dont think that specific part of autopilot tests changes within) ... thanks for the upload [09:40] *changed [10:36] hi folks [10:36] i try to compile a rom for i9300 [10:36] galaxy s3 [10:36] any idea why this is not working? [10:36] nocomp@pirebox:~/ubuntutouch$ breakfast i9300 [10:36] Couldn't locate the top of the tree. Try setting TOP. [10:36] bash: build/tools/roomservice.py: No such file or directory [10:36] ** Don't have a product spec for: 'cm_i9300' [10:36] ** Do you have the right repo manifest? [10:36] nocomp@pirebox:~/ubuntutouch$ [10:38] http://www.omgubuntu.co.uk/2014/01/how-to-dual-boot-android-ubuntu-touch-on-nexus [10:39] i tired to install ubuntu dual boot on my nexus 4 using the above tut === jgdxx is now known as jgdx [10:39] but call and wifi functionality are not working [10:40] srujan: did it have android 4.4 on it? [10:40] yes [10:41] i believe that may be why [10:41] https://wiki.ubuntu.com/Touch/DualBootInstallation#Getting_phone_calls_to_work_in_Ubuntu_and_Android_4.4 [10:43] Thanks popey [10:51] srujan: np === token_ is now known as Guest66912 [12:07] hi guys. How is the status about 4.4 rebase? [12:08] Is it possible to see the status somewhere? [12:15] FuLgOrE: i believe it's due to land at the end of the month === token_ is now known as Guest90411 === _salem is now known as salem_ === salem_ is now known as _salem === token_bucket_ is now known as token_bucket1980 [12:58] popey: thank you [12:59] popey: Is it possible to monitor the status somewhere? I don't want to bother you with my questions [13:06] all, I'm having issues upgrading click 0.4.12 from the ubuntu-sdk-team ppa. Could anyone help me? http://paste.ubuntu.com/6779871/ [13:31] vthompson: lemme see if i can reproduce that here [13:31] FuLgOrE: i dont know. but the target is end of month, keep an eye on the ubuntu-phone list as we're sending out weekly status updates for various things there [13:33] vthompson: oddly I already had that version of click from somewhere [13:33] http://paste.ubuntu.com/6779992/ [13:36] is there a release for nexus 5? [13:37] joeashin: not yet [13:37] thx. [13:43] ... [13:51] I resolved my issue by adding a new user "phablet" on my desktop. [13:53] oof [13:53] thats a bug imo [13:55] I'll go and file one. I only recently added the ubuntu-sdk-team ppa to my system === Guest56028 is now known as Zic [14:04] popey, https://code.launchpad.net/~sergiusens/reminders-app/cmake_common/+merge/202215 [14:04] popey, I see you are around ;-) [14:05] I was aiming on directly creating a fat package, but it seems to be missing some pieces still === nik90__ is now known as nik90_ [14:42] sergiusens: thanks [14:45] sergiusens: do i click-buddy it directly on the device or will it work on laptop? [14:51] popey, will work on laptop, but will build x86 [14:51] popey, still need to integrate it with click chroot [14:51] popey, although, if you have a working click chroot; doing click chroot click-buddy ... should work ;-) [14:54] so probably easier to build on device right? [14:54] (I don't have a chroot, and want to test on arm, not x86) [14:54] yup [14:55] ta [14:55] will do a bit later [15:26] I've been really good at breaking things today. I upgraded my phone to r136 and now it won't boot up with a welcome screen, but I can still "adb shell" to the device. Anyone having similar issues? [15:35] vthompson: mine is on #134, will update now and see what happens [15:36] popey, god speed [15:36] hah [15:36] * popey voluntarily breaks his phone... for the greater good === jono is now known as Guest43734 [15:40] vthompson: mine boots to desktop okay [15:40] popey, hm, maybe I'll reflash [15:52] popey, reflash worked. I must have been low on battery while upgrading... or some other hiccup === edude03_ is now known as edude03 === Ursinha-afk is now known as Ursinha === vying is now known as Guest88093 === A is now known as Guest67729 [18:37] Getting on first install on Nexus4: "ERROR:phablet-flash:Installation is taking too long or an error occured along the way" (command was "phablet-flash ubuntu-system --channel devel --no-backup") Should I just try again? Thanks :) [18:39] Ah, maybe with --pending [18:40] ah, no [18:41] "phablet-flash: error: unrecognized arguments: --pending" seems this option doesn't exist anymore [18:44] ybon, hm, try with -b instead of --no-backup [18:45] cwayne_: thanks :) [18:46] cwayne_: I've clicked on "get back" on the device [18:46] which has now rebooted [18:46] ybon, np! hope it helps :) [18:46] and it seems on Ubuntu \o/ [18:50] woo! [18:51] Trying to connect on the cellular network now :) [19:01] Humm, no cellular connection (even after unlocking the SIM card) and no wifi connection, should I try installing "stable" instead of "devel"? === VargaD_ is now known as VargaD [19:12] plars, huh, any idea whats going on? there were a bunch of builds and they're all failing pretty hard [19:12] thomi, ping [19:13] cwayne_: hey [19:14] thomi, hey, im getting a lot of failures, seems to be something with autopilot introspecting failing to load platform plugin 'ubuntu' [19:14] hmm, got a link? [19:15] http://ci.ubuntu.com/smokeng/trusty/touch_custom/mako/134:20140118:20140115.1/6136/ubuntu-ui-toolkit-autopilot/680527/ [19:15] * thomi reads [19:16] cwayne_: autopilot hasn't changed in a while now. This looks to me like the process we try and launch exits with -6 [19:16] probably due to the missing 'ubuntu' platform [19:16] I imagine that platform is provided by the qtubuntu package? [19:16] but I'm just guessing there [19:16] looks like there's a lot of issues with the regular touch test cases too [19:16] like 0 passes on mako [19:16] something is incredibly broken [19:17] ? where do you see that? [19:17] I see 90% pass rate for mako... [19:18] except for this: http://ci.ubuntu.com/smokeng/trusty/touch/mako/20140119%20%3F/6152/ where nothing ran [19:18] so... nothing failed either :) [19:18] well, that's still incredibly broken :) [19:19] http://ci.ubuntu.com/smokeng/trusty/touch/ [19:19] agreed, but there's nothing there for me to look at :) [19:20] fair enough :) [19:20] on this run, for example: http://ci.ubuntu.com/smokeng/trusty/touch/mako/20140119%20%3F/6152/ all the console logs are totally empty [19:50] hey guys, I cannot sync contacts between syncevolution and google contacts, external transport failure (local, status 20043) is what I get [19:50] any ideas? [20:20] hi all, I'm trying to install Ubuntu os on my nexus 4. but i don't know which mako files to download. and can i use cwm to install? [20:52] Any word yet on when a build of Ubuntu Touch will be available for the Nexus 7 (2013)? [20:55] cwayne: you are talking about the latest mako failure on image 136 I guess? [20:56] cwayne: looks like we had a device fall over - I'll swap it out in the configs, and rfowler will need to take a look when he's back in the office again [20:57] cwayne: or are you talking about the custom builds? the latest seems a lot beter on those, but the two previous images were pretty bad it seems - nothing changed on the ci side with those [20:58] balloons, or anyone following the Terminal app's Backspace/Enter bug. I entered a comment with some steps I was able to do to get the app to recognize the keys. The bug is probably an OSK issue and the Konsole plugin author can probably stand down on investigating. [21:13] Any word yet on when a build of Ubuntu Touch will be available for the Nexus 7 (2013, called razor I believe)? [21:15] popey, yay :-) [21:16] sergiusens: thank you [21:16] vthompson: thank you [21:16] ulkesh: end of the month, hopefully [21:16] popey: awesome, thanks a bunch! [21:17] popey, we don't really have the infra to build on jenkins yet; but I can build local and upload and discuss the rest with fginther tomorrow [21:18] eom -/+ 1 week [21:20] great, thanks [21:23] popey, if you have the cycles, care to take a stance onto that click-buddy mr? :-) [21:26] sergiusens: done, for what my comment is worth ☻ [21:57] Ah, seems that my Android version was too recent (4.4.2_r1), do I need to restore Android, then downgrade, or is there a way to downgrade from desktop command line even when Ubuntu Touch is already installed? [22:05] ah, maybe https://wiki.ubuntu.com/Touch/DualBootInstallation#Android4.4Radio === kflx-mako is now known as Rob- === Rob- is now known as Robsome [23:48] hello