[02:31] bryce: Any idea what's going on in http://paste.ubuntu.com/59086/? It doesn't look very pleasant... [02:32] It only happens on that one device, and the property is "Synaptics Edge Motion Speed" [02:35] * bryce looks [02:36] ew xcb calls [02:36] The only atom that it manages to ask the server about is this: [02:36] 000:<:000d: 8: Request(17): GetAtomName atom=0x10f(unrecognized atom) [02:36] 000:>:0x000d:60: Reply to GetAtomName: name='Synaptics Button Scrolling\000\000' [02:36] But it crashes here: [02:36] #7 0x0000000000401e6b in print_property (dpy=0x2b0aaac10a00, dev=0x60ef30, property=269) at ../../src/property.c:47 [02:36] 47 name = XGetAtomName(dpy, property); [02:37] And atom 269 is Synaptics Edge Motion Speed [02:37] usually if your stack trace shows _XReply, then it indicates there's some sort of error in the client/server interaction [02:37] which could be due to client incorrectly making its server call, or could be an error inside the server [02:37] _typically_ the former more than the latter [02:38] I'll downgrade the server. [02:38] As a client stack hasn't changed at all from the working version still fails. [02:38] wgrant: issues with _XReply I've found awfully hard to debug [02:39] Hmm. [02:39] it's hard to trace into the server and see what's going wrong [02:39] But no, I'm still running an oldish server. [02:39] xtrace doesn't show the request ever getting to the server... hmmmm. [02:40] I notice you have null pointers for vector and count... are NULLs valid for those? [02:40] I've got no idea about xcb. [02:40] wgrant, you could also set up xmond to view the protocol communication between the client and server [02:41] bryce: I've used xtrace to do that. [02:41] ah good [02:41] well the xcb bits are just the libx11 layer [02:41] whatever the bug is, it's not likely to be in that (possible, but not likely) [02:43] *most* of the issues like this one ended up being the client making an incorrect X protocol call, or passing parameters that weren't valid [02:44] http://paste.ubuntu.com/59094/ [02:45] Those are the calls that it makes before it dies... [02:45] 146,36 is XListDeviceProperties. [02:46] On other devices it then issues a GetDeviceProperty. [02:47] you mentioned you were using an old xserver... what version precisely? [02:48] 2:1.5.1-1ubuntu3 [02:48] so old only in relative terms ;-) [02:48] I'm upgrading now. [02:48] shouldn't matter [02:49] the 1ubuntu4 change was only for -psb [02:49] Hmm, maybe not, 400MB is a bit too much of an upgrade for peak. [02:49] er wait [02:49] sorry was thinking 1.5.2-1ubuntu3 [02:49] There's been a merge since then... [02:49] Yes. [02:50] right. worth the upgrade. [02:50] I'm upgrading just X bits. [02:50] glancing at the changelog, nothing that looks likely to be the cause of this [02:50] but who knows [02:51] The strangest bit is that it worked with this xserver last week... [02:52] hey while you're waiting, there was an email on u-d-d that you'd be best to answer - https://lists.ubuntu.com/archives/ubuntu-devel-discuss/2008-October/005931.html [02:53] I can pass a reply along if you don't want to sub to the list (it's kind of a noisy list) [02:59] bryce: I'm subscribed, but don't normally keep up to date. [02:59] I bet he added the options to the Synaptics part of the fdi file rather than the ALPS one. [02:59] I'll reply shortly. [03:00] Thanks for pointing it out. [03:01] great thanks [03:01] Still segfaults. [03:01] It must be a server-side change, I think. [03:02] The last updates in the amd64 chroot in which I'm testing were on the 11th, and I've only upgraded libxi6 and xinput since... [03:03] In fact, the last updates were the day I created the chroot, which means that same set of packages was working fine after that Atom size issue was fixed. [03:03] So it's not the client. [03:04] Ah, bug #283921 [03:04] Bug 283921 on http://launchpad.net/bugs/283921 is private [03:06] ew [03:06] (private bugs ftl) [03:07] valgrind reports the same sort of stuff and dies similarly on a request that works, however. [03:07] wgrant: I de-privated it [03:09] Those bad writes aren't healthy, even if they don't kill it in most cases... [03:11] And those don't happen on i386... so it's something like the same problem. [03:13] They're always of size 8... very suspicious... [03:15] * wgrant will poke it after lunch. [03:32] You know, I bet it was http://cgit.freedesktop.org/xorg/proto/inputproto/diff/XIproto.h?id=36c8a6f3faf56a8f8ca31455812c9132b379b1b3 (which we don't have) [03:36] mm [03:42] AHA [03:43] (intrepid-amd64)root@fisto:/home/fujitsu/libxi-1.1.3# xinput list-props 3 [03:43] Device 'SynPS/2 Synaptics TouchPad': Device Enabled: 1 Synaptics Edges: 1632, 0, 5312, 0 Synaptics Finger: 25, 0, 30 [03:43] It works. [03:43] \o/ [03:43] And the moral of the story is that defines suck. [03:46] the hardest bugs always seem to end up being 1-line fixes [03:46] Now to work out what needs to be rebuilt... [03:46] libxi, at least. [04:35] bryce: It appears that only 5 uploads can have been affected by that bug. [04:35] not bad [04:36] libxi, xorg-server, gnome-control-center, xf86-input-evtouch and xserver-xorg-input-evdev. [04:36] Nothing else uploaded since includes XIproto.h or anything else that includes it. [06:47] huh, I thought we had that already [06:48] since wasn't that what made properties work on amd64? [06:48] or, not fail for some [06:54] oh sorry, it's undef, not the #define Atom CARD32 -change [06:57] tjaalton: Yes, so it's causing the opposite problem now. [06:58] I'm stupid, basically. I initially fixed it by replacing the Atoms in XIproto.h with CARD32s. I tested that thoroughly. But then upstream fixed it with #define Atom CARD32, so I did too. I then only did basic property getting/setting testing, and didn't try to list them again... [06:59] don't worry, it's trivial to fix now [07:00] It's trivial to fix the header, sure. [07:00] But I had to script a grep through 300 packages to set what was going to need to be rebuilt. [07:01] It turns out to be these: https://edge.launchpad.net/~wgrant/+archive [07:03] hum, ok [07:22] hey tjaalton [07:22] I've got a patch for 261977, let me post t [07:24] http://launchpadlibrarian.net/18655616/xorg-server_1.5.2-1ubuntu6.debdiff [07:30] bryce: I like your regression potential mitigation strategy for -synaptics. [07:30] You left the patch out of debian/patches/series... [07:30] doh! [07:31] It'll need another upload once x11proto-input is fixed, anyway. [07:33] I'll prep a debdiff to fix, sorry about that [07:33] Thanks. [07:35] ping me when you want the timing is right to upload it and I'll put it in [07:35] I'll need to convince somebody to let x11proto-input in first. [07:37] lp #? [07:38] bryce: hey, cool, I'll read it through [07:38] Bug #283921 is the main symptom, but there's no debdiff attached. I'll generate one. [07:38] Launchpad bug 283921 in xinput "xinput crashed with SIGSEGV in malloc()" [Medium,New] https://launchpad.net/bugs/283921 [07:39] ok [07:39] LP's package diffing is braindead. Why won't it diff from primary as well as the old version in my PPA!? [07:41] bryce: looks good. for completeness sake it could check the system like later in the file (can't check the function now), but since we don't support !*x86 that doesn't matter much [07:43] bah, cheese can't find my camera, daughter disappointed [07:46] tjaalton: can do - it'd be helpful though first to just verify it does solve the bug [07:46] bryce: sure [07:51] bryce: See the debdiff on bug #283921. All functionality tested with i386/amd64 clients and i386 server. [07:51] Launchpad bug 283921 in xinput "xinput crashed with SIGSEGV in malloc()" [Medium,In progress] https://launchpad.net/bugs/283921 [07:57] hmm, looks like the gstreamer default video input device is wrong [07:57] should be v4l2 [08:03] strange, mouse scroll changes the desktop even when the cursor is on some gtk-based progs [08:05] tjaalton: I noticed that, and presumed it was a feature. [08:05] Albeit an annoying one. [08:05] And it's only on some widgets, AFAICT. [08:06] likely so [08:07] but anywhere on the cheese window, for instance [08:21] wgrant: with the x11proto-input debdiff, is that a complete fix for 283921 or a partial fix? [08:22] bryce: It will several no-change rebuilds afterwards. [08:22] +require [08:24] ok [08:24] The changes are all in my PPA, but the rest are just rebuilds. [08:25] any ideas what temperatures are ok for a GeForce Go 7900 GS? [08:25] None - it's an nvidia card, so it is implicitly unOK. [08:26] I agree nvidia sucks bigtime [08:30] I'm nor sure what my problem is a) The fan starts to late or b) the memory gets unstable if the card gets hot [08:30] or c) the powermixer has a bug an clocks the memory wrong [08:33] wgrant: uploaded x11proto-input [08:34] bryce: Great, thanks. [08:34] I really need to get myself some amd64 hardware at some point. [08:34] uhh there is a dell laptop controll daemon :D [08:35] For controlling what? [08:35] the fan [08:35] Ah. [09:08] bryce: I suppose you don't want debdiffs for the rebuilds? [09:10] wgrant: probably no need [09:12] tjaalton: philip langdale of VMWare fixed -vmmouse for input-hotplug [09:13] tjaalton: bugs 248521 and 285305 [09:13] Launchpad bug 248521 in xserver-xorg-input-vmmouse "vmmouse seems to register incorrect x,y values for mouseclick" [High,Triaged] https://launchpad.net/bugs/248521 [09:13] Launchpad bug 285305 in xserver-xorg-input-vmmouse "vmmouse doesn't work with input hotplug" [High,Triaged] https://launchpad.net/bugs/285305 [09:14] for 248521, the new upstream version just had one patch so I've packaged it and uploaded it [09:14] but 285305 is to add a hal fdi file. If you have time could you look at that one? [09:17] (or if we need to bug pitti about it, let me know) [09:34] bryce: ok, read the bug. I don't know why it would need a callout script, just setting the driver in the fdi should work [09:34] I'll add that to the bug [09:34] ok [09:35] ah, running vmmouse_detect is the reason [09:36] he also mailed xorg@ about it [09:39] * wgrant saw that. [09:39] Wasn't he saying that it only worked for USB? [09:40] with evdev, this is needed for PS/2 emulation [09:47] bryce: so, including the fdi file and callout-script to the package would fix both issues [09:48] the script could go in /usr/lib/hal like debian-setup-keyboard [09:52] sounds good [09:58] wgrant: your builds should all be in now, assuming I did them right. Can you doublecheck later on that they all got through okay, and let me know otherwise? [09:58] ok, I'm too tired. --> bed. night [09:59] bryce: Thanks a lot! Night. [09:59] night! [10:24] tseliot: did you see my comment? [10:34] elmargol: yes, I did [10:35] but it's not something I can fix [10:35] only NVIDIA can [10:39] tseliot: well nvidia does not care [10:39] tseliot: do you know a tool to control the gpu fan? [10:43] elmargol: try nvclock [11:12] * munckfish rolls up sleeves to work on bug 281610 (and cries) [11:12] Launchpad bug 281610 in ubuntu-ps3-port "[regression, intrepid] Xorg servers broken "No core keyboard" and "failed to initialize core devices"" [Critical,Confirmed] https://launchpad.net/bugs/281610 [11:18] how do you install a ps3 nowadays? [11:19] I've got one to try [11:25] I'll ask upstream [11:29] howdy! [11:30] how soon can we get around uploading the new geode to hardy-updates and close bug #255991 for good? [11:30] Launchpad bug 255991 in xserver-xorg-video-geode "xf86-video-geode: DDC probing broken on GX2/CS5535 since 2.9.0 (patch)" [Undecided,Fix released] https://launchpad.net/bugs/255991 [11:31] is it in -proposed? [11:32] it [11:32] it's never been uploaded [11:32] bryce had submited a debdiff and pitti approved it [11:32] an actual package just needs to be produced and uploaded [11:32] based on that diff [11:36] sigh [11:36] no patch system [11:36] hm? [11:36] should I apply the diff directly?? [11:37] I think that bryce didn't go as far as slicing his diff into a series of debian/patches [11:37] no he didn't, but since it's your package you are welcome to do so :) [11:37] but it would probably work to just throw the whole diff into debian/patches/ and enable the include for simple-patch.mk [11:38] ok [11:38] lemme do that now, then we can uplaod [11:38] don't forget the changelog, since you know the details [11:41] yup [11:41] can I strip the extraneous debian/rules content too? [11:41] there's duplicated lines that ended up there for no reason [11:41] go for it [11:44] Grumble. [11:44] There is something still not entirely 64-bit safe there. [11:45] But it doesn't affect xinput, only syndaemon, so it's probably some header order issue... [11:50] tjaalton: you can install Ubuntu on PS3 from a daily cd takes about an 2 hours all in [11:50] http://cdimage.ubuntu.com/ports/daily/current/ [11:50] Yesterdays was the first time for months I've been able to get all the way through an install [11:51] Unfortunately once installed the nightmare only begins [11:51] since last week everything changed [11:51] :D [11:53] tjaalton: I'm thinking of trying to do a git bisect between 1.5.1-1ubuntu2 and 1.5.1-1ubuntu3, do think that's a good first step ? [11:54] Or is there other info we could collect first that may help us guess the problem? [11:54] s/problem/problems/ [11:55] Seems like there's two issues here: graphics and input, not sure if they're separate problems. [12:17] I don't understand why it doesn't use evdev for the keyboard even with 1.5.1-1ubuntu2 [12:18] tjaalton: it does use evdev [12:18] a lesson for all; don't teach your daughter to play flash-games with an unstable platform [12:19] I just had to downgrade the xserver-xorg-input-evdev package to match with the 1.5.1-1ubuntu2 of the server [12:19] no sound after suspend -> flash-games don't work -> disaster [12:19] ouch! [12:19] that's with Flash 10 on Intrepid? [12:19] munckfish: well, I'll try to reproduce it [12:19] yes [12:19] nightmare I was hoping flash was more stable in v10 [12:19] :( [12:19] ho hum [12:19] but the sound issue is some alsa trouble [12:20] just that the flash game doesn't progress if there's no sound [12:20] tjaalton: if you decide to install to your PS3, you'll need a couple of workarounds to get to state where you can mess around with it [12:21] ok, I'm all ears [12:21] tjaalton: debdiff and build log attached [12:21] bug 285231 - cjwatson fixed it last night I'm not sure it's on last nights daily build [12:21] Launchpad bug 285231 in ubuntu-ps3-port "ps3-kboot fails to find rootfs so cannot boot system" [Critical,Confirmed] https://launchpad.net/bugs/285231 [12:21] basically if you can't boot that'll be why [12:22] next to stop usplash from hanging the system on boot (cries weeps) [12:22] you'll need to drop to a shell in kboot, remount the target partition and edit the bootloader config [12:22] best ping me when you get to that stage [12:23] just need to add in a "Recovery" boot config which boots with kernel parameter "single" [12:23] AH [12:23] then you can at least get to a root shell and start messing with X [12:23] Tracked down the synaptics 64-bit unsafeness issue. [12:23] all good fun! [12:24] munckfish: heh, sounds like a lot of fun [12:24] Yeah and to think it was all working so nicely just a week ago [12:25] tjaalton: hmmm git bisect isn't going well [12:25] :( [12:25] Q-FUNK: ok, I'll look at it later [12:25] tjaalton: thanks! [12:25] it's landed me in commit 4e6cbd323854709ae00c44108c93ab6596151de2 [12:26] with no debian/ dir, so I grabbed the debian dir from an earlier commit [12:26] but build is failing :( [12:31] dix/devices.c:99 error: 'XI_PROP_ENABLED' undeclared (first use ... [12:32] you must have the latest properties-patch for the server [12:32] i'd just try to revert the 3 xkb commits between 1.5.1 and 1.5.2.. [12:32] so git-bisecting the ubuntu-branch probably doesn't work [12:32] yeah, that could be it [12:41] right yes this is a nightmare with or without the debian dir, other deps are causing a pain the arse now [12:41] ok so I'll try to selectively revert different patches [12:42] jcristau: so that will deal with the keyboard issue, but I think need to deal with the no graphics at all issue first and that gets introduced in 1.5.3 as well I believe [12:42] duh [12:42] not 1.5.3 [12:43] 1.5.1-1ububuntu3 [12:43] * munckfish slaps forehead [13:27] jcristau: That conditional redefinition of Atom depending on _XSERVER64's definedness just bit me. It's rather inconvenient! [13:27] There are some really strange things lurking in the depths of the X headers... [13:43] Q-FUNK: uploaded [13:51] wgrant: yeah, it's a mess [13:53] jcristau: -synaptics' config.h is included in both its driver and clients, and it includes xorg-server.h. Chaos ensues. [13:54] wgrant: hah. should probably have a separate config header for the clients, or something [13:56] For now I've worked around it in my PPA by wrapping the #include xorg-server.h in #ifndef SYNAPTICS_CLIENT_ONLY and defining those in the clients... but that's because I'm no good with autotools and can't work out how to do it properly. [13:56] yeah, that should work too [14:08] tjaalton: thanks! can you post on the bug to show the upload has been done and close it? [14:10] sure [14:11] but it's only in proposed, so it's fix committed [14:11] ah yes [14:19] oops, bryce uploaded -evtouch when he meant to upload evdev [14:20] and a wrong version at that [14:20] -4 when we had -3ubuntu12 :) [14:20] (-4build1 but still) [14:20] well, ogra will fix it :) [14:21] shouldn't all of them have been XubuntuY instead of Xbuild1? [14:21] tjaalton: -evtouch was needed as well as -evdev. [14:21] wgrant: how so? [14:21] anyway, I think all the changes were dropped [14:22] hmm, xorg-server 1.5.2-2build1 [14:22] tjaalton: It built against the broken XIproto.h. [14:22] I think xorg-server is busted as well [14:23] libxi too. [14:23] Just the versioning is wrong, but it's still a bit messy... [14:23] hi, will u get new nv legacy drivers or not for release? [14:24] Kano: there are no new legacy versions [14:25] and what do you tell your users then ;) [14:25] force them to nv [14:26] nv does not work correctly, at least not for my nvidia 8800 gts 512 [14:26] when will the vesa override work? [14:26] patch exists [14:26] sorry, doesn't [14:29] Kano: is there a bug about it, do you know? [14:30] well not in lauchpad i guess, i told aaronp,but he said he has got no time for it [14:30] I mean the xforcevesa not working [14:31] wgrant: yep, the diff reveals that only the changelogs were modified [14:31] tjaalton: if you did not add one, i only told it here [14:32] tjaalton: I checked them on LP and came to that same conclusion. Good. [14:32] Kano: it might be filed already [14:33] wgrant: now the question is, how to fix them :) [14:33] tjaalton: We can't until we merge from Debian. [14:34] doesn't look like anyone has filed a bug about xforcevesa b0rkedness [14:34] there are 20 bugs with xforcevesa... [14:34] please tell me [14:35] searching for it gave no results [14:35] * wgrant wins. [14:35] I now have confirmation that syndaemon works without SHMConfig, even on amd64. Yay! [14:36] hehe, bug 283979 [14:36] Launchpad bug 283979 in xorg "I am having problems when I am typing anything the cursor moves and then I am typing in a different word. What I mean is when typing I always have to be careful that I am not typing in another word. IT HAPPENS A LOT.... I have tried to use the inset button but that doesn't work. It mainly happens when I am emailing or when I am typing in word processor. Can you please help me with this? It is driving me nuts. " [Und [14:36] What a summary. [14:37] yep [15:28] if I have a BLAH.patch creating using git-format-patch, how can I apply that to a "apt-get source" tree? git-am won't work but I want to try this patch on the ubuntu version of this app [15:28] patch -p1 [15:32] Kano: so you have those 20 bug reports, please share them [15:33] well i used the first search option [15:33] but there is no specific bug against xserver-xorg with xforcevesa [15:35] I get two bugs with 'xforcevesa' [15:35] you can search on first page too [15:36] what. first. page? [15:36] https://launchpad.net/+search?field.text=xforcevesa [15:37] right, so not searching the _bugs_ [15:37] and it also lists closed bugs [15:37] but yes, no current ones filed [15:38] now floorball -> [15:48] jcristau: thanks [18:05] bleah, I need to not do packaging until 2am [18:05] tjaalton: anything we can do to fix the version numbers? I clearly wasn't thinking [18:07] bryce_: hehe :) [18:12] bryce_: well, maybe ask jcristau to release the versions, and we could merge them then. libxi has only received some packaging fixes which should be trivial, and xorg-server has one commit by lool (included in our package too) [18:19] bryce_: my G45 (desktop) machine current freezes directly after login and I now finally have some clues as to why [18:19] in fact I know a specific patch that makes EXA work for me [18:19] I've tried to apply this patch to ubuntu's intel-agp.ko and ti worked [18:19] the specific change that allows G45 to boot is this one: [18:19] http://git.kernel.org/?p=linux/kernel/git/anholt/drm-intel.git;a=blobdiff;f=drivers/char/agp/intel-agp.c;h=f1fe7490131468b40c5817e232442026d9f8ff0d;hp=016fdf0623a4ce7b5f849efc8ab099a2c5026497;hb=2052746fc8397130c120f0194a89938b0b62b6cb;hpb=b34c87315b1a2822111fc8ef744ef504f9be2f85 [18:19] so it's a kernel bug? [18:19] right [18:19] file a bug on the kernel then [18:20] mnemo: cool, good work tracking that down [18:20] that change is VERY small and it's also "if its G45 then do blah" so maybe we can get it in? [18:20] ask the kernel people [18:20] I will open a bug and nominate for intrepid and we'll see what happens [18:20] yeah, and also make sure to grab a kernel guy on irc, because I don't think there's much time left to get it in [18:20] true [18:20] nominating probably won't be sufficient at this point [18:20] ok [18:21] also (esp if you can't get a kernel guy), let the release managers know about it [18:21] hi still trying to get my head around bug 281610. Could someone gives me some tips as to where input device config actually gets into the xserver if not specified on the cli or xorg.conf? [18:21] Launchpad bug 281610 in ubuntu-ps3-port "[regression, intrepid] Xorg servers broken "No core keyboard" and "failed to initialize core devices"" [Critical,Confirmed] https://launchpad.net/bugs/281610 [18:21] like cjwatson, pitti, slangasek, or hobsee [18:22] filed bug 285562 about the xforcevesa issue [18:22] Launchpad bug 285562 in xorg "xforcevesa doesn't work" [Critical,In progress] https://launchpad.net/bugs/285562 [18:22] I've been running gdb on xf86Config.c in checkCoreInputDevices but it just doesn't find any anywhere :( [18:23] munckfish: have you tried reverting the three xkb related commits? [18:24] tjaalton: not yet, my build failed so I decided to grab the -dbg package and see if I could get any hints from that. I can revert those next. [18:24] munckfish: please do, probably easier to get results that way [18:25] tjaalton: ok thx [21:31] tseliot: It seems that the dist-upgrader is commenting out the inputdevice sections, but not commenting out the lines in serverlayout. That causes problems. [21:33] wgrant: mvo wrote that script. From what I remember it should remove the entries in the serverlayout section too [21:33] I can talk to mvo again [21:34] wgrant: he didn't use my script that uses xkit because xkit removes comments (from sections) and doesn't comment things out [21:36] tseliot: Ah. I've seen at least two fairly sane reports of it on ubuntuforums. [21:38] wgrant: having the links to such reports would help [21:38] I'll see if I can find them again. [21:39] thanks [21:42] tseliot: Here's one: http://ubuntuforums.org/showthread.php?t=951659 [21:43] ok [21:44] tjaalton: Shouldn't bug #285562 be High with an Intrepid task? Critical without an Intrepid task doesn't imply release-criticality. [21:44] Launchpad bug 285562 in xorg "xforcevesa doesn't work" [Critical,In progress] https://launchpad.net/bugs/285562 [22:05] wgrant: yep, milestone alone isn't enough I guess [22:05] tjaalton: Yep. There was an email about it a while ago. [22:05] Any idea how I make my joystick not be a mouse? [22:05] Even if I add it to the fdi file, it still breaks things. [22:06] hrm [22:06] how exactly does it break things? I keep hearing that a lot but I'm missing something [22:07] It it seems to scroll up. And up. And up. [22:07] I would xinput query-state it, but it's not easy! [22:07] and there is no way to not let evdev grab them, at least no practical way (since they tend to have a input.keyboard capability) [22:09] What are other distros doing? [22:09] launchpad is failing on me [22:09] they don't care, or use input-hotplug?-) [22:10] I'll check fedora [22:10] They don't use input-hotplug, you mean? [22:10] haha [22:10] they don't have -joystick [22:10] I saw that earlier but forgot [22:10] wgrant: right, not many distros do yet. fedora is one but I'm not aware of others [22:10] besides us [22:12] Hmmm. [22:12] duh, forgot that evdev refuses to use my joysticks [22:12] How!? [22:13] (WW) Logitech Logitech RumblePad 2 USB: Don't know how to use device [22:13] (II) UnloadModule: "evdev" [22:13] (EE) PreInit returned NULL for "Logitech Logitech RumblePad 2 USB" [22:13] (EE) config/hal: NewInputDeviceRequest failed [22:13] I wonder if we should try to harvest joystick names from xorg.conf. [22:13] tjaalton: I fixed that by adding it to the -joystick fdi file. [22:13] yes, I don't have it installed atm [22:13] rumblepad should be there already since I added it [22:13]