[00:55] <wxl> elfy: kind of ot but do you have a link to the qa contest you did for stickers?
[04:10] <elopio> veebers: so, I don't fully understand. But to fall on the safe side, I can just make branches for those project to make everybody use the base from the toolkit.
[04:16] <veebers> elopio: I'm just trying something now which should hopefully clarify it for myself then I'll be able to explain it better
[04:52] <elopio> veebers: ok, so tomorrow I'll prepare the extra branches.
[04:52] <elopio> good thing we made this card.
[05:43] <elfy> wxl: http://xubuntu.org/news/help-the-community-with-testing-and-win-xubuntu-stickers/
[05:48] <wxl> elfy: thx
[05:48] <wxl> yay just booted my raspberry 2 with snappy
[05:48] <wxl> squee
[06:30] <elfy> wxl: welcome
[10:44] <pitti> vila: so adt-run -d --- ssh -d works for me with an LXC target, so this looks phone specific
[10:45] <pitti> vila: -U should never be used on a phone in general, but I suppose you are doing this on purpose? did you set the phone to r/w before?
[10:45] <pitti> ah, apparently you do as apt-get update worked
[11:06] <pitti> vila: ok, I give up on bug 1449446 for now, I need more information
[11:51] <vila> pitti: yup, writable to test silos with citrain device-upgrade
[11:51] <vila> pitti: I haven't dig deeply to understand why I need -U though
[11:56] <vila> pitti: the log file is fine but lp fails to display it, I just downloaded it to check. Apart from a couple of ^M ... which may enough to trick lp ?
[12:06] <vila> pitti: and thanks for the shell advices ! I'll probably need more for some time ;)
[12:42] <pitti> vila: no, it's like 2 out of 3 messages are missing in the log, I'm not sure what happened there
[12:51] <vila> pitti: doh
[12:51] <vila> pitti: weirdly enough, I'm currently seeing an 'echo "Reboot #$X"' disappearing when X > 3 but still presents in the log !
[12:53] <vila> pitti: with qemu in that case
[12:54] <vila> pitti: ha ha ! Comparing my buffer with the log, I got:
[12:55] <vila> shell: tee: standard output: Resource temporarily unavailable
[12:55] <vila> log: Reboot #3
[12:55] <vila> yeah, that indeed, exactly ;)
[12:57] <vila> pitti: but anyway, when you say 2 out of 3, it is some big chunks (start/end) are missing or little chunks all over the place ?
[12:57] <pitti> vila: the latter; I really have no idea what happened there :/
[12:58] <vila> pitti: ok, I'll retry with a phone later and see, any hint on what should be there and isn't ?
[12:58] <pitti> vila: for example, "adt-run: DBG: testbed init" or "adt-run: DBG: $ vserver: adt-virt-ssh  ..."
[12:59] <pitti> vila: oh wait! this log doesn't actually contain the debugging for adt-run
[13:00] <pitti> vila: so maybe it's just because the branch uses Depends: @, and that's somehow not satisfiable after the apt-get upgrade, or something strange like that
[13:00] <vila> pitti: err, as in I forgot adt-run -d or it's not supposed to end up htere ?
[13:01] <pitti> vila: it is supposed to end up there (I ran it here, and it's all in the log
[13:01] <vila> pitti: nope, it doesn't happen with the same command but without -d for adt-virt-ssh
[13:02] <vila> hmm, unless something weird happened at X: adt-run --- adt-virt-ssh (no -d) X; adt-run --- ssh -d ; adt-run --- ssh
[13:03] <vila> pitti: well, according to my own report, I didn't use adt-run -d /me blushes
[13:04] <vila> only adt-virt-ssh -d, will redo
[13:45] <boiko> vanguard: hi guys, I need some help with writing an emulator to interact with on-screen notifications in ubuntu touch
[14:12] <boiko> elopio: is vanguard working? or should I use ubuntu-qa?
[14:12] <elopio> boiko: ubuntu-qa please.
[14:12] <boiko> ubuntu-qa: hi guys, I need some help with writing an emulator to interact with on-screen notifications in ubuntu touch
[14:14] <Saviq> boiko, fwiw, this should get you on the right path
[14:14] <Saviq> http://bazaar.launchpad.net/~unity-team/unity8/trunk/view/head:/tests/autopilot/unity8/shell/tests/test_notifications.py#L159
[14:20] <elopio> fgimenez: ^
[14:22] <fgimenez> Saviq, thx, elopio does http://bazaar.launchpad.net/~canonical-platform-qa/ubuntu-sanity-tests/trunk/view/head:/ubuntu_sanity_tests/helpers/unity8/settings_wizard.py contain also a good example?
[14:22] <elopio> fgimenez: of the helpers style, yes. But boiko needs to restart unity with testability if his tests are running on touch.
[14:23] <fgimenez> elopio, ok clear now :)
[14:23] <elopio> then wait for the notification to appear, and then swipe it away. This part is easy. I think it would be mostly to help him getting a nice base test class for unity integration.
[14:43] <boiko> elopio: so, some of the notifications are dialogs with multiple actions (snap decisions?), s not sure just swiping them away would work
[14:46] <elopio> boiko: I see. But the principle is the same, if the user in your tests needs to dismiss the notification, write a dismiss method with all the steps necessary.
[14:47] <boiko> elopio: yep, well, actually right now the dismissing of the notification is not part of the test, it is just to prevent the notification from getting in the way of the subsequent tests
[14:47] <elopio> boiko: fgimenez: it's worth analyzing that if the test is not testing the notifications, maybe we can stop the notification service or something like that.
[14:48] <elopio> but we'll need other tests that check the interaction with the notifications.
[14:49] <boiko> elopio: yep, FYI: the test I am working on is to check that dialer-app is doing the right thing on a valid USSD session, the dialog appearing is just a side effect
[14:52] <elopio> right, I guess that if there's no risk of the USSD session breaking the notifications, then you can split that test. Maybe even test the notification integration with lower level API tests.
[14:54] <boiko> elopio: still I need the dialog dismissed somehow at the end of the test :)
[14:56] <boiko> elopio: I was talking to tiagosh and he gave me the idea of killing the telephony-service-indicator process at the end of the test
[14:56] <boiko> elopio: that might be the easiest fix for now
[14:57] <elopio> boiko: I let you to discuss about it with fgimenez. Whatever solution you two come out with will be good for me.
[14:57] <boiko> elopio: thanks
[15:00] <fgimenez> boiko, i guess the notification doesn't have any control to interact with, right?
[15:01] <boiko> fgimenez: it has two buttons, "Ok" and "Cancel" but they both just dismiss the notification itself
[15:02] <boiko> fgimenez: in this particular case it is useless, but we have also tests for incoming calls that show the dialog to accept/reject the call
[15:03] <boiko> fgimenez: in that case it would be nice to be able to actually click the notification. Right now what we do is to trigger a dbus call to telephony-service-approver accepting/declining the call
[15:05] <fgimenez> boiko, you can create classes that expose methods for interacting with each kind of notification, for instance http://bazaar.launchpad.net/~canonical-platform-qa/ubuntu-sanity-tests/trunk/view/head:/ubuntu_sanity_tests/helpers/unity8/settings_wizard.py#L419
[15:05] <boiko> fgimenez: the problem is: the notifications themselves are in unity (which is not running in testability mode by default) and dialer-app is in a different process
[15:06] <brendand_> boiko, you have to restart it in testability mode first
[15:07] <brendand_> boiko, then do your test
[15:08] <boiko> brendand_: ok
[15:09] <boiko> fgimenez: brendand_: thanks for the help, I will try to cook something in the next few days, let's see how it goes
[15:15] <fgimenez> boiko, you can ping the vanguard for review
[15:15] <boiko> fgimenez: nice! thanks
[15:23] <brendand_> ubuntu-qa - anyone can confirm this sanity suite regression? unity8.shell.emulators.UnityEmulatorException: No scope found with id clickscope
[15:23] <rhuddie> brendand_, I've seen that one before
[15:25] <alesage> cking ping hey that rhymes :)
[15:25] <alesage> cking I'm wanting to persuade you to present some of you coverity findings during a UOS session next week, any interest?
[15:25] <brendand_> rhuddie, intermittently?
[15:26] <brendand_> rhuddie, it seems to be plaguing the whole suite now
[15:26] <brendand_> rhuddie, unless i did something wrong maybe
[15:26] <rhuddie> brendand_, when I saw it, it was intermittent and very hard to reproduce.
[15:27] <rhuddie> brendand_, so that sounds different
[15:27] <cking> alesage, don't you mean cppcheck findings?
[15:27] <alesage> cking exactly :)
[15:27] <alesage> cking, I'd like to do a "static analysis" topic
[15:28] <cking> alesage, actually, I was aiming to just use these findings to try and get leverage and a coverty scan license
[15:28] <alesage> cking, no better forum to publicize this work :)
[15:29] <alesage> cking, but you have worked with the coverity scanner, yes?  or am I misremembering
[15:30] <cking> alesage, coverity scan is free and superior to cppcheck anyday, but it has big limitations to the number of times one can use it per week on large projects
[15:30] <alesage> cking, I'm very curious about the "onboarding" process for the free service
[15:30] <alesage> cking, I see
[15:31] <cking> alesage, it is limited, one has to either own the project or be a significant author to sign a project up to it
[15:31] <alesage> cking do you get access to their web console, etc.?
[15:31] <cking> alesage, yep, I get access to the webby front-end goodness
[15:31] <alesage> cking, anyway the session could literally be me asking you these questions :) and maybe us presenting a few interesting defects
[15:32] <cking> i use it for all projects I package into debian
[15:32] <alesage> cking, doesn't have to be longer than 15 min
[15:32] <alesage> cking, balloons and I trying to sort some QA-relevant sessions
[15:33] <elopio> projects-team: I'm breaking the rule of 2 because these cards are boooring.
[15:33] <cking> alesage, i'm more convinced we'll get better coverage if I blog about it, I get tens of K hits on my blog
[15:33] <elopio> I'm done, but waiting for three jenkins runs.
[15:33] <cking> alesage, and I'm bogged down with some critical work that needs attendind to at the mo
[15:34] <alesage> cking, whell that's fair, can't stand in the way of your work
[15:34] <alesage> cking, thanks for considering
[15:34] <alesage> cking I'll have more questions at some point, ok?
[15:35] <cking> alesage, ask anytime, I'm very happy to discuss it
[15:35] <cking> however, I really think the perfect solution is to get a coverity scan licence for devs and the QA process
[15:36] <balloons> cking, alesage thanks for considering
[15:36] <alesage> cking, we'll have to discuss that further--would you be willing to give me a tour of the free process at some point?
[15:38] <cking> alesage, sure, I can do that, it's very simple, here's a starter: https://scan.coverity.com/faq
[15:39] <cking> alesage, sign yourself up, and I'll add you to a project so you can see what it looks like
[15:39] <alesage> cking, thanks
[15:44] <elopio> vila: are you ok with this one? https://code.launchpad.net/~canonical-platform-qa/qakit/flake8-fixes/+merge/256674
[15:44] <vila> elopio: I approved it long ago didn't I ?
[15:45] <vila> elopio: fixing the key exposure will require changing it anyway
[15:46] <elopio> I can't top-approve it :/
[15:46] <elopio> alesage: can you?
[15:46] <alesage> elopio, let me check
[15:47] <vila> elopio: hmm, I can't either, NeedsFixing ;-)
[15:52] <alesage> elopio I can't either :/
[15:53] <pitti> vila: oh, you figure the phone ran out of space and thus it couldn't create /tmp/ssh_askpass.XX any more?
[16:01] <alesage> elopio, vila, seeing the problem one sec
[16:05] <elopio> oSoMoN_: alex-abreu: returning to the issue killing the web container, is there something else you need from us?
[16:05] <oSoMoN_> elopio, not at this point, alex-abreu is debugging the issue
[16:06] <elopio> cool. The bug fix in autopilot is easy, but the release is painful so it will take some time.
[16:24] <elopio> thanks alesage. I suppose we don't have autolanding, right?
[16:25] <alesage> elopio, not sure if thomi set it up, assume no
[16:25] <alesage> elopio will look into
[16:30] <elfy> wxl:  now I am awake enough to think about that - what you asked wasn;t at all offtopic for this channel :)
[17:12] <wxl> elfy: well, tangenital :)
[18:50] <teward> balloons: ping if you're still around, and don't mind a PM
[19:07] <balloons> teward, pong
[19:07] <teward> balloons: mind a PM?
[19:07] <balloons> go for it


