[00:08] <cnd> yeah
[00:08] <cnd> I only branched because of the multiarch issue
[00:08] <cnd> I haven't branched the other projects
[10:05] <dandrader> tvoss, morning
[10:06] <tvoss> dandrader, morning :)
[10:06] <dandrader> have you played with Unity's autopilot already?
[10:06] <tvoss> dandrader, a little bit, but no serious result yet
[10:07] <tvoss> dandrader, tried to prototype a class MultiTouchDevice in X11.py, like lamalex suggested yesterday
[10:07] <dandrader> tvoss, I found it a bit fragile. When I run, a good number of tests failed
[10:07] <tvoss> dandrader, did you look into autopilot yet?
[10:08] <tvoss> dandrader, I think thomi sent around an email in the morning that mentioned failing autopilot tests
[10:09] <dandrader> quite hard to make this kind of tests reliable, there are just so many variables. running from within a virtual machine with a pristine ubuntu installation might be "a must" for running it...
[10:10] <dandrader> on the other hand it's quite neat to see the whole UI moving by itself, showing and hiding launcher, dash, etc :)
[10:10] <dandrader> hmm... good to know
[10:18] <tvoss> dandrader, yeah, it's a pretty cool technology
[10:19] <tvoss> dandrader, are you planning on looking further into autopilot? I have pretty much stuff on my plate regarding chromium patch and jenkins maintenance
[10:22] <dandrader> I have to provide some testing for the utouch stuff there one way or another, since I have two bug fixes that have been blocked because they are missing tests
[10:23] <dandrader> but first I will invest some time in figuring out the feasibility of making unit tests
[10:24] <dandrader> I fear the headaches that might come from autopilot (many dependencies)
[10:38] <tvoss> dandrader, ack ... unity already uses google test
[10:38] <dandrader> yes
[12:19] <Satoris> Someone want to test this: lp:~jpakkane/arsenal/utouch-bug-script
[12:19] <Satoris> Run the file scripts/get_touch_bugs.py and redirect stdout to an HTML file.
[12:34] <Satoris> Are three and four finger actions broken for anyone else?
[12:44] <dandrader> Satoris, they were working last time I tried
[12:44] <dandrader> that was last Friday. But I'm using lp:trunk versions of utouch-* and not stuff from repositories
[12:46] <Satoris> I use the daily build PPA, which should be the same.
[12:48] <Satoris> Three and four finger touches come to applications, but two finger touches disappear somewhere.
[12:48] <Satoris> Even though I have disabled all scrolling thingies.
[12:51] <dandrader> Satoris, one thing you could do is removing synaptics xorg driver and see if you get the two-touches events
[12:51] <dandrader> that would confirm the culprit at least
[12:52] <Satoris> But doesn't that driver read the evemu interface? Without it there should be no mouse/touch events at all.
[13:01] <bregma> I believe both synaptics and evemu use the /dev/input interface
[13:02] <bregma> I mean evdev, not evemu
[13:02] <Satoris> There is a plain evdev driver for X now?
[13:02] <bregma> although evemu also uses the /dev/input interface
[13:03] <bregma> there has been for a few releases now
[13:03] <bregma> it's what gets used for touchscreens
[13:03] <bregma> it can also be used for touchpads, but we don;t normally recommend it
[13:03] <bregma> because it won;t work the way WIn 95 and Mac OS users expect
[13:04] <Satoris> Ok, I see it. Is there a way to blacklist the Synaptics driver or does one have to uninstall the package?
[13:04] <bregma> you can blacklist the synaptivs driver usiing fancy config scripts in, um, some /var/lib directory somewhere....
[13:05] <bregma> /usr/share/X11/xorg.conf.d
[13:05] <bregma> see, /var/lib
[13:08] <Satoris> It does not seem to have anything X or evdev related ...
[13:27] <Satoris> Changing the input driver from synaptics to evdev causes all touches disappear.
[13:28] <Satoris> Changing it back made touches work.
[13:29] <Satoris> Gestures, too.
[13:31] <Satoris> This does not make ANY SENSE. <o>
[13:34] <bregma> dark magic?
[13:34] <bregma> blood magic?
[13:35] <Satoris> I think this calls for magic written with a 'k'.
[13:35] <bregma> restarting X to pick up new shared libraries?
[13:35] <Satoris> By which I mean magick.
[13:36] <Satoris> In theory, yes. But the old X used the old libraries, which were working fine yesterday.
[13:54]  * tvoss will miss the standup today, ps-qa meeting
[14:06] <cnd> tvoss, when you have a chance, just pop in to let us know how things are going and what you're up to
[14:06] <cnd> Satoris, I don't have any issues with trackpad 3 and 4 touch gestures
[14:07] <cnd> four touch gestures should always work, no matter what settings you have
[14:11] <Satoris> The properties reported by xinput were strangely out of whack when the gestures were broken. Fiddling with them did not help. They are ok now, though.
[14:11] <cnd> interesting
[14:11] <cnd> Satoris, are you running the standard desktop with gnome-control-center, gnome-settings-daemon?
[14:12] <Satoris> As it comes out of the box, yes.
[14:13] <Satoris> Shared library wackiness is the most probable explanation, methinks.
[14:13] <cnd> huh
[14:13] <cnd> Satoris, I just tried your script
[14:13] <cnd> it looks pretty good!
[14:14] <cnd> I think all the data is there
[14:14] <cnd> it could be cleaned up visually, table borders and headers, etc.
[14:14] <cnd> but it'll be a great help
[14:14] <Satoris> The API differences between launchpadlib and the helper lib thingie are minimal. The only difference seems to be how you get the launchpad object.
[14:14] <cnd> it's already found lots of bugs I didn't know existed :)
[14:15] <cnd> ok
[14:15] <Satoris> Which made me suspect that one of them was deprecated.
[14:15]  * bregma stands up, scratches his arm, and yawns
[14:15] <cnd> heh
[14:15] <cnd> I'm going to be proposing a fix for bug 972012: Touchscreen touches are not rejected until they end
[14:16] <cnd> then probably weeding bugs from the new bug list that Satoris has created
[14:17] <Satoris> Made the script. Then I fought the X, and the X won.
[14:17] <bregma> I'm seeing q few memory leaks when running the geis testsuite, I'm hoping they're poorly written test cases, but I want these to run clean, so.....
[14:17] <bregma> I shot the sherriff
[14:17] <cnd> dandrader|lunch, standups :)
[14:18] <bregma> I'm trying to do a dist-upgrade in the background and it's giving me a time-to-copletion estimate of between 4 hours and 9 days, depending on when I look
[14:18] <cnd> ugh
[14:18] <bregma> right now it's down to 1 hour 15 minutes
[14:18] <Satoris> I strongly suggest having someone else do the CSSification of the bug list. I haven't done it in ages, so the end result probably won't be all that spectacular.
[14:19] <cnd> Satoris, hopefully we can reuse an existing template?
[14:19] <cnd> and change it slightly as needed?
[14:20] <Satoris> The "templates" in Arsenal are mostly test thingies rather than production. Most scripts just do their own thing, some with Gnuplot, even.
[14:20] <cnd> hmm
[14:20] <Satoris> Plus if there is not a template for the exact layout we have, it has to be recreated anyway.
[14:26] <Satoris> And the test templates are very problem specific, such as bugs-by-team.mako.
[14:27] <Satoris> They seem to be doing some sort of a JSON data transfer thingie of which I'm not entirely sure what it does.
[14:28] <cnd> ok
[14:30] <cnd> Satoris, I would love it if we could get a nice list like: http://reports.qa.ubuntu.com/reports/kernel-bugs/reports/_kernel_hot_.html
[14:30] <Satoris> Since (not all of) their scripts are not in Python, this is probably just a way to get data from one place to another rather than just using Genshi directly.
[14:32] <Satoris> Well, I _can_ do it, but someone with Web experience probably would get it done faster. Just sayin'.
[14:32] <cnd> dandrader|lunch, bregma: I just pushed a couple MPs for grail
[14:33] <cnd> biab
[14:33] <Satoris> cnd: leaving now, Skype later?
[14:33] <cnd> Satoris, sure
[14:33] <Satoris> Ok. Bye.
[14:36] <bregma> 22h 59min 27s
[14:37] <bregma> 5d 14h 6min 19s
[14:38] <bregma> I think I'm overloading a local network node or something
[14:39] <tvoss> hey folks
[14:40] <bregma> 8d 9h 10min 7s
[14:40] <tvoss> working on chromium patch set, helping out with various jenkins tasks
[14:42] <tvoss> dived into autopilot today a little mor
[14:42] <tvoss> e
[14:42] <tvoss> but no definite result, yet
[14:46] <dandrader> damn, missed the stand up.
[14:46] <dandrader> I'm working on a unit test for GestureEngine in unity
[14:47] <dandrader> for bugs https://code.launchpad.net/~dandrader/unity/lp940612 and https://code.launchpad.net/~dandrader/unity/lp969554
[16:00] <tvoss> cnd, hangout?
[16:00] <cnd> sure
[16:00] <cnd> one sec
[16:00] <tvoss> cnd, ack :)
[16:02] <cnd> tvoss, did you get an invite?
[16:02] <tvoss> cnd, no
[16:02] <cnd> hmm
[16:02] <tvoss> cnd, let me try
[16:02] <cnd> k
[17:55] <tvoss> cnd, pint
[17:55] <tvoss> s/t/g
[17:55] <cnd> pong
[17:56] <tvoss> regarding the virtual d'tor: I think every test reyling on a a custom fixture inherits the fixture
[17:56] <tvoss> iirc
[17:57] <cnd> oh right
[17:57] <cnd> didn't think of that
[17:57] <tvoss> should we put it in the comment on the mp for reference?
[17:57] <cnd> I forgot about the distinction between the test class and the fixture class
[17:57] <cnd> I'll do it
[17:57] <cnd> thanks
[17:58] <tvoss> np, happy to approve with that changes
[18:05] <cnd> tvoss, so I did some more reading
[18:05] <cnd> and the virtual destructor doesn't need to be specified if you are deriving from a base class that already has one
[18:05] <cnd> which testing::Test does
[18:05] <tvoss> ah, like a transitive virtual d'tor?
[18:06] <cnd> I guess
[18:06] <cnd> http://www.parashift.com/c++-faq-lite/virtual-functions.html#faq-20.7
[18:06] <cnd> it might also explain why it wasn't necessary in any of the other tests
[18:07] <tvoss>  yeah, wasn't aware that it is transitive, thanks for the hint :)
[18:11] <cnd> tvoss, I pushed the subscription deletion change to the test branch
[18:12] <cnd> and commented on the fix branch
[18:12] <tvoss> makes sense. Do I just need to approve the test branch then?
[18:13] <tvoss> ah, got it ... already approved
[18:13] <cnd> yay
[18:13] <tvoss> cool
[18:21] <bregma> woo-hoo, I'm back
[18:22] <bregma> seems my ISP was having some network troubles, or something
[18:34] <cnd> bregma, are you all updated too?
[18:35] <bregma> as of a few hours ago, yes
[18:35] <bregma> I have about 16 kernels I need to purge
[18:35] <cnd> dandrader, bregma: still looking for a review of: https://code.launchpad.net/~chasedouglas/utouch-grail/fix-hold-reject/+merge/100621
[18:35] <cnd> heh
[18:35] <cnd> I'm going to cut a new release of grail after it's merged