[01:51] ugh... found out what my problem was compiling xserver. nasty http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=536034 [01:51] Debian bug 536034 in dpkg-dev "dpkg-dev: dpkg-gensymbols produces broken symbols files" [Serious,Closed] [01:52] http://groups.google.se/group/linux.debian.bugs.dist/browse_thread/thread/dfcd924e8426179b?fwc=1 [01:52] guess ubuntu hasnt picked that up yet [01:58] ahh it is there, no clue why i'm still getting the errors [09:45] after switching to ati (because fglrx stopped working in jaunty), X starts up but no keyboard and no mouse. Any suggestions? [09:46] is hald running? [09:47] no indeed. I see. Should reboot out of failsafe mode first. [09:47] (xorg gets its input devices from hal atm) [09:50] err now every key sends three letters !? [09:50] I type 'd' and I see "ddd" [09:51] anyone seen that before? [09:51] do you have any input devices defined in /etc/X11/xorg.conf? I'm guessing wildly here, I'm just wondering if it's seeing the same event from several different keyboards that are actually the same keyboard defined in several places? [09:51] seems kinda unlikely though [09:52] indeed commenting out the input devices fixes it. Weird though, there was just one of each, not 3. [10:22] Ng: thanks for the help. Everything ok now. === zorael_ is now known as Zorael === michael__ is now known as michaellarabel [14:26] Sarvatt: ping [15:22] Sarvatt: never mind [15:22] ScottK: I have ported my patches for synaptics to Karmic. Have a look at my PPA (and at the bug report) [15:23] tseliot: OK. I'm reinstalling for ISO testing right now. I'll give it a try in a bit. [15:23] ok, thanks === Zorael is now known as Zorael^nb [19:37] bryce: so how goes the intel upstreaming? is it all done? [19:38] bug upstreaming that is [19:39] jbarnes, I've got 15 or so left to go. I sort of got inspired/distracted by a comment you made earlier, and have been working on a tool to do upstreaming for me [19:41] nice [19:41] there also seems to be some confusion as to whether I should set priorities on upstream bugs or leave it unset, so I'm waiting for the higher ups to get that sorted [19:43] jbarnes, http://people.canonical.com/~bryce//upstream.svg [19:46] that makes it look like only 20% are upstreamed so far? [19:46] bryce: I think it's ok to set prio [19:46] we may drop it down depending on our release schedule, but imo it's fine to set it as an indicator of its importance to you [19:46] the worry on our team was that we're using priorities as our release criteria [19:46] p1 bugs are basically release blockers [19:47] right, we got a bit over 20% but it fell lately because I pulled in 2.8.0 and closed out the upstreamed bugs that were fixed [19:48] what that chart doesn't tell is that 180 bugs are incomplete waiting on reporters [19:48] ah that's the discrepancy [19:49] yeah there's only 15-20 that I need to do something with. But they're probably mostly just dupes of known issues [19:49] cool [19:49] in most cases you don't hear back from people after asking for more information or asking to try a newer version, so the bugs sit there for a while. at least that's my experience in debian. [19:50] and those are not upstreamable [19:50] many of those incomplete bugs were ones reported with Jaunty's release, which my script asked them to re-test. Those are all scheduled to expire here this coming week. So I think we should see a nice jump in the stats within the week [19:50] jcristau, yep exactly [20:22] bryce: ok consensus is to mark prio according to what prio it is for ubuntu [20:22] like I said, we may bump it down but that can be handled at your regular meetings with yingying if there's disagreement [20:32] okie doke [22:13] I put in an openchrome git update in xorg-edgers if anyone's interested [22:14] openchrome is in git now? [22:28] s/git/svn/ [22:28] jcristau, at least I didn't say bzr snapshot ;-) [22:31] bryce: heh. you had me hoping they made the switch :) [23:03] got me too, i thought the same thing :D === jbarnes_ is now known as jbarnes