[00:21] <james_w> thanks tjaalton 
[07:53] <tseliot> tjaalton: can I have my mouse back in Intrepid, please?
[07:53] <pwnguin> heh
[07:53] <tseliot> xorg-server 2:1.4.99.906-1ubuntu1 breaks my mouse
[07:53] <pwnguin> im glad im not the only one who doesnt understand hal
[07:56] <tseliot> oh, and here's the log: http://pastebin.com/m2f6aa233
[07:58] <tjaalton> tseliot: hmm, and the xorg.conf?
[07:58] <pwnguin> xorg doesnt seem to think you need input
[07:58] <tjaalton> right
[07:58] <pwnguin> #
[07:58] <pwnguin> #
[07:58] <pwnguin> (==) ServerLayout "Default Layout"
[07:58] <pwnguin> #
[07:58] <pwnguin> (**) |-->Screen "Default Screen" (0)
[07:58] <pwnguin> #
[07:58] <pwnguin> (**) |   |-->Monitor "Configured Monitor"
[07:58] <pwnguin> #
[07:58] <tseliot> tjaalton: http://pastebin.com/m6bd06a1c
[07:59] <pwnguin> so uh
[07:59] <tseliot> pwnguin: ?
[07:59] <pwnguin> where'd that xorg.conf come from?
[08:00] <tseliot> jockey + xkit
[08:00] <pwnguin> (does input hotplug mean you can omit input from the layout?)
[08:00] <tjaalton> input-hotplug is not turned on yet
[08:01] <tseliot> it works well with the previous version of xserver-xorg-core
[08:02] <pwnguin> if you add "Configured Mouse" and "Identified Keyboard" to the ServerLayout
[08:02] <tseliot> pwnguin: Each  ServerLayout  section  must have an Identifier entry and at least one Screen entry.
[08:02] <tjaalton> yes, try adding the mouse to the ServerLayout
[08:03] <tjaalton> I'll upgrade my laptop asap
[08:03] <tseliot> "Normally at least two [input devices] are required, one each for the core pointer and keyboard devices.  If either  of  those is  missing, suitable InputDevice entries are searched for using the method described above in the  INPUTDEVICE  section."
[08:03] <pwnguin> url?
[08:03] <tseliot> therefore it shouldn't be necessary
[08:03] <tseliot> man xorg.conf
[08:04] <tjaalton> shouldn't, but I'm not sure if it's the patches or .906 that broke it
[08:04] <tseliot> and get to the ServerLayout section
[08:04] <pwnguin> if you want your mouse back asap, i think adding it to server layout would do tha
[08:04] <pwnguin> t
[08:05] <tseliot> I had to go back to the previous revision of the package
[08:06] <tseliot> I'll reinstall the latest release and try with the 2 entries in the serverlayout section
[08:06]  * tseliot tries
[08:07]  * tseliot restarts X
[08:08] <tseliot> ok, that did it
[08:08] <tseliot> I think it's a bug though
[08:10] <tseliot> tjaalton: I'll file a bug report
[08:10] <tjaalton> tseliot: already files
[08:10] <tjaalton> -ed
[08:10] <tjaalton> bug 254868
[08:11] <pwnguin> LP# 254868
[08:11] <pwnguin> i tried. bots hate me today
[08:11] <tjaalton> https://bugs.launchpad.net/bugs/254868
[08:11] <tseliot> ok, I'll add a comment there then
[08:12] <tseliot> if it's a feature they will have to update the documentation
[08:12] <tjaalton> can't be
[08:12] <tseliot> otherwise it's a bug
[08:12] <tjaalton> I'll try without the patches first
[08:15] <tjaalton> yep, no mouse
[08:18] <tseliot> ok, log, xorg.conf(s) are attached
[08:27] <tjaalton> found the problem
[08:27] <tjaalton> http://gitweb.freedesktop.org/?p=xorg/xserver.git;a=commitdiff;h=c30f36c8c1dfd85deaf1c109823a1f15dd218ac7
[08:28] <tjaalton> setting AllowEmptyInput to false fixed it
[08:28] <tjaalton> so that commit is broken
[08:29] <tjaalton> and now I remember seeing this before on debian-x@ :)
[08:33] <tseliot> yep, that's it
[11:39] <jcristau> tjaalton: i complained about it on xorg@ too (and somewhat fixed it on master) :)
[11:40] <tjaalton> jcristau: ok, well input-hotplug fixed that anyway, so no worries :)
[11:47] <tjaalton> although I did notice that my laptop had another kbmodel set in gnome, and some keys didn't work. I thought that evdev was forced
[17:09] <tseliot> federico1,bryce: I have just tried to call my program from the Screen resolution applet and it works
[17:10] <tseliot> :-)
[17:11] <tseliot> oh, and I have also removed a few files from my package of screen-resolution-extra and set up a bzr branch: https://code.launchpad.net/~albertomilone/screen-resolution-extra/main
[17:13] <crevette> tseliot, in the files com.ubuntu.ScreenResolution.Mechanism.* there are references to LIRC :)
[17:14] <tseliot> crevette: yes, I know. I took their files as an example
[17:15] <tseliot> since using PolicyKit from Python is not documented
[17:15] <tseliot> s/using/the use/
[17:33] <federico1> tseliot: w00t
[17:33] <federico1> tseliot: one second; I'm in a meeting
[17:34] <tseliot> federico1: ok
[17:54] <bryce> tseliot: sweet
[17:55] <tjaalton> hey bryce
[17:56] <bryce> heya
[17:57] <tjaalton> so, input-hotplug is now in use
[17:58] <bryce> yay
[18:00] <bryce> I've reviewed all the input configuration docs on both w.u.c and h.u.c, cleared out some obviously out of date stuff, and left a bunch that I suppose will still be valid, just not necessary (but can't say for sure without testing)
[18:00] <bryce> also none of it seems to related to input-hotplug (dynamic) configuration, so I started some new docs for that
[18:00] <bryce> it's down towards the end of https://wiki.ubuntu.com/X/Config, showing basic xinput usage
[18:01] <tseliot> bryce: I had to change the type of 2 pointers (in your patch) to make it compile and added some other things
[18:01] <bryce> I need to reorganize that page a bit
[18:01] <bryce> tseliot: ahh
[18:01] <bryce> tseliot: is it good to go, or are any other changes needed?
[18:02] <bryce> tseliot: probably we should go ahead and get all this into intrepid soon
[18:02] <tseliot> of course I will have to adapt the python part a bit so as to make sure that the changes in the API didn't break anything
[18:02] <tseliot> bryce: maybe we should upload xkit first
[18:02] <tjaalton> bryce: actually, xinput is not really dependant on input-hotplug, and it's not that useful before input properties are in
[18:06] <tjaalton> xinput has been around for some time, but recently input properties was implemented and is now in master (xinput/xserver.. needs driver support as well)
[18:11] <bryce> tjaalton: ah, hm
[18:11] <bryce> so then what would one use to do mouse/keyboard configuration now?
[18:11] <tjaalton> let evdev handle it
[18:12] <bryce> tseliot: agreed.  need help with that?
[18:12] <bryce> tjaalton: how does one configure evdev?
[18:13] <tjaalton> great, no keyboard after suspend/hibernate with evdev
[18:14] <jcristau> tjaalton: i never had a problem with that
[18:14] <jcristau> does the log give any clue/
[18:14] <tjaalton> jcristau: ok.. must be a kernel problem then
[18:15] <jcristau> s,/,?,
[18:15] <tjaalton> restarting the server makes it work though
[18:15] <tjaalton> bryce: input.x11_options.<option name> (string). see xorg-server/config/x11-input.fdi
[18:16] <tjaalton> bryce: so users/GUI's can put files in /etc/hal/fdi/policy
[18:17] <tjaalton> jcristau: need to check. I wanted to confirm that using kbd had no problems
[18:21] <tjaalton> jcristau: which kernel do you have?
[18:22] <tjaalton> intrepid has 2.6.26
[18:23] <tseliot> bryce: yes, help is always welcome (and I'm not a MOTU yet). Let me commit my latest changes so that lintian stops complaining and the package will be ready to be uploaded
[18:24] <jcristau> tjaalton: right now 2.6.26
[18:24] <tjaalton> hmm, I'll try 2.6.24
[18:25] <tjaalton> suspend never really worked on intrepid (it resumed right away), so maybe with the hardy kernel..
[18:26] <tjaalton> yep, works like a charm
[18:26] <tjaalton> keyboard too, after resume
[18:27] <tjaalton> ok, now with .26 to see if the log has anything
[18:32] <tjaalton> goddamn network-manager, please gimme a network without a user session
[18:32] <tseliot> bryce: ok, the package is ready now. It's in my bzr branch: https://code.launchpad.net/~albertomilone/xorgparser/main
[18:33] <jcristau> tjaalton: dpkg -P network-manager ;)
[18:35] <tjaalton> jcristau: well, it's useful sometimes :)
[18:36] <jcristau> i guess. otoh, seeing how i don't use gnome...
[18:37] <tjaalton> interestingly, starting another login screen (gdm, from the gnome-screensaver dialog) made the keyboard to work again, and logging as myself let me into the old session
[18:38] <tjaalton> and after the next suspend keyboard worked fine
[18:40] <jcristau> hah
[18:42] <tjaalton> so it fails once per xserver start
[18:43] <bryce> tseliot: pulling
[18:44] <tjaalton> the log only shows how it reloads evdev for the external mouse
[19:00] <tseliot> bryce: thanks
[19:05]  * tseliot > dinner
[19:05] <tseliot> bbl
[19:07] <tjaalton> home ->
[21:12] <bryce> heya tormod!
[21:13] <tormod> hi bryce :)
[21:14] <bryce> tseliot: sent some feedback on the package (nothing major).  Looks like MOTU policy is to have two MOTU's signoff on a package, so figure we should get another MOTU's thumb's up (maybe mvo or pitti?) before I shove it in.  
[21:22] <tseliot> bryce: first of all, thanks for your feedback, I'll read your email carefully. I'll bug pitti about this tomorrow. ScottK might be interested too
[21:27] <pwnguin> i wish people would stop claiming nothing uses Xinput
[21:28] <bryce> pwnguin: ??
[21:28] <pwnguin> gimp, xournal, gok, cellwriter
[21:28] <pwnguin> bryce: every talk I see on the new xorg features like mpx claim nothing uses xinput
[21:28] <bryce> ah
[21:29] <pwnguin> i bet inkscape does too
[21:29] <bryce> hmm good question
[22:29] <tormod> bryce: I put the console-fdi.sh output into a file in /etc/hal/fdi/ but it doesn't seem to be picked up by hal (as per lshal). Is something more needed? I even copied in /usr/share/doc/hal/examples/10-x11-input.fdi but I think that is not needed in intrepid (can't check now).
[22:31] <tjaalton> tormod: if you have hal ..ubuntu5, input-hotplug should work without any manual configuration
[22:31] <tjaalton> maybe your mirror doesn't have it yet
[22:31] <bryce> tormod: as per discussion on #ubuntu-devel, doesn't look like the script's needed anymore
[22:31] <tormod> is it something very new? then I haven't checked.
[22:31] <bryce> (what a short life my little script lived)
[22:31] <tjaalton> bryce: :)
[22:32] <tormod> ok I'll check the -devel logs
[22:33] <tjaalton> bryce: I did mention about discovering the fedora stuff ~24h ago, but maybe you were busy writing documentation
[22:33] <tjaalton> it's the patch for hal that made all the difference. without it you'd get the same error as I did (as mentioned on ubuntu-x@ a while back)
[22:36] <tjaalton> ie. hal-set-property complaining that hald is not running
[22:36] <bryce> ah
[22:36] <bryce> you know I find wiki.ubuntu.com extraordinarily frustrating
[22:36] <bryce> maybe I mentioned this already
[22:36] <tjaalton> you don't say
[22:37] <bryce> the help.ubuntu.com wiki isn't much better
[22:40] <tjaalton> I bet it's a mess
[22:40] <tjaalton> anyway, defaulting AllowEmptyInput to false doesn't seem to break anything, evdev still grabs the devices if hal is running
[22:42] <tjaalton> and resuming my other laptop (TP T23) results in a working keyboard, unlike on my X61
[23:23] <bryce> tjaalton: ok, updated the docs at https://wiki.ubuntu.com/X/Config to include some hal configuration examples.  I think I covered all the common cases, although I'd appreciate it if you'd sanity check it
[23:24] <bryce> the examples I used are all for things which already work and require no configuration, so they're a bit contrived.  Feel free to replace with something more realistic.
[23:26] <bryce> btw, I just finished doing a dist upgrade of my 965 laptop to intrepid.  
[23:27] <bryce> keyboard/mouse/etc. seem to work ok
[23:27] <bryce> tjaalton: I ran into that compiz-on-intel bug though.  do you know what we need to do to get that fixed?
[23:28] <tjaalton> bryce: compiz works for me.. what problem are you seeing?
[23:29] <bryce> blank screen
[23:29] <bryce> backlight on
[23:29] <bryce> switching tty's seemed to work, but nothing was displayed
[23:29] <tjaalton> ah, not a compiz problem, but kernel
[23:30] <tjaalton> disable usplash
[23:30] <bryce> issue went away after I chmod a-x /usr/bin/compiz (or maybe it was coincidental)
[23:30] <tjaalton> compiz isn't loaded until the user is logged it
[23:30] <tjaalton> -in
[23:30] <bryce> also see lp #254091
[23:31] <bryce> hmm, ok
[23:32] <bryce> anyway, issue seems to not be happening now.  guess it was just a funky upgrade situation
[23:33] <tjaalton> that bug was a dupe of bug 245888
[23:34] <tjaalton> btw, my logitech mice got the wheel axes right with i-h
[23:34] <tjaalton> ie. current evdev
[23:36] <tjaalton> there was a bug open, so I closed it, along with 10+ other evdev bugs
[23:41] <bryce> ah thanks, I wondered if it was a dupe of that 
[23:42] <tjaalton> hmm, the logitech example uses the mouse-driver
[23:53] <tjaalton> bryce: btw, what about failsafe, should it be dropped from xorg&gdm?
[23:59] <tjaalton> sheesh, it's late.. night ->