[00:09] <Sarvatt> tip for nvidia backlight bugs on lenovo laptops.. https://bugs.launchpad.net/bugs/540112
[00:35] <bryceh> best bug comment ever:  https://bugs.edge.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/522485/comments/3
[00:40] <chrisccoulson> bryceh - you're lucky. i had someone paste their entire life story on 2 bugs i'm subscribed to today ;)
[00:40] <chrisccoulson> the same essay on each...
[00:43] <bryceh> "and then my dog ran over my girlfriend..."
[00:44] <bryceh> chrisccoulson, I had one xkeyboard-config bug where two guys got into it hot and heavy over a crimean keyboard layout
[00:44] <chrisccoulson> lol
[00:44] <chrisccoulson> some comments make for an interesting read ;)
[00:44] <bryceh> something about what russians or turks did to tartars 200 years ago
[00:45] <bryceh> even made its way upstream, and the xkeyboard-config maintainer is in Moscow, and when he opted not to do the change asked for, whew knives flew
[00:46] <jcristau> yeah that one was wild
[00:49] <RAOF> How do ants eat a laptop?
[00:51] <RAOF> Hm.  My camera seems to have been infected by 10.04 branding.  Everything's a shade of purple, and streaky :(
[00:53] <BUGabundo> aahaah
[00:58] <bjsnider> what kind of ants were these exactly?
[01:02] <bryceh> bjsnider, that calls for a pun but I can't think of one
[02:24] <johanbr> bryceh, "it's better to have your computer bitten by bugs than eaten by ants" ?
[04:21] <Sarvatt> well XAA: disable render accel in -ati just now should fix part of bug #513956
[06:45] <bryceh> Sarvatt, yeah although I'm uncertain there was any configuration where EXA worked for jesse
[06:56] <RAOF> Is there any way we can fiddle with acpi lid status from userspace?  I'm suspicious that bug #53618 's low-res on laptop open is due to the intel assuming lvds is disconnected because the lid's closed, and so X bails with no screens.
[06:56] <RAOF> Leaving the actual bug as to why X is getting SIGQUITted.
[06:58] <bryceh> RAOF, I recall there were some various acpi tools, but I don't remember if they could update the lid status
[07:05] <RAOF> Hm.  i915 doesn't seem to have any lid-status options, either.  Are they just quirking lids on an as-discovered basis?
[07:22] <bryceh> Sarvatt, graph went down today :-) http://www2.bryceharrington.org:8080/X/Reports/ubuntu-x-swat/totals-lucid.svg
[07:24] <tjaalton> btw I tested whot's wacom-branch that'll likely become 0.10.5 very soon.. works fine
[07:25] <bryceh> tjaalton, great
[07:27] <tjaalton> bryceh: openchrome is twice on the graph
[07:28] <bryceh> that's weird
[07:28] <tjaalton> or is the other "the remainder"?
[07:28] <bryceh> maybe
[07:28] <tjaalton> same color though
[07:28] <bryceh> but I didn't do the remainder thing for this graph, as there weren't as many packages
[07:29] <bryceh> it's completely rewritten graph code (done in python instead of perl this time), but uses the same gnuplot code
[07:29] <bryceh> the black is suspicious
[07:30]  * bryceh adds to his todo list to investigate this one day
[07:34] <bryceh> tjaalton, sometimes I think having my sons' room right outside my office was a bad design choice
[07:39] <tjaalton> bryceh: hah :)
[07:39] <tjaalton> I woke up at 5:30 this morning
[07:39] <tjaalton> same yesterday
[07:41] <tjaalton> waiting the time when we switch to summertime
[07:41] <tjaalton> the weekend after next I think
[07:43] <tjaalton> bryceh: we keep the crib in our bedroom, and the middle-one still comes every night there, so it's pretty crowded there ;)
[07:44] <tjaalton> s/there$//
[07:48] <bryceh> heh
[08:08] <bryceh> tjaalton?
[08:08] <bryceh> tjaalton, it's baaack
[08:09] <bryceh> http://bryceharrington.org/X/Reports/ubuntu-x-swat/PkgList/versions_current.html
[08:10] <tjaalton> bryceh: excellent, thanks
[10:35] <Ng> awesome, X just crashed when I opened a huge png in firefox
[10:55] <richthegeek> Can someone take a look at #540564. Seems like it might be quite important.
[11:06] <richthegeek> prepare to type kick...
[11:07] <richthegeek> !help | richthegeek
[11:27] <tseliot> bug ##540564
[11:27] <tseliot> heck, bug #540564
[11:29] <tseliot> richthegeek: hmm... kernel oops with the Nvidia proprietary driver, it may not be easy to debug. apw, any ideas?
[11:30] <richthegeek> tseliot, one moment
[11:30] <richthegeek> sorry, I meant #540834
[11:30] <richthegeek> bug #540834
[11:30] <richthegeek> #540564 isn't exactly a massive issue compared to #540834
[11:32] <richthegeek> i gotta get to uni now, won't be able to do any testing until this evening (currently 11.31 for me, not around till 5.31)
[11:32] <tseliot> richthegeek: I guess that happens using nouveau (try booting in safe mode). Also, you might want to ask Keybuk in #ubuntu-devel about plymouth
[11:33] <richthegeek> tseliot: safe mode on a livecd? what's the key combo for that?
[11:33] <tseliot> tjaalton: ^^
[11:33]  * tseliot hasn't used that mode for a while now
[11:34] <richthegeek> right, im off, leave this running though./
[11:35] <tjaalton> it's probably hung then
[11:35] <tjaalton> if nothing works
[11:39] <tjaalton> commented
[13:09] <rye> richthegeek, are you sure it is not related to #534469 ?
[13:09] <rye> richthegeek, what happens if you actually unplug the second display?
[16:25] <Sarvatt> phew crazy morning already and it's only been 2 hours :D
[16:26] <Sarvatt> bryceh: XAA is used by -ati if <=32MB vram which that Jesse person had, he should have an option in bios to up that which would fix all his EXA problems :(
[16:28] <Sarvatt> http://www2.bryceharrington.org:8080/X/Reports/ubuntu-x-swat/totals-lucid.svg went down?? I see a huge spike, maybe that went up after you said that
[16:28] <Sarvatt> nouveau is busted for me completely
[16:29] <Sarvatt> removing quiet splash makes plymouth segfault and boot is hung
[16:29] <Sarvatt> not removing it leaves the splash screen up 100% of the time and I can't get gdm to start right
[16:33] <tseliot> Sarvatt: was this caused by a update of nouveau?
[16:33] <tseliot> an
[16:34] <Sarvatt> no, plymouth :(
[16:35] <Sarvatt> it was working fine with the same nouveau before these last few plymouth updates (back around 0.8.0-~12 or -~14)
[16:36] <tseliot> Sarvatt: you might want to ask Keybuk about that in #ubuntu-devel
[16:39] <Sarvatt> I dont have time to troubleshoot it more though, completely swamped with other things at the moment.. in the middle of trying to fix 6 other bugs and wont be near that machine today
[16:41] <Sarvatt> people emailing me "reminding" me to update xorg-edgers packages every day now..
[16:41] <rye> Sarvatt, how many displays do you have attached to your nouveau box?
[16:41] <knittl> hi. i really want suspend to work with nvidia :D
[16:41] <Sarvatt> just the 1
[16:41] <knittl> where can i install new drivers?
[16:41] <rye> hm... Then bug #533135 does not apply
[16:41] <Sarvatt> knittl: they arent in the archive yet, but the new ones will almost certainly fix your resume problems
[16:42] <knittl> Sarvatt: is there a ppa available?
[16:42] <Sarvatt> not that I know of
[16:42] <knittl> nvidia website?
[16:42] <Sarvatt> not compatable with lucid
[16:42] <knittl> will it break alternative system or sth?
[16:42] <Sarvatt> yeah
[16:42] <knittl> aw crap
[16:42] <Sarvatt> just give it a few days, everyone is swamped trying to get beta 1 ready
[16:43] <knittl> I installed 195.36.15 from the nvidia installer and I've done four
[16:43] <knittl> successful suspend/resume cycles, so it does seem to fix the problem.
[16:43] <knittl> where has he got 195.36 from? :D
[16:43] <knittl> oh hm. beta is due today. alright then
[16:43] <knittl> #534754
[16:43] <Sarvatt> tseliot: I've been marking nvidia-graphics-drivers bugs guaranteed fixed by 195.36.15 as (Needs 195.36.15) in the subject whenever you update it
[16:43] <knittl> bug #534754
[16:44] <ricotz> Sarvatt, hi, have nouveau running with compiz
[16:44] <knittl> thx ubottu
[16:44] <tseliot> knittl, Sarvatt: I've uploaded 195.36.15 to Lucid but it will be built only after the beta
[16:44] <Sarvatt> got nvidia-graphics-drivers bugs down to 1 page so they are easy to spot
[16:44] <Sarvatt> ahh there ya go knittl :)
[16:44] <tjaalton> if it's plymouth that breaks nouveau then keybuk needs to be made aware of it ASAP
[16:44] <knittl> tseliot: great. thank you :)
[16:44] <knittl> where's the build queue again?
[16:44] <tseliot> Sarvatt: really, 1 page? Impressive
[16:45] <Sarvatt> ricotz: yeah I heard, old mesa? I'll let ya know if I see any mesa commits that fix it so you can update
[16:45] <ricotz> yes, the older mesa package from ppa
[16:46] <ricotz> some graphic errors, but it is stable
[16:46] <tseliot> knittl: https://launchpad.net/builders/ perhaps?
[16:49] <Sarvatt> tseliot: why the heck is drm loading - http://launchpadlibrarian.net/41177525/OopsText.txt
[16:49] <Sarvatt> tseliot: the problem is nouveau isnt blacklisted for them
[16:50] <tseliot> let me check
[16:50] <Sarvatt> just looked at the bug you linked in another channel
[16:50] <tseliot> maybe /usr on a different partition?
[16:50] <Sarvatt> https://bugs.edge.launchpad.net/ubuntu/+source/linux/+bug/540564
[16:50] <Sarvatt> maybe, asking
[16:51] <tseliot> thanks
[16:51] <tseliot> I plan on dealing with that too
[16:51] <knittl> tseliot: no, not what i was looking for. nevermind, not that important
[16:52] <tseliot> knittl: my upload hasn't been approved yet (as we're in beta freeze)
[16:52] <tseliot> maybe you'll see it tomorrow (?)
[16:53] <knittl> no problem ;)
[16:54] <knittl> Fixed a bug that caused the X server to crash when rendering occurred while the X server was not on the active VT.
[16:54] <knittl> \o/
[16:54] <knittl> :)
[16:56] <Sarvatt> knittl: yeah the people that needed that fix were very easy to identify because they all had the same backtrace showing it still rendering after a VT switch (such as when suspending)
[16:56] <knittl> i also need that fix ;)
[17:02] <Sarvatt> ricotz: commits prefixed dri/nouveau don't apply to gallium nouveau drivers so no need to rebuild and check those incase you're doing that
[17:03] <Sarvatt> thats classic mesa nouveau_vieux_dri.so for <NV30
[17:04] <ricotz> Sarvatt, not doing that ;-), thanks
[17:04] <ricotz> Sarvatt, why does mesa hasnt got a "make dist"?
[17:11] <Sarvatt> because mesa's build system is horrible :) the maintainers mostly use scons on windows.. you can use something like this though - tar --exclude=debian --exclude=debian/* --exclude=.git --exclude=.git/* -cf - mesa | gzip -9 >mesa_7.9.0+git20100318.xxxxxxxx.orig.tar.gz
[17:12] <Sarvatt> uploading a new mesa to edgers now since it fixes the texture tiling problems on intel now that its defaulted to on
[17:14] <Sarvatt> i need to bump libdrm in there but it needs a lot of build system changes, not enough time in a day
[17:26] <bryceh> Sarvatt, whoops, yeah it was down at the point I mentioned it to you
[17:27] <bryceh> Sarvatt, looks like a bunch of new nouveau reports came in plus some other stuff
[17:29] <tjaalton> probably your tagging run that made that :)
[17:31] <bryceh> Sarvatt, btw can you renew my xorg-edgers membership?
[17:33] <Sarvatt> sure thing, done
[17:34] <Sarvatt> hmm yeah tagging run was a little off
[17:34] <Sarvatt> marked this karmic - https://bugs.edge.launchpad.net/ubuntu/+source/xserver-xorg-input-evdev/+bug/537801
[17:35] <bryceh> tjaalton, oh yeah could be
[17:35] <bryceh> tjaalton, I fixed a unicode bug that was causing the script to crash early on in processing
[17:36] <bryceh> tjaalton, btw I got the bottom bit of the graph back
[17:36] <Sarvatt> oh didnt remove the lucid tag so no big deal
[17:36] <bryceh> Sarvatt, yeah it would have put lucid on there if it saw it
[17:37] <bryceh> er, if it didn't see it there already
[17:37] <bryceh> although admittedly it's not hard to confuse the scripts
[17:38] <bryceh> ahhh ok so that's why there's so many more packages listed
[17:38] <bryceh> it used to crap out halfway through processing and was going through them package by package
[17:44] <tjaalton> bryceh: whee, ok
[17:46] <bryceh> makes the graph look smooshed though.  hmm
[17:56]  * bryceh cheats and just makes graph wider
[18:02] <bryceh> tjaalton, looks like whatever I fiddled with solved the -openchrome doubling too
[18:03] <bryceh> oh wait, now there's a double -vesa

