[00:00] <phillw> I'd be much more use checking the desktop installer, as that's where we know there were issues... but, get the alternates out of the way 1st as they are our "hey, it works" series :P
[00:27] <phillw> Ahh, Jeff Wayne; War of the Worlds... Calming on the ears :D
[00:30] <phillw> thanks que-bot... Let me just grab the only person I know to get it tested :P
[03:57] <phillw> hi, anyone on ubiquity partitioning crashing bug watch?
[04:12] <phillw> bug 1240794
[05:23] <sonu> hi, little help with info: what is "Hardware profile? URL to the hardware profile." while reporting test result?
[05:56] <Noskcaj> sonu, It helps with diagnosing hardware specific issues. If possible, have one
[06:14] <sonu> Noskcaj, agree. But how to create one?
[06:14] <Noskcaj> I think phill made a guide, one sec
[06:16] <Noskcaj> sonu, https://wiki.ubuntu.com/QATeam/Hardware should work
[06:16] <Noskcaj> If you use a VM, just add a comment saying something like "Tested on Vbox 4.2"
[06:17] <sonu> Noskcaj: wonderful! thanks!
[06:17] <Noskcaj> no problem, it's great to get more testers
[06:49] <DanChapman> morning all
[06:49] <elfy> morning DanChapman
[06:50] <DanChapman> morning elfy, how are you?
[06:52] <elfy> ok thanks - be glad when it's Friday and Smaug is released and I can forget about it for a day
[06:53] <DanChapman> :-)
[06:59] <pitti> everyone feeling saucy today? :-)
[07:04] <elfy> definitely smaug here :p
[07:04]  * DanChapman is feeling extra saucy! :-)
[07:05] <elfy> and I think we should keep that to another channel - smartboyhw or nosckaj might be about :P
[07:05] <DanChapman> hehe ;-)
[08:02] <om26er> ubuntu-qa Oy! please can anyone confirm bug 1240841 ?
[08:45] <slickymaster> morning all
[09:05] <smartboyhw> Guys, we have the Xubuntu i386 desktop and Lubuntu amd64+mac and ppc images needing testing:)
[10:01] <davmor2> Morning all Happy release day
[10:02] <jibel> Good morning davmor2 !
[11:06] <pitti> hm, adb doesn't want to come up for me today (still worked yesterday, and tried rebooting)
[11:06] <pitti> can I use phablet-flash from fastboot?
[11:11] <jibel> pitti, you can boot to recovery and use phablet-flash for there if you specific -d <device name>
[11:20] <pitti> jibel: thanks, finally got recovery to start; trying now
[11:25] <pitti> jibel: hm, still nothing in "adb devices" for recovery; I'm beginning to think it's not my phone but my workstation..
[11:26] <pitti> it's in lsusb, but adb doesn't see it
[11:26] <jibel> pitti, did you try to disconnect/reconnect the usb cable? last thing is to restart the desktop
[11:27] <jibel> s/desktop/workstation
[11:27] <pitti> jibel: yes, I rebooted phone, dis/reconnected cable
[11:27] <pitti> and killed/restarted adb
[11:27] <pitti> (daemon on desktop)
[11:27] <pitti> so I guess I'll need to reboot once I'm done with my VM
[11:27] <jibel> pitti, as user or root?
[11:27] <pitti> jibel: I never started it as user, has worked fine so far
[11:28] <pitti> jibel: indeed, works as root; wth?
[11:28] <jibel> pitti, I've a machine that I broke but didn't find how, and I can only start adb as root to make it work
[11:29] <pitti> jibel: argh, c'était moi, sorry
[11:29] <pitti> I did "sudo stop udev" earlier for testing my bug fix..
[11:30] <pitti> *brown paperbag*
[12:23] <sonu> quit
[12:41] <pitti> fginther: just logged into the otto test box; last saucy version is from Oct 1, isn't that a tad old for testing?
[12:43] <pitti> fginther: anyway, I'm afraid I can't debug the (supposed) at_console failure remotely, I'd actually need to be "in" the running session
[12:43] <sergiusens> pitti, perhaps you can polish the udev rule there for adb
[12:43] <pitti> sergiusens: what? where?
[12:43] <pitti> sergiusens: this is about the saucy/desktop autopilot tests, not the ones on the phone
[12:43] <sergiusens> pitti, would be great i you could take a look; dpkg -L android-tools-adb
[12:44] <sergiusens> pitti, I was referring to what you and jibel were talking about above :-)
[12:44] <pitti> sergiusens: oh; yeah, I had udev stopped still
[12:44] <sergiusens> pitti, oh sorry, didn't read all of it :-)
[12:44] <pitti> sergiusens: looks quite alright to me
[12:45] <sergiusens> great
[12:54] <fginther> pitti, having an older snapshot helps to expose dependency issues (although it's not a perfect solution)
[12:54] <pitti> fginther: oh, you mean versioned dependencies
[12:54] <pitti> fginther: I see
[12:54] <pitti> fginther: I answered to your otto email
[12:55] <pitti> fginther: so if I can abuse the CI system to do a few debugging steps in my proposed branch, see what the otto output is, and revert, that's ok for me (but it'd waste the runs on mako/maguro)
[12:57] <fginther> pitti, that should be ok. there isn't much going on right now (in fact it's very quiet on jenkins)
[12:58] <fginther> pitti, if you wanted to just isolate your experiments to otto I can help with that
[12:59] <fginther> pitti, you would just need to push to a branch without a merge proposal and trigger the generic-mediumtests-saucy job manually
[12:59] <pitti> fginther: mako/maguro fail as well, but for different reasons (mostly maliit and mir crashes), so starting debugging just for otto would be good
[12:59] <pitti> fginther: oh, cool; how would I do that?
[13:00] <fginther> pitti, ok, first create an account on http://10.97.0.26:8080/ and I'll enable job building access
[13:01] <pitti> fginther: done, "pitti"
[13:03] <fginther> pitti, when you go to http://10.97.0.26:8080/job/generic-mediumtests-saucy/, you should now see a build link
[13:04] <fginther> pitti, landing_candidate is your lp branch, target_branch is the branch to merge into (i.e. lp:dialer-app) and test_suite is the name of the autopilot suite, "dialer_app" in this case.
[13:05] <fginther> pitti, every other parameter can be left blank for dialer-app
[13:05] <pitti> fginther: build link -> the "Build now" on the left top menu?
[13:05] <fginther> pitti, yes
[13:05] <pitti> fginther: ah, splendid
[13:05] <pitti> fginther: thanks!
[13:29] <pitti> fginther: how do you specify a branch? lp:~... or http://bazaar... or https://code... etc?
[13:30] <smartboyhw> Good job everybody for testing 13.10!
[13:31] <fginther> pitti, lp:~pitti... works
[13:46] <pitti> fginther: do I need to specify anything in addition after all? http://10.97.0.26:8080/job/autopilot-testrunner-otto-saucy/1254/
[13:46] <pitti> /var/local/autopilot/autopilot.log: autopilot run: error: too few arguments
[13:46] <pitti> fginther: like "messaging_app" (test name)
[13:47] <fginther> pitti, yes, you do need the test_suite == messaging_app
[13:47] <pitti> fginther: ah sorry; you already said so, missed that
[13:47] <fginther> you can always look at the jenkins parameters used by an automated build
[14:07] <pitti> fginther: http://10.97.0.26:8080/job/autopilot-testrunner-otto-saucy/1255/console
[14:07] <pitti> fginther: ok, what I suspected: there is no logind session, i. e. none of the "local foreground" functionality by d-bus or policykit will work
[14:08] <pitti> fginther: curious that this didn't already come up, as these are rather common (device access, suspend, bluetooth, whatnot)
[14:08] <pitti> fginther: is that session spawned by lightdm autologin? or something manual?
[14:09] <fginther> pitti, the tests are launched via an upstart job
[14:10] <melodie> hi
[14:10] <pitti> fginther: ah, that would do it
[14:10] <pitti> fginther: I mean, explain why they aren't attached to a console
[14:10] <melodie> I would like to have a tip/information about discussions in the blueprint sections
[14:10] <melodie> can someone help me?
[14:10] <melodie> my question is : is it ok to post long texts in that section?
[14:12] <fginther> pitti, it's an xdg autostart job, I would have that that would have access to most of the user session
[14:12] <pitti> melodie: if you have more than two or three paragraphs, consider writing a wiki page and linking it in the blueprint, as that's much easier for sectioning, formatting, and reading
[14:12] <fginther> would have *thought*
[14:12] <pitti> fginther: oh; those would, but I mean how is that session itself started? apparently not through lightdm?
[14:13] <pitti> (or any dm really)
[14:13]  * fginther grammer on IRC gets badder over time
[14:13] <pitti> *chuckle*
[14:14] <pitti> fginther: I thought you meant "the whole unity session is started from a (system) upstart job"
[14:15] <fginther> pitti, I thought unity was started via auto-login, but I'll admit my ignorance here. This is all based on jibel's work
[14:15] <pitti> fginther: so this is by and large using otto as it is?
[14:15] <fginther> pitti, yes
[14:16] <pitti> fginther: I guess I should try checking what breaks otto on current saucy then (at least on my workstation), and see there
[14:16] <pitti> fginther: thanks, doing that then
[14:16] <melodie> pitti is there a preferred wiki page?
[14:16] <pitti> melodie: if you write one, you should use https://wiki.ubuntu.com/SpecTemplate
[14:17] <fginther> pitti, let me know if you find anything, I'd like to move the jenkins otto machines to saucy eventually
[14:17] <melodie> pitti I can also put it on a forum I run or on a website I run, if needed. Here is the text, can you have a look and tell me what would be best? http://pastebin.fr/29158
[14:17] <pitti> fginther: they currently run on raring?
[14:18] <fginther> pitti, raring is what's installed on the bare metal, the overlay FS is a saucy ISO
[14:19] <pitti> melodie: well, anythign which is comprehensible, explains what you want to do, and is actionable; so whether it's a link to a wiki or a forum doesn't matter that much, but folks generally prefer wiki.u.c. as then other people can make updates etc.
[14:19] <pitti> fginther: *nod*
[14:20] <pitti> bbl, otto testing
[14:23] <melodie> pitti I am not used to the Ubuntu ways when it comes to contributions, so I would like you to tell me if the text I wrote would be ok as is in the wiki side you just pointed to for me?
[14:25] <melodie> pitti I give up the wiki, it has disconnected me: Erreur OpenID : Nonce already used or out of range.
[14:26] <melodie> last time I tried to edit a page in the wiki I was never able to do so
[14:35] <pitti> melodie: hm, no idea about the OpenID thingy; you might have some old cookies around in your browser or something?
[14:36] <pitti> melodie: it's okay for a first start; proper drafting happens after UDS discussions anyway
[14:36] <pitti> jibel (FYI fginther): I found out what's wrong with otto here: http://paste.ubuntu.com/6251313/
[14:37] <pitti> jibel: so the first failure is due to that kernel option not being enabled by default, so I just commented out the limit stuff
[14:37] <pitti> jibel: the second is a bug in otto; $RELEASE is indeed not defined anywhere
[14:37] <pitti> jibel: curiously, even after destroying the container, adding that hack (to the checkout) and re-creating the container the phablet-prepare.sh is still the original version (without the export RELEASE)
[14:38] <pitti> jibel: so eventually I added the export RELEASE to /var/lib/lxc/.../phablet-prepare.sh
[14:38]  * pitti files a bug, to track that
[14:39] <pitti> jibel: oh of course, I added it to phablet-prepare, silly me
[14:40] <jibel> pitti, this is defined in a configuration file, but if the configuration file is not found then it's definitely not defined, thanks for finding this
[14:43] <pitti> jibel: filed bug 1241021 with details
[14:44] <pitti> fginther: but the main point of the exercise, that gives me a normal session, with a logind session and all bells and whistles
[14:44] <pitti> fginther: so I guess I now need to locally reproduce how you start a test, i. e. what you throw into the otto config
[14:47] <jibel> pitti, hm, http://bazaar.launchpad.net/~jibel/otto/phablet/view/head:/lxc.defaults/scripts/phablet-prepare.sh#L27
[14:47] <jibel> pitti, I don't know where the phablet-prepare.sh script comes from
[14:48] <pitti> jibel: ah, different branch
[14:48] <pitti> jibel: lp:otto is http://bazaar.launchpad.net/~otto-dev/otto/trunk/files
[14:48] <pitti> jibel: you have a ~jibel branch
[14:49] <pitti> jibel: http://bazaar.launchpad.net/~otto-dev/otto/trunk/files/head:/lxc.defaults/scripts/ has phablet-prepare
[14:49] <jibel> pitti, yes the phablet stuff has never been merged in trunk
[14:50] <jibel> well partially merged
[14:50] <pitti> jibel: err, it *is* in trunk!?
[14:50] <pitti> jibel: at least lp:otto points to the ~otto-dev one, not the ~jibel one
[14:50] <pitti> fginther: ^ which one do you use in CI?
[14:51] <jibel> pitti, that's something I never had time to merge completely because I've been swamped into phone testing
[14:52] <pitti> jibel: ah, ok; so I guess in the DC we don't run lp:otto, but your branch?
[14:53] <jibel> pitti, yes, and last time I touched it was in August
[14:54] <jibel> pitti, in summary otto for desktop -> everything is in trunk, for phone -> I must merge my work
[14:56] <elopio> good morning.
[14:58] <balloons> Welcome to Ubuntu Quality | http://wiki.ubuntu.com/QATeam | Celebrating Saucy's Release!
[14:59]  * pitti ^5s balloons
[14:59] <smartboyhw> balloons, let's celebrate?
[14:59] <smartboyhw> !
[14:59] <balloons> ^^ never give that balloons OP powers your channel :-)
[14:59] <smartboyhw> balloons, I suppose we now can really discuss about classroom sessions:P
[14:59]  * slickymaster throws same champagne all around 
[14:59] <balloons> I'm struggling to put together long sentences, but yes, totally
[15:00] <smartboyhw> balloons, how do you want the classroom sessions to be done?
[15:04] <balloons> smartboyhw, well I don't know
[15:05] <smartboyhw> balloons, I'm thinking something simliar to Ubuntu Open Week / Dev week, but I wonder if that is too ambitious
[15:05] <balloons> I'm open to ideas. I'd like to think about trying something new, but if we don't, that's ok too
[15:06] <balloons> I'd like to seperate the content out of the sessions.. So the content can be updated and the session can be more hands on
[15:06] <fginther> pitti, using lp:~otto-dev/otto/trunk
[15:06] <balloons> doing hands on things is interesting on the internet of course
[15:06] <balloons> video, text, both?
[15:07] <smartboyhw> balloons, dunno.
[15:07] <pitti> fginther: ok, thanks; so I now need to know how the tests are auto-started through otto
 melodie: hm, no idea about the OpenID thingy; you might have some old cookies around in your browser or something? // I don't think so. I have met with this before and it happens only in the wiki ubuntu, with my Firefox browser (didn't try other browsers yet)
