[00:18] bdmurray: couldn't hurt [00:18] bdmurray: bugs-without-a-package might be worth looking at as well [00:19] bryce: oh, that'd be sweet [00:19] It might help assign packages to them too [00:42] bryce: bug 266959 might be important [00:42] Launchpad bug 266959 in ubuntu "remove_conffile_commit(" [Undecided,New] https://launchpad.net/bugs/266959 [00:50] hmm [00:50] tjaalton: 266959 is for xorg 1:7.4~1ubuntu1.1 [00:53] hrm, but apt-cache madison is showing only 1:7.4~1ubuntu1 available [00:58] 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] that's what someone else said too [01:00] er, that it didn't affect them [03:21] 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] tjaalton: or let me know and I can push the release Monday. [03:24] 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] bryce: Do you know why the alpha 5 desktop CD would be losing knowledge of most of my keys often? [03:25] wgrant: not offhand, but that bug sounds familiar [03:25] Soon after restarting X, I will be able to type alpha-numerics, Ctrl, Alt, Backspace, and that's about it. [03:25] Anything I can do to debug? [03:26] it sounds very familiar - look in launchpad to see if there's a matching existing bug [03:26] Against which package? [03:26] my bet is that it's something hal-related [03:26] evdev, or the server? [03:26] Right, that's what I thought. [03:27] yeah, evdev, xkeyboard-config, xorg, or xorg-server would be most likely [03:27] Bug #254939 looks relevant. [03:27] Launchpad bug 254939 in xserver-xorg-input-evdev "No Mouse/Keyboard since update and restart on evening of 4th August." [Undecided,Fix released] https://launchpad.net/bugs/254939 [03:28] (particularly one of the comments) [03:29] I'll file a new one, as that is closed and really for another issue. [03:30] sounds good; I'm looking through some lp bugs to see if I can find the one I was thinking of [03:30] Huh. [03:31] Left arrow is Alt_R. [03:31] Down arrow is Super_R. [03:32] Somethings really broken. [03:32] anything happen if you unplug your keyboard and plug it back in? [03:32] It's a laptop. [03:32] Aha. [03:32] oh :-) [03:32] Works fine if I force the model through g-s-d. [03:33] And it works even if I now force it back to evdev. [03:33] mmmm, could it be #225643 then? [03:33] I don't think so. [03:33] I don't get that error, and it works for a while. [03:34] And I have a minimal (live CD) xorg.conf. [03:35] okay, this is the one I was remembering - bug 255008 [03:35] Launchpad bug 255008 in xorg-server "Up arrow key mapped to Print [screen]" [High,Fix released] https://launchpad.net/bugs/255008 [03:35] That's it. [03:35] Same symptom, at least. [03:36] looks like it's marked as fixed though [03:36] mdz seemed unsure. [03:36] 257855 was marked as a dupe [03:38] tjaalton will probably have a better clue than I on this one; he's been focusing on keyboard stuff lately. [03:38] I do have a keyboard troubleshooting page (mostly outdated now with input-hotplug tho) [03:39] The strange thing is that it worked for me on a 48-hour old Intrepid installation on the same hardware. [03:39] And alpha 5 is a similar age. [03:39] https://wiki.ubuntu.com/X/Troubleshooting [03:40] there's some steps for checking if the keys are being mapped by the kernel [03:41] 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] X and tty1 see different keycodes for Up. [03:42] But it all seems to be working now :( [03:43] hmm [03:43] well keep an eye out for it - sounds like the sort of issue that'd reoccur periodically [03:44] 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] so "basic" keys probably just happen to have the same mappings for both of them, which is why those work [03:44] Yep. [03:45] I'll bet gnome is involved in this at some level [03:46] Most likely. [04:01] The keycode is 111 whether or not things are working, but the keysym changes (at least as xev sees them). [04:01] (for up arrow) [04:18] 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 [04:18] Launchpad bug 262491 in xserver-xgl "Please remove xserver-xgl (universe) from the archives" [Low,Fix released] https://launchpad.net/bugs/262491 [06:59] wgrant, bryce: the keyboard-changes I talked about should fix this for everyone [07:01] 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] that's been changed upstream a couple of weeks ago when I had a chat with svu (xkeyboard-config maintainer) and daniels [07:03] bryce: yeah that bug is about the cleanup commit I made, but apparently it's not quite right yet [07:49] bryce: did you notice that the failsafeXinit doesn't have all the functions in it, or they are misnamed? [07:49] view_log should probably be view_xorg_log, and view_errors -> view_gdm_log [08:37] mm, banshee taking 9999% of cpu [08:53] bryce, bdmurray: I closed all xgl bugs already, needed the karma boost ;) [08:53] tjaalton: heh [08:58] tjaalton: ah good catch; I've pushed those fixes [08:59] cool [09:00] 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] s/fallback/autoconfig/ [09:02] sounds good to me [09:04] ok, good [09:11] 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] but since the ABI hasn't really been changed, we could revert those changes for now [09:11] and deal with the bump when intrepid+1 opens [09:12] or, do it now and sync most of the drivers from experimental [09:13] why was videoabiver bumped if the ABI hasn't really changed? [09:13] to match the source [09:13] ah [09:13] it has been 4 since March i guess [09:13] well, I don't have a problem with rebuilding all the video drivers at this point. Still plenty of time before release. [09:14] yeah, I can deal with that on Monday [09:14] sounds good [09:14] or tomorrow if I'm bored [09:14] tomorrow for me is going to involve a whole lot of pruning shrubs in the backyard [09:15] and digging stuff up [09:15] (I'm getting a deck put in a couple weeks from now so we gotta do some landscaping to make room) [09:16] hehe, sounds nice [09:16] tjaalton: we'll have to rebuild the nvidia drivers too [09:16] tseliot: sure [09:18] I've got a couple of concerts to perform on.. that said, I'm running late.. seeya -> [12:13] 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] Downgrading xserver-xorg-input-synaptics from 0.15.0+git20080820-1ubuntu5 to 0.14.7~git20070706-2.1ubuntu3 made my ALPS touchpad work again. === johanbr_ is now known as johanbr [19:43] morning [19:43] good morning [21:13] is it intended that nvidia-kernel-common recommends the actual drivers? [21:15] 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