[07:51] <tjaalton> wgrant: peter replied that the tapping commit is probably not what broke two-finger tapping, but the one which changed MaxTapMove
[11:09] <james_w> is anyone familiar with xvfb
[11:09] <james_w> ?
[11:10] <james_w> ah, typical, it works when I try it now.
[11:11] <wgrant> tjaalton: That's not my experience, nor those on the bug/forum.
[11:11] <wgrant> tjaalton: Both are needed for it to be fully operational.
[11:14] <tjaalton> "It could also be caused by 50e872cbc74f6a08ac586bc5e57d7e6a9dfce06a which
[11:14] <tjaalton> reduced the MaxTapMove - causing issues for at least two of our users. I had a
[11:14] <tjaalton> IRC discussion with one of them today and setting it back to 200 worked. 
[11:14] <tjaalton> "
[11:15] <tjaalton> dunno, maybe better if you tried explaining things :)
[11:33] <wgrant> tjaalton: People continued to complain that multi-finger tapping didn't work properly.
[11:35] <wgrant> Two-finger tapping requires both a higher threshold (at least I more my fingers more when multi-finger tapping) and that disentanglement patch reverted.
[11:35] <wgrant> Others say the same. I'm not sure why it's needed.
[11:36] <tjaalton> are you subscribed to xorg@
[11:36] <tjaalton> ?
[11:41] <wgrant> I am.
[11:41] <wgrant> I'm not up to date... I've a bit of other mail due to recent events.
[11:41] <tjaalton> looking at the forum thread it seems that setting Tap Move to 200 fixes things?
[11:42] <wgrant> There's one where I linked to a version in my PPA with the disentanglement patch reverted, and they said it fixed it.. .let me see if I can find it.
[11:45] <wgrant> Hm, still looking...
[11:45] <tjaalton> http://ubuntuforums.org/showthread.php?t=917830 ?
[11:46] <wgrant> That one.
[11:50] <tjaalton> hmm ok, if you could follow up on the thread on xorg@ when you have time?
[11:53] <wgrant> Sure.
[11:54] <tjaalton> cool, thanks
[17:10] <bryce> morning
[19:42] <james_w> thanks bryce 
[19:43] <bryce> james_w: sure thing
[22:05] <james_w> bryce: nice post, I agree with you
[22:06] <emma> how can i tell what my videodriver is?
[22:07] <bryce> emma: look in your /var/log/Xorg.0.log
[22:07] <emma> Thank's bryce 
[22:08] <emma> (incidently I'm using Intrepid development branch)
[22:09] <emma> (WW) Failed to open protocol names file /etc/X11/xserver/protocol.txt
[22:09] <emma> That's the first line in my /var/log/Xorg.0.log
[22:09] <emma> looks ominous.
[22:09] <jcristau> we should revive xserver-common, and put that file there. ignore it for now.
[22:12] <emma>     X.Org XInput driver : 2.1
[22:12] <emma> Would that be the videodriver?
[22:12] <emma> (--) PCI:*(0@1:5:0) ATI Technologies Inc RS480 [Radeon Xpress 200G Series] rev 0, Mem @ 0xd8000000/134217728, 0xfdef0000/65536, I/O @ 0x0000ee00/256, BIOS @ 0x????????/131072
[22:12] <emma> That's the video card.
[22:13] <bryce> james_w: thanks.  I'm interested in seeing how your lp/bzr integration work will help simplify things
[22:13] <emma> I've never installed any driver, wouldn't it just be the default that comes with intrepid?
[22:13] <emma> (incidentally, my purpose is to find what my driver is, in order to make a better bug report)
[22:14] <bryce> emma: probably -ati then.  try `grep _drv /var/log/Xorg.0.log`
[22:14] <bryce> you should see a line like this:  (II) Loading /usr/lib/xorg/modules/drivers//ati_drv.so
[22:15] <emma> (II) Loading /usr/lib/xorg/modules/drivers//ati_drv.so
[22:15] <emma> Yes I have that
[22:17] <james_w> bryce: it's one of my mail aims
[22:18] <emma> I actually never knew about this channel until just now.
[22:18] <emma> I guess you guys specialise in the X-server
[22:19] <emma> I have a concern related to that. In all previous releases since Edgy through Hardy I have been able to follow steps I found a long time ago on ubuntuforums, to make my Logitech Marble Mouse roller ball have full functionality by editing xorg.conf. 
[22:20] <emma> In intrepid I edited it again but no change in behavior is observed.
[22:20] <emma> I think maybe it needs a layout section at the bottom.
[22:20] <emma> but maybe xorg.conf has been emaciated somehow and lacks that.
[22:21] <jcristau> define 'full functionality'
[22:22] <emma> It's a roller ball. It has two buttons on each side and it has the roller ball on top.  Previously Ive been able to use xorg.conf to enable holding down one of these buttons while using the rollerball to emulate a scroll wheel.
[22:22] <emma> I'll show you the ubuntuforums page with the code I have always been able to use.
[22:24] <emma> http://ubuntuforums.org/showthread.php?t=169423
[22:25] <emma> in Intrepid there just is hardly anything in xorg.conf and editing it with the lines in the link did not make the marble mouse work.
[22:28] <emma> I seem to recall though that in the old xorg.conf there was something like 'layout' at the bottom of it, and that's missing. I wonder if that's what's needed in order to make the Section "InputDevice"
[22:28] <jcristau> need to use the evdev driver, with a proper Device option and ServerLayout section
[22:28] <emma> stuff work.
[22:28] <jcristau> or, set the options in hal
[22:28] <jcristau> or through xinput properties
[22:28] <emma> Is that easier than it used to be?
[22:29] <emma> I'll paste you my xorg.conf as it is right now.
[22:32] <emma> http://club-ubuntu.pastebin.com/d2e057b3d
[22:32] <emma> There is my xorg.conf as it is right now.
[23:20] <emma> Well I had some big troubles.
[23:20] <emma> I tried to put a ServerLayout section in there and it broke X and i had to do a -phigh thing.