/srv/irclogs.ubuntu.com/2008/08/21/#ubuntu-x.txt

tjaaltonbryce: I'll start uploading the input properties stuff now, starting from inputproto08:20
bryceheya tjaalton.  sounds good08:25
tjaaltonhum? lp doesn't show builds other than i386 anymore?08:45
tjaaltonneed to wait for the proto to get in the archive first, then libxi and xserver after that08:46
crevettehello08:58
tjaaltonhey12:59
=== mvo_ is now known as mvo
keesbryce: say, can include/misc.h have MAXCLIENTS raised?17:46
keesbryce: maybe to 1024 from the current 256?17:46
kees(a friend with like 20 work spaces and lots of RAM just ran into it, and it doesn't seem to be run-time configurable)17:47
pwnguinhow much extra ram will that allocate?17:56
keespwnguin: that I don't know.18:09
keesI've opened bug 260138 for it, with upstream bug links, and proposed patches.  (they're untested, though)18:10
ubottuLaunchpad bug 260138 in xorg-server "Xorg needs client limit raised" [Undecided,New] https://launchpad.net/bugs/26013818:10
pwnguini have to ask18:10
pwnguinwhy does nabble know so much about mailing lists?18:10
pwnguinkees: so uh. the stuff im reading says you'll need more than a simple header change?18:23
pwnguin(if you've tested the patches, that's at least a good sign)18:24
keespwnguin: nope, I haven't tested anything -- just prepared patches based on the discussion.18:26
keespwnguin: I have no idea what the impact would be, but I figured since I could do the other legwork, I could contribute that bit.18:27
keeshonestly, if someone who know this area says "wtf? no way" that's fine too.  :)18:27
pwnguinso that bit operation macro you wrote. it operates on ints?18:28
pwnguins/wrote/extended/18:29
tjaaltonat least rhel4 has those patches19:04
tjaalton20:52 < ajax> you trade more clients for fewer resources per client19:04
bdmurraybryce: bug 219952's recent comments don't look like an -video-ati bug right?19:11
ubottuLaunchpad bug 219952 in xserver-xorg-video-ati "ubuntu 8.04 RC donĀ“t run in acer extensa 7620G - HD 2400 XT [1002:94c8] " [High,Incomplete] https://launchpad.net/bugs/21995219:11
tjaaltonbdmurray: it might still be the driver. the original issue seems resolved though (no picture with livecd)19:14
bdmurraytjaalton: it's before X starts though right?19:15
tjaaltonbdmurray: ah, right.. that's the kernel/usplash doing something funny19:16
tjaaltonso this bug is fixed19:16
bdmurrayand they should open a new bug with those screenshots?19:16
tjaaltonI'd say so, yes19:17
bryceyep19:28
tjaaltonbryce: I've pushed the IDP patches for xorg-server in git, and it should be ready to go. Anything to add?19:36
tjaaltonafter that, driver support (evdev, synaptics) and a new xinput (and/or gui support) :)19:37
tjaaltonbryce: also, the "evdev keyboard model" mess is not over yet. Since it broke jp106 & ABNT2, svu and daniels thought that it would be best to force the evdev _rules_, not model, and to allow changing the model like before, and no need to force it in gnome-settings-daemon either19:43
brycehrm19:44
pwnguinso what's the point of no return on this19:44
tjaaltonthe evdev rules just need to add support for jp106 & ABNT2 (and whatnot)19:44
tjaaltonthis is already in upstream. we just need to make sure no-one notices anything when they upgrade. it shouldn't be too hard19:44
tjaaltonpwnguin: what do you mean?19:45
pwnguini recall someone important saying that no one feature was worth holding back the whole release, but i cant recall when a feature has been tried and rolled back19:45
pwnguini can recall a few times where a feature was pushed in and left there19:45
tjaaltonwe can't avoid evdev19:45
tjaaltonforever..19:45
jcristauit's like the future or something19:45
tjaaltonyeah, or something19:46
pwnguinim just wondering if there is such a mechanism in place19:46
pwnguinrecall pulse audio troubles in hardy =/19:47
tjaaltonpwnguin: it should not hold back anything.. the next alpha is due in two weeks so there's plenty of time to upload :)19:47
tjaaltonwell, pulse..19:47
pwnguinin the mean time, HAL is on its way out for devicekit...19:48
tjaaltonlooks like it'll get sorted out finally19:48
tjaaltonthe pulse mess that is19:48
pwnguini get the impression that pulse would have gone faster if it had been called "audioKit"19:49
pwnguinfor some reason the *Kits have a level of inevitability19:49
tjaaltonapart from the jp106 & ABNT2 brokenness, the input-hotplug change has been quite smooth19:49
bryceyup20:14
brycealthough, it's not solved as many issues as I'd hoped... quite clearly input X drivers for uncommon devices don't get as much attention as they need20:15
pwnguinthats why i worry about this devicekit thing20:27
pwnguinit seems like every few years everyone runs away from the complexity of properly handling the broken hardware of the world20:28
=== federico1 is now known as fooderico
tjaaltonbryce: what devices do you have in mind?21:01
brycetjaalton: game controllers, tablets, etc.21:08
jcristauwhy wouldn't game controllers work with evdev?21:09
pwnguindepends on your definition of game controller21:09
pwnguinas for why it might not work, have you tried any jcristau?21:09
jcristauno21:10
pwnguinwell, you're not alone21:10
* jcristau <- not a gamer21:10
pwnguinheh21:11
pwnguingamers dont use joypads on PC21:11
pwnguinthey're so pedestrian21:11
pwnguinplus, there's so many of them, with different numbers of buttons and sticks and layouts21:12
pwnguinso we wind up with a few games in Ubuntu that are Designed for Xbox 36021:14
bryceit's not so much they don't work, just that there's some manual configuration needed that we could probably do a lot more cleanly21:49
brycealso there's some driver issues, like certain buttons not working, or features not working in the same modes, etc.  little stuff21:50
=== fooderico is now known as federic1
=== federic1 is now known as federico1
tjaaltonhmm, my rumblepad doesn't seem to like evdev, or the other way around22:05
tjaalton(WW) Logitech Logitech RumblePad 2 USB: Don't know how to use device22:05
tjaaltonbut usually it's just that the fdi-files need to know about the devices (like the apple trackpads)22:05
tjaaltonevdev should have the same features as mouse has, plus properties22:08
tjaaltonand non-serial tablets should work OOTB22:09
tjaaltonby now22:09
tjaaltonevdev only has two bugs, of which one is likely fixed and the other one is asking for the moon22:10
tjaaltonmaybe I'll debug joysticks tomorrow then ;)22:14
pwnguintjaalton: so protocol IV stuff is serial -- i should be making fdi rules for that?22:22
tjaaltonpwnguin: serial devices can't be autodetected AIUI22:23
tjaaltonyou need some input from them first22:23
pwnguinheh22:23
pwnguintheres another trick22:23
pwnguindont detect the serial22:23
pwnguindetect the laptop that should have one22:23
tjaaltonthat should work22:23
tjaaltoncould22:23
pwnguinunfortunately, the laptop team is dead22:24
tjaaltonso revive it?-)22:28
pwnguinwell, i kinda have22:28
pwnguinthe toshiba tablet team!22:29
tjaaltonbtw, just matching the laptop model doesn't work. you need to match the device22:29
tjaaltonand then tell it to load the driver for that device22:30
pwnguin"device"22:30
tjaaltonyou can't say "oh, this is toshiba FOO, load wacom" and expect it to work :)22:30
tjaaltonsee the output of lshal22:30
tjaaltonyour mouse probably has several devices22:31
tjaaltonof which only one is the device that the driver can handle22:32
tjaaltonthe one that has info.capabilities ~= input.mouse22:32
pwnguinlshal's pretty damn long22:32
pwnguinheh22:33
pwnguinudi = '/org/freedesktop/Hal/devices/pnp_WACf004' info.capabilities = {'input', 'input.tablet', 'input.tablet.tabletPC'} (string list)22:33
pwnguinthose ones22:33
tjaaltonthere you go22:33
tjaaltonis that a serial device?22:33
pwnguinyes22:33
tjaaltonsweet22:34
pwnguintwo of em22:34
pwnguinerr22:34
tjaaltonso the wacom fdi should match the info.product of it22:34
pwnguintjaalton: the launchpad team "Toshiba Tablet Team" should have an email you can reach random wacom tester/motu/devs at22:35
tjaaltonok22:36
bdmurraybryce: about bug 163044 if I can't recreate that is not an indication it is fixed right?22:48
ubottuLaunchpad bug 163044 in xserver-xorg-driver-ati "[M6] terminal display error when reading PDF files" [Unknown,Confirmed] https://launchpad.net/bugs/16304422:48
brycebdmurray: generally if you were able to reproduce the bug in some fashion, and then with current code the problem does not occur, then that's considered a verification of a fix22:49
brycehowever, if you're never able to reproduce the problem, and it just works, that's not sufficient to confirm it as fixed.22:49
bdmurraybryce: okay, but I never saw the bug originally so won't comment22:49
bryceif you have identical hardware to the reporter, then *maybe* that can be considered fixed, but it'd still be good to ask the original reporter to confirm.22:49
pwnguintjaalton: where is this wacom.fdi?22:50
pwnguintjaalton: so I can see this wacom rules mentioned in the changelog and in the source package, but it's not in the binary...23:17
pwnguinanyone wanna confirm what i think is wrong with this patch?23:24
pwnguin+mkdir -p debian/$(package_xorg)/usr/share/hal/fdi/policy/20thirdparty/23:24
pwnguin+dh_install debian/10-wacom.fdi usr/share/hal/fdi/policy/20thirdparty/23:24
pwnguin+err23:25
pwnguin<-- fails23:25

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!