[00:06] <Sarvatt> bryce: uploaded a xserver-xorg-video-intel to x-updates for karmic since there are so many bug closers for it, incase people dont want to upgrade the whole x stack and mesa to try it out. fglrx for jaunty is _still_ published like 20 hours later..
[00:09] <bryce> excellent
[00:10] <Sarvatt> figured i'd let you do the version bump to reupload it :)
[00:53] <Sarvatt> oh darn, i looked for bugs by that guy to try to find one on launchpad for the changelog on the x-updates package too
[00:53] <Sarvatt> in bug 351761
[00:54] <Sarvatt> saw his upstream bug report in the git log
[22:26] <Sarvatt> does incomplete = needs info on launchpad? need more info on this bug to try to track it down https://bugs.edge.launchpad.net/bugs/390160
[22:27] <bryce> Sarvatt, yep
[22:28] <bryce> Sarvatt, technically "Incomplete" has two states
[22:28] <bryce> Incomplete w/ response, and Incomplete w/out response
[22:29] <Sarvatt> i wasnt sure if i couldnt just see the needs info option because i'm not in the right launchpad group, could have sworn i saw a needs info tag before
[22:29] <bryce> Bugs that are in the latter state we expire after about 30 days
[22:29] <bryce> ah, you probably saw that in a bugzilla bug
[22:30] <bryce> if there are ever bugs in state 'incomplete' that you ask a question on, note that this moves the bug to "incomplete with response"
[22:31] <bryce> so they won't auto-expire
[22:31] <bryce> what I usually do when asking a question is Incomplete->New, then New->Incomplete+myquestion
[22:31] <Sarvatt> by the way, heads up on something i just found in #ubuntu+1. they changed the Xv saturation ranges in the nvidia binary drivers and it doesnt transfer the settings right on upgrade
[22:32] <Sarvatt> the old value of 4096 in .nvidia-settings-rc is the new setting of 0, but upgrading with 4096 in the rc doesnt transfer it to 0 even though the control applet says its at 0
[22:33] <Sarvatt> so colors are really saturated unless you manually lower it and save, and then raise it back up to 0 and save
[22:33] <Sarvatt> this is in the 185.18.14 package
[22:34] <Sarvatt> incase you see any bugs in nvidia regarding colors being wrong with the binary drivers
[22:34] <Sarvatt> when playing back videos
[22:37] <Sarvatt> found it in this thread http://www.nvnews.net/vbulletin/showthread.php?t=133810
[22:46] <Sarvatt> is it ok if i bump the version on fglrx-installer for x-updates jaunty? i deleted the package since it had problems being binary copied but its still not deleted 2 days later so i cant recopy it
[22:46] <Sarvatt> ~jaunty2 ok? or 0ubuntu2~jaunty instead?
[22:48] <Sarvatt> i uploaded an updated synaptics to edgers too because its been like 1.5 months now that the ubuntu patches havent been readded and the amount of bugs about touchpad tapping are nuts so i figured it'd help some people at least..
[23:01] <bryce> Sarvatt, yeah feel free to up the fglrx-installer in x-updates
[23:02] <bryce> yeah it's been getting hard to ignore the touchpad tapping issues
[23:03] <Sarvatt> once gnome-settings-daemon 2.27.4 comes to karmic it wont even matter
[23:03] <bryce> if it is clear what needs done with synaptics, let me know.  otherwise I'm more or less leaving it to tseliot's judgment
[23:03] <Sarvatt> since the touchpad panel lets you enable/disable tapping properly now
[23:03] <Sarvatt> well i guess its still a problem for KDE
[23:04] <bryce> regarding the nvidia saturation values... perhaps you could talk to mvo about adding a transition for that?
[23:04] <Sarvatt> oh its really clear, theres a huge bug about it thats really clear about it, all of the ubuntu patches were dropped because the synaptics package name was changed in debian and its getting auto synced
[23:04] <Sarvatt> ah, will do regarding mvo
[23:05] <Sarvatt> http://patches.ubuntu.com/x/xfree86-driver-synaptics/extracted/104_always_enable_tapping.patch
[23:05] <Sarvatt> that patch forced tapping enabled by default, its disabled upstream by default
[23:05] <Sarvatt> the driver is called xserver-xorg-input-synaptics now
[23:07] <bryce> ahh
[23:07] <Sarvatt> the gnome-settings-daemon touchpad plugin doesnt enable/disable tapping in a way that works unless that patch is applied right now
[23:07] <bryce> ok if you assign the bug to me I'll get the patches moved over and stuff
[23:07] <Sarvatt> but that will be fixed in the next release
[23:07] <bryce> if you feel ambitious and want to do it, stick a debdiff on the bug and I'll sponsor for you
[23:09] <Sarvatt> doing that right now
[23:15] <Sarvatt> wgrant actually has it in his PPA and is the one the bug is assigned to https://edge.launchpad.net/~wgrant/+archive/ppa/+sourcepub/656773/+listing-archive-extra
[23:16] <Sarvatt> https://bugs.edge.launchpad.net/bugs/378391
[23:29] <bryce> ok thanks, I'll review and sponsor that tomorrow
[23:38] <Sarvatt> attached a debdiff to the bug anyway incase it helps any
[23:38] <Sarvatt> had already done it when i noticed :D
[23:49] <Sarvatt> the one on his ppa would be better though, i just didnt put 109 in the series because it didnt apply. they have changed around alps detection and settings upstream so i'm not sure how relevant it is at the moment though
[23:49] <Sarvatt> http://cgit.freedesktop.org/xorg/driver/xf86-input-synaptics/commit/?h=synaptics-1.1-branch&id=2b3325dc53d1a560b94b9c88aeb05b0f7f9085cd
[23:54] <Sarvatt> static Bool is_alps(LocalDevicePtr local); in 109 isnt needed anymore because they built detection into the driver to adjust the edge sizes for different devices now and that could be used, and they have changed the way tap detection happens which fixed needing to adjust fingerLow and fingerHigh for me on a synaptics model touchpad at least
[23:58] <Sarvatt> the other patch left out from jaunty's synaptics patch series here http://patches.ubuntu.com/x/xfree86-driver-synaptics/extracted/  	(108_syndaemon_xinput_props.patch)
[23:59] <Sarvatt> oops, is already upstream I meant to say