[03:22] <Takyoji> ripps: https://bugs.launchpad.net/ubuntu/+source/xf86-input-wacom/+bug/703783/comments/2 https://bugs.launchpad.net/ubuntu/+source/xf86-input-wacom/+bug/703783/comments/3
[03:22] <ubot4> Launchpad bug 703783 in xf86-input-wacom (Ubuntu) "Wacom BambooFun tablet powered, but no input (affects: 1) (heat: 6)" [Undecided,New]
[03:23] <Takyoji> in other words, apparently I've found out that only manipulates the cursor with scribbled on by-finger rather than with the pen for it.
[03:24] <Takyoji> s/with/when/
[03:38] <ripps> Takyoji: you might want to try and contact the linuxwacom developers, I think they probably have a bug tracker at sourcforge.net. They might have some idea about what's going on.
[03:38] <Takyoji> alright
=== jbs is now known as Bernardo|Away
=== Bernardo|Away is now known as jbs
=== jbs is now known as Bernardo|Away
=== njpatel_ is now known as njpatel
=== yofel_ is now known as yofel
[14:54] <bjsnider> Sarvatt, you can build this stuff in pbuilder before sending it in to the ppa
[15:50]  * apw notes that there seems to be an issue with nvidia-detect output format changing ... does anyone know exactly what the nvidia-common postinst is for as it is cirtainly affected
[15:50] <apw> bug #704471
[15:50] <ubot4> Launchpad bug 704471 in nvidia-common (Ubuntu) "nvidia-common kernel postinst hook throws test errors (affects: 1) (heat: 6)" [Undecided,New] https://launchpad.net/bugs/704471
[16:02] <tseliot> apw: let me check, I wrote that script
[16:04] <apw> tseliot, sounds fun
[16:04] <tseliot> apw: maintenance surely is ;)
[16:05] <apw> tseliot, heh ... i twiddled a bit with the script; turning off the Verbose=True seemed to make it more as the calling script expected
[16:05] <tseliot> apw: pitti modified nvidia-common changing the logic behind modaliases so maybe the debconf code needs to be updated too
[16:06]  * tseliot doesn't remember what his own code does...
[16:07] <tseliot> apw: actually, looking at the changelog, it seems that he also updated the postinst
[16:08] <tseliot> apw: BTW what do you get with Verbose=False?
[16:08] <apw> tseliot, it is defiantly not working as designed currently
[16:09]  * tseliot nods
[16:09] <apw> tseliot, for me verbose=False just says 'none'
[16:09] <apw> i have no idea what happens if you have nvidia
[16:11] <tseliot> apw: you can simulate that by overriding self.cards in getCards() in /usr/share/pyshared/NvidiaDetector/nvidiadetector.py or /usr/lib/python2.7/dist-packages/NvidiaDetector/nvidiadetector.py as in the commented lines
[16:12] <tseliot> apw: you can even pretend to have 4 cards: self.cards = ['10de:02e2', '10de:002d', '10de:0296', '10de:087f']
[16:20] <Sarvatt> NVIDIA card found (10de:0dd1)
[16:20] <Sarvatt> Removing unsupported card 10de:0dd1
[16:20] <Sarvatt> No NVIDIA package to install
[16:20] <Sarvatt> none
[16:20]  * Sarvatt wonders if this has something to do with 2.6.37-12 not working
[16:25] <Sarvatt> ah nvidia package i'm using doesnt have the backporting nightma.. i mean modalias changes
[16:26] <bryceh> heya Sarvatt and tseliot
[16:26] <Sarvatt> heyo bryceh!
[16:26] <tseliot> bryceh, Sarvatt: hey
[16:26] <Sarvatt> trying to fix up xorg-edgers, what a mess
[16:27] <tseliot> Sarvatt: ah, thanks for the output
[16:27] <Sarvatt> they made a crapload of changes to the mesa build system upstream
[16:27] <bryceh> Sarvatt, what's wrong?
[16:27] <Sarvatt> ati in there was built from debian-experimental so lost the gallium options and had a ton of emails about it
[16:27] <bryceh> Sarvatt, fwiw I'd installed it on my netbook Friday and it seemed to work fine
[16:31] <tjaalton> howdy
[16:33] <jcristau> hi timo
[16:34] <tjaalton> I should probably fix my irssi setup so I could use another server too, and join the debian channels again :)
[16:35] <tjaalton> but first edgers
[16:35] <tjaalton> jcristau: and hi :)
[16:38] <evilvish> Sarvatt: remember the RV515 bug i was mentioning about, the one where X freezes during scrolling in firefox?  it does not happen with maverick -edgers \o/
[16:39] <evilvish> oh and i am using the .37 kernel from edgers, but it was never kernel dependant though
[16:42] <bryceh> heya tjaalton
[16:44] <Sarvatt> RAOF: you'll be glad to know libdricore is broken already! :)
[16:48] <bryceh> http://www.bryceharrington.org/X/Reports/ubuntu-x-swat/totals-natty-workqueue.svg
[16:51] <bryceh> "firegl_public.c:410:5: error: unknown field ‘ioctl’ specified in initializer" hmm, isn't that one already fixed?
[16:51] <bryceh> (bug #704287)
[16:51] <ubot4> Launchpad bug 704287 in fglrx-installer (Ubuntu) "package fglrx 2:8.801-0ubuntu2 [modified: usr/lib/fglrx/etc/ati/authatieventsd.sh usr/src/fglrx-8.801/2.6.x/Makefile usr/src/fglrx-8.801/dkms.conf usr/src/fglrx-8.801/firegl_public.c] failed to install/upgrade: fglrx kernel module failed to build (affects: 1) (heat: 6)" [Undecided,New] https://launchpad.net/bugs/704287
[16:55] <tjaalton> i'll be damned, finally a proper resize-corner with the default theme
[16:56] <tjaalton> and not 1x1
[16:56] <bryceh> yeah saw that.  think it's new as of last week
[16:59] <tjaalton> hmm edgers already has newer mesa that'll get in natty?
[16:59] <tjaalton> +a
[17:00] <bryceh> tjaalton, yeah
[17:01] <tjaalton> ok..
[17:01] <bryceh> tjaalton, but it's not crazily different, just a handful of changes so far
[17:01] <tjaalton> ah
[17:01] <tseliot> bryceh: I think I can fix fglrx. I uploaded a similar fix for the broadcom driver
[17:02] <bryceh> I suppose we could put exactly the release version in, but sounds like it's close enough to not be worth the trouble.  However I do think we should avoid updating it to newer snapshots until after the upload is done.
[17:02] <bryceh> tseliot, okie, yeah this sounds like something that got fixed before
[17:03] <bryceh> at least, the error message sounds familiar... not putting my finger on the bug report yet tho
[17:03]  * tseliot nods
=== Bernardo|Away is now known as jbs
=== jbs is now known as Bernardo|Away
=== Bernardo|Away is now known as jbs
[17:21] <bryceh> Sarvatt, could you look at bug #681054 when you get a chance?  Since he can repo it on a livecd, I'm thinking next step is to send it upstream, unless you have an idea for something else he could test first?
[17:21] <ubot4> Launchpad bug 681054 in xserver-xorg-video-intel (Ubuntu) "screen repeatedly goes black for a fraction of a second (affects: 1) (heat: 6)" [Undecided,New] https://launchpad.net/bugs/681054
[17:24] <tjaalton> resume still doesn't work with .37, the thing does a cold boot
[17:25] <bryceh> tjaalton, it's been working for me
[17:26] <bryceh> tjaalton, maybe chat up the kernel team about it
[17:26] <tjaalton> yeah
[17:28] <tjaalton> heh, bug 625364
[17:28] <ubot4> Launchpad bug 625364 in linux (Fedora) (and 2 other projects) "lenovo/thinkpad T400[s]/T500/W500/X60/T6x suspend fails (affects: 53) (dups: 3) (heat: 337)" [Unknown,Unknown] https://launchpad.net/bugs/625364
[17:28] <tjaalton> on the top of the list
[17:29] <tjaalton> hmm, doesn't seem like 100% same
[17:30] <tjaalton> worked just fine on maverick
[17:30] <bryceh> file a new bug and just mention that one in reference, the kernel team prefers bugs filed individually and do duping themselves
[17:31] <bryceh> tjaalton, once it's filed make sure it's tagged 'natty' and nominated for natty, and then ping JFo on IRC.  Ask him to add it to the kernel team's review list
[17:35] <tjaalton> bryceh: alrighty
=== jbs is now known as Bernardo|Away
=== Bernardo|Away is now known as jbs
=== jbs is now known as Bernardo|Away
=== Bernardo|Away is now known as jbs
=== jbs is now known as Bernardo|Away
=== Bernardo|Away is now known as jbs
=== jbs is now known as Bernardo|Away
=== Bernardo|Away is now known as jbs
=== jbs is now known as Bernardo|Away
=== Bernardo|Away is now known as jbs
=== jbs is now known as Bernardo|Away
=== Bernardo|Away is now known as jbs
=== jbs is now known as Bernardo|Away
=== Bernardo|Away is now known as jbs
=== jbs is now known as Bernardo|Away
=== Bernardo|Away is now known as jbs
[22:26] <bryceh> RAOF, what do you think the next action should be for bug #681054?
[22:26] <ubot4> Launchpad bug 681054 in xserver-xorg-video-intel (Ubuntu) "screen repeatedly goes black for a fraction of a second (affects: 1) (heat: 6)" [Undecided,New] https://launchpad.net/bugs/681054
[22:28] <RAOF> Hm.  I seem to remember a kernel knob that could be tweaked?
[22:29] <RAOF> Or maybe that was radeon.
[22:30] <bryceh> yeah, random blanking has been a longstanding radeon issue.  Haven't really seen periodic blanking bugs on intel, at least not recently
[22:31] <tjaalton> I used to have those on intel during 9.10 or such
[22:31] <RAOF> Maybe the next thing to do is to ask whether unplugging the VGA monitor changes the behaviour?
[22:32] <bryceh> tjaalton, regular/periodic, or irregular/random?
[22:32] <tjaalton> bryceh: more like the latter
[22:33] <RAOF> There's certainly quite a lot of xrandr probing in the logs.
[22:33] <bryceh> yeah that was my first thought
[22:33] <bryceh> but tail -f on it didn't generate more
[22:33] <tjaalton> yeah i thing it was related to that when i had it
[22:33] <bryceh> (you'll recall me asking if we had something in there that quells that output after 10 entries or something)
[22:33] <RAOF> But maybe not enough to explain all teh blanking.
=== Dr_Jakob is now known as Prf_Jakob
=== Dr_Jakob_ is now known as Dr_Jakob