[10:30] <rmg51> Morning
[12:45] <icey> morning
[12:46] <icey> lazyPower: finally looks like winter over here: https://imgur.com/jj0DSeH
[13:05] <teddy-dbear> Morning peoples, critters and everything else
[13:33] <lazyPower> icey  :O
[13:34] <lazyPower> like 1/4 inch here in pgh
[13:34] <icey> something like that here


[22:48] <clusty> was just curious what are the 3 ACPI sensors i am getting for the my core 2 duo
[22:49] <clusty> IdleOne, gnome?
[22:49] <IdleOne> yes
[22:49] <clusty> it works out fo the box
[22:49] <clusty> not very well...
[22:49] <IdleOne> clusty, I cant seem to setup my wifi
[22:49] <clusty> NetworkManager is the process
[22:49] <IdleOne> is there a GUI ?
[22:49] <clusty> this is the gui
[22:50] <IdleOne> hmmm
[22:50] <clusty> put everything in roanming mode
[22:50] <clusty> plug out wired network
[22:50] <clusty> turn on wireless
[22:50] <clusty> and it should show wireless networks in rage
[22:50] <IdleOne> how do I turn on the wirless?
[22:50] <clusty> range*
[22:50] <clusty> laptop?
[22:50] <IdleOne> yes
[22:51] <clusty> what care you have?
[22:51] <clusty> card*
[22:51] <clusty> intel/broadcom/atheros?
[22:51] <IdleOne> Atheros AR242x
[22:51] <clusty> have the right module?
[22:51] <IdleOne> beats me
[22:52] <clusty> think its not supported by default in the kernel
[22:52] <clusty> madwifi drivers i think is your way
[22:52] <clusty> .....just heard
[22:52] <clusty> never had a atheros
[22:52] <IdleOne> !madwifi
[22:52] <ubotu> Wireless documentation can be found at https://help.ubuntu.com/community/WifiDocs
[22:53] <clusty> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/201180
[22:53] <ubotu> Launchpad bug 201180 in linux "[hardy] kernel 2.6.24-12 breaks wireless (atheros)" [Undecided,New]
[22:53] <clusty> some dude reported a bug
[22:54] <IdleOne> you know I have not tried kde
[22:54] <clusty> http://ph.ubuntuforums.com/showthread.php?p=4492814
[22:54] <clusty> check if module is there
[22:54] <clusty> thing is supposed to blink at least
[22:54] <clusty> scanning
[22:54] <clusty> thats kernel stuff
[22:54] <clusty> then check if it behaves right
[22:55] <clusty> lsmod |grep ath
[22:55] <IdleOne> I dont know how to check for module
[22:55] <clusty> just gave you
[22:55] <clusty> lsmod
[22:55] <IdleOne> yeah saw that
[22:55] <clusty> lsmod=list modules
[22:55] <clusty> ...loaded ones
[22:55] <IdleOne> there are 3
[22:55] <clusty> have them?
[22:56] <IdleOne> ath_pci wlan and ath_hal
[22:56] <clusty> what does ifconfig say?
[22:56] <IdleOne> ath_pifconfig
[22:56] <clusty> have eth0/ath0/wifi0
[22:56] <IdleOne> lmao
[22:56] <clusty> ?
[22:56] <IdleOne> to many pc's in front of me
[22:56] <IdleOne> says eth0
[22:56] <IdleOne> but it is plugged in wired now
[22:57] <clusty> do iwconfig
[22:57] <IdleOne> no wireless extensions
[22:57] <IdleOne> lo and eth0
[22:58] <clusty> do a dmesg|grep ath
[22:58] <clusty> do you get unknown symbols?
[22:58] <IdleOne> unknown symbols?
[22:59] <IdleOne> ummm no
[22:59] <clusty> any responses?
[22:59] <clusty> one suggestion: you are in way over your league :D
[22:59] <IdleOne> gimme a sec
[23:00] <clusty> hardy is not for people that can't troubleshoot
[23:00] <HardyOne> ok Im here
[23:00]  * HardyOne is IdleOne
[23:00] <clusty> dmesg|grep ath
[23:00] <HardyOne> [   30.488138] ath_hal: module license 'Proprietary' taints kernel.
[23:00] <HardyOne> [   30.547466] ath_hal: <IP_ADDRESS> (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413)
[23:00] <HardyOne> [   30.812973] ath_pci: <IP_ADDRESS> (<IP_ADDRESS>)
[23:01] <clusty> hmm
[23:02] <HardyOne> hmmm that is good bad indiffrent?
[23:03] <clusty> looks good
[23:03] <HardyOne> :)
[23:03] <clusty> strange though...
[23:03] <clusty> kernel saw it
[23:03] <clusty> modules loaded
[23:03] <clusty> but interface is not there
[23:04] <clusty> normally you get an when device pops up
[23:04] <HardyOne> is there a way of restarting the interface or scanning for it?
[23:04] <HardyOne> knudging it!
[23:04] <clusty> its there
[23:04] <clusty> :D
[23:04] <clusty> kernel seems to have done its job
[23:04] <clusty> think its over my competences....
[23:05] <clusty> hang around more and some guys will ask
[23:05] <clusty> i mean answer
[23:05] <clusty> damn
[23:05] <clusty> 1AM here
[23:05] <clusty> :)
[23:05] <HardyOne> ok thanks clusty
[23:05]  * clusty 's brain feels mushy
[23:05] <clusty> gnite
[23:05] <HardyOne> nite
[23:07] <hmuller> any klibc heroes present?
[23:15] <Black_Magic> Anyone else get: ** (nautilus:8197): WARNING **: Unable to add monitor: Not supported When running nautilus from terminal?
[23:16] <Black_Magic> i dont have any other monitors attached to computer..
[23:16] <hmuller> Black_Magic: I'm not getting any errors, and am using the daily-live amd64 desktop
[23:17] <Black_Magic> Im x32
[23:26] <lime4x4> anyone got a wireless card that uses a broadcom chip set to work with the bcm43 drivers?
[23:31] <Ienorand> Test...
[23:36] <AmyRose> !test | Ienorand
[23:36] <ubotu> Ienorand: Failed.
[23:37] <Ienorand> !test
[23:37] <ubotu> Failed.
[23:37] <DanaG> !test > ubotu
[23:39] <vox> anyone know why mousekeys would be turning itself on every 2-3 days?
[23:40] <bmk789> who broke virtualbox?
[23:42] <lime4x4> virtualbox is working fine here on hardy 64
[23:43] <bmk789> it didnt want to upgrade correctly
[23:43] <bmk789> had to remove the modules packages then install
[23:44] <lime4x4> don't know what to tell ya
[23:44] <bmk789> its good now
[23:47] <burner> anyone know if the new rhythmbox made it before beta freeze?
[23:55] <DanaG> Odd.. when I hotplugged my Audigy, pulseaudio didn't move my "QuodLibet" media player's stream back to it, even though that's where I put the stream last time I used the device.
[23:56] <nemo> hm. why would my laptop be ripping a CD 3 times faster than my ubuntu desktop?
[23:56] <nemo> given the desktop is newer and has fewer power constraints
[23:57] <nemo> laptop is gentoo
[23:57] <nemo> drives appear roughly comparable. 48x or whatever