[01:01] <ubotu> New bug: #48113 in xserver-xorg-video-i810 (main) "X blank after startup" [Medium,Invalid] https://launchpad.net/bugs/48113
[01:01] <ubotu> New bug: #156021 in xorg (main) "Gutsy-Upgrade-or-Live-CD: Resolution Bug with a Matrox Millenium G450 (Dualhead) Graficcard" [Undecided,New] https://launchpad.net/bugs/156021
[10:44] <ubotu> New bug: #155326 in xorg (main) "xorg crash" [Undecided,New] https://launchpad.net/bugs/155326
[10:52] <ubotu> New bug: #156138 in xorg (main) "x.org doesn't start while installation on DELL Latitude D830" [Undecided,New] https://launchpad.net/bugs/156138
[11:06] <ubotu> New bug: #155555 in xorg (main) "xorg uses large ammounts of CPU, and framerate becomes choppy" [Undecided,New] https://launchpad.net/bugs/155555
[11:41] <ubotu> New bug: #54680 in linux-restricted-modules-2.6.15 (restricted) "Dual Head gives square cursor (or "SWCursor" crashes gnome)" [Undecided,New] https://launchpad.net/bugs/54680
[12:36] <ubotu> New bug: #150054 in xserver-xorg-driver-ati (restricted) "ati restricted suggested for radeon 2600 - does not work (X crashes - vesa at least worked)" [Undecided,New] https://launchpad.net/bugs/150054
[14:50] <ubotu> New bug: #156042 in ubuntu "amd xorg driver not detected for Geode LX video controller (dup-of: 140051)" [Undecided,New] https://launchpad.net/bugs/156042
[15:59] <_jz> hi there
[15:59] <_jz> so far: 4 hours with feisty's xserver-xorg and xserver-xorg-video-ati packages and no freeze !
[16:00] <_jz> but dependancy hell i might need help with :) (how to make gutsy believe these are the right packages for me ?)
[16:14] <tepsipakki> _jz: you managed to install them anyway?
[16:14] <_jz> yes !
[16:14] <_jz> dpkg -i ! didn't even need to --force-all %)
[16:14] <tepsipakki> so where is the problem?-)
[16:15] <_jz> the problem is now when i try to install anything i got http://pastebin.com/d33b08eb
[16:16] <tepsipakki> so only downgrading ati didn't help?
[16:16] <_jz> arg i didn't try :/
[16:16] <_jz> i began with xserver-xorg
[16:17] <tepsipakki> upgrade the server
[16:17] <_jz> and when trying to launch it, it told me undefined symbol in blahbla radeon, which made me think of geting -ati too ;)
[16:17] <_jz> but what about the fact that mergefb doesn't work anymore ? 
[16:18] <_jz> i now use my old config with mergedfb again
[16:18] <tepsipakki> forget mergedfb
[16:18] <tepsipakki> it's dead
[16:18] <_jz> hmm ok  :)
[16:18] <_jz> i upgraded, let's see at the next login
[16:19] <_jz> wow no.. shit hits the fan :/
[16:21] <_jz> ok. Setting up xserver-xorg-core (2:1.3.0.0.dfsg-12ubuntu8) ... Setting up xserver-xorg (1:7.2-5ubuntu13) ...
[16:43] <ubotu> New bug: #156203 in linux-restricted-modules-2.6.22 (restricted) "New upstream madwifi release (9.3.3) fixes DoS attack" [Undecided,New] https://launchpad.net/bugs/156203
[16:46] <tepsipakki> bryce: I'll file a sync-request for a lot of packages
[17:00] <tepsipakki> ..but it would be stupid to push at this moment, before the new server
[17:00] <tepsipakki> since they'd need to be reuploaded
[17:10]  * bryce nods
[17:11] <tepsipakki> bug 156298
[17:11] <ubotu> Launchpad bug 156298 in xorg "please sync from Debian" [Undecided,New] https://launchpad.net/bugs/156298
[17:15] <ubotu> New bug: #156298 in xorg (main) "please sync from Debian" [Undecided,New] https://launchpad.net/bugs/156298
[17:15] <tepsipakki> I'll heh
[17:15] <tepsipakki> hum?
[17:15] <tepsipakki> "I'll" something
[17:17] <tepsipakki> ..be gone, for instance
[17:17] <tepsipakki> bbl
[17:18] <bryce> I wonder if MoM has been turned back on yet
[17:18] <tepsipakki> it has
[17:19] <tepsipakki> but I was looking at DaD :)
[17:19] <tepsipakki> another try ->
=== seb128_ is now known as seb128
[19:38] <ubotu> New bug: #156325 in linux-restricted-modules-2.6.22 (restricted) "New fglrx 8.42.3 to Gutsy" [Undecided,New] https://launchpad.net/bugs/156325
[19:46] <ubotu> New bug: #147372 in ubuntu "ATI Radeon x1300 not working in Gutsy (dup-of: 132716)" [Undecided,New] https://launchpad.net/bugs/147372
[19:46] <ubotu> New bug: #154130 in fglrx-driver "Auto install of fglrx 'restricted' driver results in non working system (dup-of: 132716)" [Undecided,New] https://launchpad.net/bugs/154130
[19:46] <ubotu> New bug: #154820 in fglrx-driver "[Gutsy]Random Black Screen while loading GDM (dup-of: 132716)" [Undecided,Confirmed] https://launchpad.net/bugs/154820
[20:31] <tepsipakki> bryce: hmm, are you sure 147372 is a dupe of 132716?
[20:31] <bryce> not 100%; please undupe if you think it's incorrect
[20:32] <tepsipakki> I'd close 147372 as won't fix, since he's basically asking for enabling fglrx by default
[20:32] <tepsipakki> maybe you got the dupe number wrong :)
[20:33] <tepsipakki> btw, do you think I should upload the server even though input-hotplug has issues right now?
[20:33] <tepsipakki> and the new hal exposes them
[20:35] <tepsipakki> see debian bug 442316
[20:35] <ubotu> Debian bug 442316 in xserver-xorg-input-evdev "xserver-xorg-input-evdev: evdev from experimental messes up my keyboard layout" [Grave,Open] http://bugs.debian.org/442316
[20:38] <bryce> lemme look
[20:39] <bryce> hmm, it's marked grave; that sounds bad
[20:39] <bryce> in general, at this early stage I feel we do need to "break a few eggs to make the cake"
[20:39] <tepsipakki> heh, true
[20:40] <bryce> on the other hand, for hardy it'd be nice if we could be attentive to avoid putting in stuff we already know have serious issues
[20:41] <bryce> I guess the question is, assuming this will get fixed in good time, will this problem inhibit other ubuntu developers from doing work on hardy?
[20:41] <tepsipakki> they don't need to upgrade
[20:42] <tepsipakki> :)
[20:42] <bryce> heh
[20:42] <tepsipakki> or just let them know what it might do
[20:42] <tepsipakki> mail ubuntu-devel or something
[20:42] <tepsipakki> anyway, I'll test that first
[20:42] <bryce> sure
[20:43] <bryce> as long as there is a workaround or manual solution, I think it's probably fine
[20:43] <tepsipakki> besides, the last comment by daniels makes me feel like it's "just" a configuration issue
[20:44] <bryce> yeah
[20:45] <bryce> maybe we can put a hardcoded workaround into dexconf or something
[20:45] <tepsipakki> it ignores xorg.conf completely, so that wouldn't work :)
[20:46] <bryce> btw, I've updated http://wiki.ubuntu.com/X/Projects a bit
[20:46] <bryce> erf
[20:46] <tepsipakki> at least that's how I understood it
[20:49] <tepsipakki> if it really is b0rked, then a simple hal upload would fix it for now
[20:50] <tepsipakki> just keep the file somewhere else so that it can be easily debugged
[20:50] <tepsipakki> if needed
[20:50] <tepsipakki> anyway, I'll upgrade my laptop now :)
[20:50] <bryce> I guess the main thing we need to avoid is causing major breakage for everyone here before UDS
[20:51] <bryce> since after all, we'll be in slapping distance of everyone in a week
[20:51] <bryce> after UDS... ppffft, they can suffer
[20:51] <bryce> ;-)
[20:51] <tepsipakki> hehe
[20:51] <bryce> of course, xserver 1.4.1 comes out in november, so worst case we could put things off until that
[20:56] <tepsipakki> nah, I think that mbiebl (the debian hal maintainer) will remove the fdi for now, so it shouldn't break anything after that (knocks on wood..)
[21:25] <tepsipakki> uh, x11proto-render needs to be updated for xserver to build
[21:25] <tepsipakki> =synced, not going to happen today
[21:25] <bryce> oops
[21:25] <tepsipakki> I'll build it locally
[21:25]  * bryce nods
[21:26] <bryce> I've updated this merge status page for hardy http://people.ubuntu.com/~bryce/Xorg/versions_current.html
[21:26] <ubotu> New bug: #35824 in xkeyboard-config (main) "Keyboard Layout options: The "X86AudioRaiseVolume" button stopped working in Logitech keyboard models" [Medium,Confirmed] https://launchpad.net/bugs/35824
[21:28] <tepsipakki> ah, right.. I've forgot universe (where those input-drivers are)
[22:04] <bryce> heya pcjc2 and tormod
[22:04] <pcjc2> hi
[22:04] <tormod> hi bryce, why are you duping all these fglrx bugs onto poor 132716?
[22:05] <bryce> two were dupes of each other; sounded like one of those was duping 1327716 so moved both to that
[22:05] <tormod> aha, just saw you unduped one also :)
[22:05] <bryce> I could be wrong though; I didn't review them very closely
[22:06] <bryce> they had all been filed against 'driver-fglrx' so they needed moved
[22:07] <bryce> I saw they involved blank screen, so figured they were the same bug; feel free to de-dupe if not, but make sure to list them against l-r-m instead of fglrx-driver
[22:07] <pcjc2> I'm just (painfully slowly) moving backup data of my new laptop HDD, and will try the Gutsy install CD oon
[22:08] <pcjc2> I want to see if I can reproduce the console problems people have experienced with some intel cards. (I know I tried to reproduce a bug for someone who was using intel-fb and couldn't get any console output
[22:11] <bryce> awesome!  I've also noticed you're doing some good bug triaging on -intel
[22:14] <pcjc2> There is a surprising amount of work
[22:14] <pcjc2> seems like there are lots of mis-probed resolution issues dotted about
[22:15]  * bryce nods
[22:15] <bryce> we did a ton of work on resolution issues in Gutsy, so any of those that haven't been tested on gutsy-final should be tested against that first
[22:15] <pcjc2> I heard rumours of a 2.1.2 driver being released at some point
[22:16] <bryce> I've not heard anything official
[22:16] <pcjc2> nothing official of course
[22:16] <bryce> however Jesse told me that at Intel they made the decision to put out a driver update quarterly
[22:16] <pcjc2> Mandriva have this patch, which we don't.. http://svn.mandriva.com/cgi-bin/viewvc.cgi/packages/cooker/x11-driver-video-intel/current/SOURCES/x11-driver-video-i810-vt_fix.patch?revision=15186&view=markup
[22:17] <pcjc2> related to VT switching. I'm trying to chase what it was supposed to fix
[22:17] <pcjc2> http://svn.mandriva.com/cgi-bin/viewvc.cgi/packages/cooker/x11-driver-video-intel/current/SOURCES/
[22:17] <pcjc2> You'll see that they also have something about mode-probing and the G33 issue (possibly kernel specific though?)
[22:18] <bryce> is there a bug id associated with that, or something to give some background of what issue it solves?
[22:18] <bryce> interesting; yeah I added to the projects list that we should go through mandriva's patches and snarf up anything that looks useful
[22:18] <pcjc2> there wasn't unfortunately, the changelog entry just says: "prevents the driver from doing operations when we do not have the VT lock"
[22:19] <bryce> hmm
[22:19] <pcjc2> I've emailed the person who committed it to see if he remembers (at the suggestion of Colin Guthrie at Mandriva)
[22:19] <bryce> cool
[22:20] <pcjc2> Sounds like they're continuing to ship the i810 driver due to some old 845 hardware which doesn't play nice. (He linked me some of the bugs). Mostly they're about mode detection, or black screen
[22:20] <pcjc2> sounds like you just commented on one
[22:22] <pcjc2> My neighbour is excited about the new ATI driver out
[22:22] <bryce> heh, my friend scislac is as well
[22:22] <pcjc2> apparently the old one broke suspend / resume with the Gutsy kernel due to the memory allocator changes
[22:23] <tormod> "ATI" as in "fglrx" I suppose?
[22:23] <pcjc2> I think so. Will it get backported?
[22:23] <bryce> maybe; I listed that as a task for us, but I don't know if it's feasible to put l-r-m changes in to -backports.  tormod or tepsipakki, do you know?
[22:23] <tormod> maybe, but first it has to sit in Hardy for a while?
[22:24] <tormod> and ferment...
[22:24] <tepsipakki> tormod: well, those are kernel version dependant, so not really
[22:24] <tepsipakki> I haven't seen a l-r-m update before :)
[22:24] <pcjc2> I guess  this is a down-side to having lots of packages all togeher in l-u-m or the kernel its self
[22:24] <tormod> it's the downside of restricted software :)
[22:25] <tepsipakki> bryce: subscribed ubuntu-x as bugmail contact for pixman (a build req for xserver >=1.4)
[22:25] <bryce> cool
[22:25] <pcjc2> Sounds like a quarterly release of the Intel driver will be handy...
[22:25] <tepsipakki> that needs an update as well, but it'll get autosynced
[22:26] <tepsipakki> pixman that is
[22:26] <pcjc2> What are policies like on using git versions from upstream?
[22:26] <tepsipakki> duh, I thought libpixman-0.1.6 got removed already
[22:27] <pcjc2> (I went over the logs for the Intel driver, there are _lots_ of changes, lots of fixes, and if I had 965 HW, I suspect I'd be building that to see if it fixes any of the issues)
[22:31] <bryce> tepsipakki: do you mean for debian?  I don't think it got removed for ubuntu
[22:33] <tepsipakki> no ubuntu. I filed a sync-request back in august for pixman, and also asked for libpixman to be removed, but I guess they should have been separate bugs :)
[22:33] <bryce> ahh
[22:34] <tepsipakki> actually, pixman got through NEW
[22:34] <tepsipakki> xorg-server build about to commence..
=== pcjc3 is now known as pcjc2_
[22:37] <pcjc2_> now to take pointy screwdriver to under side of laptop.. (Just finished clearing the disk, and have burned the gutsy CD)
[22:52] <bryce> an inkscape buddie of mine pimped up our logo a bit - https://launchpad.net/~ubuntu-x-swat
[22:55] <pcjc2_> I wish I had artistic talent
[22:58] <pcjc2_> The installer is nice ;).. I installed at Feisty-1 (can't remember which that was), and used the text installer
[23:16] <pcjc2_> shiney... it set up the frame buffer console better than I ever managed
[23:18] <tepsipakki> tormod: I've merged savage, because I need to build it for my laptop :)
[23:18] <tormod> there's a new one out?
[23:19] <tormod> or from git?
[23:19] <tepsipakki> yes, 2.1.3
[23:19] <tepsipakki> your patch is newer than that
[23:20] <tormod> oh yes, we have 2.1.2 in UBuntu, but it's patched up to or beyond 2.1.3 I think :)
[23:20] <tepsipakki> nah, that was the only patch
[23:22] <tormod> I see. I guess the rest was not so interesting at that time. What did you need for your laptop?
[23:22] <tepsipakki> I'm testing xserver-1.4
[23:22] <tormod> do you also have an AGP card?
[23:22] <tormod> cool, do you have any xserver-1.4 packages out there?
[23:23] <tepsipakki> yes, I'll put them somewhere when I've done some testing first
[23:23] <tormod> I guess I can just recompile 1.4 from Debian...
[23:23] <tepsipakki> yeah
[23:23] <tormod> but debs would be nice, for general consumption
[23:24] <tormod> do you also have agp freeze after resume?
[23:24] <tepsipakki> with savage? no
[23:25] <tormod> how unfair :) what card do you have?
[23:26] <tepsipakki> it's a thinkpad T23 with supersavage IX/C SDR
[23:27] <tepsipakki> and a hefty 8Mb of videoram
[23:27] <tepsipakki> ie. no DRI :)
[23:27] <tormod> ok that explain things.
[23:28] <tormod> I have a luxurious 16MB (stolen from system RAM) and can play tuxracer on my TwisterK.
[23:28] <tormod> did you upload your new savage to Hardy?
[23:30] <tepsipakki> no, makes sense to put all driver updates on hold until 1.4 is in
[23:40] <bryce> ok, got the last of the New -intel bugs triaged; we're at 0 finally :-)
[23:43] <tormod> tepsipakki: ok I understand. I'll wait impatiently for 1.4 :)
[23:43] <tormod> bryce: \o/
[23:45] <tepsipakki> now running 1.4 with us keymap :)
[23:47] <tormod> I have 1.4 on my debian partition and it works fine: actually everything GUI is much faster on Debian, Can it be the gtk themes and all that stuff that makes ubuntu slower? 
[23:47] <tormod> faster like in snappier
[23:47] <bryce> doubtful
[23:48] <tormod> it's full gnome in Debian also, but maybe without n-m and deskbar applet etc.
[23:49] <tormod> can it be 1.4 vs 1.3? I think Debian was snappier than Ubuntu even when both had 1.3.
[23:49] <bryce> hmm
[23:49] <bryce> or it could be a driver difference I guess...
[23:50] <tormod> no, the savage driver is pretty much the same.
[23:50] <bryce> hmm
[23:50] <bryce> maybe one of the ubuntu-only patches we carry in the xserver?
[23:51] <bryce> are both using xaa?  exa might make a difference
[23:51] <tormod> it's a 1Ghz 256-16 laptop, so I really get to see the nuances that many spoiled people does not see.
[23:51] <bryce> might be interesting to diff the Xorg.0.log to see if anything pops out
[23:52] <bryce> of course it could also be kernel differences I guess
[23:52] <tormod> good idea. I'll compare the logs. kernel? I have tried 2.6.23.1 on Gutsy without too much difference.
[23:53]  * bryce crosses out an item on https://wiki.ubuntu.com/X
[23:53] <bryce> er, ...X/Projects
[23:53] <tormod> though it was compiled with the Ubuntu config, so if there's a CONF_RUN_SLOW :)
[23:54] <bryce> also, if you really suspect it's a theme (which it certainly could be), then might be interesting to try switching it
[23:54] <tormod> that sounds like a logical way of finding out. will do (another day).
[23:55] <bryce> hmm, since it's a laptop, you could also check the cpufreq setting; I noticed on one of my laptops that it runs at 50% (maybe just when on battery?)
[23:55] <bryce> I've always found that laptop less "snappy" than my desktop, but I think it's more due to disk IO sluggishness (but not sure why)
[23:55] <tormod> I'll double-check.
[23:56] <tormod> Yes, my laptop got much faster when I replaced the cheap, crap Toshiba disk with a newer Samsung
[23:56] <tormod> and a lot quieter....
[23:57] <tormod> so I should check hdparm -Tt in Debian vs Ubuntu as well.