[00:02] <Ng> gallium sounds like the right kind of thing
[00:51] <emma> I use Ubuntu intrepid. Ever since Edgy the following link enabled the scroll wheel effect in my Logitech Marble Mouse --  http://ubuntuforums.org/showthread.php?t=169423
[00:51] <emma> However, now something has changed, and making that edit does not change the behavior of the mouse.
[00:51] <emma>  Does anyone have any ideas or suggestions?
[00:52] <emma> It stopped working in Intrepid.
[07:23] <tjaalton> emma: we went through it yesterday..
[10:31] <tseliot> tjaalton, mvo: I'm working to make sure that the nvidia branch of dkms tree is cleaned up by the drivers so that older versions (left there by that bug which I fixed) are removed. What do you think about this preinst file? http://albertomilone.com//ubuntu/newlrm/nvidia-173-kernel-source.preinst
[10:39] <tjaalton> tseliot: if it works, looks ok :)
[10:40] <tseliot> tjaalton: yes, I tried it with echo "rm, etc." instead of rm
[10:40] <tseliot> and it prints the right output
[10:41] <tjaalton> ok then
[10:41] <tseliot> of course I'll do some real testing here ;)
[10:43] <tjaalton> nah, why bother ;)
[10:55] <tseliot> oh, wait, a simple "rm -rf /" would be a lot easier
[10:55] <tseliot> can you test it for me? :-P
[10:57] <tjaalton> heh
[12:28] <emma> tjaalton: you said look at xinput, it's sort of opaque and does not seem to translate directly from the xorg.conf lines to anything you put in xinput.
[12:28] <emma> maybe i'm wrong, could you tell me how do you put those xorg.conf lines into xinput?
[12:30] <tjaalton> you don't put any lines anywhere, you run the command
[12:30] <tjaalton> 'xinput list' shows your devices
[12:31] <tjaalton> 'xinput list-props $id' shows the properties of the device
[12:32] <tjaalton> 'xinput set-int-prop $id $property 32 $value' changes the setting
[12:33] <tjaalton> or, you add 'Option AutoAddDevices "false"' to your ServerFlags, and configure the device in xorg.conf like before
[12:36] <tjaalton> $id can also be the full name
[16:53] <tjaalton> oh what fun it is getting winxp working on thinkpad X61
[16:53] <tjaalton> not
[16:54] <tjaalton> even with sp3 had to use a driver disk to get the hd recognized
[16:54] <bryce> heya tjaalton
[16:54] <tjaalton> and all this because vista sucks
[16:54] <tjaalton> even more
[16:54] <tjaalton> hey bryce
[16:55] <bryce> as long as vista sucks people over to ubuntu that's fine
[16:56] <tjaalton> I've been fighting with my hardware.. got a new phone yesterday and have been trying to make a dump of the contents, but gave up hope getting MMS's or bookmarks out of the old one
[16:56] <tjaalton> nokia pc suite == crap
[16:56] <tjaalton> outsourced crap, a nokia employee added ;)
[16:56] <tjaalton> (a friend)
[16:56] <bryce> hehe
[16:57] <bryce> I've still been banging my head on that keyboard hotkey bug from last week
[16:57] <bryce> I made the mistake of looking in acpi-support and got bewildered by all the other hotkeys-don't-work bug reports :-)
[16:57] <tjaalton> yeah, it's a dead-end
[16:58] <bryce> bug 267682
[16:58] <ubottu> Launchpad bug 267682 in linux "Hotkeys no longer working in Intrepid on Thinkpads" [Critical,Triaged] https://launchpad.net/bugs/267682
[16:58] <bryce> do you have any other ideas on that?  I'm going to contact the kernel team next
[16:59] <bryce> tjaalton: you'd mentioned that switching from evdev to kbd made the issue go away - did you ever sort out why?
[17:00] <tjaalton> no, but I think it's a simple matter of different scan/keycodes
[17:00] <tjaalton> some of them don't match
[17:00] <tjaalton> I'd need to know more about how this all is glued together
[17:00] <tjaalton> but pitti is on leave until next week
[17:02] <bryce> actually I think he's at the plumber's conference this week
[17:02] <tjaalton> oh right
[17:03] <tjaalton> debian has eight revisions on top of our acpi-support.. wonder if those would help
[17:03] <tjaalton> ie. sync the version from unstable
[17:12] <tjaalton> * Reinstate thinkpad_acpi.modprobe to fix "Many Thinkpad X60 keys stop working" (Closes: #481253)
[17:13] <tjaalton> that's from the debian changelog
[17:13] <tjaalton> although, since it was reported that they worked on hardy..
[17:24] <bryce> oooh
[17:25] <bryce> there's been so many contradictory comments I'm not sure who to believe
[17:34] <tjaalton> bbl->
[17:34] <bryce> in any case it seems there are multiple bugs.  Perhaps pulling the dell version of that would fix at least some.  I'll put that on my todo for today.
[18:42] <superm1> hi guys, could you check that this bug's fix got pulled in for 8.10: https://bugzilla.redhat.com/show_bug.cgi?id=461666 ?
[18:42] <ubottu> bugzilla.redhat.com bug 461666 in xorg-x11-server "Crash in X.org server during a resolution change (monitor hotplug) in VirtualBox" [Medium,Closed: nextrelease] 
[18:45] <jcristau> "Note that this bug is fixed in the release version of X.org server 1.5.0."
[19:25] <torkel> bryce/tjaalton: re #267682, suddenly Fn-F2 (lock screen) works for me, even after a reboot, on my T61
[19:30] <superm1> jcristau, i wasn't aware whether we were on the release version of xorg server 1.5.  i'm packaging the new vbox to upload, and dynamic adjustments weren't working still for me
[19:41] <tjaalton> superm1: apt-cache policy xserver-xorg-core ;)
[19:41] <tjaalton> torkel: like it does on my X61
[19:43] <superm1> ah tjaalton, the easy solution, so yeah indeed release version of 1.5.0.  thanks
[19:53] <jcristau> meh. bad virtualbox
[19:53] <jcristau> "- Bump provides of guest-utils to xserver-xorg-video-2.9"
[19:55] <superm1> it's "supposed" to work according to upstream's changelog
[19:55] <jcristau> hardcoding the abi version is bad
[19:55] <jcristau> seeing how it was bumped to 4 anyway.
[19:55] <superm1> it was hardcoded in the original debian package...
[19:56] <jcristau> i don't care whose fault it is :)
[20:09] <jcristau> wow. they ship copies of the xserver headers.
[20:10] <bryce> jcristau: oh that sounds safe
[20:11] <jcristau> the 'here, a sigsegv' sort of safe
[20:19] <jcristau> i'll try to chat with the debian maintainer...
[21:25] <bryce> tjaalton: could the recent change in hotkey behavior on thinkpads perhaps have something to do with the sep 1st change to hotkey-setup in bug 256887?
[21:25] <ubottu> Launchpad bug 256887 in hotkey-setup "thinkpad_acpi complains that hotkey-setup is doing the wrong thing" [Undecided,Fix released] https://launchpad.net/bugs/256887
[21:29] <tjaalton> bryce: doubt it, since it still works without evdev