[00:44] new touch OS coming 10/17/2013 | http://askubuntu.com/q/354617 [00:45] What kind of usable state it will be in... that's another matter entirely. === chihchun_afk is now known as chihchun === Namidairo`bnc is now known as Namidairo === anders3408 is now known as anders3408|afk === ryukafalz_ is now known as ryukafalz === Namidairo is now known as Namidairo`bnc [03:56] why would phablet-bootstrap delete android AOSP files I downloaded? === Namidairo`bnc is now known as Namidairo [04:21] OrokuSaki: hello === Namidairo is now known as Namidairo`bnc === Namidairo`bnc is now known as Namidairo [04:40] Is there a way to restore the TP to one partition without resorting to Doctor-ing? === chihchun is now known as chihchun_afk === cul- is now known as cul === chihchun_afk is now known as chihchun === joely is now known as Guest17487 === deathcrawler is now known as LockeAnarchist [06:34] good morning === alan_ is now known as Guest52790 [07:21] hello!, anyone knows when will be disponible the desktop part of ubuntu via HDMI? [07:31] Guest31817, probably 14.04, but more likely 14.10 [07:36] Laney: hi! Thanks for fixing the libexec bug in signon-ui [07:37] Laney: can you please also assign this to yourself and resolve it as approriate? https://bugs.launchpad.net/ubuntu/+source/signon-ui/+bug/1235337 [07:37] Ubuntu bug 1235337 in signon-ui (Ubuntu) "signon-ui ships files in a wrong directory" [High,New] [08:00] Morning === fmasi_afk is now known as fmasi [08:04] mardy: hey, seems Fix Committed/Released to me (not sure if it's uploaded) [08:12] jodh: hey! [08:13] jodh: there's a pretty serious bug logged by ogra_ on touch images: upstart eats memory like crazy; he didn't spot anything piling up in the list of apps, or crazy log files, so would be worth your investigation I think [08:13] ogra_: what's the bug id? [08:13] bug 1235649 [08:13] bug 1235649 in upstart (Ubuntu Saucy) "session upstart leaks massive amounts of memory on Ubuntu Touch" [Critical,Confirmed] https://launchpad.net/bugs/1235649 [08:44] Good morning all; happy Habitat Day! :-D === psivaa-afk is now known as psivaa [09:19] dbarth: would you think someone could help debug the issue Robert was seeing in https://bugs.launchpad.net/ubuntu/+source/cordova-ubuntu-tests/+bug/1235393 ? [09:19] Ubuntu bug 1235393 in cordova-ubuntu-tests (Ubuntu) "autopilot tests crash halfway through." [Undecided,New] [09:19] dbarth: rather than him doing the debug thing etc. [09:23] lool: looking [09:24] lool: yeah [09:24] lool: i need to merge in his packaging change, and then update the test suite to only test the supported apis anyway === nerochiaro_ is now known as nerochiaro [09:24] lool: but feels like an installation problem; anyway, mazim and i are on it === ritz is now known as ritz|away === oSoMoN_ is now known as oSoMoN [09:36] anyone can point me in the right direction on how to enable MIR in current phone builds ? [09:38] nerochiaro, touch /home/phablet/.display-mir ... reboot [09:39] ogra_: fyi - cpu spinner: bug 1236247. [09:39] bug 1236247 in touch-preview-images "brcm_patchram_plus runs at 100% CPU on nexus 7 (grouper) on build #82." [Undecided,New] https://launchpad.net/bugs/1236247 [09:39] jodh, thats one for cyphermox [09:39] ogra_: ack. === vrruiz_ is now known as rvr [10:01] Morning all [10:05] dbarth: ok === hikiko is now known as hikiko|lunch [10:23] seb128, let's talk about bug 1233682 [10:23] bug 1233682 in ubuntu-system-settings (Ubuntu) "Updates panel should not say Ubuntu Phone" [High,New] https://launchpad.net/bugs/1233682 [10:24] seb128, is the phone image "Ubuntu 13.10" in any sense? [10:26] mpt, we are going to have a v1 release for 13.10, and it's the same base OS/built from the Ubuntu archive [10:26] mpt, so yes, it's just a very different image than the desktop one [10:28] seb128, so if it's "v1", what is it "v1" of? :-) [10:28] mpt: we have to updaters now should be called application updater and the other system or something? Also do you know if there is a design to allow for auto updates with the application updater? [10:28] We could have a separate build number, that's no problem [10:28] mpt: official marketing will be "Ubuntu for Phones" [10:28] mpt, we call it v1, let's say it's a phone image built from the ubuntu 13.10 archive [10:28] mpt: so i guess "Ubuntu for Phones v1 (rev. 75)" or some such. [10:29] So no 13.10 anywhere? [10:29] mpt: i don't know, I would have thought it would be 13.10 none-the-less. [10:29] mpt: but do mind that very shortly after 13.10 (e.g. within 1-3 months) we will roll over all phones to the next development release (T-series) [10:30] mpt: thus it will be a very "short" support release. (Little Term Support) [10:30] (phones only that is) [10:31] So the one based on 14.04 won't be an LTS [10:32] mpt: 14.04 LTS status for products hasn't been decided yet. We will know that once we get there. [10:33] mpt: i assume phone will go LTS once we ship it pre-installed on devices. [10:33] which may or may not co-inside with 14.04 release date on desktop/server. [10:33] My only point in asking about LTS would be to tell whether the Y.MM version number was relevant at all to the phone image [10:35] mpt: the points that are relevant on the phone is: what channel and what image # one has installed. Cause in November we will have: stable, testing, development channels which can have same or different image # [10:36] mpt: stgraber/barry from system image updater can tell you actual names of channels, and image formats. [10:37] mpt: cause unlike desktop/server one will not be able to selectively upgrade, and only choose which channel of updates to subscribe to. [10:41] xnox, do you have a reference for the "Ubuntu for Phones" branding? [10:41] mpt: informal quotation [10:43] mpt: you have webteam in the office who are preparing website updates around you ;-) [10:48] ogra_: bug 1236292 # seen that on maguro? [10:48] bug 1236292 in indicator-sound (Ubuntu) "Using volume buttons on phone triggers spurious popup" [Undecided,New] https://launchpad.net/bugs/1236292 [10:50] popey: ogra_: confirmed over the weekend you get a popup saying indicator sound [10:50] will look at 83 when it has finished flashing [10:54] popey, ogra_ : http://ubuntuone.com/2vEr9fbeFbErYJrNrn5hy5 [10:54] davmor2: ta === chihchun is now known as chihchun_afk === hikiko|lunch is now known as hikiko === chihchun_afk is now known as chihchun [11:13] seb128, xnox: So where does the "v1" come from? What determines when it changes to 1.1 or 2.0? [11:14] popey, ogra_ am I mistaken or should the new image be on mir now, or did it get postponed? [11:14] probably tonight [11:14] bug 1235649 [11:14] bug 1235649 in upstart (Ubuntu Saucy) "session upstart leaks massive amounts of memory on Ubuntu Touch" [Critical,Confirmed] https://launchpad.net/bugs/1235649 [11:14] and there are a few test issues still i think [11:15] mpt: v1 was widely mentioned and used in the PRD spreadsheet w.r.t. which features go into first public release aka "v1" vs "later" [11:15] ogra_: ah thanks, that might explain why my maguro just stops working after a while then [11:15] xnox, I mean in the code. [11:15] mpt: but no idea if that's purely internal planning. [11:15] davmor2, yeah [11:15] mpt: none, as far as I know. === MacSlow is now known as MacSlow|lunch [11:15] davmor2, i think jodh and jibel are on it [11:17] seb128, so how about "Ubuntu 13.10 (r79)"? [11:17] mpt: pragramatically we ship os-release and lsb-release files that define the installed machine as "Ubuntu", code name "Saucy Salamander", version "13.10", human name "Ubuntu 13.10" [11:18] mpt: which is the same across all types of Ubuntu installation. [11:18] xnox, well, you would rather want the build stamp here too i guess [11:19] which lives in /var/log/installer/media-info [11:19] but that wont help on touch, wheer you also want the system-image number [11:20] Is the system-image number the one that's currently 75 or so? [11:20] Or is that something else entirely? [11:21] well, 82 but yes [11:21] root@ubuntu-phablet:/# system-image-cli -i [11:21] current build number: 83 [11:21] device name: maguro [11:21] channel: saucy-proposed [11:21] last update: 2013-10-06 12:08:27 [11:21] version version: 83 [11:21] version ubuntu: 20131005 [11:21] Error: Ubuntu bug 20131005 could not be found [11:21] version device: 20131003.2 [11:22] silly bot :P [11:22] i assume you would like some of this output in the UI [11:22] ogra_: no, we do not want media-info, as that's only original installation media and is optional. I know it's updated on RO/system-image updates, but it isn't on desktop/servers. [11:23] xnox, it isnt updated [11:23] (on touch) [11:23] ogra_: isn't that file part of the read-only image?! [11:23] the system-image info is, media-info always stays the same [11:23] ogra_: interesting. [11:23] that gives you the info from which initial rootfs you installed [11:24] (same as for d-i) [11:24] ogra_: so yeah, we don't care about media-info, as that's the original installation media, which may not be what is _currently_ running on the device. [11:24] right [11:24] ogra_: but very nice semantics, I like how the meaning was preserved =) [11:24] you want the system-image info [11:24] mpt, that works for me, it means the version is going to change with every bug fix update rolled out, but that's ok [11:25] root@ubuntu-phablet:/# grep version_detail /etc/system-image/channel.ini [11:25] version_detail: ubuntu=20131005,device=20131003.2,version=83 [11:25] that is where system-image-cli gets its info from [11:25] seb128, that's what it's supposed to do ... So someone can refer to this screen in saying "Problem X occurred in r84 but not in r83" [11:26] mpt, ok, that seems fine to me then [11:26] (ubuntu means the rootfs, device means the android build version, version means system-image ID) [11:28] tvoss_, can you take a look at bug 1235419 ? i wanted to wait for your input before unseeding [11:28] bug 1235419 in ubuntu-touch-meta (Ubuntu) "seed should not include ubuntu-location-service-examples" [Medium,Confirmed] https://launchpad.net/bugs/1235419 [11:28] ogra_, hey there. Looking [11:29] ogra_, I need to fix the packaging then ... [11:29] go ahead then :) [11:29] ogra_, I will find time to look into it tomorrow my morning [11:29] ogra_: examples should typically go into "sdk" package, as it's mostly interesting for developers, and not be seeded on the rest (sdk-libs, sdk-libs-dev, touch) [11:29] ogra_, just to give you an eta [11:29] k [11:29] xnox, well, its not clear its actually an example :) [11:30] ogra_: ah =) [11:30] examples shouldnt ship upstart jobs either :) [11:30] seb128, xnox, ogra_: Okay, spec updated. [11:30] mpt, thanks [11:31] looks good [11:35] mpt: I still think we need to list the mobile phone number for the device on that page [11:38] ogra_, popey: it's a side effect of the notification being added back for desktop when you wheelscroll over the indicator icon, Lars is looking at disabling that on the phone profile, that should fix it [11:39] seb128: great! [11:39] I knew you'd know, but decided not to disturb you directly ㋛ [11:39] ;-) [11:43] hi everybody. It's a know bug that with the build marked as current the wifi scan doesn't work ? [11:43] on nexus 4 [11:43] synny: what build id is this? system-image-cli -i [11:43] should work from the indicator [11:44] works here [11:44] the latest build on the ftp. Actually i'm on android [11:44] oh ok. I'll try to reinstall [11:44] how are you installing? [11:44] with multirom [11:45] what image are you downloading? [11:45] http://cdimage.ubuntu.com/ubuntu-touch/daily-preinstalled/current/ [11:45] ok [11:46] hi === fmasi is now known as fmasi_afk [11:46] @ogra what do you mean by from the indicator ? [11:46] synny, from the panel [11:46] can you port a device to Ubuntu touch even if it has no cm ROM? [11:47] in system settings ? [11:47] I have access to bottom.img, so on so forth [11:47] synny: no, drag down from top right corner [11:47] synny, from the top panel [11:47] over the wifi one [11:48] sorry I meant boot.img [11:48] hum stange, when I've tested it could'nt drag the wifi symbol, there was only the location ... [11:48] linux_unix-10, well, you definitely need the full source code for the android bit [11:48] I try to reinstall it so [11:49] MacSlow|lunch: Hey, how far did you get on the Mir input issues? [11:49] lool, Saviq beat me to it [11:50] lool, but we've discovered a bug in unity-mir [11:50] lool, but there's an issue with InputFilterArea itself, which is used to solve this, that needs to be sorted out first... [11:50] lool, that we need to tackle for this to get fixed [11:50] that ↑↑ [11:50] another issue too, I've delete the pin lock from security menu in android but I wasn't able to connect to cellular network and make call ... It's the right method that I've done ? [11:51] Saviq: Ok; so I guess I should prioritize landing the ubuntu-mir stuff then [11:51] lool, yeah... and afaik Gerry is working on that InputFilterArea issue [11:51] Saviq, did you check unity-mir trunk ? there is a bunch of stuff not landed yet [11:51] ogra_, yeah, unrelated I'm afraid [11:51] k [11:51] ogra_: there isn't much not landed [11:51] just the bring to front stuff I think [11:52] ok [11:52] MacSlow|lunch: Ok; thanks for the update [11:52] i just remembered there was something so i thought i should mention it [11:52] can you decompile the kernel and binaries? [11:52] Saviq: Do we know how many different issues we're actually looking at input-wise? [11:52] MacSlow|lunch, Gerry is on QtDevDays starting today, I'll get an update, but probably someone else will need to take over [11:52] it seemed they could possibly be related [11:52] lool, two, unrelated [11:52] Saviq, doh... right... forgot that [11:52] does anyone know how to deal with the following error: /usr/bin/system-settings: error while loading shared libraries: libSystemSettings.so.1: cannot open shared object file: No such file or directory [11:52] lool, https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1233245 [11:52] Ubuntu bug 1233245 in unity-mir "[mir] key events not working through input devices" [Undecided,In progress] [11:52] lool, https://bugs.launchpad.net/unity-mir/+bug/1235383 [11:52] Ubuntu bug 1235383 in unity-mir "InputFilterArea not always calculating geometry with respect to scene" [Critical,Confirmed] [11:53] thanks [11:53] linux_unix-10: you can't "port" android -> ubuntu, like you "port" android -> android. If you don't have source, then give up [11:53] lool, well, that one https://bugs.launchpad.net/unity-mir/+bug/1233245 is most probably related [11:53] it's the same one as the first one [11:53] lool, or well, the same, as the first one [11:54] lool, hmm I might've not filed a separate one then ;) [11:55] that's ok, if it's the same bug :-) [11:55] Saviq: I was looking at https://bugs.launchpad.net/ubuntu/+source/mir/+bug/1234903 and https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1233245 [11:55] Ubuntu bug 1234903 in telephony-service (Ubuntu Saucy) "[mir-only] On incoming calls the greeter remains and dialer-app is not started" [Critical,In progress] [11:55] Ubuntu bug 1233245 in unity-mir "[mir] key events not working through input devices" [Undecided,In progress] [11:56] Saviq, lool: btw... regarding Volume Up/Down... with the latest image I see indicator-sound triggering a notification (probably a left-over confirmation notification from desktop NotifyOSD) [11:56] MacSlow|lunch: Yes; it's also a completely broken one [11:56] MacSlow|lunch: how do we fix this? [11:56] MacSlow|lunch, yeah, not supposed to be there at all [11:56] MacSlow|lunch, see bug #1236292, it's being fixed [11:56] bug 1236292 in indicator-sound (Ubuntu) "Using volume buttons on phone triggers spurious popup" [Undecided,Confirmed] https://launchpad.net/bugs/1236292 [11:56] Saviq, lool: there are no confirmation notifications on the Phone [11:56] MacSlow|lunch, yup [11:57] Saviq, MacSlow|lunch: when do we get sync notifications in unity8? ;-) [11:57] Saviq, lool: just remove it triggering any notification [11:57] seb128, they're not supposed to be there on touch at all [11:57] MacSlow|lunch: what package am I supposed to remove? [11:57] MacSlow|lunch, it's already being adressed, please don't put more people to dup work [11:57] seb128, there's not use/Design for those [11:57] ah [11:57] lool, re: phone app not starting, will have to investigate - didn't see that one [11:57] seb128 has it alraedy [11:58] Saviq, what's the mechanism to have e.g sound level bars on screen feedback? [11:58] Saviq: I dont know whether it's related [11:58] lool, likely not, and I can see boiko has something there [11:58] Saviq, any other phone OS tell you what's the value so you can have a clue where you are [11:58] lool, no... indicator-sound just needs to be patched to not trigger a notification at all [11:58] seb128, it's there in the panel [11:58] MacSlow|lunch, IT'S ALREADY DONE [11:58] seb128, oh... ok :) sorry [11:58] seb128, not supposed to do anything else atm [11:58] Saviq, it's not really easy to read on suck a small icon [11:59] seb128, nothing else planned currently [11:59] Saviq, ok, shame [11:59] ogra_: so the upstart thing is broadcom patchram? [12:00] lool, ? [12:00] ogra_: I thought LP #1236247 was what James and you discussed [12:00] lool, i dont think they are related [12:00] Launchpad bug 1236247 in bluetooth-touch (Ubuntu) "brcm_patchram_plus runs at 100% CPU on nexus 7 (grouper) on build #82." [Undecided,New] https://launchpad.net/bugs/1236247 [12:00] ogra_: Ok; I didn't think so either [12:00] ogra_: which is why I was curious [12:00] james just pointed it out [12:01] jodh: did you reproduce the upstart issue ogra_ filed? [12:01] at least i didnt understand jodh to mean it would be related [12:05] ogra_: ok, was just the only traffic I saw on this [12:05] well, there was some traffic on the bug [12:05] jibel is collecting an strace [12:06] ogra_, I attached it a minute ago [12:06] jodh, ^ [12:06] :) [12:06] hey guys, I swipped down from the top panel and in network part I've only flight mode and cellular settings... do you think that myissue is related to multirom ? [12:07] synny, could well be, or to the rw image we dont ose them anymore [12:07] *use [12:07] (and we also dont test them anymore, so there might be issues that dont show up on ro images) [12:09] ok, I will flash the zip without multirom. If I flash these saucy-preinstalled-touch-armhf.zip and saucy-preinstalled-touch-armel+mako.zip does it will wipe my sdcard ? [12:10] why you don't test the image anymore ? [12:10] we only test the system-image [12:11] which has a completely different filesystem setup to the zips from cdimage [12:11] ah ok [12:12] so if I flash the system-image, I guess that this will erase my internal storage ? [12:13] yes === psivaa is now known as psivaa-afk [12:14] Okay, thanks for your help ! Have a nice day ;) === MacSlow|lunch is now known as MacSlow [12:15] jibel, ogra_, jodh: seems to be doing some dbus traffic with powerd [12:16] or rather, triggering some system events related to power [12:16] 1592 sendmsg(21, {msg_name(0)=NULL, msg_iov(2)=[{"l\4\1\1\256\0\0\0b\5\0\0a\0\0\0\1\1o\0\23\0\0\0/com/ubu"..., 120}, {"\26\0\0\0:sys:cpu-device-online\0\0\216\0\0\0"..., 174}], msg_controllen=0, msg_flags=0}, MSG_NOSIGNAL) = 294 [12:16] 1592 sendmsg(23, {msg_name(0)=NULL, msg_iov(2)=[{"l\4\1\1\31\3\0\0\310\0\0\0a\0\0\0\1\1o\0\23\0\0\0/com/ubu"..., 120}, {" \0\0\0:sys:power_supply-device-cha"..., 793}], msg_controllen=0, msg_flags=0}, MSG_NOSIGNAL) = -1 EAGAIN (Resource temporarily unavailable) [12:16] I wonder if it's basically the device waking up and sleeping super often [12:16] and that causing a lot of upstart system events [12:17] onTryRegister [12:17] thats what i get in my dbus.log [12:18] once or twice a second [12:18] no idea where it comes from :/ [12:18] popey, hey, is the rssreader supposed to be called Shorts only in it's friendly name? [12:18] sergiusens: shorts is technically one view in the rss reader [12:18] ogra@anubis:~/Devel/packages/powerd-0.13+13.10.20130926$ grep -r onTryRegister * [12:18] ogra@anubis:~/Devel/packages/powerd-0.13+13.10.20130926$ [12:19] not a powerd function at least [12:19] popey, well the app is called shorts in the lens; is the plan for it to be multiple apps? [12:19] no [12:19] it's one app [12:19] I'd keep it as "Shorts" [12:20] popey, something like com.ubuntu.rssreader_shorts_x.x ? [12:20] lool, the kernl notifies about power status once a minute === alan_g is now known as alan_g|lunch [12:20] sergiusens: if that matches the fomat of other apps, sure [12:20] (in dmesg that is) [12:20] besides source code, is it a requirement to have a cm 10.1 ROM running successfully or not? [12:21] popey, all other apps have pkg name ~= appname; this one is the only one a bit different [12:21] sergiusens: the package name is largely a "technical name" though isn't it? [12:22] sergiusens: or are you just after consistency? [12:22] ogra_: telepathy-ofono [12:22] popey, it affects where you can write files to too (confinement follows package name) [12:22] ah [12:22] qDebug() << "onTryRegister"; [12:22] in connection.cpp [12:23] aha [12:23] sergiusens: so lets be consistent and call it shorts [12:23] so why is it printing debug messages in the first place ? [12:23] ogra_: it's printing debug in every function it's entering there [12:23] can you make a flipped image with only binaries? [12:23] right [12:23] that one is probably the poll to check for data coming up or something [12:23] or sim card, but I'd think data [12:24] ogra_: I'm not too worried about this line every 5 seconds; not nice, but wont generate much logs [12:24] it pollutes a bit [12:24] but it's not in itself the source of the bug [12:24] yeah [12:25] can you port Ubuntu touch with only binaries? [12:25] popey, ack [12:25] linux_unix-10, no [12:25] linux_unix-10, you need the srouce of the android OS plus the binary drivers it uses [12:26] can you decompile the binaries? [12:26] it doesnt need to be cyanogenmod (note that porting will be a lot harder without CM though( [12:26] no [12:27] can I decompile and compare to aosp to make changes? [12:27] no [12:27] you cant decompile binaries [12:28] what can I do to get source code? [12:28] ask the vendor of your phone, they have to give it to you [12:29] good thing that the device's android is very close to aosp [12:29] it uses mostly vanilla configurations with only a few additions === _salem is now known as salem_ [12:31] lool, ogra_ I think I saw a lot of upower battery stat events (that and nm) [12:31] can I use source code from a device with identical hardware? (device is just rebranded) [12:31] sergiusens, where ? [12:31] ogra_, on the system bus [12:32] linux_unix-10, try it, if you manage to build a booting image for your device from that source that would be a good step forward [12:32] sergiusens, well, our bug makes the user session init eat all ram ... not sure if the system bus can cause this [12:33] i would expect fallout for this on the system side insterad [12:33] *instead [12:33] the partitioning of the two devices are different, is this a problem? [12:33] you will likely need to adjust it in the source code [12:33] ogra_, saw the bug; probably not related; I just chimed in on 'waking up often; [12:34] yeah, its definitely another one to look at [12:35] ogra_ there are more identical devices that were just rebranded [12:35] maybe I can use some source code from them when available [12:36] alecu: Re: #1235784, I'd like to gather as much as possible debug information right now as to be able to reflash my phone if I need to [12:36] but enough so that it can be resolved [12:37] Hey any way yet to enable 3G browsing on a Nexus 4? [12:37] one of the source codes for one device has code for the same partition as my device, can I merge it with the original device's code to make it compatible? === psivaa-afk is now known as psivaa [12:39] lool: what's the image # where this happens? [12:43] alecu: #83 [12:43] alecu: also see #ubuntu-ci-eng backlog [12:43] dobey: Let's perhaps move the debugging here [12:43] * alecu looks [12:43] oh ok [12:44] lool: what about signing into https://myapps.developer.ubuntu.com/dev/ ? [12:44] this is very much sounding like the server problem we found at the end of last week [12:44] dobey: I think that hole has already been fixed server side [12:44] alecu: has it been deployed to production? or only staging? [12:45] dobey: still the same [12:45] I wasn't signed in, clicked sign in from desktop, didn't get prompted for 2nd factor [12:45] still nothing happening on a different click on the phone [12:45] lool: unless you have 2fa set to "always" on that account, you shouldn't get prompted for it there (or on the software-center.ubuntu.com page either) [12:46] lool: can you paste unity-scope-click.log and ubuntu-download-manager.log from .cache? [12:46] lool: and you're definitely logging into those web pages with the samea ccount as you signed into on the device? [12:47] dobey: I only have one account [12:47] albeit I can't see the email address in the list of configured accounts [12:48] http://paste.ubuntu.com/6204781/ click-scope.log [12:48] I dont see the download-manager log [12:49] lool: perhaps .cache/ubuntu-download-manager/ubuntu-download-manager.log ? [12:49] lool: it's ~/.cache/ubuntu-download-manager/ubuntu-download-manager/ubuntu-download-manager.log i think [12:49] slangasek: nothing in fuser -vm / 2>&1 | grep F; might be android side? [12:50] it's actually http://paste.ubuntu.com/6204794/ [12:50] /home/phablet/.cache/ubuntu-download-manager/ubuntu-download-manager/ubuntu-download-manager.log [12:50] crazy [12:52] the unity-scope-click.log looks either incomplete, or like it's hanging on getting the credentials [12:53] lool: if you kill system-settings then go back to the accounts page, does it show your e-mail address for the u1 account? [12:54] dobey: no [12:54] it lists one account, no email [12:55] lool: remove the account, and re-add it. [12:55] hello [12:55] dobey: pretty sure that will fix the bug though :-) [12:55] I was wondering what will be the video/audio app on Ubuntu Touch ? [12:56] lool: how did you create the account? [12:56] dobey: how is that empty account being created? [12:56] Is it plan to developp something related to WebRTC ? [12:56] dobey: as usual, prompted to go to settings to add account, added account with 2nd factor [12:56] as "major" video/audio app won't work on Ubuntu Touch [12:57] lool: I think there was a bug where the account ended up being created empty, when the user used the "Back" button from the toolbar instead of "cancel" in the u1 dialog [12:58] copied some video onto my device.. should I expect it to show up in the video lens yet? [12:58] dobey: is there a way to list the token in lool's UOA entry? [12:59] alecu: yeah, that sounds more like it [12:59] alecu: on the device, i think it's stored in an sqlite db [12:59] alecu: was this actually fixed? [13:00] did you use the back button? [13:00] lool: I don't. let me ask ralsina or mmcc (when he starts) [13:01] alecu: the back fix? it's in trunk and in the latest release but it's not in the image yet [13:01] popey, I saw them show up in the home lens [13:01] popey, don't recall video though [13:03] lool, alecu: the back button issue is fixed, yes [13:04] dobey: do you have a reference? [13:04] bzr revision or such [13:04] lool, alecu: in ubuntuone-credentials 13.10-0ubuntu1 [13:04] ralsina: ^^ did you add that to the landing requests page? [13:04] from one hour ago [13:05] dobey: Hmm what landing slot was this? [13:05] dobey: not yet [13:05] lool: I was going to ask for it to be in the general click stack landing you mentioned earlier [13:05] ralsina: yes but note that this package is not under CI, so it just went straight through proposed and into archive [13:06] lool: yes, we do manual testing on it, will get it into CI after the release. Too much process breakage at this point :-/ [13:07] ralsina: I could have arranged to stage it in proposed though [13:07] lool: didn't know that, sorry. Let's do it for the next one [13:07] well, there shouldn't be a next one :) [13:08] (if there is a next one before release, which is not certain) [13:08]