=== _salem is now known as salem_ === salem_ is now known as _salem [01:46] knome: are you near your computer? === chihchun_afk is now known as chihchun [04:22] Good morning [04:36] pitti: good morning, hope you had a good hew hours sleep. [04:36] phillw: indeed, thanks! how are you? [04:39] pitti: awaiting the rush of bug 1220165 being re-spun. That's the only error I'm seeing for installer [04:39] bug 1220165 in parted (Ubuntu) "Error informing the kernel about modificatons" [Critical,Fix released] https://launchpad.net/bugs/1220165 [04:41] pitti: there is https://launchpad.net/bugs/1194898 but, heck; that's only been there since June LP [04:41] Ubuntu bug 1194898 in ubiquity (Ubuntu) "resize tool does not show partition numerical sizes" [High,Confirmed] [04:41] :P [05:01] pitti: could i ask a massive favour? As https://launchpad.net/bugs/1220165 is marked fixed released, when can it it be spun into the ISOs'? [05:01] Ubuntu bug 1220165 in parted (Ubuntu) "Error informing the kernel about modificatons" [Critical,Fix released] [05:01] phillw: I would think infinity is on that; but I suggest to ask in #ubuntu-release, I'm not involved with the release process/ISO spinning [05:03] good morning [05:03] bonjour jibel, ça va ? [05:04] bonjour pitti, ça va et toi? comment était le Taekwondo? [05:05] pitti: I', [05:05] jibel: c'était bien, merci; not too hard yesterday, we were practicing forms a lot [05:06] I'm not allowed on -release area; ces't la vie. [05:23] phillw, Are you actually not allowed there anymore? [05:24] Noskcaj: per my breaking of the CoC; no, I am not. You may ask on there when it is expected for the re-spin correct https://launchpad.net/bugs/1220165 will be available :) [05:24] Ubuntu bug 1220165 in parted (Ubuntu) "Error informing the kernel about modificatons" [Critical,Fix released] [05:29] Noskcaj: I've had a hard enough time for being told the bug was not "entered into bugs that would have to be solved for saucy list". I'd have got banned all over again over that :( [05:45] infinity: <> === chihchun is now known as chihchun_afk === chihchun_afk is now known as chihchun [06:50] elfy: a very gentle nudge.... are you in awake mode? [06:51] just [06:51] elfy: do you need more coffee before I ask about a bug? [06:52] more tea possibly - but ask away and if I can answer I will :p [06:55] elfy: as every one knows, I'm persona non gratis on the -release area. Would you be so kind as to ask as to when it is expected for the re-spin correct https://launchpad.net/bugs/1220165 will be available :) it does affect all teams just so I can let the testers know. there has been no notifications of respins on the the mailing lists :/ c'est la vie. [06:55] Ubuntu bug 1220165 in parted (Ubuntu) "Error informing the kernel about modificatons" [Critical,Fix released] [07:02] phillw: I asked - but if I don't get a reply in the next 40 minutes it'll be this afternoon before I see it [07:03] elfy: that will be i [07:03] finw [07:03] *fine* [07:04] phillw: can't you request a rebuild once the fix is released? [07:19] elfy: as there is no notification by email / etherpad of fixes being there; I cannot ask for a respin :D [07:22] phillw: I get mails from bugs I'm subscribed too - tells me when fix released [07:25] elfy: so do I; but tgat is not the same as in available for a build:) [07:26] well - the likelihood of me noticing in -release is slim - just so you know :) [07:50] phillw, i think you'll find the whole of the release team was up pretty late (my time) so i suspect there is some sleeping involved [07:51] phillw, but i am keen to test that same specific bug, so will be watching for the respins [07:56] apw: as there no announcements made on the ML's as to why re-spins are being made, us testers are just mushrooms :D [07:57] phillw, in my experience the #ubuntu-release channel is the only place the whys and wherefores are announced [08:05] apw: they used to have an ether pad : [08:05] :) [08:14] morning all [09:09] morning all [09:23] phillw: A respin will be happening for the partition bug soon, yes. [09:31] phillw, i'm here. === vrruiz_ is now known as rvr [10:00] Morning all === chihchun is now known as chihchun_afk [11:50] gema, I think bug 1234185 is fixed. could you confirm? [11:50] bug 1234185 in signon-ui (Ubuntu) "Login to some online accounts unavailable from settings" [High,Confirmed] https://launchpad.net/bugs/1234185 [11:53] jibel: confirmed, it is fixed [12:44] ubuntu-qa, or anyone, for that matter: is there an easy way to check if the phone has a gps location? [12:45] nuclearbob: maps.google.com :) [12:45] nuclearbob: I think jfunk had a piece of code that I am trying to track down it might be on the wiki so I'll look there [12:46] davmor2: okay, thanks. That wasn't working the last time I tried it on maguro, so I'll try again today [12:47] nuclearbob: it kept switching back off from the indicator when I tried yesterday [12:47] nuclearbob, yes I have just done some location testing. Beware it can take up to 15 mins to get a GPS fix from cold start... [12:47] rhuddie: ouch [12:48] that is ridiculous [12:48] rhuddie: good to know. I'll try it when I'm outside [12:51] rhuddie: how did you test by the way/ [12:51] ? even [12:51] Assisted GPS doesn't seem to be supported yet, that speeds things up a lot [12:51] I tested using google maps [12:51] to get a location fix [12:52] I'll try that again, last time it told me it couldn't get a fix [12:52] yeah, you have to be patient :) [12:52] rhuddie: now you think I have patients :D [12:53] make sure the GPS settings are enabled in the location notifiers too === _salem is now known as salem_ [12:54] all right [12:55] fginther, jibel: I'd appreciate some ideas how to set up the phonesim tests/dependencies; I followed up in https://code.launchpad.net/~pitti/messaging-app/phonesim-tests/+merge/191121 [12:56] there's some conflict between the "tests with phonesim" and "tests with real SIM" packages, but I'm not sure how much the latter actually work [13:00] pitti, the maguro had the same failure as otto, "The following packages have unmet dependencies: [13:00] messaging-app-connected-autopilot : Conflicts: ofono-phonesim-autostart but 1.19-0ubuntu4 is to be installed" [13:00] fginther: ok, expected; I don't think we can sensibly run both tests in the same environment without root privileges to control phonesim [13:00] pitti, both test runners attempt to install all debs produced by the build [13:01] fginther: that's what I asked about in my mail the other day, how to activate phonesim automatically (and "package with upstart job" was proposed) [13:01] fginther: do the -connected tests for messaging/dialer actually do something useful? [13:02] they don't have much code, and require manual configuration [13:02] pitti, I honestly don't know what's in there. Is there harm in having them both installed? [13:02] pitti, but just running the phonesim tests? [13:03] fginther: no harm, but the phone simulator will "shadow" any real SIM [13:04] fginther: as I said, the connected tests don't really do anything useful unless our CI machines all have the config file in $HOME; do they? [13:04] pitti, no they are not setup to run those [13:04] fginther: ok; I'll push dropping the Conflicts:, and see how far that gets then [13:04] pitti, so the harm comes when we do want to run the connected tests and the phonesim is running [13:04] fginther: right [13:05] fginther: that's why I started with adding the conflicts:, to avoid confusion [13:05] got it [13:05] fginther: it'd be easier if the test itself could turn on/off phonesim, but it requires root [13:05] fginther: oh wait, I could make them spit out a big error message if phonesim is running [13:06] that's less intrusive than the conflicts: [13:06] pitti, that would be good. I'm sure we'll forget this converstation inside 2 months [13:06] at least I will [13:07] pitti, I think to solve this problem, we need to support some selective package installation inside the test runner, instead of just blindly installing them all [13:08] fginther: at least once we actually do "real" connected tests in CI [13:08] pitti, right [13:08] fginther: but with phonesim we actually get quite far [13:09] pitti, and I think for MPs, that may be all the further we ever get [13:09] so my gut feeling is we don't really need to actually run real sim/hw tests for every MP, as everything on top of ofono (the apps, telephony-service, telepathy stack, etc.) doesn't really carea about specific hw [13:09] pitti, agreed [13:09] fginther: ok, thanks; I'll drop the conflict, add the warning/skip for connected tests [13:09] fginther: just pushing a new commit will re-trigger tests, right? [13:10] pitti, yes [13:10] fginther: great, thanks for your time! [13:10] pitti, you're welcome [13:10] $ autopilot run messaging_app_connected [13:11] fun, that immediately crashes without proper configuration [13:26] fginther: how come that the CI tests never complained about the completely broken messaging_app_connected tests then? [13:27] fginther: (they always immediately crash unless you have a valid ~/.testnumbers.cfg) [13:27] psivaa: have you checked out ubuntu one account setup in ubiquity? I got it to work once yesterday, but it's failing for me again now [13:27] fginther: or more fundamentally, how does it determine which tests to run? is that in that big magic manually maintained cu2d list, or do they just run all autopilot tests they can find? [13:29] plars: hm? [13:29] xnox: it's just getting stuck there [13:29] xnox: after entering my login info [13:29] plars: =( it really shouldn't, anything in syslog? [13:29] pitti, it is in the big magical cupstream2distro-config file [13:30] plars: is that "personal" u1 accounts, or 2fa enabled one? [13:30] plars: it's working for me.. atleast the setup stage [13:30] pitti, it only runs one autopilot test suite [13:30] i have not used it after the installation though [13:30] xnox: it's 2fa [13:30] xnox: it worked for me once yesterday though - one difference is that I typed a wrong password first on this attempt [13:30] plars: that doesn't work, you should either get a warning message, or skip through to slideshow (and in the installed system, not working at all) [13:30] plars: hm. [13:30] debconffilter_done: ubi-ubuntoone (current: ubi-ubuntuone) [13:30] xnox: ^ is he last message in syslog [13:31] plars: can you paste all of it? [13:31] plars: one line is not helpful at all =) [13:31] plars: pastebinit or something. [13:31] xnox: I know, it's on another system so it was just something quick I could do... one moment [13:32] xnox: paste.ubuntu.com/6240550 [13:33] xnox: installer/debug.log: http://paste.ubuntu.com/6240552 [13:33] plars: is that stuck? as in didn't switch to slideshow / finish the install? [13:33] plars: from u1 plugin point of view it's all fine. [13:34] xnox: I'm still at the ubuntu one account screen with the spinner and the options "log in later" "back" Continue [13:34] fginther: ah, http://bazaar.launchpad.net/~cupstream2distro-maintainers/cupstream2distro-config/trunk/view/head:/stacks/saucy/phone.cfg has "messaging_app" for for messaging-app, not the -connected ones; I see [13:34] xnox: it doesn't seem to let me select any of them right now though [13:34] fginther: so that's fine, it should actually run the new phonesim tests now. /me eagerly awaits :) [13:38] plars: i tried entering a wrong password, it notified of that and then when i clicked login later the installation continues [13:41] plars: and i get the email/password error message in the syslog as well [13:44] psivaa: perhaps the difference was that I entered the right password after entering the wrong one once? [13:44] plars: ahh i dint try that, will do that now :) [13:51] plars: entering the right password after wrong one also works for me.. not sure if installation path etc makes any difference [13:57] psivaa: I'm hitting a lot of launchpad.net/bugs/864530 on both i386 and amd64 [13:58] bug 864530 [13:58] bug 864530 in indicator-datetime (Ubuntu) "indicator-datetime-service crashed with signal 5 in ffi_call_SYSV()" [Medium,Confirmed] https://launchpad.net/bugs/864530 [13:58] afternoon all [13:58] plars: i do too for every install but it does not affect any usage though [13:58] psivaa: yeah === psivaa is now known as psivaa-afk === psivaa-afk is now known as psivaa [15:07] good morning team. [15:08] elopio: hey dude [15:11] morning elopio [15:11] o/ [15:24] hi elopio [15:28] hello elopio [15:28] jibel, did you get back with DanChapman about setting up ubiquity? [15:28] I know it's a mad dash these past couple weeks [15:28] Hey balloons [15:28] balloons, no I couldn't do much on ubiquity sadly, phone takes all my time [15:29] no worries, I thought that might have been the case [15:33] balloons: seen reply to merge thing - did you note what I said in the e-mail? [15:34] elfy, about syncing the changes to the tracker? [15:34] yea [15:38] elfy, shouldn't be an issue to sync them as they are minor tweaks and bugfixes [15:38] however you are correct none of them are synced [15:39] I know they aren't - if it's ok to whack them through I'll do it as soon as I can if you want [15:39] I planned to sync them both right now actually ;-) [15:40] okey doke - I can forget all about it then [15:40] indeed, hehe.. thanks! [15:42] I'll follow up with any of the others needing the same change now we've got wording how we want for these ones I've been fiddling with [15:43] elfy, that would be wonderful. [15:44] balloons: consider it written on a scrap of paper in pencil then :p [15:44] elfy, hehe.. I know all about stuff like that [15:44] :) [15:46] hey balloons, jibel and elfy [15:47] hey DanChapman [15:47] hi DanChapman [16:03] hey DanChapman [16:25] elopio, Autopilot Working Group meeting on my calendar for today 20:30 UTC. I think we canceled last weeks hangout? You up for it today if thomi is? I think weekly meeting about AP is a good idea [16:26] elopio, I also bought a webcam and need to do a hangout to try it out :) So, I'll be live! [16:26] cgoldberg: I have never attended one, but I can, sure. [16:26] cgoldberg: oh, nice. So long without seeing you... :) [16:26] :) [16:27] ive grown a beard (by accident/lazyness) since the sprint [16:31] jeje, that's the same reason I have one. [16:45] cgoldberg, elopio: admit it, you realised my breakage power is contained in my beard and realised you needed one too, to be as good at breaking stuff ;) [16:55] davmor2: I won't admit it. I have a beard to survive the harsh Costa Rican winter. [16:55] elopio: What harsh Costa Rican winter? [16:56] elopio: let me guess it protects your chin from sunburn [16:57] elopio: :D> [16:58] davmor2, you have a proper beard.. like trimmed. I just forget to shave for a month and have scraggly hacker beard [16:58] cgoldberg: hahaha [16:59] jibel: are you the right person to ask about tests like https://jenkins.qa.ubuntu.com/job/autopilot-testrunner-otto-saucy/1185/console ? [16:59] it seems it ran: /var/local/autopilot/setup.log: I: Running messaging_app [16:59] and then no further test ("No test left to run") [17:00] but there's no output for that test, just https://jenkins.qa.ubuntu.com/job/autopilot-testrunner-otto-saucy/1185/artifact/results/autopilot/results/test_messaging_app.xml (which is all 0) [17:01] so, apparently the test was skipped, which is some bug; but what exactly is the failure here? [17:32] good evening. does this sound familiar to you: [17:33] on upgrade to saucy, the desktop uses the wrong keyboard layout. [17:34] temporary solution: switch to virtual console (ctrl+alt+f1) and back.... [17:38] pitti, well, that's odd. It's like there is no test in messaging_app [17:38] balloons ^ - any idea which package to check for existing known bugs? [17:40] dkessel, weird [17:40] hmm keyboard layout [17:41] fginther, would you know what's wrong with https://jenkins.qa.ubuntu.com/job/autopilot-testrunner-otto-saucy/1185/console ? [17:41] I just managed to lock an online account because of typing the password wrong three times in a row :/ [17:41] fginther, all the packages are installed but it's like autopilot doesn't find any test for testsuite messaging_app [17:42] dkessel, ouch [17:42] pitti, I suppose autopilot run messaging_app works locally? [17:42] dkessel, what does the layout settings say? [17:42] are they not what they are supposed to be? [17:43] jibel, autopilot starts, but appears to bail out almost immediately [17:43] dkessel, "De" - which is correct. But the layout is definately english after booting [17:44] dkessel, look in 'text entry' under system settings [17:44] look good? how about language and keyboard settings? [17:44] fginther, right, and it doesn't crash because it produces an xml file with 0 test run. like if messaging_app testsuite is empty [17:45] jibel, the MP didn't change the dir structure perhaps? [17:46] balloons, "language settings": hmmm it says language support is not installed completely... [17:47] balloons, i thought that only installs manuals and spell checking stuff [17:52] jibel, does phonesim run on x86? it looks like all the tests may have been skipped due to have_phonesim== False? [17:55] jibel, looks like ofonod started according to syslog, timestamps indicate this was done before autopilot ran [17:55] jibel: yes, that's how I develop it [18:03] dkessel, what about the keyboard? [18:03] dkessel, the settings say german... no english in the list [18:04] balloons, i mean... lol [18:04] I'm just curious what's going on? Are you saying everything works after you switch to a vterm? [18:05] balloons, yup. when the vterm login prompt shows, the keyboard layout is german [18:05] and after switching back to X, it stays [18:07] balloons, could the new indicator icon for the keyboard layout be influencing it? [18:07] dkessel, that's my thinking perhaps [18:07] does it say en? [18:08] balloons, it says "De" [18:08] all the time [18:09] keyboard layout? [18:09] and text entry input also de? [18:09] if so, then I think I've got enough understanding :-) [18:10] yup [18:18] want to file the bug then dkessel ? [18:18] let's see.. ubuntu-bug and which package [18:19] balloons, yes i'll do in a few minutes [18:20] dkessel, looking for existing bugs.. I'll pass along what I see [18:20] https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1231520 [18:20] Ubuntu bug 1231520 in ubiquity (Ubuntu) "Desktop image ignores installation language setting for locale" [Undecided,New] [18:22] balloons, hmmm. but i upgraded... from raring. no fresh installation here [18:22] dkessel, ahh, gotcha [18:22] balloons, and i guess the geographic location detected for me should be germany too [18:23] what does locale return for you dkessel ? [18:23] de_DE.UTF-8 balloons [18:23] yep, it all looks correct.. this is something sneaky [18:24] dkessel, I would file against ubuntu-control-center, but I feel like there is more [18:26] err gnome-control-center, my bad [18:26] * balloons checks this time [18:30] dkessel, more fun :-) what does /etc/default/keyboard look like? [18:32] http://paste.ubuntu.com/6241805/ [18:32] darn, also unexciting [18:33] looking in here https://bugs.launchpad.net/indicator-keyboard and https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/ shows me nothing simimlar [18:34] dkessel, one final question.. does the indicator allow you to select a different layout? [18:35] and if you say change it and swap it back does it fix everything> [18:39] balloons, yes, that works... [18:39] looking at the bugs for indicator-keyboard it really does look a bit messed up i must say.... [18:44] going to check behaviour after reboot again.... [18:47] balloons, after rebooting> back on english lazout [18:47] argh [18:47] sounds like you've got a nice bug report now [18:47] and yes, argh! [18:47] mention it was an upgrade not fresh install [18:49] balloons, k thanks [18:53] ty dkessel :-) [18:55] balloons, bug 1240198 :) [18:55] bug 1240198 in indicator-keyboard (Ubuntu) "wrong keyboard layout active after booting into desktop, after upgrade to saucy" [Undecided,New] https://launchpad.net/bugs/1240198 [18:56] balloons, Hi [18:56] Letozaf_, hello! [18:57] balloons, howzit ? [18:57] did you perchance experience dkessel's bug ^^? [18:57] hehe, good idea [18:57] Letozaf_, busy :-) How's about yourself? [18:57] balloons, fine [18:58] dkessel, I ask because Letozaf_ potentially might use a non-english keyboard/locale.. but maybe not :-) [18:58] I'm excitied for the release [18:58] balloons, for the keyboard, I have an Italian keyboard but I keep US English layout, so I do not know about the problem [18:58] Letozaf_, gotcha, thanks [18:58] meh :) well, let's see what happens with the bug... i gotta go, bye! [18:59] balloons, what about the rssreader app test ? has it got problems ? [18:59] Letozaf_, apparently so [18:59] I wasn't around yesterday [19:00] balloons, :( [19:00] balloons, yes I know it was an American holiday of some king [19:00] Letozaf_, well it's not the only one.. lots of stuff [19:00] sorry kind [19:00] balloons, yeah sure! [19:01] yes we must celebrate the re-discovery of north america by columbus :p [19:01] http://reports.qa.ubuntu.com/smokeng/saucy/touch_mir/mako/97:20131015:20131015/4730/ [19:01] rssreader; http://reports.qa.ubuntu.com/smokeng/saucy/touch_mir/mako/97:20131015:20131015/4730/ubuntu-rssreader-app-autopilot/ [19:02] balloons, suppose there is nothing I can do to help you guys out [19:03] balloons, I mean for solving the problems [19:03] balloons, for the failing tests [19:06] Letozaf_, you can certainly help out :-) [19:06] Any errors you see should be reproducable and fixable [19:06] you have a device after all! [19:06] :-p [19:07] did you see my note about how to run autopilot tests with click packages? [19:07] balloons, I read it but did not try it [19:07] balloons, I can try now :p [19:07] Letozaf_, got a minute and want to try? [19:07] ahh ok, perfect [19:07] balloons, sure [19:08] I'll walk you through it [19:08] balloons, ok [19:08] so make a folder to branch some tools into and to place a script [19:09] ok done [19:09] bzr branch lp:~sergiusens/+junk/click_ready [19:09] ok got it [19:10] Letozaf_, http://pastebin.com/rpqpLwBV [19:11] save that as a bash script.. then run it with the 3 args you see on top [19:11] so testclick.sh lp:ubuntu-rssreader-app com.ubuntu.rssreader rssreader_app I believe is the command for rssreader [19:12] morning [19:12] make sure your phone is plugged in [19:12] morning thomi [19:15] balloons, I get errors [19:15] balloons, just a second [19:15] Letozaf_, ok where at? [19:15] btw it's testclick.sh lp:ubuntu-rssreader-app com.ubuntu.rssreader ubuntu_rssreader_app [19:15] the tests are ubuntu_rssreader_app, not rssreader_app [19:15] I was close :-) [19:15] balloons, oh! let me try again :) [19:16] it runs for me after fixing that [19:17] balloons, I get ./testclick.sh: line 2: branch: command not found [19:17] balloons, let me check [19:17] Letozaf_, ohh you need to replace the tool_path [19:18] after you branch the click_ready branch, put the full path in there as "tool_path" [19:18] it's the first line [19:18] balloons, sorry I just copied it [19:18] balloons, ok just a second [19:20] * Letozaf_ changed PC and I-m missing phablet tools I will install them now [19:20] yep need those too [19:21] * Letozaf_ is installing === salem_ is now known as _salem [19:24] Letozaf_, I spruced it up a little, hehe.. made is simple, but it pulls things each run this way: http://pastebin.com/rDhysJ2J [19:26] balloons, It ran and I got 2 failures :) [19:27] balloons, do you need the output of the failures ? [19:27] balloons, I see this: No tracing available - install the python-autopilot-trace package! [19:27] balloons, do I need that python-autopilot-trace package_ [19:28] Letozaf_: do you want tracing? [19:28] thomi, I suppose it's best to [19:28] thomi, right ? [19:28] * Letozaf_ is installing it [19:29] Depends if you're ever going to look at the tracepoint logs, and what else you're running. You probably don't need it unless you're trying to debug mir issues right now [19:29] it simply emits an LTTNG tracepoint at the start and end of every test [19:29] thomi, oh! [19:29] thomi, ok then better not install it :D [19:51] balloons, in the error output it says that '-testability' is an invalid option do you also get that ? [19:51] Letozaf_, so at any rate you can now investigate and fix anything needed [19:54] Letozaf_, umm, let me try [19:54] Letozaf_, I'm updating atm so it'll be a few [19:54] if they run I wouldn't worry to much about it [19:57] balloons, no they do not run :( [19:58] Letozaf_, what do you have flashed to your device? [19:58] adb shell cat /etc/media-info [19:58] adb shell system-image-cli -i [19:58] balloons, Ubuntu 13.10 - armhf (20131014) [19:58] balloons, should be the last image [19:59] Letozaf_, http://pastebin.com/UungwHsD [19:59] current build number: 96 [19:59] device name: mako [19:59] channel: stable [19:59] last update: 2013-10-14 21:16:08 [19:59] version version: 96 [20:00] ^^ that's the start for me [20:00] version ubuntu: 20131014 [20:00] Error: Ubuntu bug 20131014 could not be found [20:00] version device: 20131014 [20:00] balloons, ooops sorry [20:00] Letozaf_, :-) no worries. Ok so you have latest stable [20:01] balloons, this is what I get http://paste.ubuntu.com/6242232/ [20:02] ohh.. hmm.. Is the device on? [20:02] make sure it's unlocked [20:02] balloons, yes [20:02] so when it starts screen is on and it's unlocked? [20:02] OHH [20:02] balloons, let me try with it unlocked, could have been locked [20:03] balloons, its the same with the device unlocked [20:05] Letozaf_, I have seen that before I swear but I don't remember [20:05] try a quick reboot of the device [20:05] balloons, ok I will [20:09] balloons, no :) after reboot the same happens, I changed PC could it be I have got some wrong version of some packet for intance ? [20:10] balloons, but the tests run on the device [20:10] Letozaf_, coming up blank on what the issue is [20:11] balloons, :( sorry I cannot help :( [20:11] Letozaf_, so according to the trace it just exits right away [20:11] Letozaf_, did the click package install? [20:11] balloons, let me check [20:11] Letozaf_, ohh right.. yea it's not launching click [20:12] Letozaf_, are you in r/w mode? [20:12] balloons, nope ! forgot :P [20:12] Letozaf_, no you odn't need to be [20:12] don't turn it on :-) [20:12] balloons, oh!! [20:15] Letozaf_, retry things using this script http://pastebin.com/rDhysJ2J [20:15] the output should look like this: [20:16] http://pastebin.com/73kCq0ZP [20:16] Letozaf_, the key piece you want to see is "Click package com.ubuntu.shorts_shorts_0.2.114 has been launched" [20:16] during the autopilot test run [20:16]