[18:11] <bryceh> aha there we go
[18:14] <Sarvatt> woohoo, my wife was using one of my laptops for 2 weeks or so and now she's complaining about going back to windows now that hers is fixed because she got so used to having all the useful info on the panel :) its just too bad I had lucid on there and she got frustrated hitting enter restarted gdm and the splash is pretty pointless on with non KMS since we only have the smooth transition stuff with KMS 
[18:14] <Sarvatt> drivers and its only there for a second
[18:14] <Sarvatt> no photoshop is the deal breaker for her though
[18:15] <Sarvatt> plus she hated the new min/max/close button placement and moving things to the right in the correct order looks messed up since the minimize button border is designed to be in the middle
[18:16] <Sarvatt> I dont think anyone on the design team uses gnome panel drawers because the background is screwed up also :)
[18:16] <hyperair> heh
[18:16] <hyperair> go complain on #ayatana
[18:17] <bryceh> Sarvatt, email shuttleworth ;-)
[18:18] <bryceh> Sarvatt, my wife is not fond of the button movement idea either
[18:18] <hyperair> i am not fond of the button movement.
[18:18] <bryceh> but I have so far refrained from upgrading her to new ubuntus until they're released
[18:19] <bryceh> (and usually not for a couple weeks after)
[18:19] <hyperair> but i've never once used any of ubuntu's default themes for more than a day.
[18:19] <tjaalton> my wife eats my dogfood
[18:19] <Sarvatt> i loved the stock human netbook theme
[18:20] <tjaalton> though I had karmic until january
[18:26] <Sarvatt> anyone used photoshop through wine? i'm guessing cs4 wont work but she usually uses cs3 anyway
[18:27] <tjaalton> check winehq
[18:28] <tjaalton> http://appdb.winehq.org/objectManager.php?sClass=application&iId=17
[18:29] <tjaalton> looks like cs3/4 won't work
[18:30]  * hyperair hasn't used photoshop in over two years.
[18:30] <hyperair> i think i installed it once, but never used it
[18:30] <hyperair> i think it was cs3.
[18:52] <bryceh> Sarvatt, there is a photoshop-like UI for gimp.  I forget the name though
[18:55] <tjaalton> it's merged for 2.8
[18:55] <tjaalton> which should arrive for christmas
[19:33] <kazade> Hi all, I need some help. My bro has just upgraded to Lucid, but now KMS causes him a blank screen, he's using nouveau how do I instruct him into a failsafe (vesa) mode?
[19:33] <kazade> he can only see as far as grub, and only then by pressing shift otherwise the refresh rate goes out of range or something immediately after
[19:37] <kazade> anyone?
[19:51] <rafiyr> I've just reported bug 541453, which requires a small patch be applied to the wacom X driver to get basic functionality for ntrig devices to work on lucid, out of the box.
[19:54] <tjaalton> rafiyr: is it upstream?
[19:55] <rafiyr> no
[19:55] <tjaalton> huh, didn't know there was a project called lucid
[19:55] <rafiyr> and won't be
[19:55] <tjaalton> why not?
[19:56] <rafiyr> lucid lynx, ubuntu 10.04
[19:56] <tjaalton> yes, but you filed it against a project, not package
[19:56] <rafiyr> The only thing that patch does is enable the wacom driver to support another manufacturer's hardware.  They didn't seem particularly interested when I sent the patch to the mailing list
[19:57] <rafiyr> Ah
[19:57] <tjaalton> "Lucid Editor NOT UBUNTU"
[19:57] <rafiyr> Sorry, not quite sure where to file.  I suppose it would have been easier to file the patches separately to the packages
[19:57] <rafiyr> :)
[19:57] <tjaalton> done
[19:58] <tjaalton> who proposed the patches and when?
[19:58] <tjaalton> I'd check the list
[19:59] <rafiyr> I proposed a similar patch several months ago rafi@ugcs.caltech.edu is the address I think I used
[19:59] <bryceh> rafiyr == Rafi Rubin I assume?
[19:59] <tjaalton> found it
[20:00] <bryceh> rafiyr, oh hey you're a caltechie too?  :-)
[20:00] <rafiyr> Yup
[20:00] <rafiyr> undergrad plus a number of years as research staff after
[20:00] <rafiyr> currently at upenn working on my phd
[20:01] <rafiyr> Are there a lot of techers making trouble for ubuntu?
[20:01] <tjaalton> rafiyr: well seems like you need to resend it, Ping didn't decline it but want's to be sure it doesn't break anything
[20:01] <bryceh> rafiyr, I just went there for my masters
[20:02] <bryceh> rafiyr, haven't run into any others
[20:02] <rafiyr> tjaalton: oh. I guess I misread or missed something, that was a while ago
[20:02] <rafiyr> when were you there?
[20:02] <bryceh> rafiyr, btw it will work with various processes better to attach files individually to bug reports rather than in a tar
[20:02] <tjaalton> rafiyr: since it needs kernel support too it's likely too late for lucid, especially since it's not upstream
[20:03] <rafiyr> understood
[20:03] <bryceh> for example, patch files get auto-detected and make it through certain filters so they bubble up to the top of priority lists
[20:03] <tjaalton> indeed
[20:03] <bryceh> also makes it easier to look at the patches online, rather than downloading and uncompressing the tar
[20:03] <rafiyr> I'll check with jiri to see why its not upstream yet, and if he can fix that.
[20:03] <bryceh> so stuff gets more review
[20:03] <tjaalton> rafiyr: yeah it needs upstream review
[20:04] <rafiyr> I didn't see an obvious method to attach multiple patches
[20:04] <tjaalton> one at a time
[20:04] <bryceh> rafiyr, there isn't, just do separate comments for each
[20:04] <rafiyr> Ah
[20:04] <bryceh> well, if you reply to a bug via email you can do multiple attachments
[20:04] <bryceh> but not thru the web
[20:05] <bryceh> btw xf86-input-wacom_ntrig_2010_02_03.patch is already in lucid; I put that one in last week, for 0.8.4.1-0ubuntu5
[20:05] <rafiyr> Well, first time using launchpad, so I'll just call this a learning experience.
[20:05] <rafiyr> oh, thought that only hit your ppa
[20:05] <rafiyr> thanks
[20:05] <bryceh> no it looked sane so I just put it in the distro proper
[20:06] <rafiyr> And yeah, I'll resend it to linuxwacom.
[20:06] <bryceh> 2010_03_10_ntrig.patch - this is a kernel patch?
[20:07] <bryceh> yep
[20:13] <Sarvatt> kazade: adding blacklist=nouveau to the kernel command line in grub should work
[20:14] <tjaalton> Sarvatt: but is plymouth busted as you suggested?
[20:14] <kazade> Sarvatt, thanks that's good to know. Luckily he had a previous kernel so that got him into vesa mode :)
[20:15] <tjaalton> blacklisting does the same
[20:15] <Sarvatt> it wont load the drm renderer for plymouth if nouveau is blacklisted so it should still work for vesa?
[20:16] <Sarvatt> i haven't tested that
[20:20] <rafiyr> If the march 10nth patch isn't applied to the release kernel, can we shift to using wacom instead of evdev by default?
[20:21] <rafiyr> More context: wacom as the default driver to support the n-trig touch sensor.  wacom is already the default for the pen sensor.
[20:48] <tjaalton> bryceh: you said on the n-trig patch that you uploaded something a week ago? the one in the archive was touched by me though
[20:48] <tjaalton> s/patch/bug
[20:48] <tjaalton> and there's no wacom-tools anymore :)
[20:53] <bryceh> tjaalton, durff
[20:56] <bryceh> tjaalton, I see there's no xsfbs/ in -wacom's debian dir, should I add that so I can set up the patch system?
[21:02] <tjaalton> bryceh: that's one option
[21:03] <bryceh> tjaalton, other options?
[21:04]  * bryceh adds xsfbs
[21:06] <tjaalton> well that's probably the easiest one, though it adds some bloat to the diff
[21:19] <bryceh> tjaalton, hey with the xorg-pkg-list versions report, I've been collecting each day's page, I guess for historical reference.  Is there actually some value to continuing to do that?
[21:20] <bryceh> if you care only about the current day's versions, I could limit it to just producing one page, and get rid of the historical data
[21:21] <bryceh> if there's some value to it I can leave it as is, it doesn't actually take up that much disk space
[21:26] <tjaalton> bryceh: oh, didn't know/remember that. can't think of a reason to keep those right now
[21:26] <bryceh> alright
[21:26]  * bryceh todos a cleanup
[21:26] <tjaalton> but if they are harmless, then why not keep them for awhile
[21:26] <tjaalton> or not :s
[21:26] <bryceh> hehe
[21:27] <bryceh> well now that I've got more reports I'm trying to mold the older ones into some sense of consistency with the new ones
[21:27] <bryceh> -wacom uploaded for real this time
[21:28] <rafiyr> bryceh: how do I grab the src package to take a look?
[21:29] <bryceh> rafiyr, not sure if the source package is available.  I can pop it into the ppa though.
[21:29] <bryceh> ...done
[21:29] <bryceh> should show up there in a couple minutes
[21:30] <rafiyr> bryceh: If I just do a general update of the package will I get the fixed binary, or is that pushed to beta1?
[21:30] <tjaalton> rafiyr: does it work without the kernel bits?
[21:31] <bryceh> rafiyr, if you have the ppa installed, yeah you should get it by just doing a general update
[21:31] <bryceh> if you don't have the ppa installed, then it will come via a regular update in a day or two
[21:31] <tjaalton> the archive is frozen, no?
[21:31] <tjaalton> at least until tomorrow
[21:31] <bryceh> tjaalton, right, which is why it will come in a day or two
[21:32] <tjaalton> hum right
[21:32] <rafiyr> tjaalton: I think it should work fine with the 34-rc1 kernel
[21:32] <rafiyr> but the last couple firmwares really broke everything, and will at least need that update
[21:32] <tjaalton> rafiyr: so the kernel patches were from .34rc1?
[21:33] <rafiyr> tjallton: mostly, but the last one was a minor fix for BTN_TOUCH, that hasn't made it to the mainline yet.
[21:33] <rafiyr> -wacom doesn't really care about that event and is unaffected
[21:33] <tjaalton> ok
[21:34] <tjaalton> wonder if the waltop will work with a similar patch
[21:35] <rafiyr> It should be easy to test
[21:35] <tjaalton> yeah I'll try that next weekend
[21:37] <rafiyr> I will need to test -wacom from that ppa.  I know the pen works fine, but I haven't used touch on such an old version for quite a while
[21:40] <bryceh> rafiyr, I have a fujitsu multitouch laptop I can use for testing.  How do I check to see what mt hardware it uses?  lsusb, lshw, lspci don't give any indication of what manufacturer it is
[21:41] <bryceh> other than Intel or 'Linux Foundation'
[21:41] <rafiyr> no vendor id?
[21:41] <rafiyr> Bus 003 Device 002: ID 1b96:0001 N-Trig Duosense Transparent Electromagnetic Digitizer
[21:41] <rafiyr> That first 4 digit hex code is manufacturer
[21:41] <bryceh> rafiyr, nope
[21:42] <rafiyr> is it serial?
[21:42] <tjaalton> which model is it?
[21:42] <rafiyr> wacom was mostly serial for a long time
[21:43] <bryceh> http://pastebin.com/gmkcEnfg
[21:43] <rafiyr> Oh, try "sudo lsusb"
[21:43] <bryceh> http://pastebin.com/p6zPqQP5
[21:43] <bryceh> lshw for good measure:  http://pastebin.com/GfWg11AR
[21:44] <tjaalton> it's a wacom
[21:44] <tjaalton> probably serial then
[21:45] <bryceh> how can I verify that?
[21:45] <rafiyr> Xorg.0.log
[21:46] <Sarvatt> hmm thats odd, nouveau headers in libdrm get installed to ${includedir}/nouveau ?
[21:46] <bryceh> (II) config/udev: Adding input device Serial Wacom Tablet (/dev/ttyS0)
[21:46] <bryceh> aha
[21:46] <tjaalton> it doesn't work?
[21:46] <rafiyr> for what its worth there was a press release that fujitsu and n-trig are going to work together for a next gen device.  One capable of supporting (gasp) more than 5 fingers
[21:46] <bryceh> heh, like the most obvious place for it, didn't even think to look
[21:47] <tjaalton> the pen should work at least
[21:47] <bryceh> rafiyr, awesome, the venusians will be so happy
[21:47] <tjaalton> wow, I have ten fingers
[21:47] <tjaalton> :)
[21:47] <rafiyr> well they actually said 10 or more
[21:48] <tjaalton> lots of handwaving
[21:48] <Sarvatt> too bad wacom only handles 1 or 2 finger gestures :D
[21:48] <rafiyr> plenty of talk about mt being interesting for multi-person interaction.  And for that, I could see wanting a bit more than 10.  Like for elementary schools wanting to support 10+ children finger painting on a giant table display that cost more than the teacher
[21:49] <nishanth> can someone help me fix the desktop visual effects
[21:50] <nishanth> ?
[21:50] <tjaalton> just ask, don't ask to ask
[21:50] <Sarvatt> would kind of help if you gave us more info on what the problem is :)
[21:51] <bryceh> tjaalton, can I ping you?
[21:51] <bryceh> ;-)
[21:51] <tjaalton> bryceh: well you just.. oh, nevermind ;)
[21:51] <bryceh> ok, so stylus works out of the box.  nice.  no eraser though, and touch is not working
[21:52] <nishanth> well i tried to change the appearance preference from none to extra and it does not do it
[21:52] <rafiyr> is it just a matter of the X  config?
[21:52] <nishanth> it gives a prompt saying desktop effect could not be enabled after blinking a couple of times
[21:52] <Sarvatt> where's this wacom patch at that extends it for n-trig support?
[21:52] <Sarvatt> the udev rules need updating for sure
[21:53] <rafiyr> http://ofb.net/~rafi/xf86-input-wacom_ntrig_2010_02_03.patch
[21:53] <nishanth> is there a way i can fix this?
[21:54] <Sarvatt> nishanth: please run ubuntu-bug xorg and link the bug report here, we need to see logs
[21:54] <rafiyr> The actual delta is just:
[21:54] <rafiyr> -	{ 0xE3, 2540, 2540, &usbTabletPC   }  /* TabletPC 0xE3 */
[21:54] <rafiyr> +	{ 0xE3, 2540, 2540, &usbTabletPC   },  /* TabletPC 0xE3 */
[21:54] <rafiyr> +	{ 0x1 , 1122,  934, &usbTabletPC   }  /* N-Trig TabletPC */
[21:54] <rafiyr>  
[21:54] <rafiyr> -	if (sID.vendor == WACOM_VENDOR_ID)
[21:54] <rafiyr> +	if (sID.vendor == WACOM_VENDOR_ID || sID.vendor == 0x1b96)
[21:54] <bryceh> mm, with some futzing in gimp, pressure sensitivity works, and the eraser will draw if I push hard, but no erasing
[21:54] <nishanth> can you tell me how to do it plz... i am very new to linux
[21:55] <Sarvatt> open a terminal or press alt+f2 and type ubuntu-bug xorg
[21:55] <bryceh> Sarvatt, it's in the multitouch ppa you set up for me
[21:56] <rafiyr> bryceh: first off test the input device to make sure you're seeing the events (xinput test).  And if so, you might want to futz with the pressure curve setting with xsetwacom
[21:56] <Sarvatt> sheesh chrome is using REDICULIOUS amounts of ram the past week or so, 10 launchpad tabs is using 1.5GB memory
[21:57] <rafiyr> Yeah, things have gotten so bloated, lynx is eating 3.5MB, tsk tsk
[21:57] <bryceh> rafiyr, yeah xinput test is seeing the eraser events
[21:58] <rafiyr> bryceh: xsetwacom -x get eraser Presscurve
[21:58] <Sarvatt> i believe you need to create a input/wacom symlink and another symlink for input/wacom-touch for the touch device? the wacom udev rules are only creating the symlinks for wacom vendor id's
[21:59] <tjaalton> are those links used by anything, or just for convenience?
[21:59] <rafiyr> Do udev and hal actually just poke at serial devices looking for wacom digitizers?
[22:00] <rafiyr> The driver can certainly tolerate using a single device node for all three tools (that's the way I used to use it, until I split off touch).
[22:01] <Sarvatt> oh it's a serial device? are you sure its even using wacom and not evdev then bryceh?
[22:02] <tjaalton> evdev doesn't handle serial devices aiui
[22:02] <rafiyr> If it did, you could check by trying to draw a straight line :)   (wacom smooths, evdev doesn't)
[22:03] <Sarvatt> oh bryceh> +(II) config/udev: Adding input device Serial Wacom Tablet (/dev/ttyS0)
[22:03] <nishanth> ok i did "ubuntu-bug -p xorg" it opened something called launchpad
[22:04] <nishanth> now what?
[22:04] <Sarvatt> guess he added the new match to the rules, are the subdevices not getting set up?
[22:04] <Sarvatt> do everything it says to file it and paste a link to the bug report when its done
[22:04] <tjaalton> the wacom rules already have entries for serial devices
[22:04] <tjaalton> has
[22:04] <Sarvatt> yeah but only wacom and fujitsu
[22:05] <tjaalton> and this was wacom
[22:05] <Sarvatt> huh.. i thought he was working with n-trig.. I'll shut up now :)
[22:06] <tjaalton> he thought so as well ;)
[22:06] <tjaalton> I think
[22:06] <tjaalton> now I'll shut up
[22:06] <rafiyr> <sheep mode> shutting up</sheep mode>
[22:07] <nishanth> is there a way to fix the desktop visual effects
[22:07] <nishanth> also does anyone know how to fix plymouth?
[22:07] <tjaalton> what hw do you have?
[22:08] <tjaalton> the graphics card
[22:09] <nishanth> tjaalton : are you asking me?
[22:09] <tjaalton> yes
[22:09] <nishanth> oh ok
[22:10] <nishanth> is there a way to find out what it is?
[22:10] <tjaalton> lspci |grep VGA
[22:12] <nishanth> VGA compatible controller: Intel Corporation Core Processor Integrated Graphics Controller (rev 02)
[22:12] <rafiyr> While multitouch isn’t factory enabled for the touchpad, it can be turned on through the Control Panel.
[22:12] <rafiyr> bryceh: there's you're problem just go to the control panel...
[22:13] <rafiyr> More seriously is the screen actually multi touch, or just the touchpad
[22:13] <rafiyr> The xorg log should report the actual wacom model, I think, that might help to answer the question.
[22:13] <rickspencer3> RAOF, hi
[22:13] <nishanth> tjaalton: VGA compatible controller: Intel Corporation Core Processor Integrated Graphics Controller (rev 02)
[22:13] <rickspencer3> just checking wrt the x meeting on Thursday
[22:14] <rickspencer3> it's been a couple days, wondering if you've been able to make progress?
[22:14] <tjaalton> nishanth: got it
[22:14] <bryceh> yep, wacom.  draws nice straight lines
[22:15] <nishanth> tjaalton; is this some driver related problem?
[22:15] <tjaalton> nishanth: if you already have effects working it's not a driver problem
[22:15] <bryceh> got the eraser working.  was a pebkac bug
[22:15] <rafiyr> what's pebkac?
[22:15] <nishanth> tjaalton: I dont have effects working
[22:15] <tjaalton> bryceh: needed to configure it in gimp?
[22:15] <bryceh> (i.e. have to click the eraser on the eraser button first.  dhurr)
[22:15] <RAOF> rickspencer3: I presume you mean the meeting on Wednesday (or Tues your time?).  I've had some progress on the bug triage, but I wanted to finish off f-spot first.  I've got more time scheduled for X going forward.
[22:15] <rickspencer3> RAOF, yest hat meeting
[22:16] <rickspencer3> RAOF, ok, thanks
[22:16] <nishanth> tjaalton: i tried to change the visual effect from none to extra and it could not do it
[22:16] <rafiyr> um, yeah, with each physical tool, you click the gimp tool you want it to represent.  Just like drawing with the mouse.
[22:16] <tjaalton> nishanth: then file the bug
[22:16] <tjaalton> nishanth: create the lp account etc
[22:16] <Sarvatt> thats an arrandale :(
[22:16] <RAOF> rickspencer3: I've got all the nouveau bugs in either upstreamed or waiting for information from the reporter state, at least.
[22:17] <tjaalton> Sarvatt: ok, so won't work?
[22:17] <nishanth> tjaalton: i did 
[22:17] <rickspencer3> RAOF, nice
[22:17] <Sarvatt> it should work, theres just issues for some people, need a bug report to look at it more
[22:17] <tjaalton> nishanth: so which bug # is it?
[22:17] <tjaalton> can't see it on the xorg list
[22:18] <bryceh> (--) Serial Wacom Tablet eraser: Wacom General ISDV4 tablet
[22:18] <nishanth> tjaalton: how can i check if it is there?
[22:18] <bryceh> (II) "Fujitsu FUJ02E3": Device reopened after 1 attempts.
[22:19] <tjaalton> nishanth: check your profile bug stats
[22:19] <Sarvatt> i dont see a nishanth user on launchpad, what name did you create the account with?
[22:19] <bryceh> rafiyr, pebkac == 'problem exists between keyboard and chair'
[22:20] <bryceh> or in this case I guess it should be pebsac == 'problem exists between screen and chair' ;-)
[22:20] <rafiyr> ;)
[22:21] <nishanth> tjaalton : check now
[22:21] <tjaalton> Driver		"vesa"
[22:22] <tjaalton> there's your problem
[22:22] <tjaalton> you are not using the intel driver..
[22:22] <nishanth> is there a  way to know what driver i am using?
[22:22] <tjaalton> for one reason or another failsafe kicked in
[22:23] <tjaalton> well, vesa
[22:23] <nishanth> i think it is vesa
[22:23] <tjaalton> I just said that :)
[22:23] <tjaalton> it says so on your xorg.conf
[22:23] <tjaalton> sudo rm /etc/X11/xorg.conf
[22:24] <Sarvatt> nishanth: you manually changed the driver to vesa?
[22:25] <Sarvatt> or did you install it recently with the safe graphics option maybe?
[22:25] <Sarvatt> not sure if casper's xforcevesa xorg.conf gets transferred if you install in that mode
[22:26] <bryceh> what is "Virtual core XTEST pointer" ?
[22:26] <tjaalton> the appearance capplet should probably point out if the driver is vesa
[22:27] <nishanth> ok i removed it
[22:27] <nishanth> tjaalton: why did you want me to remove it?
[22:27] <tjaalton> nishanth: because you don't want to use it
[22:28] <tjaalton> nishanth: then reboot
[22:28] <nishanth> i installed 9.10 with safe graphics mode and then i upgraded to 10.04
[22:28] <nishanth> so  all i had to do was remove xorg.conf?
[22:29] <tjaalton> yes
[22:29] <nishanth> is there any other thing that i need to install to take its place?
[22:29] <tjaalton> no
[22:29] <Sarvatt> nope
[22:29] <nishanth> ok
[22:29] <Sarvatt> that was the problem though, i'm surprised vesa even worked for you
[22:30] <Sarvatt> makes sense though, you should need to install karmic in safe graphics mode because its too old to support that new of a video card
[22:31] <tjaalton> should jockey offer to remove the obsolete xorg.conf if it knows the hw is properly supported?
[22:31] <tjaalton> in the new version
[22:35] <ricotz> Sarvatt, i think you need to update xserver-xorg-video-nouveau aswell http://cgit.freedesktop.org/nouveau/xf86-video-nouveau/commit/?id=e2146d3b29a4bea3d584c145e3190c3313692ed9
[22:36] <nishanth> yay!! it worked
[22:37] <tjaalton> there you go
[22:37] <nishanth> but still did not fix plymouth
[22:37] <tjaalton> run 'ubuntu-bug linux' then
[22:37] <tjaalton> or perhaps it's plymouth again
[22:38] <Sarvatt> ricotz: i needed to update libdrm and such first before anything and that *just* finished... give me some time man :)
[22:38] <nishanth> so just type ubuntu-bug linux in terminal ?
[22:38] <tjaalton> yes
[22:38] <nishanth> ok
[22:39] <tjaalton> it'll gather logs that the kernel team needs
[22:39] <ricotz> Sarvatt, sorry dont wanted to push you
[22:41] <bryceh> rafiyr, since this is a serial touchscreen laptop, is it at all relevant for our testing of MT?
[22:42] <bryceh> otherwise I'll have to wait until the new hw comes
[22:43] <tjaalton> bryceh: btw, some errors in the versions_current list. for instance -ati versions in debian are old
[22:43] <rafiyr> bryceh: if its mt, it will be eventually
[22:43] <bryceh> tjaalton, ok I'll investigate
[22:44] <tjaalton> bryceh: seems to be the only one
[22:45] <nishanth> strange it did not give me a  new launch pad  page saying report it 
[22:56] <Sarvatt> oops, looks like I got booted from freenode, nishanth: what exactly is your problem with plymouth?
[22:56] <nishanth> i dont see the plymouth animation when booting
[23:04] <Sarvatt> when is the last time you updated your system?
[23:05] <Sarvatt> you don't see the ubuntu logo at all when you boot up?
[23:06] <nishanth> today afternoon
[23:08] <Sarvatt> theres not really much animation to it, if you boot fast enough I dont think it even loads the progress indicator dots, thats why I was wondering if you saw the ubuntu logo at all
[23:09] <nishanth> i am having a new problem now
[23:09] <Sarvatt> whoa is this new?? Get:1 http://ppa.launchpad.net/xorg-edgers/ppa/ubuntu/ lucid/main libosmesa6-dev 7.9.0~git20100318.3c0eab71-0ubuntu0sarvatt [828kB] -- I swear it used to just say the ppa.launchpad.net part not the specific PPA its from
[23:09] <nishanth> my mouse does not work on youtube videos
[23:10] <RAOF> Sarvatt: Yeah, I think that is new.
[23:10] <nishanth> i think it has got to do something with compiz cofig setting manager
[23:11] <RAOF> nishanth: What do you mean by “does not work”, and why do you think it has something to do with ccsm?
[23:12] <Sarvatt> firefox or chromium? does it work with effects set to normal instead of extra?
[23:12] <RAOF> Hooray for user-error bug reports.
[23:12] <nishanth> well let us say you want to watch  a video from the middle  instead of the begining
[23:12] <nishanth> i am going to uninstall compiz
[23:13] <RAOF> nishanth: You mean: left mouse button doesn't work in youtube?  Right, nspluginwrapper bug.  Hold down the right mouse button & left click works :)
[23:14] <nishanth> oh it worked
[23:14] <Sarvatt> nishanth: this kind of thing is more appropriate in #ubuntu+1
[23:15] <nishanth> is there a way to fix it?
[23:20] <apw> bryceh, here are some test kernels with the i915 powersave turned off for <= 945: http://people.canonical.com/~apw/i915-powersave-broken-lucid/
[23:20] <apw> [    4.719350] [drm] dynamic power saving: broken=1 enabled=0
[23:20] <apw> that tells you that we think it was broken, and it was not enabled ... kerenel command line option is king
[23:21] <apw> bryceh, images are actually still syncing ... be there in < 10m
[23:21] <apw> Sarvatt, RAOF ^^
[23:22] <RAOF> apw: Thanks.
[23:25] <Sarvatt> apw:  sweet, will give it a spin as soon as its up
[23:26] <Sarvatt> btw i'm fairly sure only intel_i915gm_info intel_i945gm_info need it, it's a framebuffer compression problem here on mine and only those two have .has_fbc = 1
[23:29] <Sarvatt> but being safe just incase is nice anyway :)
[23:34] <RAOF> Damnit!  apport-collect is failing again :(
[23:35] <bryceh> RAOF, error?
[23:36] <RAOF> https://bugs.edge.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/537745/comments/5 seems to be one, and another apport-collect just set the tag without attaching anything.
[23:37] <bryceh> oh that nutty precondition failed thingee again
[23:37] <RAOF> I think the backtrace in that comment means that it's a launchpad problem, not an apport one, right?
[23:41] <Sarvatt> oh hmm, i didn't think 915-945 ever had lvds downclocking support which would make the first hunk in drivers/gpu/drm/i915/intel_display.c useless but looks like it can