[00:18] <bryce> bdmurray: couldn't hurt
[00:18] <bryce> bdmurray: bugs-without-a-package might be worth looking at as well
[00:19] <bdmurray> bryce: oh, that'd be sweet
[00:19] <bdmurray> It might help assign packages to them too
[00:42] <bdmurray> bryce: bug 266959 might be important
[00:50] <bryce> hmm
[00:50] <bryce> tjaalton:  266959 is for xorg 1:7.4~1ubuntu1.1 
[00:53] <bryce> hrm, but apt-cache madison is showing only 1:7.4~1ubuntu1 available
[00:58] <bryce> bdmurray: thanks for pointing that one out; I wonder where that .1 comes from though (I've done an upgrade just now and don't see it)
[00:59] <bdmurray> that's what someone else said too
[01:00] <bdmurray> er, that it didn't affect them
[03:21] <bryce> tjaalton: I noticed you did a merge with xorg.  The changes I have queued there are good to go if you're waiting on that for doing a release.
[03:21] <bryce> tjaalton: or let me know and I can push the release Monday.
[03:24] <bryce> tjaalton: also I got the -ati sync in, but found it FTBS on my system due to mismatched build-deps requirements.  I've fixed that, as well as uploaded the quirks system patch
[03:25] <wgrant> bryce: Do you know why the alpha 5 desktop CD would be losing knowledge of most of my keys often?
[03:25] <bryce> wgrant: not offhand, but that bug sounds familiar
[03:25] <wgrant> Soon after restarting X, I will be able to type alpha-numerics, Ctrl, Alt, Backspace, and that's about it.
[03:25] <wgrant> Anything I can do to debug?
[03:26] <bryce> it sounds very familiar - look in launchpad to see if there's a matching existing bug
[03:26] <wgrant> Against which package?
[03:26] <bryce> my bet is that it's something hal-related
[03:26] <wgrant> evdev, or the server?
[03:26] <wgrant> Right, that's what I thought.
[03:27] <bryce> yeah, evdev, xkeyboard-config, xorg, or xorg-server would be most likely
[03:27] <wgrant> Bug #254939 looks relevant.
[03:28] <wgrant> (particularly one of the comments)
[03:29] <wgrant> I'll file a new one, as that is closed and really for another issue.
[03:30] <bryce> sounds good; I'm looking through some lp bugs to see if I can find the one I was thinking of
[03:30] <wgrant> Huh.
[03:31] <wgrant> Left arrow is Alt_R.
[03:31] <wgrant> Down arrow is Super_R.
[03:32] <wgrant> Somethings really broken.
[03:32] <bryce> anything happen if you unplug your keyboard and plug it back in?
[03:32] <wgrant> It's a laptop.
[03:32] <wgrant> Aha.
[03:32] <bryce> oh :-)
[03:32] <wgrant> Works fine if I force the model through g-s-d.
[03:33] <wgrant> And it works even if I now force it back to evdev.
[03:33] <bryce> mmmm, could it be #225643 then?
[03:33] <wgrant> I don't think so.
[03:33] <wgrant> I don't get that error, and it works for a while.
[03:34] <wgrant> And I have a minimal (live CD) xorg.conf.
[03:35] <bryce> okay, this is the one I was remembering - bug 255008
[03:35] <wgrant> That's it.
[03:35] <wgrant> Same symptom, at least.
[03:36] <bryce> looks like it's marked as fixed though
[03:36] <wgrant> mdz seemed unsure.
[03:36] <bryce> 257855 was marked as a dupe
[03:38] <bryce> tjaalton will probably have a better clue than I on this one; he's been focusing on keyboard stuff lately. 
[03:38] <bryce> I do have a keyboard troubleshooting page (mostly outdated now with input-hotplug tho)
[03:39] <wgrant> The strange thing is that it worked for me on a 48-hour old Intrepid installation on the same hardware.
[03:39] <wgrant> And alpha 5 is a similar age.
[03:39] <bryce> https://wiki.ubuntu.com/X/Troubleshooting
[03:40] <bryce> there's some steps for checking if the keys are being mapped by the kernel
[03:41] <bryce> so I'd suggest your debugging should start by looking showkey to see if the kernel is reporting the keycodes, and then if so, use xev to see if X sees them
[03:42] <wgrant> X and tty1 see different keycodes for Up.
[03:42] <wgrant> But it all seems to be working now :(
[03:43] <bryce> hmm
[03:43] <bryce> well keep an eye out for it - sounds like the sort of issue that'd reoccur periodically
[03:44] <bryce> but it sounds like X is getting confused about the keyboard layout and isn't in sync with what the kernel is using
[03:44] <bryce> so "basic" keys probably just happen to have the same mappings for both of them, which is why those work
[03:44] <wgrant> Yep.
[03:45] <bryce> I'll bet gnome is involved in this at some level
[03:46] <wgrant> Most likely.
[04:01] <wgrant> The keycode is 111 whether or not things are working, but the keysym changes (at least as xev sees them).
[04:01] <wgrant> (for up arrow)
[04:18] <bryce> bdmurray: hey if you feel like going on a WONTFIX rampage, as of bug #262491 xserver-xgl is no longer a Ubuntu package, and all of its (many) bugs can be WONTFIX'ed
[06:59] <tjaalton> wgrant, bryce: the keyboard-changes I talked about should fix this for everyone
[07:01] <tjaalton> now you need to force the model to be evdev, but that breaks exotic layouts (ABNT2, jp106). so the solution is to force the rules instead
[07:01] <tjaalton> that's been changed upstream a couple of weeks ago when I had a chat with svu (xkeyboard-config maintainer) and daniels
[07:03] <tjaalton> bryce: yeah that bug is about the cleanup commit I made, but apparently it's not quite right yet
[07:49] <tjaalton> bryce: did you notice that the failsafeXinit doesn't have all the functions in it, or they are misnamed?
[07:49] <tjaalton> view_log should probably be view_xorg_log, and view_errors -> view_gdm_log
[08:37] <tjaalton> mm, banshee taking 9999% of cpu
[08:53] <tjaalton> bryce, bdmurray: I closed all xgl bugs already, needed the karma boost ;)
[08:53] <bryce> tjaalton: heh
[08:58] <bryce> tjaalton: ah good catch; I've pushed those fixes
[08:59] <tjaalton> cool
[09:00] <tjaalton> what about the fallback patch for xserver? if we applied that, we could drop failsafeDexconf and let the failsafe-mode run without xorg.conf
[09:01] <tjaalton> s/fallback/autoconfig/
[09:02] <bryce> sounds good to me
[09:04] <tjaalton> ok, good
[09:11] <tjaalton> also, as jcristau pointed out, the videoabiver has been bumped on debian (2.9->4) which would mean rebuilding all the video drivers if we uploaded current xorg/xorg-server from git
[09:11] <tjaalton> but since the ABI hasn't really been changed, we could revert those changes for now
[09:11] <tjaalton> and deal with the bump when intrepid+1 opens
[09:12] <tjaalton> or, do it now and sync most of the drivers from experimental
[09:13] <bryce> why was videoabiver bumped if the ABI hasn't really changed?
[09:13] <tjaalton> to match the source
[09:13] <bryce> ah
[09:13] <tjaalton> it has been 4 since March i guess
[09:13] <bryce> well, I don't have a problem with rebuilding all the video drivers at this point.  Still plenty of time before release.
[09:14] <tjaalton> yeah, I can deal with that on Monday
[09:14] <bryce> sounds good
[09:14] <tjaalton> or tomorrow if I'm bored
[09:14] <bryce> tomorrow for me is going to involve a whole lot of pruning shrubs in the backyard
[09:15] <bryce> and digging stuff up
[09:15] <bryce> (I'm getting a deck put in a couple weeks from now so we gotta do some landscaping to make room)
[09:16] <tjaalton> hehe, sounds nice
[09:16] <tseliot> tjaalton: we'll have to rebuild the nvidia drivers too
[09:16] <tjaalton> tseliot: sure
[09:18] <tjaalton> I've got a couple of concerts to perform on.. that said, I'm running late.. seeya ->
[12:13] <johanbr> Hmm. After the latest Intrepid updates (X, among many other things, but not kernel) my touchpad only functions in "dumb mouse emulation" mode and Xorg.log says "(WW) AlpsPS/2 ALPS GlidePoint can't grab event device, errno=16"
[17:37] <johanbr> Downgrading xserver-xorg-input-synaptics from 0.15.0+git20080820-1ubuntu5 to 0.14.7~git20070706-2.1ubuntu3 made my ALPS touchpad work again.
[19:43] <bryce> morning
[19:43] <tseliot> good morning
[21:13] <Adri2000> is it intended that nvidia-kernel-common recommends the actual drivers?
[21:15] <Adri2000> nvidia-kernel-common being a dependency of linux-restricted-modules, every machine using a non-free driver will also get the nvidia non-free driver installed, even if it has no nvidia card