[00:16] <sergiusens> veebers, have a minute?
[00:20] <veebers> sergiusens: hey, what's the haps?
[00:20] <sergiusens> veebers, thought you might be interested in my ugly hack https://code.launchpad.net/~sergiusens/phablet-tools/click_testing_python_modules/+merge/189744
[00:21]  * veebers looks
[00:23] <veebers> sergiusens: ah ok cool, so this resolves for the python deps. right, but not the likes of unity8-fake-env et. al?
[00:24] <sergiusens> veebers, not yet, but that will come soon
[00:24] <veebers> sergiusens: and by 'ah cool' I mean it's cool we have a hack work around, not ah cool, that's an awesome solution ;-)
[00:24] <veebers> sergiusens: sweet, cheers for working on that
[00:25] <veebers> sergiusens: hey, what happens if the read on diff line 58 fails? does it throw an exception message and the cleanup catches any hanging cruft?
[02:48] <jrr> it's very difficult for Ubuntu to make progress on bugs that are crashes during an apt upgrade
[02:48] <jrr> it seems that because the system is mid-upgrade, it has outdated packages, and apport closes the bug immediately
[02:55] <jrr> here's the bug in question https://bugs.launchpad.net/ubuntu/+source/docky/+bug/960609
[05:12] <jibel> Good morning
[05:17] <pitti> Godo morning
[05:19] <jibel> Good morning pitti, how are you?
[05:20] <pitti> jibel: much better, a good night's sleep was what I needed
[05:20] <pitti> jibel: and you?
[05:20] <jibel> pitti, another night was needed to evaporate French wine, right ? ;)
[05:21] <jibel> pitti, I'm good. I'll be happy when the phone is released. I've the impression to live this 80s movie with Bill Murray
[05:22] <pitti> "Und taeglich gruesst das Murmeltier"?
[05:22] <jibel> pitti, Groundhog Day what the english title :)
[05:22] <jibel> *was
[05:22] <pitti> ah, right
[06:43] <jibel> iahmad, is there a known bug with the SDK where buttons doesn't work if OSK is revealed?
[06:44] <iahmad> jibel, there is some OSK issue which hides the controls if they are on the lower part of the screen and takes the focus
[06:45] <iahmad> jibel, now whether it takes the focus for the entire screen, I am not too sure as I didn't see that problem myself.
[06:45] <jibel> iahmad, the issue I have is if there are buttons just above OSK, they cannot be pressed.
[06:53] <pitti> jibel: hm, is wazn unhappy again?
[06:53] <pitti> jibel: http://10.189.74.2:8080/view/Saucy/view/AutoPkgTest/job/saucy-adt-udisks2/80/ARCH=i386,label=adt/console
[06:53] <pitti> jibel: I retried a few times
[06:53]  * pitti looks at wazn
[06:53] <jibel> pitti, I retried it too, looking
[06:54]  * pitti cleans up the ~ 5 udisks2 VM images
[06:55] <pitti> jibel: hmm, it seems happy overall!?
[06:55] <pitti> net user: could not set up host forwarding rule 'tcp:54324::22'
[06:55] <pitti> that ought to be free, firefox VM is using 54323
[06:56] <pitti> tcp        0      0 localhost:54324         localhost:54323         ESTABLISHED 36548/ssh
[06:56] <pitti> tcp        0      0 localhost:54323         localhost:54324         ESTABLISHED 36491/qemu-system-x
[06:56] <pitti> hmm, what the heck is that?
[06:57] <jibel> j-lallement@wazn:~$ sudo lsof -itcp|grep 54324
[06:57] <jibel> qemu-syst 36491 auto-package-testing   89u  IPv4  99822442      0t0  TCP localhost:54323->localhost:54324 (ESTABLISHED)
[06:57] <jibel> ssh       36548 auto-package-testing    3u  IPv4  99933474      0t0  TCP localhost:54324->localhost:54323 (ESTABLISHED)
[06:58] <pitti> jibel: yeah, that's what I saw in netstat, but I can't see a process for that
[07:00] <jibel> the processes are
[07:00] <jibel> qemu-system-x86_64 -enable-kvm -m 3072 -smp 2 -monitor unix:/dev/shm/adt/saucy-amd64-firefox-20131008_034509.GC32hU.img.monitor,server,nowait -localtime -no-reboot -net user -redir tcp:54323::22 -drive file=/dev/shm/adt/saucy-amd64-firefox-20131008_034509.GC32hU.img,if=vir
[07:00] <jibel> ssh -o UserKnownHostsFile=/dev/null -o StrictHostKeyChecking=no -o CheckHostIP=no -i /home/auto-package-testing/cache/disks/adtkey -tt -p 54323 -l ubuntu localhost sudo /home/ubuntu/run-adt  -P firefox
[07:00] <pitti> so the running firefox test uses 54324 as well? that sounds wrong
[07:13] <jibel> pitti, also there is a lock file for 54324 which isn't locked. 2 options: 1. wait for FF to finish, 2. flock /var/lock/adt/ssh.54324.lock and start udisk tests
[07:14] <pitti> jibel: or disable wazn as executor until ffox is finished?
[07:14] <pitti> but your 2. sounds good, too
[07:14] <jibel> pitti, yes, that's another, more radical, option
[07:16] <jibel> trying option 2
[07:17] <jibel> pitti, it's running
[07:17] <pitti> jibel: thanks; re-running gvfs too
[08:25] <DanChapman> morning all
[08:26] <elfy> hi DanChapman smartboyhw
[08:26] <DanChapman> heya elfy
[08:27] <smartboyhw> Hello elfy
[08:28] <elfy> smartboyhw: you done anything with this yet?  https://bugs.launchpad.net/ubuntu-manual-tests/+bug/1225669
[08:28] <smartboyhw> elfy, the damn, ENOTIME.... Can you take over the bug (if you wish?)
[08:29] <elfy> done
[08:29] <elfy> that
[08:59] <elopio> ping iahmad, can you take care of this one? https://bugs.launchpad.net/ubuntu-ui-toolkit/+bug/1236464
[09:00] <jibel> iahmad, do you know if the 'wpa password' dialog a component of ubuntu-ui-toolkit or ubuntu-system-settings?
[09:00] <jibel> when I press the button the component behind the dialog receives the event
[09:00] <jibel> button=cancel or connect
[09:22] <iahmad> jibel, ubuntu-ui-toolkit doesn't provide ready made dialogs as far as I know, I am guessing it should be ubuntu-system-settings.
[09:23] <jibel> iahmad, thanks, that's where I reported it
[09:25] <iahmad> elopio, I am not completely understanding if this feature should be part of UITK or in the AP emulators ?
[09:27] <elopio> iahmad: it should be part of the AP emulators that are on UITK
[09:27] <elopio> the emulators.py needs a ListItem class, or something like that.
[09:28] <elopio> with a swipe_to_delete method.
[09:28] <elopio> iahmad: nerochiaro will know better.
[09:29] <iahmad> elopio, are you not working on emulators anymore?
[09:29] <elopio> iahmad: I am.
[09:29] <iahmad> elopio, ok
[09:29] <elopio> I am almost done with the textfield emulators.
[09:29] <elopio> but that's all I'll have time to do this week.
[09:42] <elfy> balloons: when you are about I've pushed a change to 1300-1302 re Ubuntu One screen - once I know that's ok I'll look at the remaining image testcases
[09:47] <elopio> iahmad: it's done. Want to take a look?
[09:47] <elopio> https://code.launchpad.net/~elopio/ubuntu-ui-toolkit/textfield_emulators/+merge/189796
[10:01] <davmor2_> Morning all
[10:01] <elfy> morning davmor2_
[12:53] <om26er> elopio, hey
[12:54] <om26er> elopio, I implemented the UnlockScreen thing in the UIToolkit a few weeks ago. Who do I need to get it reviewed ?
[13:16] <elopio> om26er: iahmad and somebody from the SDK team.
[13:16] <elopio> I would like to give it a look too.
[13:17] <elopio> om26er: do you have some time to review this one for me? https://code.launchpad.net/~elopio/ubuntu-ui-toolkit/textfield_emulators/+merge/189796
[13:23] <iahmad> elopio, ok will do it shortly
[13:28] <elopio> thanks. iahmad, robotfuel will help writing some emulators too. I think he was working on the slider.
[13:28] <om26er> iahmad, this please https://code.launchpad.net/~om26er/ubuntu-ui-toolkit/screen_unlock/+merge/188289 :)
[13:29] <robotfuel> elopio: iahmad yes, I have the live slider finished, I am working on edge cases for the non-live slider it's more difficult.
[13:29] <iahmad> elopio, ah it seems chrisgagnon is writing emulators too, and slider emulator is in progress
[13:29] <elopio> :)
[13:30] <elopio> iahmad: chrisgagnon is robotfuel. But don't tell anyone, it's his vigilante name.
[13:31] <iahmad> elopio, ah..:)
[13:31] <alesage> was wondering why you never see them in the same place at the same time
[13:32] <robotfuel> elopio: iahmad: I have this one for the button https://code.launchpad.net/~chris.gagnon/ubuntu-ui-toolkit/autopilot-button-emulator/+merge/189703
[13:32] <iahmad> elopio, since robotfuel is on emulatos then it would make sense if he takes care of that slide-to-delete defect as well...:)
[13:33] <iahmad> robotfuel, yes, I saw that this morning, jenkins didn't approve it as all three button emulator tests are failing for all platforms
[13:33] <robotfuel> iahmad: oh? hmm it worked locally. :(
[13:34] <iahmad> robotfuel, http://10.97.0.26:8080/job/generic-mediumtests-runner-maguro/2116/?
[13:35] <iahmad> robotfuel, if tests fail for all platforms there is enough ground to doubt the tests or the implementation...:)
[13:37] <robotfuel> iahmad: ah I see there is no hover on touch
[13:37] <iahmad> robotfuel, in that case you might want to make the test conditional
[13:37] <iahmad> robotfuel, to desktop only
[13:38] <elopio> robotfuel: 27	+ self.pressed.waitfor(False)
[13:38] <elopio> that's wait_for
[13:38] <robotfuel> iahmad: right and not use hover in the press function
[13:40] <iahmad> elopio,     if not clear_button.visible:
[13:40] <iahmad> AttributeError: 'NoneType' object has no attribute 'visible'
[13:40] <iahmad> elopio, this while running the textfield emulator test cases on saucy
[13:41] <elopio> iahmad: I added an objectName to the clear_button, so you will have to remake your modules
[13:41] <elopio> and export the environment variables.
[13:41] <elopio> source export_modules_dir.sh
[13:42] <iahmad> elopio, ok,
[13:43] <elopio> robotfuel: also, on the test case test_button_emulator_release, I would add at the end self.assertEqual(self.button.text, "Click Me! 1")
[13:43] <elopio> the rest I like, thank you!
[13:44] <elopio> I wonder if it's a bug that the phones don't have a hovered.
[13:44] <elopio> if you leave your finger pressing the button, then it's pressed=True and hovered=True, isn't it?
[13:47] <iahmad> elopio, but then what would be the purpose of hover, it will merely have the same states as pressed almost always?
[13:47] <elopio> iahmad: on the phone, yes, the only way to hover is to leave pressed.
[13:47] <elopio> but I'm not sure about this.
[13:47] <elopio> maybe hover means mouse over, but not pressed.
[13:48] <iahmad> elopio, right,
[13:49] <elopio> I was just wondering. A good thing to ask the devs.
[13:49] <elopio> om26er: I have some comments about your branch.
[13:49] <elopio> are you here?
[13:49] <om26er> elopio, Yes I am
[13:49] <elopio> om26er: 30	+class ScreenUnlock(UbuntuUIToolkitEmulatorBase):
[13:50] <elopio> ScreenUnlock is not an object provided by the toolkit.
[13:50] <elopio> so I think it's not right to inherit from UbuntuUIToolkitEmulatorBase.
[13:51] <elopio> actually, that's something that should be on the unity project, in my opinion. Not on the uitoolkit. We should just import it here.
[13:51] <om26er> elopio, I just inherited from there because it was giving the pointing_device I can go with another solution if you suggest
[13:51] <elopio> om26er: yes, I would duplicate the pointing_device code, and inherit from object.
[13:51] <om26er> elopio, for that first we have to depend all the apps on unity8-autopilot.
[13:52] <elopio> om26er: I think that's the current scenario. I think it's bad, but as long as jenkins can't give us a unity without a greeter, we are stuck with that case.
[13:52] <elopio> so making it explicit on the dependencies is a good thing.
[13:54] <om26er> elopio, right. I'll look a bit into unity8 autopilot tree and see where to put this. It may just work there as is.
[13:54] <elopio> om26er: yes. I have some other random PITA comments. Are you with patience for me today? :)
[13:55] <om26er> elopio, sure.
[13:55] <om26er> l)
[13:55] <om26er> ;)
[13:55] <elopio> 83	+ print("Could not find autopilot interface for unity8 "
[13:55] <elopio> I got your comment, but we should never ever print something. Always use logging.
[13:56] <elopio> there are cases where we want the run to be the less verbose possible. For that, the default runner only prints a letter per test.
[13:56] <om26er> elopio, I think people will just ctrl+c believing nothing is happening
[13:56] <elopio> so if you print something, it will be ugly.
[13:56] <om26er> elopio, its only printed once in a test suite because that code path is only executed when there is no autopilot interface for unity8
[13:56] <elopio> om26er: yes, but those people should run the tests with -v if they want to keep track of what's going on
[13:57] <om26er> which is probably once per device, till its flashed
[13:57] <elopio> om26er: Corey was changing the autopilot runner to use the default text runner. And we have a logging method on autopilot 1.4. Both things will make it a lot nicer when you put things on the log, instead of printing them directly.
[13:57] <om26er> elopio, I used the logger in my first implementation then removed its use on purpose.
[13:58] <elopio> om26er: yes, I see that from your comment. I think you are right assuming that people will think it's stuck, but for that we need better logging, instead of skipping logging :)
[14:00] <om26er> well thats debatable. from the normal docs that we provide people to run their autopilot tests, we don't ask them to run with -v... the point is its not always going to be us who is running those tests. there are other people, in many cases someone who is running a test for the first time
[14:00] <om26er> or even using autopilot for the first time ?
[14:01] <elopio> om26er: yes, for them the default logging should be at the info level.
[14:01] <om26er> elopio, ok, don't have much clue about new logging in 1.4. So I think the first step for me would be to move the code over to unity8, we can discuss things further in that MR
[14:01] <elopio> there should be an option to change the logging level to debug, to error, or to warn, to get less output, or to be completely silent. But that's only configurable if we use logging everywhere, no prints.
[14:02] <elopio> om26er:
[14:02] <elopio> 76	+ if unity8:
[14:02] <elopio> 77	+ pass
[14:02] <elopio> I think that does nothing, right?
[14:02] <elopio> you can remove that code with the same result.
[14:03] <om26er> elopio, right, I actually have a better solution for that, which I am using elsewhere in camera-app integration test. I;ll port that over
[14:04] <om26er> I am going to just move the stuff in _get_unity8_autopilot() over to unlock_screen()
[14:04] <elopio> om26er: about the test case 156	+class TestScreenUnlock(tests.ScreenUnlockTestCase):
[14:05] <elopio> it's complex. There are many ways to make it clearer. That's what the book thomi mentioned on the sprint is about. Clean Code, by Robert Martin.
[14:05] <elopio> totally recommended :)
[14:05] <elopio> I'll try to clean it a little so you see the difference.
[14:08] <elopio> actually, I think that the problem is that the ScreenUnlockTestCase is not needed. We will be good enough with the ScreenUnlock class.
[14:08] <elopio> and it will be a lot easier to test that class than the test case.
[14:12] <om26er> elopio, cool, that makes code simpler, if you say.
[14:12] <om26er> and less
[14:13] <elopio> om26er: yes. And generally it's a bad idea to use inheritance on the test cases. It's hard to understand what the parent classes set up do.
[14:13] <elopio> we found a lot better to use python-fixtures
[14:13] <elopio> that will come with autopilot 1.4 too. So the object can be wrapped in a fixture, and it will look really pretty.
[14:27] <sergiusens> balloons, can you take care of this one? https://code.launchpad.net/~sergiusens/ubuntu-calendar-app/click_fixes/+merge/189865
[14:45] <balloons> sergiusens, done
[14:45] <sergiusens> balloons, thanks!
[15:15] <elopio> I hate that when I receive a message on the phone, it sounds just like when I receive one on the desktop
[15:16] <elopio> I switch through all the open windows looking for a message, until I realize it's the phone. It has been like this for two weeks.
[15:18] <jfunk> ping rhuddie - you around?
[15:18] <rhuddie> jfunk, sure
[15:19] <jfunk> can you reproduce - bug 1235263 - and see if there is a crash there? the powers that be would like to know
[15:20] <rhuddie> jfunk, sure I'll try that
[15:21] <jfunk> rhuddie, do you look for crashes when you find bugs?
[15:24] <rhuddie> jfunk, yes I have, but often difficult to narrow down cause or reproduce. I'll check this one again.
[15:26] <jfunk> cool
[15:34] <jfunk> nuclearbob, my name is off the list - looks like your fix worked :)
[15:35] <nuclearbob> jfunk: rad.  I guess it must be running faster now too if it's already done
[15:36] <rhuddie> jfunk, yes there is crash files for gallery and unity8
[15:43] <jfunk> rhuddie, can you add them to the bug report?
[15:44] <rhuddie> jfunk, sure
[15:55] <rhuddie> jfunk, done
[16:30] <dkessel> good evening
[16:37] <alesage> is there a phablet-tools command to "revert to a clean image"?
[16:37]  * alesage goes to rtfm
[16:46] <balloons> evening dkessel, how are you?
[16:46] <dkessel> hey balloons, i am fine thanks :) how are you?
[16:47] <dkessel> remembered the other day that i have this xchat icon on my screen...
[16:47] <balloons> :-) I'm doing quite well
[16:48] <davmor2> ubuntu-qa can someone on a mir running phone use the camera and let me know if it shows photos taken in the usermetrics on the welcome screen please
[16:49] <om26er> davmor2, didn't update for me
[16:49] <om26er> davmor2, it was showing 8 photos taken today, I took 2 more, still shows 8
[16:49] <davmor2> om26er: I'll write a bug
[16:49] <balloons> davmor2, correct, no updates for me
[16:50] <davmor2> balloons: om26er thanks it works in SF so definitely a mir issue woohoo!
[16:52] <om26er> davmor2, the information is updated once I restarted my phone btw
[16:54] <jfunk> ping ubuntu-qa is there a bug already for the time/usermetrics not updating before displaying the screen?  Ie. phone sleeps overnight, shows the same time and calls made as yesterday
[16:55] <dkessel> is today a good day to upgrade my raring to saucy? any showstopper bugs?
[16:56] <jpds> dkessel: You tell us.
[16:56] <om26er> jfunk, I don't think there is a bug. davmor2 just asked for verification of that issue.
[16:56] <dkessel> jpds :p
[16:56] <om26er> I'll report
[16:57] <davmor2> om26er: thanks
[16:57] <om26er> davmor2, I am going for unity8 first. I think the greeter changes might have caused that (?)
[16:58] <davmor2> om26er: works fine on SF
[16:58] <om26er> davmor2, yeah, I think unity8 will need to do something about that.
[16:59] <davmor2> om26er: libusermetrics might be better than unity8 and hen add mir to the bug
[17:00] <davmor2> om26er: although I guess unity8 is all incompassing ;)
[17:01] <jfunk> om26er, davmor2 - I notice that if I wake the phone and sleep it when it wakes up again, it's been updated - davmor2  you see the same hting>?'
[17:01] <jfunk> om26er, did it update to 10 photos after wake/sleep/wajke
[17:02] <om26er> jfunk, I had to reboot to see the updates. I am now trying the sleep thing you suggested
[17:02] <jfunk> om26er, because specifically for time, the two clocks area out of sync until the method I mentioned above
[17:03] <om26er> jfunk, the greeter time and top panel time being out of sync is already reported
[17:04] <davmor2> jfunk: no updates for me
[17:05] <om26er> davmor2, jfunk restarting unity8 updates them. So bug in unity8
[17:06] <davmor2> om26er: restarting unity8 on mir also restarts mir though ;)
[17:06] <jfunk> alesage, are you seeing crashes in the System Settings
[17:07] <alesage> jfunk nothing new today
[17:07] <om26er> davmor2, right, but we should aim for a higher level component than Mir :)
[17:07] <alesage> jfunk, what do you see?
[17:09] <jfunk> alesage, when I use the top indicators to change the settings I am crashing left right and center
[17:09] <om26er> davmor2, bug 1236960
[17:10] <alesage> jfunk note that there is no location settings, that may be causing a cascade
[17:10] <jfunk> om26er, davmor2 - is the defect only visible in mir?
[17:10]  * alesage digs up that bug
[17:10] <davmor2> jfunk: yeap
[17:11] <jfunk> alesage, is there a defect for location settings somewhere?
[17:11] <cgoldberg> no interwebz from home... i'm about ready to strangle Comcast
[17:11] <alesage> jfunk, /me believes so, is looking
[17:11] <jfunk> davmor2, om26er - if it's not visible in SF, please also affects Mir project
[17:11] <om26er> jfunk, davmor2 its duplicate of bug 1234904 I have been told.
[17:12] <om26er> fix is on the way. needs-review only
[17:12] <alesage> jfunk, https://bugs.launchpad.net/indicator-location/+bug/1234975
[17:13] <davmor2> wow that got duped with uber speed
[17:14] <jfunk> davmor2, good
[17:21] <om26er> that was a result of a direct ping :p
[17:23] <jfunk> alesage, can you confirm that trying to set the location settings causes a crash
[17:24] <alesage> jfunk, confirmed: trying to open location settings from the location indicator causes ubuntu-system-settings to crash, just updated that bug
[17:25] <jfunk> alesage, can you set it to critical
[17:25] <jfunk> alesage, and also see if it is the same in SF
[17:26] <alesage> ok jfunk shall test, discovered pre-mir but will confirm
[17:26] <jfunk> alesage, so you confirmed on SF?  I can confirm on Mir
[17:27] <alesage> jfunk, will confirm on SF now
[17:27] <jfunk> Mako / Mir = crash
[17:30] <jfunk> alesage, would you be so kind as to upload the crash reports to the defect as well plz
[17:30] <alesage> jfunk ok shall do
[17:33] <jfunk> alesage, looks like Mir only to me
[17:33] <jfunk> nm, nope, it's just more severe on Mir
[17:34] <jfunk> in SF it look slike U8 comes back up right away after a short blank
[17:34] <alesage> jfunk interesting--yes right it's in SF too, I don't get a crashfile there though
[17:40] <alesage> jfunk otherwise I'm only able to open settings inconsistently from indicators, trying to get it repeatable, but not seeing other crashes
[17:47] <jfunk> nuclearbob, how goes it?
[17:51] <cgoldberg> rfowler, ping.. any idea if you lost internet service at your house since this morning?  do you have comcast/xfinity?
[17:51] <rfowler> cgoldberg: around what time?
[17:52] <rfowler> cgoldberg: i've been in lex
[17:52] <rfowler> cgoldberg: and I have comcast business
[17:52] <cgoldberg> rfowler, mine went out at 9:30 AM and still isn't back... comcast says there is a problem in the area..   I'm working at Oficio on newbury
[17:55] <rfowler> cgoldberg: hmm... i can ping my gateway
[17:58] <cgoldberg> rfowler, with my luck it's just on this side of dartmouth... at dartmouth/newbury they have the street closed and the road all torn up.. im betting that's the prob
[17:58] <rfowler> cgoldberg: by the parking lot?
[17:59] <rfowler> cgoldberg: i lost count of how many times i've seen them rip up that intersection
[18:00] <cgoldberg> rfowler, yea
[18:01] <cgoldberg> unfortunately, i think my interwebz run under there :/
[18:25] <phillw> rfowler: get a payg 3G dongle, no price plan, just pop 10 quid on it for 1 GB of data when the need arises (I use mine once ~ 4 weeks when I go with parents to little 'sea-side' house' )
[18:33] <phillw> sorry, meant that for cgoldberg ^^
[18:34] <cgoldberg> phillw, i do need a backup 3g.. but they make it hard here in the USA.. we're all slaves of the large telcos and carriers
[18:36] <phillw> cgoldberg: let me ask a friend of mine over there, he works/ed for a couple of different i/net companies over there :)
[18:37] <cgoldberg> phillw,  id love a mifi modem... with no contract.. just pay per megabyte used.... but nothing I know of like that exists here.
[18:38] <cgoldberg> i love how easy it was to get a data plan in UK.. id have like 5 backups if I lived there :)
[18:40] <balloons> doug5, woot! Time to merge :-)
[18:40] <jfunk> nuclearbob, and ubuntu-qa - do you think it's better to filter based on when the defects were entered, or when they were 'last-updated' in terms of "last week" "last day" etc
[18:40] <phillw> cgoldberg: is http://www.engadget.com/2012/04/18/att-announces-new-gophone-data-packages/ of no use to you? I'm just browsing what UK people are advised to use :)
[18:41] <doug5> balloons, finally! my first merge, sigh...sigh...
[18:41] <nuclearbob> jfunk: last updated will give us more movement info, but it also may give us too much info if bugs are being updated without a          lot of movement
[18:42] <cgoldberg> phillw, perhaps.. i do hate AT&T though.  but thanks ill look whats available
[18:43] <davmor2> cgoldberg: get an open wrt based modem with a usb connector you get a usb 3g dongle plug it in and switch, you can ask popey for more info :) and bigcalm on #ubuntu-uk :D
[18:43] <jfunk> nuclearbob, perhaps we can do a trial run with both, side-by-side and see which one makes more sense in the long run?
[18:44] <davmor2> jfunk: you need a when defect is logged and last touched I'd of thought.  Defect logged to know how long a fix took, last touched so you know what is happening with the bug
[18:45] <jfunk> davmor2, this is specifically a filter, for instance, if we want to see bugs that were touched in the last day
[18:46] <cgoldberg> doug5, congrats on first merge!   :)
[18:47] <davmor2> jfunk: I'd of thought that last touched is the most important then.  It helps for knowing what is happening with the bug when a bug needs more info etc
[18:48] <doug5> cgoldberg, thanks! :-)
[18:48] <jfunk> davmor2, we have 'incomplete' which is the status that devs give when the bug needs more info
[18:49] <jfunk> davmor2, sometimes I like to see what new bugs came in from the last day, without seeing all the excess information
[18:49] <jfunk> davmor2, perhaps you can help nuclearbob with a list of projects from Online Services that aren't currently listed in the report
[18:52] <davmor2> jfunk: who will be using the dash board predominately I would tailor it to their needs the most.
[18:52] <davmor2> nuclearbob: I don't know all the projects this might help though https://launchpad.net/ubuntuone
[18:53] <nuclearbob> davmor2: if all the projects you want are subprojects of that, then that's easy and I can use that
[18:54] <davmor2> nuclearbob: that is a full list of all the projects that I know of I'll have a dig around and see if there are any missing for you though
[18:55] <jfunk> nuclearbob, davmor2 - Pay / SSO?
[18:55] <davmor2> jfunk: listed in that lot
[18:56] <davmor2> jfunk: I think the only ones that might not be are a couple of the brand new projects
[18:56] <nuclearbob> davmor2: I'm getting 5 bugs tagged with qa-touch under those projects.  Does that sound like a reasonable number, or do you think I'm missing some?
[18:57] <nuclearbob> right now I'm just asking the api for the ubuntuone project, but I can ask it for all of those individual projects if necessary
[18:57] <davmor2> nuclearbob: no that is about right, on touch there is only UOA and SmartScopes currently I think
[18:58] <nuclearbob> davmor2: okay, this will be relatively easy to implement.  I'll let you know when I've got something readiiiiiiiier
[18:58] <davmor2> oh and click of course
[18:58] <nuclearbob> er, readier
[18:58] <nuclearbob> synergy is doing weird things with key repeat
[18:59] <jfunk> davmor2, I think elopio is working with nuclearbob on the click projects into the list
[19:14] <alesage> finding that apps marked with a red x in Recent Apps are always marked, so one can't tap to re-open 'em, wonder if we think this is a design bug, e.g.?
[19:14] <alesage> e.g. start with 2 and kill one
[19:14] <alesage> maybe this is already documented somewheres
[19:22] <davmor2> alesage: press and hold again?
[19:23] <davmor2> alesage: long press enables the cross to kill apps, long press again disables it
[19:23] <alesage> davmor2, aha I learned something
[19:24] <alesage> surprised on mir as you're navigated away from the recent apps view to the most recent active app, returning they're still marked; makes sense though thx
[19:57] <PESHuk> testing install of entire disc desktop i386 saucy
[20:07] <alesage> gah! trapped in the messaging app
[20:25] <elopio> veebers: do you have an idea of how hard would it be to get unity running without a greeter for the jenkins tests?
[20:25] <elopio> well, for the non-unity jenkins tests.
[20:28] <veebers> elopio: no I don't know sorry , I'll ask if Saviq is still around or find out otherwise
[20:29] <elopio> veebers: I think it will be very important after the release to make sure our tests run isolated. And unity seems to be the biggest blocker there. Maybe we can just set up a call in two weeks.
[20:32] <veebers> elopio: Makes sense. I've asked saviq in ubuntu-unity but can't promise an answer anytime soon.
[20:36] <letozaf> balloons, Hello
[20:40] <balloons> letozaf, hello!
[20:41] <letozaf> balloons, I have almost finished another test for rssreader-app but I have a weired error : http://paste.ubuntu.com/6210990/
[20:41] <letozaf> balloons, I was wondering if you could help understand what it could be
[20:42] <letozaf> balloons, if you got time
[20:42] <letozaf> balloons, the test is here: https://code.launchpad.net/~carla-sella/ubuntu-rssreader-app/edit-topic-test
[20:43] <letozaf> balloons, this error has no sense for me, code looks fine
[20:53] <balloons> letozaf, let me look
[20:53] <letozaf> balloons, thanks
[20:54] <balloons> letozaf, looks straightforward enough :-)
[20:54] <letozaf> balloons, :O
[20:54] <balloons> what is canonicalfeed?
[20:54] <balloons> are you wanting to make sure it's not blank?
[20:54] <balloons> self.assertFalse(not canonicalFeed)
[20:55] <letozaf> balloons, :) thanks I will try it
[20:56] <balloons> letozaf, that's from my brain, fair warning
[20:56] <balloons> as in not tested :-p
[20:56] <letozaf> balloons, well at least you have an idea of the problem ! I don't
[20:56] <letozaf> balloons, :p
[21:00] <letozaf> balloons, looks like your solution works but got another error, but I will try to fix it on my own thanks (at least I hope :p)
[21:01] <balloons> letozaf, glad it worked.. heh surprised myself
[21:01] <letozaf> balloons, :D
[21:01] <balloons> feel free to share whatever other issues you encounter
[21:01] <letozaf> balloons, ok thanks
[21:01] <letozaf> balloons, going to bed now see you tomorrow :D
[21:01] <balloons> ciao letozaf
[21:02]  * balloons needs to learn to say see you later
[21:02] <letozaf> balloons, ciao
[21:02] <letozaf> balloons, ci vediamo piu' tardi
[21:02] <balloons> hehe.. that's alot to remember.. I shall try
[21:02] <letozaf> balloons, or ci vediamo domani (see you tomorrow)
[21:02] <letozaf> balloons, :D
[21:02] <balloons> ci vediamo domani
[21:02] <balloons> much easier :-)
[21:03] <letozaf> balloons, yes good night :D