[01:28] <Guest60692> Hi, I am stuck at installing ubuntu phone on my galaxy nexus
[01:28] <Guest60692> I am running $ ubuntu-device-flash --channel=trusty --device=maguro --device-tarball=Downloads/takju-imm76i-factory-e8c33767.tgz
[01:28] <Guest60692> dies with 2014/08/25 03:27:51 Cannot cleanup /cache/recovery/ to ensure clean deploymentexit status 255
[01:29] <Guest60692> i cleaned up the /cache directory and that didn't work
[02:11] <nondem> So, I got Touch installed ok...booted up and put in my 4 digit pass...it goes gray like it is logging me in...sits there about 10 minutes so far.
[02:27] <nondem> 20 minutes now :) This is on a Nexus 10(manta)
[02:34] <Beldar> nondem, I would try a reinstall things happen.
[02:38] <Guest84587> when running ubuntu-device-flash, what does it mean "Recovery image not found, cannot continue with bootstrap"?
[03:23] <Guest84587> i have succeeded installing ubuntu
[03:24] <Guest84587> all it needed is to reset android and rerun ubuntu-device-flash --channel=trusty --device=maguro  --bootstrap
[03:25] <Guest84587> however ubuntu didn't start. i can open its bootloader, but no idea where to go from there.
[03:26] <Guest84587> the options are "reboot system now", "install zip from sdcard/sideload", wipe data...
[03:26] <Guest84587> how can i proceed from this state?
[03:29] <Guest84587> a few reboots actually made it work! :) superb!
[05:08] <pitti> Wellark: ack silo12> err, where do I need to do that?
[05:31] <Mirv> pitti: thanks, that's enough :)
[05:32] <pitti> Mirv: what is enough, asking the question where to ack it? :-)
[05:32] <Mirv> pitti: like, on IRC
[05:32] <pitti> Mirv: I don't know what to ack yet
[05:32] <Mirv> pitti: oh, sorry, I thought it was "ack 12". the debian/rules part of https://ci-train.ubuntu.com/job/ubuntu-landing-012-2-publish/lastSuccessfulBuild/artifact/packaging_changes_indicator-network_0.5.1+14.10.20140824-0ubuntu1.diff
[05:33] <pitti> Mirv: ah, thanks; ack!
[05:33] <Mirv> thanks! :)
[05:33] <pitti> Mirv: aah, now I know where to see the changes
[05:33] <pitti> I missed the artifact on https://ci-train.ubuntu.com/job/ubuntu-landing-012-2-publish/8/
[05:33] <pitti> Mirv: btw, llvm got reverted, so my silo 7 built now; I'll test it now
[05:34] <pitti> Mirv: I'm not sure why it still says "ready to build packages" while everything got built, but *shrug*
[05:35] <Mirv> pitti: not sure, possibly it got reconfigured after the build or something like that. if you want to keep the current packages, it's useful to now run build with 'watch only' checked.
[05:36] <pitti> oooh! thanks to whoever finally added asking for the SIM  pin right at startup
[05:36] <pitti> this was a major pain
[05:36] <pitti> Mirv: ah yes, that was the case (one MP was moved to another silo)
[05:36] <pitti> Mirv: ack, will do that
[05:41] <pitti> urgh, ./phablet-config writable-image reboots
[05:41]  * pitti adds TODO item to fix that
[05:42] <pitti> ah well, can't call mount -o remount once we switch to user adb
[05:47] <pitti> Mirv: while I'm at it, core-dev ack for silo 5
[05:48] <Mirv> pitti: thanks for that, too, veebers will be happy.
[05:49] <pitti> Mirv: where do you set that status? in the spreadsheet?
[05:51] <Mirv> pitti: core-dev ack? sadly the only papertrail on that is IRC logs :( to be fixed by CI Airlines...
[05:51] <pitti> Mirv: ah, so you just click "publish"
[05:51] <Mirv> pitti: I only click "publish" with "ack_packaging"
[06:28] <pitti> Mirv: ppa 7 is no good any more, telephony-service is broken (another big change landed in trunk which isn't yet in my branch/PPA)
[06:28] <pitti> Mirv: I locally merged trunk now; can I push that to the same MP, and request a rebuild?
[06:37]  * pitti does
[06:37] <Mirv> pitti: yes
[06:38] <pitti> hm, I figure I need to again do the same dance for rtm now
[07:03] <dholbach> good morning
[07:22] <pitti> Mirv: PPA 7 is good  to go now; want me to publish, or shouldn't I (and only sil2100/robru/you do that)?
[07:22] <Guest23501> Hi all! I have a quick question. How hard to porting Ubuntu Touch to an other device, like Sony Xperia Z, L or SP?
[07:27] <Mirv> pitti: in normal landings mode, there's no reason why a core-dev wouldn't publish himself :) so, feel free.
[07:29] <pitti> ack
[07:35] <pitti> Mirv: hm, the publish job succeeded, but nothing on https://launchpad.net/ubuntu/+source/messaging-app (and the dashboard rightfully complains about it); is that normal?
[07:38] <sil2100> pitti: launchpad just didn't catch the package in -proposed yet (most probably)
[07:40] <pitti> sil2100: hmm, copies betwenn archives are pretty much instantaneous
[07:40] <pitti> ah, it's there now
[07:42] <sil2100> pitti: CI Train takes the info about where the package is from LP itself, so if something would be broken it would mention that the package is 'in no known space' for a longer time :)
[07:43] <sil2100> If it said it's in -proposed, then this was the info it got from LP API calls
[07:44] <sil2100> It's usually accurate, although sometimes hasty
[07:50] <Mirv> pitti: "pretty much" instantaneous :)
[07:50] <pitti> Mirv: with sync-package it's literally < 5 seconds (i. e. smaller than the time to load the +source web page)
[07:51] <Mirv> oh, ok, that's fast then
[07:51] <pitti> I had thought it was the same for train copies
[07:51] <pitti> but anyway, nevermind
[08:29] <tsdgeos> can someone top approve https://code.launchpad.net/~aacid/messaging-app/update_pot/+merge/231534 ?
[08:29] <pitti> looking
[08:29] <pitti> +msgid " "
[08:30] <pitti> 19+msgstr ""
[08:30] <pitti> err?
[08:31] <pitti> tsdgeos: reviewed
[08:31] <pitti> tsdgeos: would be nice if you could fix that space along with the new string, while fixing i18n issues
[08:32] <tsdgeos> pitti: yeah, not going to do that
[08:32] <pitti> tsdgeos: oh, why not? it doesn't make sense to have a single space marked as translatable, it's only going to cause trouble
[08:32] <tsdgeos> pitti: because people complain you change their code
[08:33]  * pitti looks at the code
[08:33] <pitti>     title: selectionMode ? i18n.tr(" ") : i18n.tr("Chats")
[08:33] <pitti>     title: selectionMode ? i18n.tr(" ") : i18n.tr("Chats")
[08:33] <tsdgeos> yes it's wrong
[08:33] <tsdgeos> i know
[08:34] <tsdgeos> it's not like i care if that's wrong
[08:34] <pitti> similar in Messages.qml -- the i18n.tr() should just be dropped
[08:34] <tsdgeos> what i care is that we have an untranslatble phone
[08:35] <tsdgeos> which is not even my job so i shouldn't be caring for it
[08:35] <pitti> I know this wasn't your fault, but slipping this into this MP will take an extra 10 s
[08:36] <pitti> making an entirely new MP and landing that will take three magnitudes more than that, with our current process (which absolutely doesn't work for small fixes..)
[08:36] <tsdgeos> fix the process then :)
[08:36] <pitti> three magnitudes isn't even enough
[08:36] <tsdgeos> i mean you may as well complain there's a missing ; in some line and that should also be fixed
[08:37] <pitti> well, it's that MP which introduces that space into the .pot
[08:37] <pitti> which is going to cause headaches to translators
[08:58] <pitti> ogra_: do you happen to have an i386 deb for the non-root adbd (for the emulator)?
[08:59] <ogra_> pitti, hmm, no ... i'll try to build one during the day (i dont even have the source on an x86 machine ... dead architecture ... :) )
[08:59] <pitti> ogra_: I'm happy to build it myself, if you have a pointer to the source/MP/branch
[09:00] <ogra_> i can push the source package somewhere ...
[09:00]  * pitti pats his utopic-i386 schroot
[09:02] <pitti> ogra_: so with my phablet-network branch things mostly work, except for having to enter the PIN manually (same what plars was pointing out)
[09:03] <pitti> that'd be an unity8 bug, I think -- we need a D-BUS CLI to unlock the screen
[09:03] <ogra_> pitti, right, the --password option to ubuntu-device-flash will handle that
[09:03] <pitti> we didn't yet need it without a pin, starting an app when the screen was locked unlocked it
[09:03] <ogra_> oh, the autopilot issue with unlocking you mean
[09:03] <pitti> ogra_: right
[09:04] <pitti> ogra_: everything else works fine now (I made enough adjustments to the adb setup script) \o/
[09:04] <ogra_> yay
[09:05] <pitti> ogra_: it now tries "phablet" and "0000" as sudo passwords, and also has a --password option; and most tests shouldn't need root (e. g. calculator tests run fine without sudo, too)
[09:05] <ogra_> yeah
[09:05] <pitti> but all tests fail while the lock screen is still running (i. e. waiting for pin)
[09:05] <ogra_> the plan was that in future releases the image doesnt need to be writable and the pahblet user can do all tests
[09:05] <pitti> it seems with a pin a starting app doesn't just get rid of the lock screen
[09:06] <pitti> ogra_: yes, that has worked for some time already (with autopkgtest, not with phablet-test-run)
[09:06] <ogra_> right mterry should be able to help you
[09:08] <pitti> ogra_: yeah, I'll file a bug against unity8; I already asked for this a month ago, but it wasn't necessary yet then
[09:08] <ogra_> janimo`, hmm you didnt add udev rules for the new arch when you added the device id to adb, did you  ?
[09:09]  * ogra_ upgraded his desktop to trusty on the weekend and cant connect anymore with "no permissions"
[09:09] <tsdgeos> pitti: i've removed those i18n.tr(" ")
[09:09] <pitti> tsdgeos: cheers
[09:10] <ogra_> should we not use that in general ?
[09:10] <ogra_> (i know the app-dev documentation talks about it everywhere)
[09:10] <pitti> tsdgeos: top-approved now
[09:10] <tsdgeos> now someone just needs to land it
[09:11] <tsdgeos> who said the process was not agile? :D
[09:11] <pitti> *smirk*
[09:11] <pitti> that's the kind of change one would usually directly commit to trunk and just let it flow in with the next update
[09:12] <pitti> same like simple mass-packaging changes or fixing typos, etc.
[09:12] <ogra_> tsdgeos, it will get better...
[09:12] <pitti> i. e. ci-quick-walk-to-the-bakery, not everything needs the overhead of an airline :)
[09:12] <ogra_> pitti, thats the prob, with the current model (which i heard asac asekd for now) you have to have two branches for *every* project
[09:12] <pitti> but that had been discussed in the airline designs, I think
[09:13] <ogra_> which kind of contradicts the initial idea of "handle it like SRUs" we had
[09:13] <pitti> ogra_: yeah, with rtm it's harder (I also need to land 7 more MPs now for an utterly trivial change)
[09:13] <ogra_> pitti, we are trying to get a model in place where you can automatically PPA copy the source package into an rtm silo when you land in utopic
[09:14] <pitti> hmm, it seems with every other install the nice numeric keypad "enter your pin" gets replaced with a "Hello" input line and I have to use a letter keyboard for PIN entry
[09:14] <ogra_> so that the distro handling happens on a package level and doesnt force you to try to keep two constantly diverged branches in sync
[09:14] <ogra_> pitti, i think that happens onyl if your pw is non numeric and 4digits long
[09:14] <pitti> ogra_: that would only work as long as rtm still ships the trunk branch, though?
[09:15] <ogra_> pitti, right, with is 80% of our landings
[09:15] <pitti> ogra_: no, I always use "0000"
[09:15] <ogra_> there are a few projects that will target rtm directly
[09:15] <ogra_> pitti, weird ... there is another dbus settings for the account stuff
[09:16] <ogra_> swipe/passcode/passphrase ... i have to look up how exactly it is called
[09:16] <pitti> ah indeed, system settings says password, not pin
[09:16] <ogra_> right you can set that via dbus
[09:17] <pitti> so it seems sometimes it mis-sets the pin as password; I'll try to reproduce that
[09:18] <pitti> ogra_: what I was actually doing was a fresh reinstall to confirm that we now have an r/w image by default; that's not intended, is it?
[09:18] <pitti> /dev/loop0 on / type ext2 (rw,relatime,errors=continue)
[09:18] <pitti> which component would that be for filing a bug?
[09:18] <ogra_> oh no, definitely not !!!
[09:18] <ogra_> pitti, initramfs-tools-ubuntu-touch
[09:18] <pitti> yeah, I was wondering why my test run instaslled all the autopilot bits with dpkg
[09:18] <pitti> ogra_: cheers, filing bug
[09:19] <ogra_> that seems to be the partitioning changes causing it
[09:21] <pitti> bug 1361124
[09:22] <ogra_> janimo`, ^^^^
[09:25] <pitti> janimo`: ah, would you be the appropriate assignee for that?
[09:27] <pitti> ogra_: sorry for keeping bothering you -- who should I ask for reviewing the phablet-tools MP?
[09:28] <ogra_> pitti, i can approve it ... just busy with getting the packaging support into phablet-config too ... i'll make sure your change goes in with the same landing
[09:28] <pitti> ogra_: ah, ok; danke!
[09:35] <Saviq> jibel, trying to reproduce the lock-up you're getting here, obviously can't... but anyway, does it play with both speakers for you? at least the case suggests there's two speakers at the bottom, but I'm only getting sound through the right one (can cover it and it goes almost completely quiet)
[09:37] <jibel> Saviq, it plays only from the right one.
[09:37] <Saviq> jibel, right, wonder if that's expected...
[09:39] <Saviq> jibel, but yeah, no lockup here ;|
[09:40] <jibel> Saviq, yeah, it's really difficult to reproduce. I had it twice yesterday but nothing today. asac and victorp also had it several times a day last week.
[09:40] <Saviq> jibel, and it's not bug #1295623 for sure?
[09:41] <jibel> Saviq, yes I'm sure. it's really frozen. For example, in one of the case the greeter stopped in the middle of the screen. In the other case the dash was displayed and I couldn't reveal the launcher or indicators
[09:42] <Saviq> jibel, right
[09:42] <jibel> Saviq, it's really like when unity8 is crashing, excepted that it is not crashing
[09:43] <Saviq> jibel, yeah, sounds like a deadlock somewhere
[09:43] <Saviq> jibel, the gdb trace will help a lot next time you see it
[09:46] <jibel> Saviq, sure, I'll add this information next time it happens. Thanks for looking.
[09:49] <pitti> ogra_: I did an initial review of your phablet-config branch; I debug this further why it doesn't work yet
[10:06] <ogra_> pitti, hmm, your bug above ... (writable root) is that on a device or emulator ?
[10:06] <ogra_> could be that the emulator still mounts it rw
[10:06] <pitti> ogra_: on mako; it has always been writable on the emulator (which is another bug)
[10:07] <pitti> ogra_: bug description updated to clarify
[10:07] <ogra_> thanks
[10:18] <pitti> ogra_: do you have a branch to make system-image-cli -i work as user?
[10:19] <pitti> (PermissionError: [Errno 13] Permission denied: '/root/.cache/system-image')
[10:19] <pitti> or does that get wrapped by phablet-config somehow?
[10:19] <pitti> ah, it apparently tries /var/log/system-image/client.log first, then falls back to the above, but both are root-only
[10:24] <ogra_> pitti, http://people.canonical.com/~ogra/ubuntu-touch/adbd-no-root.patch for your x86 build ...
[10:24] <pitti> ogra_: cheers!
[10:24] <ogra_> pitti, system-image-cli can not work as user
[10:24] <ogra_> barry would kill me if i changed that
[10:24] <pitti> ogra_: ok, I'll adjust the test for "is that an ubuntu phone"; thanks
[10:25] <ogra_> there is some way around the log issue that the autopilot test for system-settings uses i think
[10:25] <pitti> ogra_: don't worry, I replaced it with "type unity8"
[10:26] <pitti> adt-run can't determine/log the image version then, but *shrug*
[10:27] <ogra_> you could just grep it from /etc/system-image/channel.ini
[10:42] <vitimiti> nik90, could you find anything about my problem? I couldn't fix it yet
[10:43] <nik90> vitimiti: no I couldn't. The XmlListModel seems to be defined correctly
[10:43] <nik90> so I cant think why it doesnt unless I dive deeper
[10:43] <nik90> I am a bit busy atm to do that
[10:43] <vitimiti> I see, thanks for trying, anyway
[10:44] <vitimiti> I split the pages to make it more readable, though
[10:45] <t1mp> are there known issues in image #207 (on mako) that the screen doesn't turn on?
[10:45] <t1mp> the device appears to boot (I can connect to it with adb), but the screen stays black
[10:46] <ogra_> the tests in the lab ran fine ... so the devices there must work
[10:47] <ogra_> http://ci.ubuntu.com/smokeng/utopic/touch/mako/207:20140825:20140811.1/9930/
[10:48] <ogra_> t1mp, do you see the google logo or actually a black screen
[10:49] <t1mp> ogra_: hold on, I am re-flashing the device. I'll tell you in a few minutes
[10:49] <nik90> vitimiti: yup I noticed that
[10:50] <nik90> vitimiti: so is the xml listmodel data displayed correctly in HospitalPage0.qml but not the rest?
[10:51] <vitimiti> nik90, exactly, the name appears no matter how much I change it, but the news, staff and so only appear on the console.log test I put there
[10:52] <nik90> vitimiti: may be then the XML ListModel is faulty
[10:52] <ogra_> pitti, answered your MP commants for phablet-config ...
[10:53] <nik90> vitimiti: how about you create a single page when you show the hospitalName, hospitalNews and see if they are displayed correctly?
[10:53] <nik90> s/when/where
[10:53] <pitti> ogra_: ah, I'm just testing a fix for the sync issue, I'll post it there once confirmed to work
[10:53] <vitimiti> nik90, I will try to put all of them where the name is and not display the other pages
[10:53] <ogra_> pitti, heh, i meant your comments on my MP :)
[10:53] <pitti> ogra_: yes, so do I :)
[10:54] <ogra_> ah
[10:54] <nik90> vitimiti: yeah just see if the xml model even returns the hospitalNews variable
[10:55] <vitimiti> nik90, yeah, still a blank label
[10:56] <nik90> vitimiti: why do you have @ infront of the queries?
[10:57] <vitimiti> Because it's <tag name="stuff" /> instead of <tag>stuff</tag>
[10:57] <vitimiti> Just like in the developer's page tutorial
[10:58] <vitimiti> The console.log() does I funny thing I just saw, it adds a lot of empty lines that shouldn't be there
[10:58] <nik90> ah yes
[10:58] <nik90> why do you define the xml file like it is?
[10:58] <nik90> cant you change to <tag>stuff</tag> ?
[10:58] <vitimiti> I found it easier to understand for me, but it does the same with <tag>stuff</tag>, I tried it too
[10:59] <vitimiti> I will try with all in one page, though
[11:01] <pitti> ogra_: why do we need the non-dbus call code paths?
[11:02] <pitti> ogra_: (there's no followup comment from you except the new commit -- was that eaten by LP from some email reply?)
[11:02] <ogra_> pitti, yes, until the stable channel is gone/updated
[11:02] <t1mp> ogra_: after re-flashing the device works again. I'll try to figure out if I broke it or if there is a bug that I can reproduce
[11:02] <pitti> ogra_: ah, of course; I see
[11:03] <vitimiti> nik90, now there's something new, apart from being now "undefined" instead of blank, this error appears: Error XPTY0004 in file:///usr/lib/x86_64-linux-gnu/qt5/bin/qmlscene, at line 2, column 54: Required cardinality is zero or one("?"); got cardinality one or more("+"). (three times)
[11:03] <ogra_> t1mp, did you have any click packages installed (beyond the preinstalled ones) ?
[11:04] <ogra_> t1mp, that can cause a lot of apparmor stuff on boot and might keep you on the google logo for minutes
[11:06] <vitimiti> nik90, but if I reduce it to just one new, service and staff, it works. Now I have to find a way to make it read several of them
[11:08] <pitti> ogra_: followup sent; you may vomit now, but at least it works :/
[11:09] <pitti> ogra_: oh, and yay for LP killing initial space in my patch :)
[11:11] <pitti> ogra_: I haven't tested the writable part; does calling the SetProperty() thing actually do the remount? (hopefully without reboot)? or does that need a manual reboot afterwards
[11:11] <ogra_> pitti, the dbus service just touches /userdata/.writable_image and triggers a reboot ...
[11:12] <pitti> ogra_: ah; what's the source project for that? I'd like to eliminate the reboot
[11:12] <ogra_> pitti, i missed re-adding the adb.wait_for_device() and wait_for_network() bits ... i'll add that now
[11:12] <pitti> "mount -o remount,rw /" is quite enough
[11:12] <ogra_> no
[11:12] <pitti> ogra_: ah, thanks
[11:12] <ogra_> thats not the allowed/preferred way for devs
[11:13] <pitti> why not? it's the same result without having to wait for a full boot again
[11:13] <ogra_> (i prefer it too btw ... but the file is the "right way" )
[11:13] <pitti> ogra_: yes, sure -- touch the file, remount rw
[11:13] <pitti> ogra_: so that on next boot it'll stay r/w
[11:13] <ogra_> no. it will handle the writable bits mounting differently iirrc
[11:13] <pitti> hm, we've use the remount,rw for a fair while (and ignored phablet-config as it's too slow)
[11:13] <ogra_> (i would have to check the initrd scripts, but there is a differentce ... also some tools check for that file)
[11:14] <pitti> ogra_: well, of course it should continue to touch that file
[11:14] <ogra_> i dont want to change functionality anyway
[11:14] <ogra_> phablet-config writable-image has always needed the reboot ... if you want to remount, fell free :)
[11:14] <pitti> ogra_: yes, not in that MP 9just something for later)
[11:15] <pitti> ogra_: well, s/needed/done/
[11:15] <ogra_> yeah, we can discuss that
[11:15] <pitti> I was just asking which project provides PropertyService
[11:15] <ogra_> oh, the dbus part is an ugly shellscript in dbus-property-service
[11:15] <pitti> ah, https://code.launchpad.net/~phablet-team/dbus-property-service/trunk
[11:16] <pitti> thanks
[11:16] <ogra_> (that initially only *did* set properties ... i need to find a new name at some point)
[11:16] <pitti> device-munging-service :)
[11:16] <ogra_> haha
[11:16] <ogra_> well, i might also split it after rtm
[11:17] <pitti> yeah, not critical, it just occurred to me
[11:17] <vitimiti> I lagged too much
[11:17] <ogra_> to keep a clean "peroperty-service" backend for android properties
[11:17] <ogra_> (which was the initial idea behind that service)
[11:23] <vitimiti> Sorry about that
[11:37] <nik90> vitimiti: np. I will try to use your xmllistmodel to create an app to display the data in a page. But no promises :)
[11:40] <vitimiti> nik90, ok, thanks again.
[11:41] <t1mp> zsombi: if you have a pitch-black screen, but you can connect with adb, then you have the same problem that I just had
[11:41] <janimo`> pitti, I'll look at that, since indeed it may be due to recent changes I had been involved with
[11:41] <t1mp> zsombi: did you see the google  logo when booting?
[11:42] <t1mp> ogra_: ^ it seems someone reproduced my issue
[11:42] <zsombi> t1mp: yes, I did
[11:42] <zsombi> t1mp: but now the screen is on...
[11:43] <t1mp> ok, I had to reflash for that
[11:43] <ogra_> so it just took long ?
[11:43] <ogra_> yeah, thats aa-clickhook running when it finds non default click packages  installed ... can take up to 5min
[11:46] <vitimiti> nik90, I found a way around: if I want more data, instead of using <news>stuff</news>, I should use <news><news>stuff</news><news>stuff</news>...</news>
[11:46] <vitimiti> nik90, that using a listmodel and a function y the xmllistmodel to append every new data it finds
[11:46] <vitimiti> y=and*
[11:47] <nik90> cool
[11:47] <nik90> vitimiti: I would go different naming
[11:47] <nik90> vitimiti: like the container which holds all the news children could be called <NewsCollection>
[11:48] <nik90> so something similar
[11:48] <vitimiti> I'll try
[11:48] <nik90> otherwise it is a bit confusing imo
[11:48]  * ogra_ curses pep8 ... 
[11:50] <vitimiti> nik90, yeah, that works too and looks better, perfect
[11:51] <vitimiti> nik90, I the listmodel isn't even needed, changing from name="" to <name></name> was definitely the solution
[11:52] <nik90> vitimiti: atm too many changes that I cannot imagine the code without seeing it :D. But if it works great
[11:56] <ogra_> pitti, did you ddo a fresh flash when you saw the image being writable ?
[11:56] <ogra_> or was that an OTA upgrade ...
[11:56] <janimo`> pitti, I'll try to reproduce this, for now I dont' see why the initrd change itself would make that writable though. hmm
[11:56] <ogra_> also did you use --wipe or --bootstrap
[11:57] <ogra_> right, i was just talking with janimo` in the other channel
[11:57] <vitimiti> I just pushed it, if you want to see, nik90
[11:57] <ogra_> i think if you made the image writable only --wipe or --bootstrap will make it non-writable again (i.e. remove the file)
[11:58] <janimo`> ogra_, he says there's no Note that there is no /userdata/.writable_image stamp at all
[12:00] <nik90> vitimiti: so much better. nice work
[12:00] <vitimiti> Yeah, that feels good, after 4 days
[12:00] <vitimiti> heh
[12:01] <nik90> :D
[12:08] <ogra_> GRRR
[12:08] <ogra_> why does the jenkins bot not like me today :(
[12:14] <ogra_> sigh, i dont get that, the indendation is correct ... yet the bot moans
[12:16] <rickspencer3> hi all, I would like to file a bug for mtp not quite working. do I log it here? https://bugs.launchpad.net/ubuntu/+source/gvfs/
[12:16] <ogra_> rickspencer3, no, against the mtp package
[12:17] <rickspencer3> ok
[12:19] <ogra_> lol
[12:20] <ogra_> so adding a blank line makes the bot not moan anymore ... how silly ... (since i didnt change any indendation for the indendation complains)
[12:20]  * ogra_ wonders why he always runs into the false positives 
[12:20] <rickspencer3> sil2100, I was told that you might want to track this bug wrt new (and awesome) stuff in mtp:
[12:20] <rickspencer3> https://bugs.launchpad.net/ubuntu/+source/mtp/+bug/1361181
[12:20] <ogra_> rickspencer3, assign to cyphermox
[12:21] <rickspencer3> ogra_, cyphermox if you guys would like me to do anything to help get some info off the phone, just let me know
[12:21] <ogra_> sil2100, ^^ ... seems realted to the mtp-server crashers we see on tests
[12:22] <rickspencer3> ogra_, oh, I see, I have _usr_bin_mtp-server.32011.crash
[12:22] <rickspencer3> should I have ubuntu-bugged that?
[12:23] <ogra_> well, i guess we already have a few of these on errors.u.c
[12:24]  * rickspencer3 nods
[12:25] <jibel> rickspencer3, it's likely bug 1360569
[12:25] <jibel> it's one of the winner on errors.u.c
[12:25] <rickspencer3> nice
[12:26] <rickspencer3> :(
[12:26] <rickspencer3> when I rebooted the phone, my sd card didn't show up
[12:26]  * rickspencer3 tries again
[12:34] <pitti> ogra_: no, fresh install (I think I wrote that in the bug)
[12:34] <ogra_> yeah, saw that
[12:34] <ogra_> sorry
[12:34] <pitti> ogra_, janimo`: I used the dual-boot installer under android
[12:34] <ogra_> oh
[12:35] <pitti> but that was r/o before
[12:35] <ogra_> you should have written that you use an unsupported method :P
[12:35] <janimo`> pitti, hmm maybe ondra knows something about that
[12:36] <pitti> ogra_: oh, is that unsupported? sorry
[12:36] <ogra_> :)
[12:36] <ogra_> we never supprted dual booting officially
[12:36] <pitti> but it was r/o before
[12:36] <ogra_> right
[12:36] <ogra_> but it might be the dual-boot bit thats broken here
[12:36] <janimo`> pitti, I asked ondra, let's see if he's around
[12:36] <pitti> so if it works on a full install, then you can at least downgrade the importance
[12:36] <janimo`> guess not, Bank Holiday in the UK
[12:36] <ogra_> someone with mako should verify
[12:37] <pitti> but it wasn't clear right away that it would only affect dual boot
[12:37] <pitti> as it's now r/w in both dualboot and the emulator
[12:37] <ogra_> yes, but emulator is by design
[12:37] <pitti> uh, why's that?
[12:37] <pitti> I thought it was a bug
[12:37] <ogra_> iirc its a workaround for other issues ... yes its a bug ...
[12:38] <ogra_> but its known
[12:56] <nondem> I loaded the stable verson instead of dev and it works ok(relatively)
[13:07] <Wellark> boiko_: could you comment on: https://bugs.launchpad.net/ubuntu/+source/share-app/+bug/1360670
[13:07] <Wellark> so that I can perform
[13:07] <Wellark> https://bugs.launchpad.net/ubuntu/+source/libhud-qt/+bug/1360671
[13:09] <plars> pitti: I sent mterry an email about the screen unlock needs but haven't heard back. I wonder if someone else from the unity8 team could adjust their unlocker to account for that?
[13:09] <pitti> plars: yeah, I hope so; I also discussed that about a month ago, but there was not much response to that either
[13:10] <pitti> plars: back then I tried rather hard, but didn't find a way to get rid of this lock screen programatically
[13:13] <ogra_> plars, well, it is tricky withug ripping a giant security hole
[13:13] <ogra_> plars, per security design the lock screen is our major secutity check ... once you are in you can do a ton of stuff you wouldnt be able to normally
[13:14] <pitti> ogra_: err, no -- if you are in an adb shell, you are "in"
[13:14] <pitti> you have all the data and access to phablet's processes, etc.
[13:14] <pitti> you can even kill unity8
[13:14] <ogra_> so adding any kind of way to work around the lockscreen should be handed to the security team for review at least
[13:14] <boiko_> Wellark: hmm, I don't now anything about share app,
[13:14] <pitti> so I don't see anything wrong with adding a d-bus method for it
[13:15] <plars> ogra_: I understand, I'm not complaining, just saying that I pinged mterry on it who did the unlock code currently in there. Hopefully someone will have a way to fix it though, because it's also not possible to get automated results without a way to get the screen unlocked
[13:15] <ogra_> pitti, well, that shouldnt be possible anymore once the dev mode is fully implemented
[13:15] <pitti> (or ssh even, which is what I'm more interested in)
[13:15] <ogra_> you will need a pw set to get in
[13:15] <pitti> right
[13:15] <pitti> and we have that
[13:15] <ogra_> and you will need an unlocked screen to get in too
[13:15] <ogra_> per design
[13:15] <pitti> so if you know the pw and can ssh phablet@localhost, you are in
[13:16] <ogra_> this is the final barrier to make sure you are safe
[13:16] <plars> we can absolutely be fine with running the unlocker under sudo though
[13:16] <ogra_> if we pierce that i think jdstrand will haunt you at night
[13:16] <pitti> ogra_: you mean there won't be ssh until you unlock the screen?
[13:16] <ogra_> there wont be adb
[13:16] <ogra_> and you will need adb to enable ssh
[13:16] <pitti> then I guess we need some --testing mode again for that
[13:16] <ogra_> well
[13:17] <ogra_> once sergiusens has added the --password option to u-d-f you know the password
[13:17] <pitti> ogra_: yes, but that doesn't help if there's neither adb nor ssh :)
[13:17] <ogra_> you need to find the dbus runes to hand that tp the screen unlocking
[13:17] <ogra_> *to
[13:17] <pitti> and even if you have it, there's no way to unlock through them
[13:17] <pitti> erk, no
[13:18] <pitti> if you can do that, then you can as well do a d-bus call to do that properly
[13:18] <pitti> making it hard is not a security measure
[13:18] <pitti> it's just making it a pain to test
[13:18] <ogra_> well, talk to the security team
[13:18]  * sergiusens thinks the --password option should die in favor of pitti's 'testing-mode' option
[13:18] <ogra_> i dont think such a swithc is currently planned
[13:18] <sergiusens> or just create a channel with the device ready for testing
[13:18] <ogra_> sergiusens, i surely wont start over with dev-mode now
[13:19] <pitti> well, I don't see anything wrong with having a d-bus call or other programmatic way to unlock the screen *if you are already on the device*
[13:19] <pitti> (ssh or adb)
[13:19] <sergiusens> the image is already bastardized enough to consider it not in the original state
[13:19] <ogra_> this was all agreed on in malta
[13:19] <sergiusens> ogra_: you should know I never agree to anything :-P
[13:19] <ogra_> haha
[13:19] <pitti> plars: ok, that's going to be fun :)
[13:19] <ogra_> well, in fact it was even agreed earlier in a vUDS session
[13:20] <ogra_> and i know you were there :P
[13:20] <pitti> but as soon as that lands, the entire dashboard will be red, so that'll be quite a blocker for promoting an image
[13:20] <asac> so how will infra be able to unlock?
[13:20] <asac> will adb ask for a pass/pin?
[13:20] <ogra_> asac, thats the question
[13:20] <pitti> enabling ssh with --developer-mode and requiring the --password doesn't seem unreasonable to me
[13:20] <asac> what are the options discussed?
[13:20] <ogra_> asac, no, adb cant ask for a pw
[13:21] <pitti> ssh does, though
[13:21] <asac> will ssh go through adb?
[13:21] <ogra_> ssh cant be enabled without adb
[13:21] <asac> we dont want to go through flaky wifi in lab anymore
[13:21] <asac> really!!
[13:21] <ogra_> or without a password set
[13:21] <pitti> asac: ok, good point
[13:21] <asac> its not your home ... its a rack and a cage with many phones stacked above each other
[13:21] <ogra_> adb blocks everything if there is no pw
[13:21] <asac> so whatever we do it should be going through a cable :)
[13:21] <pitti> ogra_: I thought we settled the pw already
[13:21] <ogra_> yeah
[13:22] <ogra_> pitti, right
[13:22] <pitti> that can be set during flashing with --password or --pin or so?
[13:22] <pitti> and all that works now
[13:22] <pitti> it's just the lock screen which is in the way
[13:22] <ogra_> pitti, but we didnt settle the "needs to be unlocked" case
[13:22] <ogra_> this only comes after my dev mode landed
[13:22] <asac> cant adb go into a honeypot sandbox where you can unjail through "escape PASSWORD" ?
[13:22] <ogra_> which is still blocked on --password
[13:22] <asac> hehe
[13:23] <ogra_> (and package installs that i still need to finish)
[13:23] <asac> well. /me waits for the options discussed
[13:23] <boiko_> Wellark: maybe it would be better if bfiller or someone who knows about share-app commented on that?
[13:24] <pitti> ogra_: ah, you're working on adding "sudo" (with SSH_ASKPASS, etc.) to the add-apt-repository/apt-get calls? yeah, argh :/
[13:24] <ogra_> asac, the giant  prob with dev mode is that even though we asked for it nobody seems to actually use pahblet-tools ... so a lot might/will break
[13:24] <ogra_> pitti, no
[13:24] <ogra_> pitti, that was rejected by security :) ... rightly so
[13:24] <pitti> hm, I do use phablet-tools for autopkgtest
[13:25] <ogra_> pitti, but phablet-test-run doesnt
[13:25] <ogra_> and you use phablet-test-run :)
[13:25] <pitti> ogra_: no, I don't use phablet-test-run
[13:25] <ogra_> oh, i thought you did
[13:25] <pitti> that's the thing I like to get rid of
[13:25] <pitti> I use phablet-config for disabling wizard, enabling the autopilot probe, etc.
[13:25] <pitti> (and soon saving/restoring network, in my branch)
[13:26] <pitti> it's still broken now, as adb doesn't run after a reset
[13:26] <ogra_> pitti, so for the package bit i thought to simply add a function to dbus-property-service that can enable silos ... hardcoded so you can onyl supply a silo name
[13:26] <pitti> but at least the non-reset paths work again
[13:26] <pitti> heh -- hacks'r'us
[13:26] <ogra_> and then indeed a function that aloows you to install packages from either archive or silo
[13:26] <pitti> quite frankly, calling sudo seems much simpler and safer, though
[13:26] <ogra_> that at least limits it to official archive
[13:26] <pitti> developers will have to do that anyway for testing their local packages or PPAs
[13:27] <pitti> and sudo isn't going anywhere
[13:27] <ogra_> they will have to use silos or manually use sudo
[13:27] <ogra_> this is for automation ... i dont want sudo involved in that if possible
[13:27] <pitti> well, for testing local packages they won't need any of this, so it's probably moot
[13:27] <ogra_> at home you use sudo all the time anyway
[13:27] <pitti> but it seems weird why you should spend the time on this hack, when phablet-test-run (or whatever) coudl just run sudo
[13:28] <ogra_> pitti, convince mdeslaur and jdstrand
[13:28] <pitti> it's not like the PIN numbers in the CI devices would be a secret or so
[13:28] <ogra_> no, but anyone being able to use it is the issue
[13:28] <pitti> jdstrand: what's wrong with calling "sudo" to add-apt-repository/apt-get in phablet-tools?
[13:28] <ogra_> its not like you cant use phablet scripts at home
[13:28] <pitti> sure, you are meant to use them
[13:29] <ogra_> pitti, that we need to open sudo for that somehow is the issue
[13:29] <pitti> but like that you introduce two different methods for doing things
[13:29] <pitti> we already have sudo
[13:29] <pitti> (if you have a pwd/pin)
[13:29] <ogra_> but not open
[13:29] <pitti> well, I'm nto talking passwordless here
[13:29] <ogra_> today you can use it without any pw
[13:29] <pitti> just the good old sudo which asks you for password
[13:29] <pitti> ogra_: ah well, I mean in the "new" world with pin/pwd only
[13:29] <ogra_> and you cant ask programmatically for a pw
[13:29] <pitti> sure you can
[13:30] <ogra_> since adb messes up the tty handling
[13:30] <ogra_> try it :P
[13:30] <pitti> --password, pass it through SUDO_ASKPASS
[13:30] <ogra_> yes, that would work
[13:30] <pitti> (we already discussed that on the ML)
[13:30] <ogra_> but that measn to store the pw locally on the PC
[13:30] <ogra_> the prob is that you cant do anything like: "adb sudo foo"
[13:30] <ogra_> that wont accept your input
[13:31] <pitti> it's going to look a tad more complicated, but in principle you can
[13:31] <ogra_> so if we wnat to use that tool automatically as well as interactively this wont work
[13:31] <ogra_> and this woould be a regression to todays functionality
[13:31] <pitti> provide a --password option, and if it's not given, make it interactive (through sudo)
[13:31]  * ogra_ wishes adb would just be saner
[13:32] <pitti> or ask beforehand with a read command and stuff it into SUDO_ASKPASS then
[13:32] <ogra_> yeah, that would probably work
[13:33] <ogra_> shielding the interacive bits ...
[13:33] <pitti> right, we can't use sudo's own interactivity
[13:33] <pitti> otherwise you'd run into eternally hanging scripts
[13:34] <pitti> and -S is ugly and limited, but SSH_ASKPASS works quite well
[13:34] <pitti> it'll either fail immediately (if wrong or not given password), or just work
[13:34] <jgdx> kenvandine, hey, can you try out these debs[1] on your dual sim device? [1] http://jenkins.qa.ubuntu.com/job/generic-mediumtests-builder-utopic-armhf/5220/artifact/work/output/*zip*/output.zip
[13:34] <jgdx> kenvandine, fixes what we saw before the weekend.
[13:35] <kenvandine> jgdx, cool, will do
[13:37] <tsdgeos> pitti: maybe you can also review https://code.launchpad.net/~aacid/dialer-app/update_pot/+merge/231559 ?
[13:39] <pitti> tsdgeos: done, thanks!
[13:40] <pitti> and FWIW, our i18n infrastructure leaves somethign to be desired :(
[13:40] <tsdgeos> of course it does :D
[13:41] <boiko_> pitti: tsdgeos: regarding pot file updating, I waxs just discussing with salem_ about that
[13:42] <boiko_> pitti: tsdgeos: we have added CMake rules to update the pot file automatically when running 'make', but the problem is: we hardly land MPs individually, and having the pot file updated in multiple branches always cause conflicts
[13:43] <pitti> boiko_: yeah, I think this should be done at the time when merging branches, not in MPs
[13:43] <pitti> people will never remember to update the pot every time (and shouldn't need to)
[13:43] <pitti> for Ubuntu packages we update the pot during package build, which then gets fed to LP
[13:44] <pitti> due to how we set up the train and branches that won't work here, but the equivalent would be to run something "make update-pot" like at the time of merging branches into trunk
[13:44] <pitti> as for those projects, the POT references is in the trunk, not in the source package that gets uploaded
[13:45] <boiko_> pitti: that makes sense, and would actually be the best solution indeed
[13:45] <pitti> that of course reuqires that there's only very few standard ways to update it (which doesn't need a gazillion dependencies or configuring, etc.)
[13:45] <boiko_> yep
[13:46] <boiko_> tsdgeos: are you going to take care of landing that pot update for dialer?
[13:47] <tsdgeos> boiko_: no, i need people to land stuff
[13:47] <tsdgeos> i am not a lander
[13:47] <tsdgeos> boiko_: need dialer-app and messaging-app landed
[13:48] <boiko_> tsdgeos: so, as for dialer, I have submitted a branch that already updates the pot file: https://code.launchpad.net/~boiko/dialer-app/history_all_missed/+merge/232077
[13:48] <boiko_> tsdgeos: as I changed some strings in there
[13:49] <tsdgeos> boiko_: it'd been cool if you guys looked at my branch when i opened it one week ago
[13:49] <tsdgeos> but sure, feel free to cancel it
[13:49] <tsdgeos> and land yours
[13:49] <tsdgeos> i just want the thing to be translatable
[13:50] <boiko_> tsdgeos: yeah, I know, sorry about that, we have been in a hurry to finish our own stuff and ended up not flushing the pile of MRs we already have
[13:51] <boiko_> tsdgeos: I still have a couple MRs from elopio I promised to review last week but didn't get to them yet :/
[13:51] <tsdgeos> yeah, we're all in a hurry
[13:51] <pitti> boiko_: did that by any chance include fixing the "+ Create New" string?
[13:52] <boiko_> pitti: the create new string comes from the address-book-app qml plugin
[13:52] <boiko_> pitti: so maybe we need to tweak the domains used from there?
[13:54] <pitti> boiko_: I particularly meant the "+ " in front of it (there's also no translator comment what that should be -- if it's always going to be + it shoudln't be transaltable
[13:54] <pitti> boiko_: I don't know QML, but hopefully ther's the equivalent of dgettext()? perhaps something like i18n.tr("foo", domain="otherproject") ?
[13:55] <boiko_> renatu: ^
[13:55] <boiko_> renatu: read about the "+ Create New" string above
[13:58] <renatu> pitti, I added a translator comment for that
[13:58] <renatu> let me check if it was released already
[13:58] <pitti> renatu: ah, thanks; is that + supposed to be translated?
[13:59] <renatu> pitti, no
[13:59] <renatu> pitti, I do not know
[13:59] <renatu> how do you want translate that?
[13:59] <pitti> well, I don't know what it is :)
[14:00] <pitti> it just looks like a buggy string to me
[14:00] <pitti> if that's kind of an UI element, it shouldn't be part of the translatable string
[14:00] <pitti> like "+ " + i18n.tr("Create New")
[14:01] <pitti> or perhaps in other languages you'd just skip it and say "Add new"
[14:02] <renatu>                 // TRANSLATORS: this refers to creating a new contact
[14:02] <renatu>                 text: i18n.tr("+ Create New")
[14:02] <pitti> so supposedly it should be taken out?
[14:03] <pitti> (I'm just guessing)
[14:03] <renatu> pitti, this was a designer decision, I am not sure how we should handle that in the other languages
[14:03] <renatu> :D
[14:04] <renatu> maybe we should kee the "+" always, but I do not know how the Chinese language works
[14:06] <pitti> some translator will screw that up, especially as there's no explanation what the + is
[14:06] <pitti> so perhaps the comment could be extened to explain that?
[14:11] <dobey> yes, the comment needs to explain that
[14:12] <dobey> doing "+" + i18n.tr() is bad, because it means placement of "+" might be wrong in some langauges
[14:12] <dobey> although, i'd just say that having it in the string at all is wrong
[14:13] <pitti> dobey: if it's a poor man's UI design element, it would always be there
[14:13] <dobey> we're switching to ncurses for the UI instead of qml/qt? :)
[14:13] <pitti> but a comment like "always keep that plus at the left" doesn't make sense -- just don't make it translatable then
[14:14] <pitti> or say "this might be dropped or moved around consistently with <that other string>" in the comment
[14:14] <dobey> pitti: "Don't translate the '+' but only change its position if needed."
[14:14] <pitti> dobey: yeah, whatever; I honestly don't know what the + means, I just saw it in the pot and (with my German translator hat on) wondered what it is
[14:14] <dobey> ie, the same thing we have to do for string formatting things
[14:15] <dobey> pitti: yeah i have no idea either. it makes no sense to me
[14:15] <pitti> and I've seen enough msgids which were actually buggy (people split them in the middle of the sentence etc), so I wondered if that was actually intended
[14:16] <dobey> i see a "+" in the bottom edge "tab" in contacts
[14:16] <dobey> i guess this is the string for that?
[14:17] <dobey> i'd wonder why it wouldn't just say "New" though, instead of trying to be clever
[14:34] <kenvandine> jgdx, ok... i'm not getting cellular data on the second sim (using your debs)
[14:34] <kenvandine> 2014-08-25 10:33:00,493 - WARNING - file:///usr/share/ubuntu/settings/system/qml-plugins/cellular/Components/CellularMultiSim.qml:59: ReferenceError: sim2 is not defined
[14:34] <kenvandine> jgdx, cell data is turned off... and turning it on produces that
[14:36] <cyphermox> rickspencer3_: you broke SD card file dragging? :)
[14:37] <rickspencer3_> cyphermox, yeah, at your service :)
[14:37] <cyphermox> alrighty
[14:37] <rickspencer3> just going my job :)
[14:37] <kenvandine> jgdx, which i guess is just cruft, and should be sims[1] ?
[14:38] <cyphermox> rickspencer3: it's good; so you manually installed packages from a silo?
[14:39] <rickspencer3> cyphermox, no
[14:39] <kenvandine> jgdx, so changing the references to sim1 and sim2 fixes the error and the control seems to work
[14:39] <rickspencer3> cyphermox, it just showed up when I re-installed with the new partitions this morning
[14:40] <rickspencer3> where "it" == the sd card icon under Krillin in nautilus
[14:40] <cyphermox> rickspencer3: ah
[14:40] <pitti> ogra_: sorry, krillin rules are already in /lib/udev/rules.d/69-libmtp.rules in utopic, I just didn't see them
[14:40] <cyphermox> rickspencer3: it's still in rtm silo 2
[14:40] <ogra_> pitti, right
[14:40] <ogra_> pitti, we need them in trusty and precise though
[14:40] <cyphermox> rickspencer3: could you get me the version number of mtp-server then?  dpkg -l mtp-server | cat | pastebinit
[14:40] <jgdx> kenvandine, which branch?
[14:40] <rickspencer3> cyphermox, sure
[14:40] <cyphermox> err, when piping to pastebinit you don't actually need the cat there ;D
[14:41] <kenvandine> jgdx, the debs you sent me this morning
[14:41] <ogra_> rickspencer3, you switched to rtm inbetween, no ?
[14:41] <rickspencer3> ogra_, no
[14:41] <ogra_> ah, k
[14:41] <cyphermox> ogra_: regardless, silos don't appear magically :)
[14:41] <kenvandine> jgdx, don't have the link handy anymore :)
[14:41] <ogra_> (just because the new mtp changes didnt enter that)
[14:41] <jgdx> kenvandine, right, so the second sim is limited to 2g. Might cause issues when you try to set it to anything else. See https://code.launchpad.net/~jonas-drange/ubuntu-system-settings/adapt-to-modemtechnologies/+merge/231646 :)
[14:42] <rickspencer3> cyphermox, http://pastebin.ubuntu.com/8141253/
[14:42] <jgdx> kenvandine, haven't seen that particular warning before. Fixing!
[14:42] <kenvandine> jgdx, yeah...  it's set to 2g but the indicator isn't showing it's connected
[14:42] <kenvandine> jgdx, but clearly the ref to sim1 and sim2 are wrong :)
[14:43] <jgdx> kenvandine, yep
[14:43] <cyphermox> oh
[14:43] <cyphermox> rickspencer3: turns out you actually need cat after all
[14:43] <rickspencer3> ok
[14:43] <kenvandine> jgdx, oh... the branch you just linked has this fix :)
[14:43] <cyphermox> the version number gets truncated otherwise :(
[14:43] <jgdx> kenvandine, what does list-modems say about connman.powered and radiosettings.technologypreference?
[14:43] <jgdx> kenvandine, :))
[14:44] <kenvandine> powered 1
[14:44] <kenvandine> and tech pref = gsm
[14:44] <jgdx> hm, I've been seeing the exact same thing, but that was on the farm
[14:44] <jgdx> assumed bad coverage
[14:47] <kenvandine> jgdx, good news is call waiting and call forwarding works :)
[14:48] <jgdx> kenvandine, that is good news. I spent a large part of my Sunday figuring that out
[14:50] <kenvandine> jgdx, so what's the eta on that WIP progress branch with the sim1 and sim2 fix?
[14:50] <kenvandine> maybe that has other fixes we need :)
[14:56] <jgdx> kenvandine, I fixed it for the callfwd branch too
[14:56] <jgdx> r888
[14:56] <jgdx> so I think we're good to put that in a silo
[14:57] <jgdx> the modemtechnologies branch is done
[14:57] <jgdx> maybe they can go in a silo together
[15:06] <kenvandine> jgdx, ok
[15:18] <kenvandine> jgdx, i'm going to hold off on modemtechnologies and get the call fwd/waiting branch landed
[15:19] <kenvandine> to get the sim1/sim2 bug fixed, which is in the current image
[15:20] <jgdx> kenvandine, cool
[15:20] <jgdx> thanks
[15:21] <kenvandine> thanks for the fix :)
[15:22] <jgdx> kenvandine, thank you! I have a test for this, but it's obiously not good enough.
[15:22] <kenvandine> now if i can just figure out why it isn't getting data
[15:23] <kenvandine> must be at the ofono level
[15:25] <kenvandine> jgdx, oh... how does it know which sim to use for data?
[15:25] <jgdx> kenvandine, the online state (connman.powered) persists
[15:26] <Wellark> bfiller: could you state here that share-app is indeed abandoned and it's OK to remove from archive:
[15:26] <Wellark> https://bugs.launchpad.net/ubuntu/+source/share-app/+bug/1360670
[15:26] <ubot5`> Ubuntu bug 1360670 in share-app (Ubuntu) "drop from archive" [Undecided,New]
[15:26] <bfiller> Wellark: yes it's abandones
[15:26] <kenvandine> jgdx, so powered and attached?
[15:26] <bfiller> you can drop it
[15:27] <kenvandine> jgdx, if so... it all looks right
[15:27] <jgdx> kenvandine, yeah, I'm not sure who deals with attached, but uss control connMan.powered
[15:27] <kenvandine> ok, the right one is powered... but i have no network :/
[15:28] <jgdx> apn issue?
[15:29] <jgdx> or does it work in the other slot?
[15:29] <kenvandine> i didn't change slots
[15:30] <kenvandine>  /ril_1     gsm               connecting (prepare)
[15:33] <Wellark> bfiller: please state that in the bug, thanks!
[15:34] <bfiller> Wellark: done
[15:38] <Wellark> bfiller: thanks!
[15:41] <jgdx> kenvandine, what produced that output?
[15:41] <kenvandine> nmcli d
[15:41] <kenvandine> it seems to connect if i switch slots
[15:43]  * jgdx bbiab
[15:46] <seb128> kenvandine, jgdx, hey, do you have any idea why some of the sim autopilots started to have issues on CI runs?
[15:46] <kenvandine> could have been because of the bad reference to sim2 in one of the multisim  files
[15:46] <kenvandine> which i have a fix for in a silo
[15:47] <kenvandine> but that bug had made it through CI :(
[15:48] <kenvandine> jgdx, grrr... well after switching slots nmcli showed it as connected until i turned off wifi...
[15:48] <kenvandine> then wifi and gsm went to disconnected
[15:56] <seb128> kenvandine, k, so you have a fix pending?
[15:57] <kenvandine> if that's the problem :)
[15:57] <kenvandine> can you point me at a failure?
[15:57] <seb128> kenvandine, btw, the update panel layout-using-column should be go to do, gatox +1ed it as well
[15:57] <seb128> kenvandine, https://jenkins.qa.ubuntu.com/job/autopilot-testrunner-otto-utopic/2507/testReport/junit/ubuntu_system_settings.tests.test_cellular/DualSimCellularTestCase/test_changing_sim1_name/
[15:58] <seb128> "should be good to go"
[15:58] <seb128> if you want to add it to the next landing
[15:59] <seb128> (Diego is going to do more work on the panel, so would be nice to have that first changeset landing to avoid rebases)
[15:59] <kenvandine> 2014-08-25 14:48:19,050 - WARNING - file:///usr/share/ubuntu/settings/system/qml-plugins/cellular/Components/CellularMultiSim.qml:50: ReferenceError: sim1 is not defined
[15:59] <kenvandine> that is probably the same bug
[15:59]  * kenvandine wonders how we got a CI pass on this...
[16:00] <seb128> kenvandine, you are sure we did? or did you just land things with red CI? ;-)
[16:00] <kenvandine> unless i was confused and CI passed on a different rev
[16:01] <kenvandine> anyway, that fix is building in silo 8 now
[16:01] <kenvandine> i want to get that landed quickly
[16:01] <pmcgowan> Wellark, hows it coming along?
[16:01] <kenvandine> seb128, i'll will look at add your's to another landing
[16:02] <kenvandine> jgdx, maybe i need to go for a walk and see if my device can connect... perhaps it is just a weak signal
[16:02] <seb128> kenvandine, thanks
[16:03] <kenvandine> i really want more confidence that settings isn't introducing this problem :)
[16:03]  * kenvandine goes to move around outside to see if things improve... bbiab
[16:14] <Wellark> pmcgowan: I got myself really good redwine for this evening
[16:54] <nondem>  I've been trying to give myself time to learn the GUI for Touch but it is aggravating...I used to select system settings to get to the setting pages - but now it just brings up the right slide-out that use to have them but it just says UPDATE w/a blank area and a BACK icon that does nothing.
[16:54] <nondem> rebooting got it back but that isn't acceptable
[16:56] <ogra_> sounds like you are testing on manta ...
[16:56] <ogra_> ... which has been left behind quite a bit
[16:56] <ogra_> all focus is on getrting the phones ready atm
[16:59] <nondem> Yea...it is a Nexus 10
[16:59] <ogra_> right, that might have issue
[16:59] <ogra_> *issues
[16:59] <nondem> bummer...time to find another way to run linux on my Manta
[17:00] <nondem> Interesting you knew it was manta :)
[17:04] <ogra_> mvo, yo
[17:04] <ogra_> nondem, the only arch we have using a side stage atm
[17:04] <mvo> hi ogra_
[17:04] <ogra_> nondem, which is most likely also what causes your issues
[17:05] <ogra_> mvo, soo ... we will have to roll back your click upload ... unless you have a bright idea how to allow people to still install clicks from cmdline with pkcon
[17:05] <ogra_> mvo, it breaks the SDK otherwise
[17:05] <ogra_> (or already broke it)
[17:05] <mvo> ogra_: let me look into this, I saw the mail. I think pkcon has a --allow-unauthenticated like mechanism as well
[17:05] <mvo> ogra_: we can't run click direct with --allow-unauthenticated?
[17:06] <ogra_> we ask people to use pkcon and all tools do too
[17:06] <ogra_> click directly wont work as phablet user
[17:06] <ogra_> and we are working on dropping root access
[17:09] <mvo> ogra_: so can we make the tools pass additional options?
[17:09] <ogra_> i guess so
[17:09] <ogra_> bzoltan, ^^^^
[17:09] <ogra_> i think jdstrand was alos affected with his tests
[17:09] <bzoltan> mvo: hello there
[17:09] <mvo> hello bzoltan
[17:09] <jdstrand> I was
[17:10] <jdstrand> mvo: (click requires sudo whereas pkconf does not due to policykit perms)
[17:10] <jdstrand> pkcon*
[17:12] <bzoltan> mvo https://bugs.launchpad.net/ubuntu/+source/phablet-tools/+bug/1360582
[17:12] <mvo> ok, let me look into the pkcon again to see if there is a option to override
[17:12] <mvo> bzoltan: yeah, I saw it this monrning
[17:13] <mvo> so if we could run pkcon --allow-unauthenticated or similar it would work
[17:13] <mvo> ?
[17:13] <mvo> I mean, is that a acceptable change?
[17:15] <bzoltan> mvo:  if that would work as phablet user
[17:18] <bzoltan> mvo:  that is what we do http://bazaar.launchpad.net/~ubuntu-sdk-team/qtcreator-plugin-ubuntu/trunk/view/head:/share/qtcreator/ubuntu/scripts/qtc_device_applaunch.py#L200
[17:19] <mvo> bzoltan: ok, let me look into this. may jdstrand can comment too, but it seems risky to allow this by default. pardon my ignorance here, but what is the planed workflow for putting a device into developer mode? could we simply check if the device is in developer mode and only then allow --allow-unauthenticaed?
[17:20] <ogra_> mvo, jdstrand cant polkit tell apart iof we are on console or UI ?
[17:20] <bzoltan> mvo:  that would be fine with the SDK
[17:20] <ogra_> if you only allow it for console that should work
[17:21] <bzoltan> mvo:  anything works for the SDK what does not need much user interaction and scriptable for the phablet user
[17:23] <mvo> bzoltan: right, the trouble here is (of course) that if the sdk can bypass the signature checking, how do we prevent attackers to just do the same?
[17:32] <jdstrand> sorry, was in a meeting
[17:32] <mvo> jdstrand, bzoltan: is there anything that runs as root when the sdk is used or when the device is put into developer mode? I think we need something that can set a flag/option to allow unauthenticated clicks. we can't just allow phablet to install unauthenticated package or we can remove the change again as we do not add security if we do
[17:33] <ogra_> mvo, root support will be completely gone soon
[17:33] <ogra_> you can use sudo programmatically with some hacks but thats rather painful and ugly
[17:34] <ogra_> (though we might have to fall back to that for package install in phablet-tools too)
[17:36] <jdstrand> mvo: we want to support sideloading. according to the spec, it is not tied to developer mode. we don't want to allow unauthenticated packages by default or toggle that via the gui
[17:37] <jdstrand> mvo: we want the gui to fail on unauthenticated packages
[17:37] <jdstrand> mvo: which leaves the cli
[17:37] <jdstrand> the cli is protected by either adb cert checks or terminal password prompting
[17:38] <jdstrand> so adding a cli option is ok
[17:38] <mvo> jdstrand: ok, so a flag/environment it is then, let me look at this
[17:38] <jdstrand> the spec says: "Packages manually installed through the command line tool without a debsigs 'origin' signature type should present an appropriate warning and ask the user for confirmation. "
[17:38] <jdstrand> that seems fine ^, and I think it is fine to make that automatable
[17:39] <jdstrand> mvo: thanks!
[17:39] <mvo> thank you
[17:39] <jdstrand> mvo: and to be thorough-- if the package *has* the signature and it fails, it should fail
[17:40] <jdstrand> that is different than unsigned (of course)
[17:40] <mvo> that is the case right now, it only overrides missing sigs, not wrong ones
[17:40] <jdstrand> we all know that, I just wanted to be explicit :)
[17:40] <mvo> :)
[17:40] <jdstrand> cool :)
[17:59] <mihir> nik90: popey http://imgur.com/d3QA3v2
[17:59] <mihir> nik90: it is now in page does, design looks okay ?
[17:59] <mihir> balloons: ^^
[18:00] <balloons> mihir, you split it out.. that's an improvement
[18:00] <mihir> balloons: yup , it was too cumbersome in new event
[18:00] <mihir> balloons: popey nik90 any other suggestion ?
[18:07] <nik90> mihir: much better
[18:08] <nik90> mihir: although I feel that the recurrence textfield can be replaced by a slider
[18:08] <nik90> mihir: since a user will nto go beyond 20 occurences max
[18:08] <mihir> nik90: i am studying that compononat
[18:13] <nhaines> mihir: "After X Occurrence" should probably be "After a number of occurrences" or "After x occurrences"
[18:13] <mihir> nhaines: i believe that won't feet into screen
[18:13] <mihir> nhaines: that's why we kept as X
[18:13] <nhaines> mihir: fair enough.  "Occurrences" should be plural at least.
[18:14] <nhaines> (In English, leastwise.)
[18:14] <mihir> nhaines: yup agreed, will make that change ,thanks for your input
[18:14] <nhaines> +1
[18:44] <jgdx> seb128, right, weird how that got through
[18:44] <jgdx> kenvandine, walking helped?
[18:51] <bzoltan> mvo:  All I need is a capability to install and remove application under development from the QtCreator.
[18:53] <bzoltan> mvo:  I do not know much about the policy or the security strategy. All I know is that the SDK is broken with the Ubuntu images from #205
[18:54] <bzoltan> mvo:  so I need either a way to sign a package or a way to install unsigned packages as phablet user. The sudo is not an option as it can not be scripted.
[18:58] <bzoltan> mvo: The SDK is not running anything as root as ogra_ said.
[19:00] <bzoltan> jdstrand:  mvo: please note that the SDK tools can not interact with background scripts easily ... and even if it would be possible a confirmation dialog at each app running would be rather annoying.
[19:01] <ogra_> bzoltan, i'll roll back click for 206 ... then you guys have time to figure it out
[19:02] <bzoltan> ogra_: thank you
[19:03] <bzoltan> jdstrand:  mvo: I would vote on a policy that if the developer mode is enabled then the developer is free to install whatever apps. If that is not possible, than the SDK should be able to sign the packages and the device should accept signed packages from a certified SDK.
[19:09] <jdstrand> bzoltan: the solution mvo is working on is adding an option to pkcon to allow it to install unsigned packages
[19:12] <jdstrand> bzoltan: you'll have to change the script for the extra arg/add an envvar, but otherwise it will work the same
[19:18] <jgdx> after #189, how do you enable ssh on your device? the dbus call fails for me
[19:18] <kenvandine> https://code.launchpad.net/~ken-vandine/ubuntu-system-settings/lp1361297/+merge/232124
[19:19] <kenvandine> jgdx, ^^  mind a quick ack on that one liner?
[19:19] <ogra_> jgdx, adb shell android-gadget-service enable ssh
[19:19] <jgdx> kenvandine, sure
[19:19] <ogra_> or simply use phablet-shell once
[19:19] <popey> https://wiki.ubuntu.com/Touch/ReleaseNotes#Accessing_the_device_over_SSH is probably going to need updating isn't it?
[19:19] <ogra_> (that will be changed soon though)
[19:20] <jgdx> right, tried phablet-shell, but I guess there's something wrong somewhere else
[19:20] <jgdx> thanks ogra_
[19:20] <ogra_> popey, once developer mode is done i'll go over the docs
[19:24] <popey> kk
[19:24] <cwayne1> so how do we properly sign a click so it can be installed in 207?
[19:25] <ogra_> cwayne1, by sending it to the store ?
[19:25]  * ogra_ guesses thats the only plACE THE SECRET KEY IS AVAILABLE 
[19:26] <ogra_> OOPS
[19:26] <cwayne1> ogra_: what about for testing before we do that
[19:26] <ogra_> sorry
[19:26] <ogra_> you install it unsigned
[19:26] <cwayne1> oh is that an option to pkcon now?
[19:26] <ogra_> not yet ... but see backlog
[19:27] <ogra_> cwayne1, "<jdstrand> bzoltan: the solution mvo is working on is adding an option to pkcon to allow it to install unsigned packages"
[19:27] <cwayne1> ah ok, sorry
[19:32] <jdstrand> yeah, no developer signatures yet
[19:41] <cwayne1> mardy: ping
[19:55] <bzoltan> jdstrand:  adding extra arg is not a problem. Thank you.
[20:02] <jdstrand> cool
[20:03] <mihir_> nik90: ping !!
[20:03] <mihir_> balloons: ping
[20:05] <balloons> mihir_, pong
[20:06] <mihir_> balloons: we need to make most of the changes into emulator if we try to finish this new design before RTM ?
[20:07] <mihir_> popey: if we can finish this up , is it possible to push this in RTM ?
[20:10] <balloons> mihir_, I'm not sure of the question, but of you can get everything work SOON, it should be possible
[20:10] <mihir_> balloons: okay.
[20:24] <matv1> forgive my ignorence but zeitgeist being unreachable should not be enough of a reason for a system crash?
[20:25] <nhaines> Does the phone have zeitgeist running?
[20:26] <matv1> i assume so because a log is complaining about it after a crash
[20:27] <jgdx> kenvandine, does your second slot even implement the radiosettings interface?
[20:27] <matv1> nhaines it says Critical: zeitgeist not responing and then watchdog kicking in
[20:27] <Cimi> kenvandine, I was trying bacon2d, but I cannot compile... complains missing box2dbody.h
[20:27] <Cimi> hi first of all :D
[20:27] <Cimi> which package I need?
[20:27] <kenvandine> Cimi, hey!
[20:28] <kenvandine> Cimi, you need to init the submodule
[20:28] <kenvandine> look at the README
[20:28] <kenvandine> it has the command
[20:28] <matv1> nhaines i am trying to figure out wether these are causes of the crash or effects
[20:28] <kenvandine> jgdx, yes, the 2nd does have radiosettings
[20:29] <Cimi> kenvandine, right, thx!
[20:29] <kenvandine> Cimi, np!
[20:31] <jgdx> ahayzen, it's my sim that doesn't offer it.
[20:32] <mike432> hello on wendnesday is feature freeze, I want to request and ask, if there is an manual updater for the OS is in the touch version, so it is updating with one click and no a flash process needs to be done
[20:33] <nhaines> mike432: that's been around since... as long as I can remember.
[20:33] <nhaines> Unless you're asking if there's a way to upgrade the system without rebooting, in which case, no.
[20:34] <mike432> sailfish has an update function, the current ubuntu touch too ? I dont see it
[20:34] <mike432> but maybe when 14.10 is out my nexus 7 tablet shows the command
[20:34] <mike432> further: some apps cannot be installed. why? even not updated on nexus 7
[20:38] <mike432> does anyone know why? some app cannot be updated, process error dbus
[20:45] <matv1> matv1 is terminal app crashing consistently (even after reboots) a known bug atm ? (channel devel latest image)
[20:46] <nhaines> mike432: under System Settings you'll see Updates.
[20:47] <mike432> yes but only the apps, not the drivers and OS itself
[20:47] <nhaines> Not true.
[20:47] <mike432> so you want to tell me, that, when 14.10 is out, i can load it on that page?
[20:47] <nhaines> What revision are you running?
[20:48] <mike432> battery is empty, i gues rev 333
[20:50] <nhaines> I don't think there's any way to upgrade from trusty.  uptopic is currently on r203 in the devel channel, r207 in devel-proposed.
[20:50] <mike432> so i need to flash the nexus again new to update ?
[20:50] <nhaines> I suspect it will either show an update to utopic when there is one, or it will never be updated again.
[20:50] <mike432> and then with 14.10 i have a button  like in sailfish ?
[20:51] <nhaines> I don't know anything about sailfish.
[20:51] <mike432> there is a button, checks if there is a new update, then it downloads it, reboots and installs.
[20:51] <nhaines> Your phone already has a button.  But it will only show available updates and there are none.
[20:51] <mike432> so a button is doing the flash process
[20:51] <nhaines> Yes.
[20:51] <mike432> i have it on nexus 7 tablet
[20:52] <mike432> ok so i can load 14.10 from that button as well, lets hope
[20:52] <nhaines> That doesn't matter.
[20:52] <nhaines> What matters is what's actually installed.  If you installed from the stable channel, the last update was in April.
[20:52] <mike432> but there are 20 apps which do not update, there is a process error shown, even when I uninstall, the install process does not work
[20:53] <nhaines> The apps probably no longer support trusty
[20:54] <mike432> ok, the point is I want to give the tablet away as a gift, and then these people need to be able to updated on their own by the button, and not by flashing the device over commandline
[20:56] <nhaines> Okay, then you shouldn't do that until after 14.10 comes out.
[20:57] <mike432> that is mid of october, right`?
[20:57] <nhaines> Once there's a public release and not a developer release, that's the time to give out Ubuntu as a present to non-technical users.  :)
[20:57] <nhaines> Yup.
[20:57] <mike432> but the 14.10 develope rrelease would update too ?
[20:58] <nhaines> To 15.04 where things are breaky, yes.
[20:59] <nhaines> The phones are getting a 14.09 type of release, anyway.  So... I'd wait.
[20:59] <nhaines> (But if you want to play with it so you can give support to the recipient, installing utopic isn't a bad idea.)
[21:00] <nhaines> It's very different, and very polished.  But I think there are still some changes to drop in the next week.  :)
[21:02] <mike432> ok i have 14.04 r303
[21:02] <popey> mike432: ye olde
[21:02] <nhaines> Yup, that's the latest version.
[21:02] <popey> mike432: update to 14.04 and you'll have an update mechanism for apps and the system
[21:02] <nhaines> popey: he's using 14.04.
[21:03] <mike432> yes
[21:03] <popey> i know
[21:03] <popey> oh, typo
[21:03] <popey> 14.10
[21:03] <mike432> so 14.04 has not the update button for the OS ?
[21:03] <nhaines> mike432: there's nothing to update to.
[21:03] <popey> mike432: 14.04 is so long ago most of us have long forgotten what it did/didn't have
[21:03] <mike432> where is the developer image for 14.10 ? i would like to do it now, ok so.. no update
[21:03] <nhaines> The last stable release is 14.04.
[21:04] <popey> mike432: what host OS are you using?
[21:04] <mike432> where to see ?
[21:04] <popey> no, what OS are you using on your PC
[21:04] <popey> mike432: fyi this is what the update process looks like http://popey.mooo.com/screenshots/device-2014-08-25-220423.png http://popey.mooo.com/screenshots/device-2014-08-25-220437.png
[21:05] <mike432> dunno, its off, I guess i installed as well a fresh image so 14.04
[21:05] <popey> mike432: oh, which nexus 7 is it? 2012 or 2013?
[21:05] <mike432> 2013
[21:05] <popey> ok
[21:06] <mike432> thanks for the screens, yes. e.g. the gallery, this is not updating, there is an error process
[21:06] <popey> so i would recommend you plug the device into a pc running ubuntu and use the ubuntu-device-flash tool to update it
[21:06] <mike432> even i can uninstall it and then the download does not install
[21:06] <mike432> not the update
[21:06] <mike432> update to which version ?
[21:06] <popey> do you have an ubuntu pc handy?
[21:07] <mike432> handy means not mobile but nearby? yes there is one, but offline now, will try then tomorrow
[21:07] <popey> ok
[21:07] <mike432> ok thanks will try to update the tablet then
[21:07] <popey> I'd do a wipe and clean install
[21:08] <mike432> mhh i think i used this help: http://smartphoneinside.wordpress.com/2014/03/14/ubuntu-touch-auf-nexus-gerate-flashen/
[21:08] <mike432> so I can run it again ?
[21:08] <popey> https://wiki.ubuntu.com/Touch/Install
[21:09] <popey> i would recommend you use ubuntu-device-flash --channel=devel --wipe
[21:09] <nhaines> popey: he's trying to install Ubuntu 14.10-based apps on his 14.04 device because that's what the appstore gives him.
[21:09] <popey> which will wipe the device
[21:09] <popey> yes, i know
[21:09] <popey> mike432: so you'll lose all your data on the device if you do the above, is that okay?
[21:09] <mike432> yes
[21:09] <popey> ok
[21:10] <mike432> ok thanks will try
[21:10] <popey> mike432: feel free to drop by here again tomorrow if you get any issues
[21:11] <matv1> so terminal app failing to start anyone :) ? might it have to do with recent security enhancements like setting a password and the developer mode setting.. ?
[21:11] <mike432> did anyone tried to install on lenovo yoga tablet 8 ?
[21:11] <popey> mike432: is that an intel device?
[21:12] <nhaines> mike432: http://developer.ubuntu.com/start/ubuntu-for-devices/installing-ubuntu-for-devices/ ist aktualisiert.  Die andere Seite ist nicht mehr aktuell.  Das ist wichtig zu kennen. :)
[21:12] <popey> matv1: works here
[21:13] <mike432> yoga has: •MTK 1,2-GHz-Quad-Core-Prozessor
[21:13] <matv1> popey ok thats good to know. so thats means its crashing consistently here
[21:13] <mike432> http://shop.lenovo.com/de/de/tablets/lenovo/yoga/yoga-8/#tab-customize
[21:14] <mike432> this is the only one with sustainable battery
[21:14] <matv1> also i dont see a logfile in logviewer. is that to be ecpected?
[21:14] <popey> don't think anyone has ported to that
[21:14] <mike432> it has 40 hours of battery and many days
[21:14] <mike432> very good
[21:15] <popey> golly
[21:15] <nhaines> That *is* what I call sustainable.
[21:15] <mike432> i load the power akku once a week
[21:16] <mike432> very cool and has a clap to have several positions, you can stand it up and use it as TV standalone, very cool
[21:16] <mike432> i watch a lot of tv over it
[21:16] <mike432> aynway
[21:17] <popey> ☻
[21:17] <mike432> will meizu or bq bring out a tablet too ?
[21:17] <popey> no plans for that yet
[21:17] <mike432> one last idea for feature freeze, the buttons pressed on the ubuntu touch do not cause a vibration or sound, please enable that
[21:18] <popey> some do here
[21:18] <mike432> k
[21:18] <mike432> on nexus ?
[21:19] <pmcgowan> popey, did you see my request about another app scan?
[21:19] <nhaines> mike432: the keyboard does, and that's nice.
[21:19] <popey> i did pmcgowan
[21:19] <popey> i even put a little gold star on it
[21:19] <pmcgowan> oh I bet :)
[21:19] <popey> ☻
[21:21] <mike432> dont know what that is
[21:21] <popey> mike432: i have a nexus 4 and nexus 7, but mostly use the nexus 4
[21:22] <mike432> nexus 4 is not produced anymore
[21:22] <popey> yeah, we bought a load some time back
[21:22] <mike432> shoudl i buy a nexus 4 used or the new nexus 5 ?
[21:23] <mike432> do you want to send me one nexus 4 then?
[21:23] <popey> for what purpose?
[21:23] <popey> hehe
[21:23] <mike432> :-)
[21:23] <popey> Nice try
[21:23] <nhaines> mike432: I run Ubuntu on my Nexus 5 (not new, it's a year old now!) but it's not supported.
[21:23] <mike432> to test touch and to give it away as gift
[21:23] <nhaines> popey: make that two.  ;)
[21:23] <popey> i wish
[21:23] <nhaines> mike432: I'd wait until the phones are available for sale in the next few months.
[21:23] <mike432> not supported means it does not run on nexus 5 ?
[21:24] <popey> well
[21:24] <mike432> ok but the drivers are propietary ?
[21:24] <popey> Canonical make images for Nexus 4, 7, 10.
[21:24] <mike432> ok
[21:24] <popey> Community maintain ports to other devices including Nexus 5
[21:24] <nhaines> mike432: means it runs quite well except the screen doesn't turn off.  And right now, there's no cellular data either.
[21:24] <mike432> urgh
[21:24] <nhaines> mike432: but there's only one or two people working on it.
[21:24] <mike432> k
[21:24] <mike432> so mezu mx4
[21:24] <mike432> or bg for cheaper
[21:25] <nhaines> mike432: whatever's available for sale at ubuntu.com.
[21:25] <mike432> why is there no pre-oder page ?
[21:25] <mike432> oh at ubuntu.com?
[21:25] <mike432> cool
[21:25] <mike432> why is there no preoder page ?
[21:25] <nhaines> That's where the links will show up once they're available.
[21:25] <nhaines> Question for BQ and Meizu. :)
[21:25] <mike432> sailfish did this 3/4 year before
[21:25] <mike432> for the ubuntu page ?
[21:25] <nhaines> Probably because they can't advertise anything because the software designs aren't final.
[21:25] <popey> Ok, so to clarify some things.
[21:26] <popey> We make the software, not the hardware
[21:26] <popey> Jolla did both AIUI
[21:26] <mike432> but sell it over unutu.com `
[21:26] <mike432> ?
[21:26] <popey> We have partners who make the devices. It's up to them how and when they sell them.
[21:26] <mike432> so my order page will be not ubuntu ?
[21:26] <popey> However, I'd recommend bookmarking ubuntu.com, at the point when they go on sale, you can bet we will update the site!
[21:26] <nhaines> mike432: I assume ubuntu.com will link to BQ and Meizu, not sell the phones directly.  But in any case, I am certain it'll be featured there once available.
[21:27] <popey> Yeah, we're not a hardware company.
[21:27] <mike432> ok
[21:27] <mike432> thx
[21:27] <mike432> i cannot await it
[21:27] <mike432> and i will order 5 devices at least
[21:28] <popey> hah
[21:28] <popey> I'll certainly order a couple for my kids ㋛
[21:28] <mike432> yes
[21:29] <mike432> ubuntu touch has a briht future, as sailfish gui is closed source as far as i see
[21:29] <mike432> we need an open mobile OS and that is ubuntu
[21:30] <mike432> ok then, time to go to bed, anyone able to compile an app for touch?
[21:31] <matv1> popey as it stands your kids will have a terrible time using the terminal :)
[21:31] <matv1> whats files should i adb pull to see whats going on?
[21:31] <popey> mike432: jolla recently open sourced their stuff
[21:32] <mike432> uRL to source ?
[21:32] <Stskeeps> nah, not all of it - just parts of it (browser, office)
[21:32] <popey> there we go
[21:32] <popey> oh, I thought it was all GPL'ed/
[21:32] <popey> mike432: Stskeeps knows way more
[21:32] <Stskeeps> nah, you guys have the lead in that area ;)
[21:33] <mike432> no the kernel is open, and the gui is closed like apple does
[21:33] <popey> heh
[21:33] <mike432> as far as i know
[21:33] <popey> http://reviewjolla.blogspot.fi/2014/08/jolla-sailfish-os-source-codes.html
[21:33] <popey> thats the post i saw recently
[21:33] <mike432> ok thanks and good night
[21:33] <popey> nn
[21:34] <Stskeeps> popey: bit of misunderstanding of GPL source code offer dvd
[21:34] <popey> ahhh
[21:34] <Stskeeps> also, not just the gpl stuff.. anyhow, i'm offtopic :)
[21:34] <popey> Good. I can continue to have jolla on my "shitlist" for not open sourcing everything then ㋛
[21:34] <Stskeeps> ;)
[21:38]  * tbr chuckles at people misunderstanding things in various ways.
[21:38] <popey> ☻
[21:42] <tbr> jftr: pleasantly surprised that the blog got it right. But then I try to always stick "GPL parts" or such in my tweets and there should be a readme I added to the source dumps.
[21:44] <tbr> yeah, the readme is still there: http://images.formeego.org/jolla/sources/readme.txt
[22:21] <jelkner> Hi all, I'm trying to install ubuntu touch on a nexus 4
[22:21] <jelkner> I can boot it into a screen with an ubuntu logo
[22:21] <jelkner> and the following menu choices:
[22:22] <jelkner> - reboot system now
[22:22] <jelkner> - wipe data/factory reset
[22:22] <jelkner> - backup and restore
[22:22] <jelkner> - advanced
[22:22] <jelkner> The wiki instructions aren't so good here.
[22:23] <jelkner> They say "Wait until the reboot is done"
[22:23] <jelkner> but don't tell me what to do from where I am now.
[22:24] <popey> what step in what instructions are you at?
[22:25] <jelkner> I got through step 3 under "Install Ubuntu"
[22:27] <jelkner> I think I got it.
[22:27] <jelkner> Nope
[22:28] <jelkner> I tried - wipe data/factory restore
[22:28] <jelkner> that was wrong :-(
[22:28] <jelkner> I'm back to Android
[22:30] <greyback_> jelkner: so you ran "ubuntu-device-flash --channel=devel --bootstrap" - could you share with us the output of the tool? (use http://pastebin.ubuntu.com/ please)
[22:33] <jelkner> greyback: just pasted
[22:33] <jelkner> It seemed to get stuck on the last step
[22:33] <jelkner> I never got a prompt back
[22:33] <jelkner> even after leaving it run over night
[22:34] <matv1> jelkner i believe there is another option at the bottom. its something like "go back" . I think that will finish the install
[22:34] <greyback_> jelkner: you need to give us the URL of the pastebin - so when you pasted, you went to a new page with your pasted content there - please share that URL so we can all see it
[22:34] <jelkner> http://pastebin.ubuntu.com/8144773/
[22:35] <greyback_> jelkner: ok, it detected your device correctly, and was downloading a correct image
[22:35] <greyback_> but it appears not have got much further.
[22:35] <jelkner> ok, it may have been my connect dropped
[22:35] <jelkner> Thanks
[22:35] <jelkner> I'm going to try again.
[22:35] <greyback_> jelkner: are you still at the recovery screen? (the ubuntu logo + menu options?)
[22:36] <greyback_> if so, just run the command again
[22:36] <jelkner> No, I messed up and selected wipe data/factory reset
[22:36] <jelkner> time to do it again :-(
[22:36] <greyback_> that's ok, you can get back to recovery just by holding both volume up/down keys with power down
[22:37] <greyback_> or typing "adb reboot bootloader"
[22:37] <greyback_> which should reboot your phone to a boot menu, from which you can use the volume up/down keys to find the "recovery mode" - press power to select
[22:37] <jelkner> That worked
[22:37] <jelkner> I have the ubuntu logo screen again
[22:38] <greyback_> cool, run that ubuntu-device-flash command, and it should hopefully work
[22:38] <jelkner> thanks!
[22:38] <greyback_> you're welcome
[22:44] <jelkner> greyback_: It finished downloading the image and rebooted the phone.
[22:44] <jelkner> but that is where i was before
[22:45] <jelkner> oh wait
[22:45] <jelkner> it's going further this time
[22:45] <jelkner> yea, ubuntu touch! ;-)
[22:45] <jelkner> cool
[22:45] <greyback_> jelkner: great :)
[22:45] <jelkner> thanks again!