=== dzan is now known as dzan|away
=== ripps_ is now known as ripps
[08:51] <Sarvatt> RAOF: so the spinning at 100% cpu usage bug with the newer X is utouch-geis, downgrading to the oneiric one fixes that
[08:51] <RAOF> Whee!
[08:51] <tjaalton> great
[09:15] <Sarvatt> RAOF: apparently cnd's unity in the PPA also works after downgrading utouch geis with x-staging, woohoo
[09:15] <tjaalton> confirmed!
[09:15] <RAOF> Wooo!
[09:15] <Sarvatt> now who to bug about utouch-geis
[09:16] <tjaalton> chase?? :)
[09:16] <tjaalton> -?
[09:16] <ricotz> https://bugs.launchpad.net/ubuntu/+source/utouch-geis/+bug/879348
[09:16] <ubot4> Launchpad bug 879348 in utouch-geis (Ubuntu) (and 1 other project) "evince segfaults (affects: 9) (dups: 2) (heat: 36)" [Undecided,Incomplete]
[09:16] <ricotz> so i guess https://launchpad.net/~bregma
[09:16] <ricotz> hello
[09:17] <tjaalton> yeah
[09:18] <ricotz> https://bugs.launchpad.net/ubuntu/+source/utouch-geis/+bug/898175
[09:18] <ubot4> Launchpad bug 898175 in utouch-geis (Ubuntu) "uTouch hangs using XCB back end if X server does not support gesture protocol (affects: 6) (heat: 28)" [Undecided,Confirmed]
[09:18] <Sarvatt> yep thats the one
[09:18] <Sarvatt> ricotz: i see what you mean about acceleration being different in newer synaptics :)
[09:21] <tjaalton> .xsessionrc isn't read on startup, meh
[09:29] <Sarvatt> ricotz: heh that was close, almost uploaded git xserver when there's abi breaks that are going to get reverted
[09:30] <ricotz> Sarvatt, oh, 1.11 branch or master?
[09:30] <Sarvatt> ricotz: master http://www.mail-archive.com/xorg-devel@lists.x.org/msg27845.html
[09:31] <ricotz> oh
[09:32] <ricotz> i was hoping to push an update too
[09:32] <ricotz> Sarvatt, so 1.12 for edgers ;)
[09:32] <Sarvatt> yeah was about to upload it when timo pointed that out :)
[09:33] <ricotz> i guess you need to push some deps first
[09:33] <Sarvatt> got them locally
[09:33] <ricotz> like x11proto-input 2.1.99.5
[09:33] <ricotz> ok
[09:33] <Sarvatt> guess i'll just push the proto and copy your xserver actually
[09:34] <Sarvatt> and reupload all drivers
[09:34] <ricotz> you can copy the proto too
[09:34] <Sarvatt> oh thought you had 2.1.99.3, even easier
[09:34] <ricotz> jammed ppa builders doesnt make it easy
[09:35] <Sarvatt> wow hardly any builders atm
[09:35] <Sarvatt> yeah better off waiting
[10:37] <ricotz> tjaalton, hi, could you update libwacom and maybe upload, they released 0.1
[10:37] <ricotz> tjaalton, to debian
[10:38] <tjaalton> ricotz: upload to debian? no
[10:39] <tjaalton> oh libwacom
[10:39] <ricotz> tjaalton, yes, is this possible?
[10:40] <tjaalton> i can update git, but not upload there
[10:40] <ricotz> and to ubuntu?
[10:40] <tjaalton> ubuntu yes
[10:41] <ricotz> this would be nice!
[10:41] <ricotz> g2g, bye
[10:44] <seb128> ricotz, tjaalton: you guys packages libwacom?
[10:45] <tjaalton> seb128: it's not uploaded yet, but packaged yes
[10:45] <seb128> grrr
[10:45] <seb128> http://launchpadlibrarian.net/89491492/libwacom_0.1-0ubuntu1_source.changes
[10:45] <tjaalton> oh it was :)
[10:45] <seb128> robert_ancell did package it today
[10:45] <tjaalton> ah
[10:45] <seb128> tjaalton, no, it's work duplication
[10:45] <seb128> <- bit annoyed
[10:45] <tjaalton> why not ask before? :)
[10:46] <seb128> we asked bryce and RAOF here at the platform rally before starting on it
[10:46] <tjaalton> ok
[10:46] <seb128> they didn't know that you were working on it apparently
[10:46] <seb128> well anyway, it's done
[10:46] <tjaalton> yeah ok
[10:46] <tjaalton> it was discussed here mid-december'ish
[10:47] <seb128> it's just annoying that people get stuff in ppas and other redo the same work in the archive
[10:47] <tjaalton> forgot about it due to the holidays
[10:47] <seb128> no worry
[10:47] <tjaalton> we've forked all of wacom by now, since it's not maintained in the xsf git on debian
[10:48] <tjaalton> so I pulled ricotz's package and pushed it to my personal git space (writable by pkg-xorg)
[10:48] <tjaalton> (like -wacom)
[10:49] <tjaalton> seb128: do you want to maintain it? there was some confusion about what the consumers were, since the driver didn't need it at that point
[10:49] <tjaalton> and probably still doesn't
[10:49] <tjaalton> but will
[10:49] <seb128> tjaalton, we don't especially want to maintain it ;-)
[10:49] <seb128> robert_ancell wanted to build g-c-c from git
[10:49] <seb128> which requires it
[10:49] <tjaalton> yeah
[10:49] <seb128> so it was a "scratch an itch"
[10:50] <jcristau> gnome requires wacom?
[10:50] <jcristau> wow...
[10:50] <tjaalton> jcristau: the capplet does, libwacom
[10:50] <seb128> jcristau, they are a wacom configuration capplet
[10:50] <tjaalton> it's the source of all the model->feature mappings, and the driver will end up using it too
[10:51] <jcristau> you'd think the driver would expose what features are there, so the clients wouldn't need to guess
[10:51] <jcristau> or, well, s/you/i/
[11:17] <tjaalton> hmm, maybe I should adjust the packaging to match the libwacom upload then
[11:17] <tjaalton> libwacom0 vs libwacom-0 for instance
[11:19] <Sarvatt> ricotz: mind copying mesa from edgers to your unstable ppa?
[11:21] <Sarvatt> tempted to binary copy the proto and 2 libs and xserver from your ppa but that'd still mean edgers would be broken for 5 hours before i could upload drivers then another 5 hours waiting for those to build
[11:21] <Sarvatt> also yay OpenGL version string: 3.0 Mesa 7.12-devel
[11:23] <tjaalton> seb128: would robert mind if I merged some of the changes and reuploaded that instead?
[11:23] <seb128> tjaalton, go for it
[11:24] <tjaalton> seb128: ok thanks
[11:24] <seb128> tjaalton, he just wanted to see that in so we can build g-c-c easily
[11:24] <tjaalton> seb128: well, I'm going to revert the libwacom-0 package name to just libwacom0, seems more "correct" to me, and multiarchify it too
[11:24] <seb128> ok
[11:25] <seb128> tjaalton, what's the lib name on disk?
[11:25] <tjaalton> not sure :)
[11:26] <tjaalton> I need to build it first to see
[11:26] <tjaalton> but I think it's libwacom.so.0
[11:26] <tjaalton> good that he added the symbols file
[11:27] <tjaalton> seb128: can you drop the package from NEW?
[11:27] <tjaalton> I'll get it done before lunch
[11:28] <seb128> tjaalton, done
[11:28] <tjaalton> seb128: nice thanks
[11:28] <seb128> yw
[11:29] <tjaalton> ./usr/lib/libwacom.so.0.0.0
[11:30] <seb128> I wonder why he added a "-" then, seems wrong
[11:31] <tjaalton> yeah, but in any case it wasn't all for nothing, I'll merge the good bits :)
[11:32] <seb128> good
[11:54] <tjaalton> seb128: meh, some issues with the git repo having stuff the tarball doesn't, so I need to look at that before uploading, after lunch for sure :)
[11:57] <seb128> tjaalton, ok
[14:48] <Sarvatt> tseliot: nvidia is defaulting to nvidia-173 in precise?
[14:49] <tseliot> Sarvatt: no, I don't think so, unless someone else changed its priority to something bigger than nvidia-current's. update-alternatives --display x86_64-linux-gnu_gl_conf should show what's going on
[14:50] <tseliot> or -display i386-linux-gnu_gl_conf if your system is i386
[14:50] <Sarvatt> bryce was saying there is a flood of bug reports where jockey is defaulting to nvidia-173 instead of nvidia-current
[14:50] <Sarvatt> in precise
[14:52] <tseliot> Sarvatt: maybe the card is not marked as supported? What bug reports are you referring to?
[14:52] <tseliot> oh boy, I forgot to patch the drivers to build against linux 3.2...
[14:55] <tjaalton> :)
[15:06] <bryceh> yeah, 2 bugs
[15:06] <bryceh> a.  nvidia-173 doesn't build against the new kernel
[15:07] <bryceh> b.  for some reason jockey defaults to nvidia-173 a lot when it shouldn't
[15:08] <bryceh> a. is lp #576648
[15:08] <ubot4> Launchpad bug 576648 in nvidia-graphics-drivers-updates (Ubuntu) (and 4 other projects) "package nvidia-* failed to install/upgrade: nvidia-* kernel module failed to build (Unable to determine the target kernel version.) (affects: 213) (dups: 195) (heat: 1502)" [Undecided,Triaged] https://launchpad.net/bugs/576648
[15:09] <bryceh> b. is lp #876499
[15:09] <ubot4> Launchpad bug 876499 in jockey (Ubuntu Precise) (and 2 other projects) "Incorrect Nvidia driver installed by checking 3rd party box (affects: 8) (dups: 6) (heat: 60)" [High,Triaged] https://launchpad.net/bugs/876499
[15:10] <tseliot> bryce: oh, there's a merge request for a) already. I wasn't notified though...
[15:12] <tseliot> bryceh: I'll take care of both bugs. Thanks
[15:12] <bryceh> tseliot, great
[15:14] <bryceh> tseliot, I suspect b. is something wrong in jockey's nvidia internal selection logic.
[15:15] <bryceh> tseliot, comment #17 describes as far as I got analyzing it
[15:15] <tseliot> bryceh: the weird thing is that, according to the bug report, nvidia-common makes the right choice, so I'm wondering what's going on in Jockey...
[15:15] <bryceh> tseliot, I wonder if it is something peculiar with the installation environment
[15:16] <tseliot> bryceh: maybe something else is pulling nvidia-173 in?
[15:16] <tseliot> so yes, it could be the environment
[15:16] <bryceh> tseliot, don't think so; it seems to be jockey specifically deciding it's the driver it wants
[15:17] <tseliot> bryceh: but it's designed to pick whatever nvidia-common says it's best for the card
[15:18] <bryceh> ironically, one of the community folks has been dutifully duping all these bugs together, but since he's duping against a really old bug report, that has kept it off my radar
[15:18] <tseliot> too bad
[15:36] <tjaalton> seb128: uploaded libwacom to the queue, btw
[15:36] <seb128> tjaalton, thanks
[20:44] <FernandoMiguel> evening
[20:49] <Sarvatt> bryce: funny because I was digging through 9xxxxx bugs trying to find it and didn't, no wonder :)
=== yofel_ is now known as yofel