[00:15] <jcristau> Sarvatt: we'll probably have to update libdrm in sid to 2.4.21 soon (for intel 2.12), keeping the .33 nouveau ABI, fwiw
[02:46] <Sarvatt> ripps: that's really tricky, I'm sure debian doesn't want it because it shouldn't be needed and will probably be useless in the future whenever they do upstream it
[02:46] <Sarvatt> the dkms package for the linuxwacom module makes the most sense to me personally..
[02:47] <Sarvatt> I mean it's going over a year where it's been required for newer tablets, we need *something*
[02:48] <ripps> Sarvatt: it's trapped in bueracracy. I was hoping I could at least get a package into Ubuntu, and than maybe a version into the Lucid backport repo. But neither look like they're making much progress. I guess my dkms ppa is gonna have to be the fix for a while.
[02:48] <Sarvatt> you aren't a MOTU?
[02:48] <ripps> Sarvatt: nope
[02:48] <ripps> alot of people have been asking me that today ;P
[02:49] <ripps> maybe I should take that as a sign
[02:50] <Sarvatt> linux-backports-modules for wacom doesn't make any sense to me since its not a backport from anything, I'm going to apply for MOTU soon and I'll upload it if noone else will by then :D
[02:52] <Sarvatt> i've been using it for months with no problems and it fits a real need people have
[02:53] <ajmitch> ripps: aside from uploading to REVU, what else have you tried for getting it into ubuntu?
[02:55] <ripps> ajmitch: I filed a wnpp for it in debian, but they were pretty rude about how it was pointless.
[02:55] <ajmitch> yeah, that can happen
[02:55] <ajmitch> you've probably seen that the REVU queue is somewhat massive & not getting much shorter, so it's generally a help to ping someone about it
[02:56] <ripps> technically, it's still on debian-mentors, but It doesn't look like I'm gonna get anybody to sponsor it for me
[02:57] <Sarvatt> I can understand that viewpoint too because it could be useless in the not too distant future but it's been over a year where newer low end wacom tablets were only supported by that and they dont seem intent on pushing it to the upstream kernel anytime soon
[02:57] <ajmitch> it's a bit hard for me to test the package itself, but I can at least check out that the packaging is sane
[02:58] <ajmitch> RAOF would probably be a good person to review & sponsor it, he's familiar with DKMS iirc :)
[02:58] <RAOF> He is, yes.
[02:58] <ajmitch> and he's even alive!
[03:00] <ripps> RAOF: the wacom-source package is on REVU.
[03:01] <ajmitch> RAOF: sorry if I've dropped you in it :)
[03:02] <RAOF> ripps: Added to my todo.
[03:02] <ripps> RAOF: thanks :)
[03:03] <Sarvatt> ripps: btw about your question regarding l-b-m packaging in case you wanted to mess with it take a look at the git history for lucid's lbm to see how they added nouveau
[03:03] <ripps> Sarvatt: that's pretty good advice
[03:03] <ripps> Sarvatt: have you taken a look at l-b-m's packaging?
[03:04] <Sarvatt> yeah i used to package lbm-nouveau updates in edgers
[03:04] <Sarvatt> http://kernel.ubuntu.com/git?p=ubuntu/ubuntu-lucid-lbm.git;a=commit;h=06e957ce818ba7dc6bbd9314eca356200a5c7b57
[05:25] <jcristau> Sarvatt: were the upstream devs contacted about that stuff sitting in linuxwacom and not getting upstream?  what was the response?
[05:33] <tjaalton> yeah the upstream kernel git repo should get moving..
[05:33] <tjaalton> if it hasn't already
[05:34] <jcristau> s/getting upstream/getting in mainline/
[05:34] <tjaalton> i'd rather concentrate on that than ship something temporary
[05:37] <ajmitch> given how close to feature freeze it is, my opinion is to go both ways for now - it's easy to drop the package if it's included upstream by release
[05:44] <Sarvatt> i'll have to dig through a year of the linuxwacom-devel archives to find it but yeah i've seen it brought up multiple times there, there are new features on those bamboo pen and touch models very different from the other ones so its not as easy as just adding the id's
[05:46] <RAOF> Do the nvidia drivers work against the 1.9 ABI yet?
[05:47] <Sarvatt> xf86-input-wacom handles them fine though, its just the wacom kernel module that needs updating
[05:48] <Sarvatt> i've got the newest packaged in x-updates, haven't heard anyone say anything about it yet though. wife went to visit family for a few days and has my nvidia testing laptop with her so i can't try it
[05:48] <RAOF> I guess I have to test it myself, then. :)
[05:55] <Sarvatt> if 256.44 doesn't it'd be worth trying 256.38.02 too - http://developer.nvidia.com/object/opengl_driver.html
[06:00] <tjaalton> that's nice, raising a window on lucid (nvidia&compiz) takes two seconds
[06:01] <tjaalton> well, closer to one
[06:01] <tjaalton> but one too man
[06:01] <tjaalton> y
[06:01] <tjaalton> oh it was just the lp window
[06:03] <tjaalton> btw, there's also a reason why the linuxwacom kernel features are not in mainline. for instance the multitouch support is never going in
[06:03] <tjaalton> it'll support the "proper" multitouch once it's mainline
[06:06] <Sarvatt> yeah nvidia knows about the launchpad problem, they blame firefox :)
[06:06] <Sarvatt> http://www.nvnews.net/vbulletin/showthread.php?t=152295
[06:06] <tjaalton> typical :)
[06:13] <RAOF> Firefox has been rather good at exploring rendering paths not typically taken.
[06:19] <tjaalton> btw, I'm mostly online again, so if you need a sponsor just poke me
[06:22] <Takyoji> raof: it appears the issue still persists, even after I added the repository and updated
[06:23] <RAOF> Takyoji: Can you pastebin /var/log/Xorg.0.log, please?
[06:23] <Takyoji> I'm reproducing the issue by going through different screensavers randomly, which is the way I can reproduce it quickly
[06:24] <Takyoji> I'm unable to get to a virtual terminal via Ctrl+Alt+F1; I'll have to use a LiveCD then
[06:25] <RAOF> Your logs should be saved after the crash.
[06:25] <Takyoji> the odd thing though, is when I press the power button, to make it shutdown, Plymouth appears again, and is functioning
[06:25] <Takyoji> and shutdown properly
[06:25] <Takyoji> shuts down properly*
[06:30] <RAOF> Yeah; that's because the problem is that the GPU has hung, so anything which requires the GPU to do anything interesting won't work.  Plymouth just writes some bits to where the GPU has told the hardware to scanout to the screen, so doesn't muchcare that the GPU isn't working.
[06:31] <Takyoji> ahh
[06:32] <RAOF> It'll be /var/log/Xorg.0.log.old after you've restarted, by the way.
[06:33] <Takyoji> actually I booted a LiveCD, so it should just be /(location of the room partition mounted seperately)/var/log/Xorg.0.log, correct?
[06:35] <RAOF> Yeah.
[06:36] <Takyoji> RAOF: http://paste.ubuntu.com/472504/
[06:37] <RAOF> That's the wrong driver; 2.9.1
[06:37] <RAOF> Are you sure you installed the newer xserver-xorg-video-intel package & restarted X?
[06:37] <RAOF> Alternatively, that might be the wrong log.
[06:38] <Takyoji> This section, or? https://wiki.ubuntu.com/X/Bugs/Lucidi8xxFreezes#Legacy Driver
[06:38] <Takyoji> https://wiki.ubuntu.com/X/Bugs/Lucidi8xxFreezes#Legacy%20Driver
[06:39] <RAOF> That section, yes.
[06:39] <Takyoji> Erm, stupid me; all I did was add the repository and upgrade packages; I had forgotten about disabling KMS
[06:50] <Takyoji> one other thing I notice is that an update for xserver-xorg-video-intel (if I remember correctly) is held back as well; after adding the repository
[06:51] <RAOF> It shouldn't be held back; that's what you want to update.
[06:51] <Takyoji> So I'll have to force it then?
[06:51] <RAOF> There probably will be a held-back libdrm-nouveau1 which you shouldn't upgrade.
[06:51] <Takyoji> Yea, there's libdrm-nouveau1 AND xserver-xorg-video-intel held back
[06:52] <RAOF> Why is xserver-xorg-video-intel held back?
[06:52] <RAOF> You do want that.
[06:52] <Takyoji> I'm not sure myself why it's heldback for updates.
[06:52] <Takyoji> anyway, I shall try forcing it to update that package
[06:53] <Takyoji> (just 'xserver-xorg-video-intel' specifically)
[07:03] <Takyoji> It appears that the problem no longer persists now
[07:03] <Takyoji> after updating that package
[09:27] <ricotz> RAOF, hi
[09:29] <ricotz> have you looked into the gnome-do slowdown related to newer cairo versions? i have expierenced this with some development code for docky, so this might happen with inproper using of cairo.context