[00:26] Sarvatt: Doh! If that doesn't fully fix your touchpad you might want to ping whot; he's under the impression that'll fix his redhat bug :) === yofel_ is now known as yofel [21:31] cnd, I'm doing some debug prints in x-x-i-s for the bcm5974 s3 problem. My assumption is that all events from the touchpad will go through the loop in EventReadHwState. Is that correct? [21:31] yeah [21:32] okay, so here's what I see then... [21:32] UninitializeTouch is called on the way down, InitializeTouch is called coming back up [21:32] no events come in before I touch the touchpad [21:32] yet it's still messed up [21:33] maybe the state is still somewhat screwed up even after uninit and init? [21:33] that would be my guess [21:34] so resetting num_touches isn't enough I guess [21:36] sforshee, what are you seeing when you hit the bug? [21:37] basically most things kind of acts like I have one additional finger down, except for moving the pointer which works fine [21:37] so a click generates a right click [21:37] a 2-finger drag moves windoes [21:37] *windows [21:38] etc. [21:39] actually the click behavior with one finger is inconsistent, sometimes I get right click, sometimes left click [21:39] two-finger drag very consistently moves windows though [21:40] that's odd [21:41] I'm wondering if there is an issue with mtdev [21:41] hmm, now something is wedged [21:41] here's my theory [21:42] mtdev takes untracked touches [21:42] and tries to follow touches and assign them to tracked slots [21:42] let's imagine that mtdev thinks there's a touch in the middle of the trackpad [21:42] if you then physically touch in the middle of the trackpad, it will think it's the same touch [21:43] but if you touch somewhere else, it will think it's a different touch [21:43] that would explain why sometimes it acts like there's one touch, and sometimes two [21:44] I was trying to see if the right vs. left click correlated with where I clicked, but I didn't get a good feel for it before it wedged [21:49] sforshee, I wonder if you can reproduce by keeping one finger touching while you log out to restart the X server? [21:50] cnd, just during the logout? or hold it down when logging in too? [21:53] just during the X server restart [21:54] once you hit the greeter you can release [21:54] then type your pw to log in [21:54] then test [21:56] something doesn't like that very much :( [21:56] the one time it worked it didn't reproduce the bug. but I got several hangs [21:58] hmm [21:58] what kinds of hangs? [21:58] I can ssh in, so the system is still up, but the desktop is completely frozen [22:00] sforshee, keyboard input doesn't work? [22:00] because a stuck pointer would look like a hung system [22:00] nope [22:00] in fact this last time it hung before displaying the greeter [22:01] hmm [22:01] can't switch to vt1 either [22:01] what about from your ssh session [22:01] sudo chvt 1 [22:01] sudo stop lightdm [22:01] either of those work? [22:02] sudo killall -9 X [22:02] :) [22:03] chvt 1 doesn't work, it seems to be stick in ioctl(3, VT_WAITACTIVE [22:03] service lightdm stop works [23:33] I love that the X server can disallow VT switching. It makes everything so much more robust :/