[00:01] <Sarvatt> cant just install ginn and reassign the 4 finger tap gesture?
[00:10] <cnd> Sarvatt, no
[00:10] <cnd> unity has a root window grab
[00:11] <cnd> which takes precedence
[00:11] <cnd> there's no way to override it without telling unity to stop doing it
[00:11] <cnd> Sarvatt, it sounds like maybe our touch stack shouldn't listen to touches that are below a certain threshold for pressure or width
[00:12] <cnd> maybe you could play around with utouch-frame to make it ignore touches until they cross a threshold?
[00:55] <RAOF> Sarvatt: Winning!
[00:55] <RAOF> :(*
[01:49] <bjsnider> RAOF is a big chuck sheen fan
[01:50] <RAOF> Am I?
[01:50] <bryceh> yes he's a wizard
[01:50] <RAOF> I should use “wizard” as a superlative more often.
[02:19] <Sarvatt> hmm http://paste.ubuntu.com/933420/
[02:20]  * Sarvatt wonders why he always finds bugs at 11pm when hes trying to go to sleep :)
[02:22] <RAOF> Because your tired brain is less able to filter out all the strange behaviour :)
[02:22] <bjsnider> answer: it's the curse of working from home
[02:26] <Sarvatt> cnd: which update in the past week actually turned the 4 finger gestures back on?
[02:26] <Sarvatt> i cant find it in the changelogs
[02:28] <Sarvatt> its getting triggered from 2 finger scrolling 100% for sure, switched how i'm scrolling and absolutely only doing 2 finger :(
[02:28] <Sarvatt> Warning: failed to get previous touch value
[02:28] <Sarvatt> GRAIL WARNING (v3/slice.cpp:GetValues:207): failed to get touch from frame
[02:28] <Sarvatt> those get spammed when it happens
[02:31] <Sarvatt> heh whole screen is stuck orange now that i figured out what 3 finger pinch does
[02:33] <Sarvatt> RAOF: caught the bouquet? :)
[02:34] <RAOF> Sarvatt: It didn't get thrown :)
[02:34] <Sarvatt> oh all the bridesmaids have the same one in an earlier pic
[02:35] <RAOF> Ah, yes.
[02:36] <cnd> Sarvatt, there were some fixes in unity 5.10
[02:37] <cnd> in particular, three touch pinch was fixed so it works again
[02:37] <cnd> and three touch gestures in general work again due to a fix in the window finding code
[02:37] <cnd> nothing really changed in four touch handling though
[02:38] <Sarvatt> thats... weird
[02:38] <Sarvatt> it 100% for sure wasnt working a week ago
[02:39]  * Sarvatt disables coasting and hopes that has a knock off effect at stopping making dragging trigger it then
[02:39] <cnd> Sarvatt, there may have been some fixes in the utouch stack
[02:39] <cnd> but nothing really comes to mind
[02:41] <Sarvatt> if that fixes it i'm gonna be bummed, the coasting is super nice
[02:41] <Sarvatt> downgrading to synaptics 1.5.99.902-0ubuntu4
[02:44] <Sarvatt> oh freaking fun, that actually does seem to have fixed it
[02:44]  * Sarvatt gives it a day to be sure but i could trigger it just 2 finger scrolling for 10 seconds before making it pop up the dash
[02:46] <RAOF> That sounds like the dash is receiving scroll events or somesuch?
[02:47] <Sarvatt> well its getting stuck sending touch events that arent really happening for some reason, i had 3MB of Warning: failed to get previous touch value in ~/.xsession-errors with 1.5.99.902-0ubuntu5
[02:48] <Sarvatt> from ~8 hours uptime
[02:49] <Sarvatt> that stinks, coasting was nice :)
[02:50] <Sarvatt> its definitely fixed not popping up the dash all the time on macs with 1.5.99.902-0ubuntu4
[02:50] <cnd> Sarvatt, I'm not sure how coasting could be involved
[02:50] <cnd> but we have coasting turned off anyways in ubuntu
[02:50] <cnd> because synaptics coasting is a terrible hack
[02:50] <cnd> :)
[02:51] <Sarvatt> cnd:  have you seen 1.5.99.902-0ubuntu5? ignore the commit message in the patch, it was altered when it got uploaded
[02:53] <Sarvatt> i'd bet 10 beers at uds that patch was causing the spurious dash popups on bcm5974, been scrolling for 5 minutes now and havent triggered it
[02:54] <cnd> Sarvatt, are you turning the momentum on yourself?
[02:54] <Sarvatt> no
[02:54] <cnd> it should be disabled ootb
[02:54] <cnd> hmm...
[02:55] <cnd> how is it getting turned on?
[02:55] <Sarvatt> straight stock, with that patch coasting works out of the box
[02:55] <cnd> there's a problem here...
[02:55] <Sarvatt> when its coasting its getting stuck sending craploads of invalid touch events and eventually thinking 2 fingers touch is a 4 finger touch
[02:56] <Sarvatt> if i interrupt the coast and change directions the dash pops up
[02:58] <cnd> I don't understand why it would be sending touch events
[02:58] <cnd> but still, coasting should be off by default
[02:59] <Sarvatt> whats the coasting property you're thinking of?
[03:00] <Sarvatt> with 1.5.99.902-0ubuntu5 2 finger scroll coasts with no changes, its definitely on
[03:01] <cnd> I'm pretty sure that in the past I patched ubuntu's synaptics to disable scroll coasting
[03:01] <cnd> but I confirm it is enabled by default
[03:09] <cnd> Sarvatt, this is the bug I was thinking of: https://bugs.launchpad.net/xorg-driver-synaptics/+bug/728643
[03:09] <cnd> I guess I remember the resolution wrong
[03:13] <Sarvatt> filed https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-synaptics/+bug/983614 to follow up on tomorrow, i cant keep my eyes open anymore and have to pass out :)
[03:37] <Sarvatt> cnd: bugfix: make clickpads have a button area is still an ok "bug fix" imo personally even still this late :) only people who complained were on apple where the button area is blocked with the upstream synaptics xorg.conf.d file
[03:37] <Sarvatt> have you ever seen a non apple without a button area? i haven't
[03:39] <Sarvatt> lots of bugs on it that could be closed
[03:42]  * Sarvatt feels bad for complaining when it was initially enabled now when disabling it for macs was such an easy fix
[05:00] <cnd> Sarvatt, there's nothing stopping you from proposing the fix?
[05:01] <cnd> I won't stand in your way :)
[05:01] <cnd> I think it would probably be fine either way, but I don't have a strong enough opinion to fight for it
[11:35] <cprofitt> https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers/+bug/982710
[11:35] <cprofitt> Nvidia has acknowledged and is aware
[11:35] <cprofitt> http://www.nvnews.net/vbulletin/showthread.php?t=178460
[13:53] <tjaalton> seb128: btw, I think we should drop the current wacom patch on g-s-d and go with http://git.gnome.org/browse/gnome-settings-daemon/commit/?id=e40cb71a910164d1cb2c366d3c001eeaac79aaaf instead (edited to apply)
[13:53] <seb128> tjaalton, feel free to do an upload ;-)
[13:53] <tjaalton> seb128: oh right, sure
[13:53] <seb128> tjaalton, I though that was not working though?
[13:54] <tjaalton> seb128: it isn't but it's a step in the right direction
[13:54] <tjaalton> current one actually regresses for some
[13:54] <tjaalton> since the function returns random data
[13:54] <seb128> ok
[13:57] <tjaalton> oh, it's already in 3.4.1, so we're good :)
[13:57] <tjaalton> or is it
[13:58] <tjaalton> it is
[14:04] <seb128> tjaalton, right
[14:05] <seb128> tjaalton, it got merged before the tarball
[14:08] <tjaalton> yeah
[16:47] <bryceh> heh https://bugs.freedesktop.org/show_bug.cgi?id=48652#c39
[17:54] <hyperair> RAOF: ping. do you happen to find that the pixel-perfect scrolling from synaptics hangs up every now and then in precise?