[04:24] <ubotu> New bug: #146142 in xorg (main) "gnome-mouse-properties: Horizontal Scrolling is useless" [Low,Fix released]  https://launchpad.net/bugs/146142
[04:39] <ubotu> New bug: #85746 in xorg (main) "feisty kubuntu installer - X started but nothing shown" [Undecided,Incomplete]  https://launchpad.net/bugs/85746
[04:52] <ubotu> New bug: #128526 in xresprobe (main) "probing for X, causes scrambled Frame Buffer" [Undecided,New]  https://launchpad.net/bugs/128526
=== tehk [n=tehk@c-69-249-157-157.hsd1.nj.comcast.net]  has joined #ubuntu-x
=== mvo [n=egon@p54A67E6B.dip.t-dialin.net]  has joined #ubuntu-x
[06:46] <ubotu> New bug: #149260 in mesa (main) "wine-git/google earth crashes with DRM_I830_CMDBUFFER: -22 on Thinkpad X60" [Undecided,New]  https://launchpad.net/bugs/149260
[08:15] <tepsipakki> bryce: hey, seems that tormod has been doing great work with -ati
[08:15] <bryce> :-)
[08:15] <bryce> tepsipakki: what in particular?
[08:15] <tepsipakki> hopefully there'll be a new release soon, or should we upload his version?
[08:16] <tepsipakki> tracking upstream changes and asking people test his ppa
[08:16] <bryce> I was looking at the changelog from upstream and noticed a lot of fixes it would be nice to have
[08:16] <bryce> including bug 86072
[08:16] <ubotu> Launchpad bug 86072 in xserver-xorg-video-ati "ATI ES1000 515e not recognized" [Medium,In progress]  https://launchpad.net/bugs/86072
[08:17] <bryce> hmm, well it would be a shame to waste his hard work - if you're comfortable with how it looks, I would favor uploading it as well
[08:18] <tepsipakki> if RC is next Thursday, we should act soon I think
[08:18] <bryce> agreed
[08:18] <bryce> tepsipakki: yesterday it was decided to postpone the freeze until Friday
[08:18] <bryce> (maybe it's friday for you already?)
[08:18] <tepsipakki> yep, 09:18 here :)
[08:18] <tepsipakki> AM
[08:18] <bryce> heh
[08:19] <bryce> btw, I packaged up a snapshot of the intel git head for testing:  http://people.ubuntu.com/~bryce/Testing/intel/
[08:20] <tepsipakki> oh, something happening there too :P
[08:57] <ubotu> New bug: #148686 in xserver-xorg-video-intel (main) "screen blinks a lot during boot " [Undecided,New]  https://launchpad.net/bugs/148686
[09:12] <tepsipakki> bryce: I'll merge -ati by tormod and ask his opinion if it should be uploaded when he shows up
[09:21] <bryce> great
[09:50] <ubotu> New bug: #149297 in xserver-xorg-video-intel (main) "xserver-xorg-video-intel package missing changelog" [Undecided,Confirmed]  https://launchpad.net/bugs/149297
=== seb128 [n=seb128@ubuntu/member/seb128]  has joined #ubuntu-x
[10:05] <ubotu> New bug: #149304 in xorg (main) "Use of "next" instead of "continue" in bash script failsafeXServer" [Undecided,New]  https://launchpad.net/bugs/149304
=== mvo_ [n=egon@p54A65B9A.dip.t-dialin.net]  has joined #ubuntu-x
[12:40] <ubotu> New bug: #149367 in xrandr (main) "plug my HD tv makes xrandr display wrong resolution for my active screen" [Undecided,New]  https://launchpad.net/bugs/149367
[01:01] <ubotu> New bug: #149377 in xrandr (main) "window title stuck where gnome panel was if moved while using dual head with xrandr " [Undecided,New]  https://launchpad.net/bugs/149377
=== seb128 [n=seb128@ubuntu/member/seb128]  has joined #ubuntu-x
[03:10] <ubotu> New bug: #138079 in dell "Dell Inspiron 1520 nVidia 8600M GT doesn't work" [Medium,Confirmed]  https://launchpad.net/bugs/138079
[03:45] <ubotu> New bug: #149430 in xserver-xorg-video-intel (main) "No DMPS on DVI port of ADD2 card" [Undecided,New]  https://launchpad.net/bugs/149430
=== seb128 [n=seb128@ubuntu/member/seb128]  has joined #ubuntu-x
[06:03] <ubotu> New bug: #149490 in xserver-xorg-video-intel (main) "X crashes on suspend" [Undecided,New]  https://launchpad.net/bugs/149490
[07:25] <ubotu> New bug: #97637 in compiz (main) "Beryl/Emerald won't allow gnome-screensaver screen-unlock dialog to have input focus (dup-of: 122549)" [Undecided,New]  https://launchpad.net/bugs/97637
=== tormod [n=tormod@80-219-112-71.dclient.hispeed.ch]  has joined #ubuntu-x
[08:50] <tepsipakki> tormod: looks like there is going to be a new -ati this weekend :)
[08:50] <tormod> the 6.7.195?
[08:51] <tepsipakki> probably yes, since pci-rework isn't complete yet afaik
[08:52] <tormod> will you push it into Gutsy as soon as it is out?
[08:53] <tepsipakki> well, I asked someone to take a look at the debdiff of a merger with your package, but apparently it had too many changes already..
[08:53] <tormod> but all the changes are good :)
[08:53] <tepsipakki> so, why not upload a version with a subset of them
[08:53] <tepsipakki> I know :)
[08:54] <tepsipakki> but then the delta between a shipping driver and the new upstream would be smaller :)
[08:54] <tepsipakki> cunning plan, eh? :)
[08:54] <tormod> wicked :)
[08:55] <tormod> but many of alex's commits depend on each other
[08:55] <tepsipakki> true..
[08:56] <tormod> those you asked, did they see a debdiff between 194-1ubuntu1 and -tv6 ?
[08:58] <tepsipakki> basically, yes
[08:59] <tepsipakki> http://users.tkk.fi/~tjaalton/dpkg/ati/ati.debdiff
[09:01] <tormod> if the fixed bugs would be triaged properly with high,important etc it would maybe be easier to slip it through the release managers?
[09:01] <tormod> X not starting is pretty critical. But I don't have the triaging magic power.
[09:02] <tepsipakki> you should join ubuntu-bugs then :)
[09:09] <tormod> qa-team? that sounds like... work :)
[09:10] <tormod> seems like many people have tested the -tv6 and are happy. maybe we should make a list of hardware tested?
[09:11] <tepsipakki> actually, bugsquad is the team name I think
[09:11] <tormod> I think it would be scandalous to release gutsy with the current gutsy ati, especially when fixes are available.
[09:11] <tepsipakki> I agree
[09:13] <tepsipakki> but, the freeze is not yet effective, so _technically it could be uploaded :)
[09:13] <tormod> when's the freeze
[09:14] <tepsipakki> later today..
[09:14] <tepsipakki> bryce: ping?
[09:14] <bryce> hi tepsipakki
[09:15] <tepsipakki> bryce: hi, we were just discussing the ati situation
=== bryce nods
=== bryce reads backlog
[09:15] <bryce> sorry, was caught up in email discussion about agenda items for uds
[09:15] <tormod> we could take out the "remove cruft and dead code" commits, if that would help some release manager
[09:16] <bryce> if you point me at bugs, I can take care of marking them triaged/high/-rc candidates, etc.
[09:16] <tepsipakki> me too
[09:16] <tepsipakki> I have the list in front of me
[09:17] <bryce> tepsipakki: who did you talk to that said the delta was too much?
[09:17] <tepsipakki> if we mark all the "fix committed" bugs as high/critical and milestone rc?
[09:17] <tepsipakki> bryce: mdz, but he didn't say it quite like that.. a sec
[09:18] <bryce> the angle I've been working is to demonstrate it fixes 86072.  James Troup is the guy in charge of all of Canonical's IT infrastructure
[09:18] <bryce> so if the newest -ati solves his problem, it gives us a LOT of weight
[09:18] <tepsipakki> 17:43 < mdz> tepsipakki: I won't speak for the release team, but "works for someone" is not  very compelling.  wouldn't you prefer to upload something better tested after  release, rather than pushing in something less tested before release?
[09:19] <bryce> ah
[09:19] <tepsipakki> bryce: I think it does fix that
[09:19] <bryce> yeah sounds like we just need to tighten up our story a bit, with good evidence of proven things it fixes, etc.
[09:19] <bryce> ideally, associating each change with a specific high priority bug would help
[09:20] <tepsipakki> yes, I didn't do that.. easily fixed
[09:21] <bryce> I've been taking that approach with some of my other changes.  sort of a PITA, but reviewers are getting more strict, so I find it helps a lot
[09:21] <bryce> in any case, the extra triaging work helps clear more bugz :-)
[09:21] <tepsipakki> sure. I did point out those three "fix committed" bugs which all had the same issue; no X
[09:22] <tormod> could we work out this together on a wiki page or using gobby?
[09:22] <tepsipakki> heck, I'll mark those as critical :)
[09:22] <bryce> no, let's save critical for nuclear bomb situations... High should be sufficient
[09:23] <tepsipakki> hrm, ok :)
[09:23] <tormod> critical is only for bugs reaching a good portion of the users.
[09:23] <tepsipakki> right
[09:28] <bryce> also at some point here, maybe next week, we should go through the whole xserver-xorg-video-ati bug list and close out all the ones that are fixed now, and ask folks to re-test the ones we're not sure about
=== kylem [n=kyle@amnesiac.heapspace.net]  has left #ubuntu-x [] 
[09:30] <bryce> (unless you feel it's all already covered - but I think a top-to-bottom review focused on -ati could be a big help going into Hardy since so much has changed.)
[09:32] <tepsipakki> absolutely
[09:32] <tepsipakki> I've now marked those bugs we talked about as high
[09:38] <tepsipakki> bryce: so, do you think we could upload 194-1ubuntu2 with fixes for these bugs, or wait for .195 and file a FFe request?
[09:38] <tepsipakki> or do both
[09:39] <bryce> tepsipakki: I think your strategy of uploading an intermediate, to make the delta between it and the release smaller, is quite wise
[09:39] <bryce> it'll also help for testing
[09:44] <bryce> so, for Hardy it sounds like the focus will be for "shoring up old features"
[09:46] <bryce> colin says that in our past releases, sometimes features were completed for the release, and folks moved on; some of those features need additional polish or rework based on findings since then
[09:46] <tepsipakki> bryce: ok, I'll re-merge and upload then :)
[09:46] <bryce> for X, really the only thing that came up was discover-data
[09:47] <bryce> what I've proposed doing for Hardy is for us to extract the pci id list from discover-data, so discover can finally be dropped entirely
[09:47] <tepsipakki> upstream&debian are going to do that from the drivers
[09:47] <bryce> I think we still need something like the pci id list, in order to do overrides, but in general I think we can rely more on X to autodetect stuff, and try to minimize the size of it
[09:48] <tepsipakki> what about new upstream versions, any chance of xserver-1.5?
[09:48] <tepsipakki> scheduled for February I think
[09:49] <bryce> the discussion was focused only on ubuntu-specific things
[09:49] <bryce> well, definitely definitely 1.4 of course
[09:49] <tepsipakki> ah
[09:50] <bryce> since Hardy is a LTS, I'm a bit iffy on putting in 1.5 at the last minute
[09:51] <tepsipakki> is it going to be LTS right from the start, or later (like 8.04.1 or so)
[09:51] <tepsipakki> ?
[09:51] <bryce> on the other hand, I'm a lot more comfortable with what the process is now, so if we have to do it, it scares me less than 1.4 for gutsy
[09:51] <bryce> I assume from the start
[09:51] <tepsipakki> ok
[09:53] <tormod> tepsipakki: by "re-merge" do you mean you will take out some patches?
=== tehk [n=tehk@c-69-249-157-157.hsd1.nj.comcast.net]  has joined #ubuntu-x
[09:54] <tepsipakki> tormod: yes..
[09:55] <tormod> which ones?
[09:56] <tepsipakki> I guess only 02 and 04 can be safely removed?
[09:56] <tepsipakki> haven't tried
[10:02] <tormod> and the "cruft" part of 09
[10:03] <tepsipakki> well, 02 needs to be there, otherwise 03 won't apply
[10:04] <tormod> are you sure 02 can be removed .ok
[10:04] <tepsipakki> can't be removed
[10:04] <tormod> it's basically one piece of work, that Alex commited bitwise.
[10:06] <tepsipakki> the cruft part of 09 is self-explanatory, so that can stay IMHO
[10:06] <tormod> we could do 08 separately/later but that would just be kind of ridiculous.
[10:06] <tepsipakki> 04 is big though
[10:06] <tepsipakki> right
[10:08] <tormod> 04 is big in lines, but it's removing an unused function...
[10:08] <tepsipakki> I was just coming to that :)
[10:08] <tormod> (two unused functions)
[10:09] <tormod> the question is if the release managers have put on their "manager" hats :)
[10:17] <tepsipakki> well, if the idea was to upload this intermediate version first then they need not to bother.. :)
[10:19] <tepsipakki> ok, new debdiff with bug-closers (?) http://users.tkk.fi/~tjaalton/dpkg/ati/ati.debdiff
[10:22] <tepsipakki> now tv for awhile->
[10:23] <tormod> tepsipakki: so same patches, but with LP links?
[10:25] <tormod>  /(LP: #86072. #144011)/s/./,  (if that matter, not sure)
[10:42] <tepsipakki> oh, right
[10:42] <bryce> too bad we don't have more LP ID's
[10:43] <tepsipakki> well, bug #139241 should be easy :)
[10:43] <ubotu> Launchpad bug 139241 in xserver-xorg-video-ati "DRI hangs on radeon Xpress 200M [1002:5975] " [High,Confirmed]  https://launchpad.net/bugs/139241
[10:44] <bryce> I might suggest rephrasing things a little, so that for instance if patch 02 is a pre-req for another patch that fixes a LP issue, to describe it as "pre-requisite for patch X, which fixes LP NNN"
[10:45] <tepsipakki> sounds good
=== tehk [n=tehk@c-69-249-157-157.hsd1.nj.comcast.net]  has joined #ubuntu-x
[10:59] <tepsipakki> I think bug 141547 is another candidate that this version should fix
[10:59] <ubotu> Launchpad bug 141547 in xserver-xorg-video-ati "[Gutsy]  after ati driver update, only a black screen (light is on)" [Undecided,Incomplete]  https://launchpad.net/bugs/141547
[11:00] <tepsipakki> oh, that's fixed already
[11:00] <tormod> 139241 needs a patch though
[11:00] <tepsipakki> yep
[11:03] <tepsipakki> that's also a big strange, since I think he had a different card when he reported that
[11:12] <tormod> I think the pci id list has changed in between
[11:12] <tepsipakki> RS482 is 10025974, RS485 is 10025975 :)
[11:12] <tormod> are you sure?
[11:13] <tepsipakki> yes
[11:13] <tepsipakki> looking at current discover-data
[11:13] <tormod> I saw the same in another bug
[11:16] <tormod> bug #144760 also made me pretty confused with pci ids
[11:16] <ubotu> Launchpad bug 144760 in xorg "compiz/DRI crashes on Xpress200M/AMD64 [1002:5975]  (dup-of: 139241)" [Undecided,Confirmed]  https://launchpad.net/bugs/144760
[11:16] <ubotu> Launchpad bug 139241 in xserver-xorg-video-ati "DRI hangs on radeon Xpress 200M [1002:5975] " [High,Confirmed]  https://launchpad.net/bugs/139241
[11:18] <tepsipakki> ah, ok
[11:18] <tormod> http://launchpadlibrarian.net/9504887/vvnn clearly shows 482=5975 at the time
[11:18] <tepsipakki> yes, maybe that has been since fixed
[11:19] <tepsipakki> so it really is 485
[11:19] <tormod> yes I guess so
[11:19] <tormod> I try to put the confirmed pci id in the summary when I can
[11:21] <tormod> however in the driver source you'll find PCI_CHIP_RS482_5975 !
[11:23] <tepsipakki> lovely
[11:35] <bryce> http://people.ubuntu.com/~brian/testing_graphs/xserver-xorg-video-ati.html - nice to see the big drop over the past week
[11:39] <tormod> tepsipakki: you saw my upstream bug for 139241?
[11:39] <tormod> bryce: yes, I take some of the honour :)
[11:40] <tepsipakki> tormod: yes, that patch should do it?
[11:40] <tormod> tepsipakki: yes it looks simple enough
[11:41] <tormod> tepsipakki: you could ask upstream anyway, why they haven't committed it?
[11:41] <tepsipakki> hmm, alex is not online
[11:45] <tormod> tepsipakki: maybe because there was no upstream reports about RS485
[11:46] <tepsipakki> but that's the one :)
[11:47] <tepsipakki> you just said that the source lists both 5974 and 5975 as RS482
[11:47] <tepsipakki> when in fact 5975 should be RS485
[11:51] <tormod> the source just uses it as macros
[11:52] <tormod> it will report them as ATI Radeon XPRESS 200 5974 (PCIE) and  ATI Radeon XPRESS 200M 5975 (PCIE)
[11:59] <tormod> nobody complained about 5974, so I guess 5974 cards work and 5975 cards fail. Probably all "mobility" versions fail.
[11:59] <tepsipakki> ok
[12:02] <bryce> tormod yes good work!  :-)
[12:02] <tepsipakki> but the point was that 5975 is RS485, and 5974 is RS482 :) so, the source should be updated to reflect that like the current pci-ids :)
[12:02] <tepsipakki> but that's not important now
[12:03] <tepsipakki> I'll mention that in the changelog though..