[03:27] <cnd> bryceh, have you and RAOF looked into gtest?
[03:27] <cnd> I'm looking at your unit tests for xrandr-utils
[03:27] <RAOF> Which one is gtest?
[03:27] <cnd> RAOF, google-test
[03:27] <cnd> I'm in love with it
[03:27] <RAOF> Ah, ok.  That one.
[03:27] <cnd> just thought I'd mention it
[03:27] <RAOF> I'm not really familiar with it.  What does it do to make you fall in love with it?
[03:28] <cnd> it's based on c++, which means test environments, fixtures, and such can all be managed in a hierarchical way
[03:28] <cnd> and you don't have to write a main() or register any test cases
[03:28]  * RAOF sees that it's written in C++, which may result in madness.
[03:29] <cnd> RAOF, you can check out xorg-gtest, which we posted to xorg-devel today
[03:29] <RAOF> Hm.  How does automatic test-case detection work in a language with no introspection?
[03:29] <cnd> we're using it in utouch-frame
[03:29] <cnd> RAOF, magic?
[03:29] <RAOF> Aieee.
[03:29] <cnd> RAOF, check out http://people.freedesktop.org/~cndougla/xorg-gtest/
[03:30] <cnd> look at the example
[03:30] <cnd> that's literally all you need to code if you want to have something that builds and tests
[03:30] <cnd> there's no other code that has to be written
[03:31] <RAOF> That looks like something that could indeed be useful.
[03:31] <RAOF> We should really get rid of the "need to be root" bit, there.
[03:32] <cnd> RAOF, I don't think it's possible if you want to fire up an Xorg server
[03:32] <RAOF> It should be possible with the dummy drivers, but it isn't at the moment.
[03:32] <cnd> because any config file you specify must be in /etc/X11 or /usr/share/X11/xorg.conf.d, *unless* you are root
[03:32] <cnd> yeah, that's true
[03:33] <cnd> it still doesn't help us for the touch team because we need to use uinput to replay device events
[03:33] <cnd> which requires root to interact with the kernel
[03:33] <cnd> but I'm not really suggesting that xorg-gtest would be worth your while as-is
[03:34] <cnd> because the dummy video driver probably won't get you very far with xrandr
[03:34] <cnd> but gtest in general is going to be much better than rolling your own
[03:34] <cnd> I was skeptical at how much better it could make my life, but I really love it after having developed tests and frameworks with it
[03:35] <RAOF> Yeah, I'm a big fan of not rolling my own.
[03:36] <RAOF> Actually, aren't there patches to enable xrandr on the dummy driver?
[03:36] <cnd> I wouldn't know
[03:36] <cnd> if there were, then xorg-gtest would be perfect :)
[03:36] <RAOF> The documentation there also suggests that it can hook you up with an existing X11 server, which would be the next best thing.
[03:36] <cnd> yeah
[03:37] <cnd> by default when you run tests with --no-dummy-server it will use $DISPLAY
[03:38] <cnd> and I suppose --no-dummy-server can be used when not root
[03:38] <cnd> anyways, time to eat dinner and stop working!
[03:38] <cnd> back tomorrow!
[03:41] <RAOF> :)
[05:04] <bryceh> cnd, interesting.  I'm trying to keep xrandr-utils close to X standard practices; what I've got in there parallels the xserver test suite
[05:04] <bryceh> I like C++ myself but know keithp is not a fan.
[05:06] <bryceh> heya RAOF, btw I tossed the xrandr-utils patches up on xorg-devel@ a couple hours ago; thanks for your review earlier, I took out that perl test.
[05:07] <RAOF> bryceh: Sweet; I'll throw some reviewed-by tags your way.
[05:09] <bryceh> RAOF, thanks!
[05:10] <bryceh> I had another chance today to learn just how much git rebase kicks ass
[05:11] <RAOF> Sometimes your own :)
[05:23] <tjaalton> RAOF: cool, I'll give it a go today :)
[05:24] <RAOF> tjaalton: It seems to do weird things to wine; I'll be interested to see if you also notice that.
[05:24] <tjaalton> after going through the xmas shopping mayhem..
[05:24] <tjaalton> ah, does wine work on amd64 currently?
[05:27] <RAOF> You can't install ia32-libs-multiarch, but equivs will let you install ia32-libs which will let you install wine.  Then it's just a matter of hunting down libfoo:i386 :)
[05:35] <tjaalton> ugh, ok
[06:11] <bryceh> RAOF, I stuck the ppa on a radeon box.  Boots to the ubuntu logo, shows a mouse cursor, but no greeter
[06:12] <RAOF> Huh.  Odd.
[06:12] <RAOF> Anything interesting in the logs?
[06:12] <bryceh> bryce@dorset:~$ apt-cache policy lightdm-gtk-greeter 
[06:12] <bryceh> lightdm-gtk-greeter:
[06:12] <bryceh>   Installed: (none)
[06:12] <bryceh>   Candidate: 1.0.6-0ubuntu4
[06:12] <RAOF> Heh.
[06:12] <RAOF> Oh, no.  You're after unity-greeter rather than lightdm-gtk-greeter.
[06:13] <bryceh> ah right  $ apt-cache policy unity-greeter
[06:13] <bryceh> unity-greeter:
[06:13] <bryceh>   Installed: 0.1.1-0ubuntu1
[06:13] <bryceh>   Candidate: 0.1.1-0ubuntu1
[06:14] <bryceh> skimming through logs... nothing interesting so far
[06:14] <cnd> bryceh, are you becoming a git convert?
[06:14] <bryceh> root@dorset:/var/log/lightdm# more x-0-greeter.log 
[06:14] <bryceh> (unity-greeter:1864): Gtk-WARNING **: cannot open display: :0
[06:15] <bryceh> ah, potentially I had fglrx installed
[06:15] <RAOF> Ah.  I haven't uploaded an fglrx to the ppa.
[06:15] <bryceh> hmm, no evidence so far
[06:16] <RAOF> There's a new -ati in there (I think); I may have bollocksed that up.
[06:20] <bryceh> xserver-xorg-video-ati:
[06:20] <bryceh>   Installed: 1:6.14.99~git20111219.aacbd629-0ubuntu1
[06:20] <bryceh>   Candidate: 1:6.14.99~git20111219.aacbd629-0ubuntu1
[06:22] <RAOF> Yeah, that's a newer snapshot than in the main archive.
[06:23] <RAOF> Which should be fine.  :)
[06:23] <bryceh> yeah it feels like X is basically ok, it's just the greeter is refusing to do its thing
[06:24] <bryceh> actually when I restart lightdm I see a brief glimpse of my desktop
[06:25] <bryceh> then it comes back to a black screen with movable mouse cursor.
[06:26] <bryceh> switching to vt1 and back to vt7 gives me the console text with mouse cursor.  maybe something's not painting
[06:26] <bryceh> [  914.068497] lightdm[915]: segfault at aaaaaaae ip 08051ee8 sp bff44560 error 4 in lightdm[8048000+28000]
[06:26] <bryceh> [  914.070871] init: lightdm main process (915) killed by SEGV signal
[06:26] <bryceh> ooh
[06:27] <bryceh> hmm that might be irrelevant though
[06:27] <bryceh> root@dorset:/var/log# ps aux | grep lightdm
[06:27] <bryceh> root      2684  0.0  0.1  40844  3540 ?        Ssl  22:24   0:00 lightdm
[06:27] <bryceh> root      2688  0.6  1.8  63240 38320 tty7     Ss+  22:24   0:01 /usr/bin/X :0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
[06:30] <bryceh> ah the lightdm segfault occurs when restarting the service
[06:31] <bryceh> Dec 21 22:30:11 dorset kernel: [ 1274.512212] type=1400 audit(1324535411.385:27): apparmor="DENIED" operation="open" parent=1 profile="/usr/lib/telepathy/mission-control-5" name="/home/bryce/.cache/dconf/user" pid=3445 comm="mission-control" requested_mask="rwc" denied_mask="rwc" fsuid=1000 ouid=1000
[06:31] <bryceh> wonder if that's relevant
[06:35] <RAOF> That's empathy being denied access to dconf; I should report that bug.
[06:36] <RAOF> It does, however, indicate that you appear to have made it all the way through to your session.
[06:36] <bryceh> yeah
[06:36] <bryceh> this is what is printed to syslog when I do a sudo service lightdm restart:
[06:36] <bryceh> http://pastebin.ubuntu.com/778322/
[06:38] <bryceh> intriguing... ppa-purge of the ppa results in working X session.
[06:38] <bryceh> let's try again
[06:41] <bryceh> hmm, apport caught something... crash in "fts.py"
[06:41] <bryceh> part of zeitgeist
[06:41] <bryceh> guess coincidental
[06:44] <bryceh> lp #907661
[06:44] <ubot4> Launchpad bug 907661 in zeitgeist (Ubuntu) "fts.py crashed with DatabaseLockError in __init__(): Unable to get write lock on /home/bryce/.local/share/zeitgeist/bb.fts.index: already locked (affects: 1) (heat: 8)" [Undecided,New] https://launchpad.net/bugs/907661
[06:46] <cnd> RAOF, bryceh, fyi, I plan on pushing mt versions of xorg-server and evdev to the x-staging ppa tomorrow
[06:47] <RAOF> cnd: Awesomesauce.
[06:47] <cnd> I was hoping keithp would pull Peter's mt branch today, but I can cherry-pick it as-is if he doesn't get to it
[06:48] <cnd> maybe I'll look into forward porting the qt multitouch patch after that :)
[06:48] <cnd> anyways, bed time for me
[06:48] <bryceh> cnd, sounds good
[06:49] <bryceh> I'm running the ppa on a devoted test box, I can update and test whatever whenever
[06:50] <bryceh> hmm this is weird, after ppa-purging and re-adding, it doesn't want to install the new X bits
[06:50] <RAOF> Oh!  Are you trying to run Unity?  It still won't start without mt/gestures.
[06:52] <bryceh> RAOF, heh ok that'd do it
[06:55] <cnd> RAOF, that hasn't been fixed yet?
[06:55] <bryceh> RAOF, ok, I assumed it just required the new input stack.  I take it cnd's upload tomorrow is required then?
[06:55] <cnd> grrr...
[06:56] <cnd> bryceh, it's a unity bug
[06:56] <bryceh> cnd, mm
[06:56] <cnd> there was a "fix" for it that was obviously wrong on further inspection
[06:56] <cnd> a week ago I assigned it back to the original fixer, hoping they would resolve it
[06:56] <bryceh> ok, and I have auto-login enabled so it just logs me into unity automatically; presumably if I switch that off I could go into unity2d or classic
[06:56] <cnd> maybe they've been on vacation?
[06:58] <bryceh> at least I've learned ppa-purge isn't reversible with apt-add-repository (as it probably should be)
[06:59] <cnd> bryceh, https://bugs.launchpad.net/ubuntu/+source/unity/+bug/860707
[06:59] <ubot4> Launchpad bug 860707 in unity (Ubuntu) (and 1 other project) "Unity crashes when started in an environment without utouch support (affects: 58) (dups: 2) (heat: 270)" [High,Triaged]
[06:59] <cnd> I might have to fix that myself
[06:59]  * cnd tries to stay away from unity development
[07:00] <bryceh> they've probably all been repurposed into cloud developers or something
[07:01] <bryceh> ok yep switching to gnome classic (no effects) boots in fine
[07:30] <tjaalton> cnd: btw, debian wants multitouch soon, so there's no need for our own upstream branches, could've used -experimental there
[07:30] <tjaalton> but it's no biggie
[07:37] <tjaalton> oh unity still busted? maybe i won't test the ppa afterall :/
[08:29] <bryceh> tjaalton, definitely busted
[08:29] <bryceh> tjaalton, classic seems to work
[08:32] <tjaalton> bryceh: yeah, i'll hold off then.. though it's just my laptop to break, hmm
[08:48] <bryceh> *nod*
[14:55] <FernandoMiguel> damn.... my touchpad is a MESS
[15:25] <cnd> tjaalton, were people getting upset about me pushing ubuntu specific packages?
[15:25] <cnd> KiBi seems a bit miffed that I would do that
[15:50] <tjaalton> cnd: yeah we discussed it on debian-x the other day, and told that we didn't know what their plans were and forgot to ask. no harm done :)
[15:51] <cnd> I just chatted with him on #debian-x, I think he's ok once I mentioned this is a one-time, time-sensitive deal
[15:51] <cnd> I'm trying to get things into the ppa before I go on vacation
[15:51] <tjaalton> yeah he's cool
[15:51] <tjaalton> Sarvatt told him that we (you) were on a deadline
[16:21] <cnd> I just pushed a fix for the utouch-unity crash: https://code.launchpad.net/~chasedouglas/unity/utouch-crash/+merge/86727
[16:21] <cnd> hopefully it is reviewed and uploaded soon
[16:22] <cnd> but I don't know if it will be before the holiday break
[17:10] <FernandoMiguel> rebooting seems to have fixed my touchpad probs.... for now
[17:30] <cnd> I decided to create a unity package with a fix for the utouch issue
[17:30] <cnd> after I see that it builds, I'll push it to the staging ppa
[18:11] <tjaalton> cnd: oh great, thanks
[18:22] <cnd> it's now uploaded
[18:22] <cnd> I haven't had a chance to test it yet
[18:22] <cnd> I'm just now updating behemoth to precise
[18:22] <cnd> but it's a simple fix, so it should work
[19:43] <tjaalton> cnd: hmm don't see unity on the ppa yet?
[19:43] <cnd> tjaalton, it probably hasn't built yet
[19:44] <tjaalton> cnd: ah, right..
[19:45] <tjaalton> start in 23min
[19:45] <tjaalton> i can wait :)
[20:02] <ricotz> cnd, hi, you probably want to put fglrx in there too
[20:03] <cnd> ricotz, RAOF (and maybe others) are handling anything non-input related
[20:03] <cnd> I don't really know about anything outside of input :)
[20:03] <ricotz> alright ;)
[20:08] <tjaalton> ricotz: the version in precise should already handle the new abi
[20:09] <tjaalton> unless it needs a rebuild to fix the deps
[20:10] <ricotz> tjaalton, yes, just a rebuild is needed
[20:10] <ricotz> but an update would be nice too since there is a newer upstream
[20:11] <ricotz> same goes for nvidia
[20:12] <tjaalton> tseliot will handle updates
[20:12] <tjaalton> in january :)
[20:12] <tjaalton> ie. before those are pushed to precise
[20:13] <ricotz> alright
[21:05] <cnd> tjaalton, unity is built
[21:06] <cnd> have you had a chance to test?
[21:07] <tjaalton> cnd: upgrading..
[21:07] <cnd> tjaalton, there *may* be an issue with evdev in the ppa right now
[21:08] <cnd> but I think it should work if you aren't using a multitouch device
[21:08] <cnd> it needs to be rebuilt after xorg-server is built in the ppa
[21:08] <tjaalton> seems to work fine otherwise, but compiz takes all the cpu
[21:10] <cnd> I get:
[21:10] <cnd> Xorg: symbol lookup error: /usr/lib/xorg/modules/input/evdev_drv.so: undefined symbol: InitTouchClassDeviceStruct
[21:10] <cnd> which is what I expect
[21:11] <tjaalton> huh, works here
[21:13] <tjaalton> unity-2d loads, apart from the dock
[21:14] <cnd> ok
[21:18] <tjaalton> ah, unity-2d-launcher taking 100% cpu :)
[21:18] <RAOF> tjaalton: Yeah, unity-2d-launcher *also* hates missing multitouch/gestures it seems :)
[21:19] <tjaalton> at least the upgrade itself was rather uneventful
[21:20] <RAOF> ricotz: There's already a build on nvidia-current in there; there will be fglrx & the rest of the drivers in there before they land in precise.
[21:23] <ricotz> RAOF, hi, yeah i figured that, just didnt know when it will be moved
[21:26] <RAOF> Not before Christmas :)
[21:34] <ricotz> yeah no more breaks for this year! :)
[22:32] <cnd> once evdev rebuilds in the ppa it should be all ready for testing
[22:32] <cnd> and it should have multitouch for touchscreens
[22:32] <cnd> \o/
[22:33] <bryceh> cnd, sweet, ping us once it's ready
[22:53] <cnd> tjaalton, unity-2d probably crashes because qt's multitouch code is now incompatible with the upstream XI implementation
[22:53] <cnd> I'll probably upload a new qt with the patch commented out
[22:53] <tjaalton> i'll just wait for evdev though :)
[22:53] <tjaalton> to build
[22:59] <tjaalton> though maybe I'll just check it in the morning
[23:05] <tjaalton> oh, building..
[23:27] <tjaalton> cnd: ok so the same still happens with these, will check in the morning if there's a new qt available :)