[15:09] <jibel> pitti, it's an autologin with an autostart
[15:10] <pitti> jibel: hm, then I have no idea why these don't have a logind session :/
[15:11] <jibel> pitti, http://bazaar.launchpad.net/~otto-dev/otto/testsuite_autopilot-unity/view/head:/target-override/etc/xdg/autostart/autopilot.desktop
[15:12] <pitti> jibel: thanks
[15:12] <jibel> which executes http://bazaar.launchpad.net/~otto-dev/otto/testsuite_autopilot-unity/view/head:/target-override/usr/local/bin/run-autopilot.sh
[15:13] <pitti> jibel: thanks; that all looks fine
[15:15] <balloons> smartboyhw, we can lay out the schedule. There are some other changes I'd like to broach that might make it more interesting. We have the problem of giving training before it can be used by folks.. IE, testing is done largely at the end of the cycle
[15:22] <melodie> pitti thank you, I have been able to finish writing it here: https://blueprints.launchpad.net/lubuntu-brainstorming/+spec/zram-config
[15:30] <jibel> pitti, where is the branch you want to test?
[15:30] <pitti> jibel: lp:~pitti/messaging-app/phonesim-tests-debugging
[15:30] <pitti> jibel: I pushed two extra commits there to debug why there is no logind session; running another CI test now
[15:31]  * pitti kicks off http://10.97.0.26:8080/job/generic-mediumtests-builder-saucy-amd64/966/
[15:31] <pitti> jibel: originally, it's https://code.launchpad.net/~pitti/dialer-app/enable-phonesim-tests/+merge/191248
[15:32] <pitti> jibel: I pushed a separate branch for the debugging stuff to kick off CI builds on otto manually, to avoid wasted runs on phones
[15:37] <smartboyhw> balloons, agreed
[15:41] <pitti> need to leave for today, will continue with this tomorrow (although I don't have a great idea now); current build shoudl show me syslog, auth.log and so on
[19:03] <melodie> bbl
[19:08] <thomi> morning
[19:10] <cgoldberg> morning thomi
[19:48] <elopio> robotfuel: I don't really understand bug #1231939
[19:48] <elopio> maybe I'm not doing it fast enough. But I don't understand where and why the text should be disabled.
[19:48] <robotfuel> elopio: the text is disabled a disabled grey instead of black
[19:49] <robotfuel> elopio: the text should not be disabled
[19:49] <elopio> robotfuel: can you make a screenshot? I seee the selected text always black.
[19:50] <robotfuel> elopio: maybe it was fixed with #1231936? I'll reproduce now
[19:51] <elopio> robotfuel: I'm using image 100.
[19:51] <robotfuel> elopio: I just tried it on my desktop and it's there in the examples on the option selector
[19:53] <elopio> robotfuel: I might not be doing it right, but on the gallery I also see the text black.
[19:58] <robotfuel> elopio: http://imgur.com/a/Du1ON
[19:59] <elopio> robotfuel: got it!
[19:59] <robotfuel> maybe it's the animation hasn't finished and the level remains the same
[19:59] <elopio> I was using the installed package, not from trunk.
[19:59] <elopio> must be a recent regression.
[20:00] <robotfuel> elopio: the level of grey/black is depending on how quickly I click the item in the combobox/list
[20:03] <robotfuel> I've updated the bug
[20:03] <elopio> robotfuel: thanks. I think I'm done with your bugs. Let me know if I missed something.
[20:03] <elopio> we should be meeting weekly with the SDK team to have a voice on the priority of these bugs.
[20:04]  * elopio walks with the dog.
[20:05] <robotfuel> elopio: it looks like you got them all.
[20:05] <robotfuel> elopio: thanks!
[20:18] <Letozaf_> balloons, hi
[20:19] <balloons> Letozaf_, hello
[20:19] <Letozaf_> balloons, I re-flashed my device as I has too many weird things happening
[20:20] <balloons> Letozaf_, ahh..
[20:20] <Letozaf_> balloons, I wanted to ask you what do I need on it after re-flashing to make the click packes stuffu work
[20:20] <balloons> I've got build 100 running now
[20:20] <Letozaf_> balloons, so have I, finally the first official one :P
[20:20] <balloons> I reflashed at one point to transition out of the rw mode with all the edits I had
[20:21] <Letozaf_> balloons, what do I have to install on it to make the click packages install work ?
[20:22] <balloons> http://pastebin.com/rDhysJ2J
[20:22] <balloons> Letozaf_, nothing... you should install nothing on it
[20:22] <balloons> run that script and it should work
[20:22] <Letozaf_> balloons, ok I will try it now, thanks
[20:25]  * elopio <- lunch
[20:33] <Letozaf_> balloons, :(  http://paste.ubuntu.com/6253131/
[20:33] <Letozaf_> balloons, maybe I'm missing something
[20:38] <balloons> rssreader_app
[20:39] <Letozaf_> balloons, do I have to install ubuntu-rssreader-app-autopilot on the device
[20:39] <balloons> hmm
[20:39] <balloons> no
[20:39] <balloons> the module name is ubuntu_rssreader_app
[20:39] <balloons> I blame the script author
[20:39] <balloons> <--
[20:39] <Letozaf_> balloons, :D
[20:39] <balloons> I don't use it
[20:40] <balloons> ahh I see one issue
[20:41] <Letozaf_> balloons, what ?
[20:47] <balloons> the script sucks
[20:47] <balloons> regardless the point is if the click package installed it would find the tests
[20:48] <Letozaf_> balloons, yes I was looking under /home/phablet/autopilot ...
[20:49] <Letozaf_> balloons, well if you got time, otherwise I will be back tomorrow evening or when you can
[20:52] <balloons> i'm playing with it but the script has nothing to do with your issues
[20:52] <balloons> is there a click package in /tmp?
[20:52] <balloons> you can see it installed, so it should run
[20:52] <balloons> simple as that
[20:53] <Letozaf_> balloons, I'v got com.ubuntu.shorts_0.2.120_all.click in /tmp
[20:53] <Letozaf_> balloons, it's a file
[20:53] <balloons> yep
[20:53] <balloons> and your log shows it installed
[20:53] <Letozaf_> balloons, but it does not run :(
[20:54] <Letozaf_> balloons, it's owner and group are root while all the other files in /tmp hav phablet as owner and rott
[20:54] <Letozaf_> balloons, sorry root
[20:54] <Letozaf_> balloons, could that be an issue ?
[20:55] <Letozaf_> no owner and group
[21:00] <Letozaf_> balloons, I will be back tomorrow, going to bed now, it's getting late for me :D
[21:00] <balloons> Letozaf_, best to ask sergio I think
[21:00] <balloons> you installed the click package it should work
[21:00] <balloons> end of story
[21:00] <Letozaf_> balloons, ok maybe tomorrow I will ask him
[21:01] <balloons> yea, sorry I've really no idea why it doesn't
[21:01] <balloons> but I think I made a better script anyway..
[21:01] <Letozaf_> balloons, doesn't matter, I was curious to see it run on my device that-s all
[21:01] <Letozaf_> balloons, thanks anyway :D
[21:02] <Letozaf_> balloons, going to bed now, good night!
[21:02] <balloons> Letozaf_, night :)
[21:02] <balloons> here's the fixed version: http://pastebin.com/nFcF8RpR
[21:02] <Letozaf_> balloons, ok I will try this tomorrow, thanks
[21:14] <phillw> balloons: (and any one else) "so is there a do-releases-upgrade log somewhere? the error "an unresolvable problem occurred while calulating the upgrage." is pretty much as useful as just failing without any error." A Question that has just been asked.
[21:16] <balloons> /var/log/dist-upgrade
[21:16] <balloons> phillw, ^^
[21:16] <phillw> balloons: thansk!
[21:21] <jfunk> ping veebers - can you meet now?
[21:22] <veebers> jfunk: sure can
[21:22] <jfunk> cool, see you there
[23:23] <slickymaster> good night all