[03:11] <RAOF> Huh.
[03:12] <RAOF> Synaptics would be much more useful if it didn't reset the pointer position to (0,0) every five seconds of movement or so.
[03:16] <Sarvatt> RAOF: the fix went into rc6 :)
[03:17] <Sarvatt>  s/fix/revert/
[03:17] <RAOF> Right.  rc6 makes this Dell all manner of pleasant.
[03:17] <Sarvatt> cool beans, not surprised
[03:17] <RAOF> Or, rather, the lack of that fix makes this Dell all manner of unpleasant :)
[03:18] <RAOF> Sarvatt: Do you remember a bug where synaptics would keep resetting to (0,0)+
[03:18] <RAOF> ?
[03:18] <Sarvatt> hmm
[03:18] <Sarvatt> so theres a bug where unity does that regardless of the driver with wine
[03:18] <Sarvatt> i havent reported that yet
[03:18] <Sarvatt> its very annoying with steam menus
[03:19] <RAOF> Yeah.
[03:19] <Sarvatt> it happens on evdev and synaptics and mtouch here
[03:19] <Sarvatt> so its not a synaptics bug if thats what you're hitting
[03:19] <RAOF> No.
[03:19] <RAOF> This is the pointer moving, rather than the menu moving.
[03:20] <Sarvatt> click a menu entry in steam under wine, everything moves up to 0,0 including the menu contents
[03:20] <Sarvatt> dropdown shows up at 0,0
[03:20] <RAOF> Yeah, know that one.
[03:20] <Sarvatt> ok so different
[03:20] <Sarvatt> synaptics moving to 0,0.. do you have an accelerometer device also?
[03:20] <RAOF> This is just the pointer resetting to (0,0) in the middle of touchpad movement, which is unsettling.
[03:20] <Sarvatt> thats the only one i remember
[03:20] <RAOF> Also interacts really poorly with gnome-shell ;)
[03:22] <Sarvatt> i haven't actually used synaptics in almost a year here so if its busted i'm not sure, damn alps touchpads being in everything now
[03:23] <Sarvatt> what system is it busted on? the x201s?
[03:23] <RAOF> The Inspiron N4110
[03:24] <RAOF> Which I'm using because (a) I was testing out whether fglrx supports hybrid on it (it doesn't) and (b) it's the fastest i5 in the house with a working harddrive.
[03:24] <Sarvatt> cool they sending you more crap?
[03:25] <Sarvatt> its funny the cheaper mainstream dells are using synaptics and the more expensive latitude/precisons are using alps crap
[03:26] <RAOF> I don't know if it's a synaptics touchpad; it's using the synaptics DDX, though.
[03:26] <RAOF> No, this is one of the two hybrid systems I got at UDS.
[03:26] <Sarvatt> precise?
[03:26] <RAOF> Since the T420s decided to bail on me ☹
[03:26] <RAOF> Yah, precise.
[03:26] <Sarvatt> actually i think sforshee made alps use synaptics in precise
[03:26] <RAOF> It works, as long as you're using -rc6 :)
[03:26] <Sarvatt> havent played with that yet
[03:27] <RAOF> dmesg reports synaptics.
[03:27] <RAOF> So I guess this has an honest to goodness touchpad in it.
[03:28] <Sarvatt> wow i really need to put in a feature request for hexr now, it only lists lspci devices so touchpad doesnt show up
[03:29] <RAOF> Heh.  Whoops :)
[03:33] <Sarvatt> RAOF: so its an alps, there may be something screwy with sforshee's kernel drivers to make alps use synaptics thats already upstream
[03:33] <Sarvatt> on that specific machine
[03:33] <RAOF> It could also be the franken input ;)
[03:33] <RAOF> It looks like evtest is seeing correctish numbers.
[03:33] <Sarvatt> oh you're on frankenserver?
[03:34] <RAOF> Yah.
[03:34] <Sarvatt> very likely then :)
[03:34]  * Sarvatt makes mental note to try it out in the morning
[03:34] <Sarvatt> same touchpad as in the e6420 from what i can see
[03:35] <Sarvatt> i haven't tried sforshee's alps driver out yet that lets it use synaptics
[03:35] <RAOF> I'll give it a whirl on the e6420 too, once it's finished slurping all my data off the failing harddrive.
[03:36] <Sarvatt> i'm still in oneiric land, trying to get ivb on oneiric going good before it needs to be done in a month or two
[03:37] <Sarvatt> RAOF: did you get my messages about frozen synapse?
[03:37] <RAOF> YEah.
[03:37] <Sarvatt> i can send ya the linux client that works with the key i sent you if you want
[03:37] <RAOF> Thanks.
[03:38] <RAOF> I'll give it a whirl :)
[03:38] <Sarvatt> or would ya rather have a steam one?
[03:38] <RAOF> I like steam.  Steam is good :)
[03:40] <Sarvatt> boo
[03:40] <RAOF> Boo?
[03:40] <Sarvatt> i only have a multiplayer key to spare for the non steam one :)
[03:40] <Sarvatt> you missed the humble bundle with it!
[03:40] <RAOF> I have tons of games to play :)
[06:30] <RAOF> Aw, man.  This laptop's keyboard layout is *specificly* designed to make me hit "menu" instead of "control"
[19:47] <Prf_Jakob> Sarvatt: do you have a list of commits that you cherry-picked for the vmware build to work against 11?
[21:56] <RAOF> Sarvatt: Were you going to do a libdrm/Intel DDX update?
[21:57] <RAOF> Sarvatt: Because if not, I might as well do it during 1.11 world-rebuilding.
[22:03] <bryceh> cnd, wow not even a sliver of lip service that you did anything to help with upstream multitouch - http://www.phoronix.com/scan.php?page=news_item&px=MTAzMDQ
[22:04] <jcristau> meh, phoronix.
[22:05] <RAOF> Eh, yeah.
[22:19] <bjsnider> phoronix is always right about everything
[22:25] <broder> is mesa supposed fail miserably under valgrind because of some sort of deep graphics magic?
[22:27] <broder> i'm seeing a lot of uninitialized values on natty in various mesa calls
[22:27] <jcristau> not afaik
[22:27] <jcristau> there's a lot of false positives from drm ioctls, but..
[22:28] <RAOF> Piglit has a "run under valgrind" set of tests, as evidence for the "supposed to work under valgrind" hypothesis.
[22:30] <broder> working on getting a test with full debug symbols, but i get lots of stuff during mutter's startup: http://paste.ubuntu.com/775784/
[22:33] <jcristau> all of that is false positives, maybe except the last one
[22:34] <jcristau> not completely sure about the i965 ones but you don't have symbols for that so meh
[22:36] <broder> jcristau: http://paste.ubuntu.com/775793/ has symbols
[22:36] <broder> all of that is during startup
[22:46] <Sarvatt> RAOF: was waiting on libdrm 2.4.30 which was supposed to be pushed out awhile back so an intel-gpu-tools release could go out too but i guess thats no excuse not to do intel 2.17
[22:46] <Sarvatt> broder: https://bugs.freedesktop.org/show_bug.cgi?id=35071
[22:46] <ubot4> Freedesktop bug 35071 in Drivers/DRI/i965 "Valgrind warnings in _mesa_texstore_argb8888" [Enhancement,New: ]
[22:47] <broder> oh, awesome. thanks
[22:47] <Sarvatt> Prf_Jakob: it was just http://cgit.freedesktop.org/xorg/driver/xf86-video-vmware/commit/?h=vmware-11.1-branch&id=26845eb54a15d43f09288a87c5f74beac8fb6ec7 which caused a bad compilation on amd64 even though it was successful
[22:48] <Sarvatt> that was already in a release, vmwgfx_branch was on the old 11.0.3
[22:49] <Prf_Jakob> ah ok
[22:49] <Sarvatt> https://launchpadlibrarian.net/79714941/buildlog_ubuntu-oneiric-amd64.xserver-xorg-video-vmware_1%3A11.0.3-2ubuntu0_FAILEDTOBUILD.txt.gz
[22:49] <Prf_Jakob> Hmm I thought Thomas merged the vmwgfx_branch to master, apperently not.
[22:49] <Sarvatt> yeah it was merged when i looked this afternoon
[22:50] <Sarvatt> yup still merged
[22:50] <Sarvatt> oh you mean the vmwgfx_branch is still on 11.0.3, sorry
[22:50] <Prf_Jakob> Well we should probably kill that branch now.
[22:51] <Prf_Jakob> Oh I just followed your link when I looked at log, no wonder I didn't see the merge (was on the vmware-11.1 branch)