[03:57] tjaalton: lrm-2.6.20 xorg bugs are wontfixing away ;-) [04:33] bryce: dull and boring, dare I say ;) [04:39] tjaalton: Been watching the discussion in #ubuntu-devel? [04:39] The property issues have changed, but still exist. [04:39] Something isn't 64-bit-safe. [04:40] (or at least fails to work sanely on amd64, while it does on i386 on the same hardware, so it's probably 64-bit-unsafeness...) [04:43] wgrant: no, just got up and am on a train [04:48] tjaalton: You're not allowed to sleep! Anyway, I'll be gone for about an hour in a few minutes. [04:49] But it certainly seems to occur on amd64 and not i386. [04:49] The symptoms of the issue have changed, but it seems to be the same thing. [04:53] ok, so the joystick-crashes and properties go together? [04:56] hmm, sounds like update-manager should make sure that input-all is installed in the system, or the server should depend on evdev [05:15] tjaalton: ~2200 -> ~2000 [05:15] whee [05:15] I finished up and unsubbed us from lrm-2.6.20 [05:15] great [05:16] btw, did ou notice that we now have nouveau? [05:16] I've also incompleted all the New bugs that didn't have something resembling an Xorg.0.log attached [05:16] ah, no I didn't. good to hear [05:16] ..which just happens to be useless [05:16] tjaalton: have you been seeing that there are people successfully using -radeonhd? [05:16] that surprised me, but hey [05:16] nope [05:17] mentioned in a number of -ati bug reports [05:17] that it wrks better than ati? [05:17] blah blah, -ati is busted, blank screen yada yada... works ok when I switch to -radeonhd [05:17] +o [05:18] er hey actually I did know about nouveau... I'd had slangasek sync it in a few weeks back. but does it work at all? [05:19] it was synced yesterday [05:19] won't build [05:19] requires newer libdrm and drm-modules [05:19] * bryce nods [05:20] is it causing any breakages? [05:20] hardly, since there are no packages :) [05:21] heh true. [05:29] ok, I'll be offline the next 40h or so.. the ferry to estonia departs in 30min :) [05:38] cya tjaalton [05:39] tjaalton: yeah I've got monday off and am going to try to spend it all out in the wood shop [12:30] Anybody have any ideas on https://bugs.edge.launchpad.net/ubuntu/+source/xserver-xorg-input-synaptics/+bug/267611/comments/53? [12:30] Launchpad bug 267611 in xserver-xorg-input-synaptics "[intrepid] cannot see touchpad tab in mouse configuration" [High,In progress] [23:09] tjaalton: Can you please cherrypick db6e631d31d4ffd476ccd105f8adb8d8b4727b29 into our -synaptics soon? [23:33] hrm, did something change about input property stuff [23:33] my scroll enabling script isn't working anymore! ;) [23:33] Wheel Emulation: 1 [23:33] Wheel Emulation Y Axis: 4, 5 [23:33] but no scrolling seems to be happening [23:40] Ng: Yes, we have large changes in that area. [23:40] Hmmm. [23:41] I would have thought that should be working. [23:41] Which arch, and is that plain evdev? [23:41] i386 [23:41] And it works fine for me. [23:41] Have you rebooted since the new stuff appeared on Friday? [23:42] yeah i did an update early afternoon then did a battery drain test with a bootable CD [23:43] I assume it's an all-evdev setup, I don't have an xorg.conf so it's just using hal [23:43] It's not a touchpad, I presumeE? [23:43] no, trackpoint [23:44] Not a combined trackpoint/touchpad, like they often are? [23:44] I do have both, and the touchpad is usually on the same device, but I have that disabled in the BIOS [23:45] -synaptics has a bug whereby it will partially break property setting, but if it's not on that device... [23:45] So it just doesn't work at all? [23:45] I've never used wheel emulation before, but setting Wheel Emulation to 1 and Wheel Emulation Button to 2 worked fine. [23:45] I think it thinks it's doing it - the mmb is obeying the wheelemulation timeout and when I try to scroll the mouse pointer doesn't move (which is correct) [23:46] hrm [23:47] (WW) Sony PLAYSTATION(R)3 Controller: Don't know how to use device [23:47] (II) UnloadModule: "evdev" [23:47] does that mean it just unloaded it for that device, or has it unloaded the module entirely?! [23:47] (I don't know how to get a list of currently loaded X modules) [23:47] just for that device [23:48] ok [23:48] grep _drv.so /proc/$(pidof X)/maps should work [23:49] jcristau: Hi. Do you have any idea why libxi is spewing crap at the server like in https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-synaptics/+bug/267611/comments/53? Most of the code seems fairly similar to Get(Window)Property, which works fine... [23:49] Launchpad bug 267611 in xserver-xorg-input-synaptics "[intrepid] cannot see touchpad tab in mouse configuration" [High,In progress] [23:49] evdev is listed three times [23:49] wgrant: no clue [23:50] I guess it might be handy if it logged what it was using for a device when it picks it up from hal [23:50] wgrant: i build a server from the ubuntu branch, and libXi/xinput from upstream git, and playing with the 'device enabled' property seemed to work [23:50] jcristau: On amd64? [23:50] but then i'm on i386 [23:51] Ah. [23:51] There's no problem there. [23:51] Identical hardware works on i386 but fails on amd64. The issue only appears if and only if one is using amd64. [23:53] that's just weird [23:54] Precisely. [23:54] The ordering is even stranger. [23:54] yeah [23:55] At least it's probably easier to debug that poking around in the server. [23:56] Actually... [23:56] I suppose I can use SSH X forwarding to a remote amd64 machine. [23:56] Since it looks client-side...