[00:00] <bryce> tormod, tjaalton_: either of you think it'd be a problem if we left MODEDEBUG on by default in the release?
[00:01] <tormod> bryce, that's intel only right?
[00:01] <bryce> it's an xserver option
[00:04] <bryce> tormod, googleearth-package sponsored
[00:05] <tormod> like the ModeDebug in xorg.conf then, I remember intel was doing something on its own there
[00:05] <tormod> bryce, great, for my proprietary sins
[00:05] <bryce> pretty sure it's the same option throughout, but Intel does insist on it being set more than other driver upstreams do
[00:11] <tormod> bryce, don't forget to do the bzr merge of the googleearth-package
[00:12] <bryce> bryce@chideok:~/src/googleearth-package/karmic-bugs2$ bzr merge 
[00:12] <bryce> Merging from remembered parent location bzr+ssh://bazaar.launchpad.net/~tormodvolden/ubuntu/karmic/googleearth-package/karmic-bugs2/
[00:12] <bryce> Nothing to do.     
[00:59] <tormod> bryce, oh I thought you had to push to lp:ubuntu/googleearth-package but that's maybe auto-updated?
[01:03] <wgrant> Since I upgraded this morning, the framerate appears to get really low once Compiz is running. With Metacity 3D stuff is fine. GM45, was using xorg-edgers' PPA, but it happens even without it.
[01:04] <wgrant> "really low" meaning that I see lag while typing.
[01:18] <wgrant> -intel 2.8.1 is good... now to try intermediate xorg-edgers versions...
[01:24] <bryce> wgrant, "upgraded" == to karmic or to latest xorg-edgers?
[01:25] <bryce> $ bzr push lp:ubuntu/googleearth-package
[01:25] <bryce> bzr: ERROR: Cannot lock LockDir(lp-46082192:///~ubuntu-branches/ubuntu/karmic/googleearth-package/karmic/.bzr/branchlock): Transport operation not possible: readonly transport 
[01:26] <wgrant> bryce: Upgraded to latest karmic xorg-edgers. Was previously a couple of days behind.
[01:26] <wgrant> I then removed xorg-edgers, and it still happened.
[01:26] <wgrant> I downgraded to -intel 2.8.1, and the problem went away.
[01:27] <wgrant> Then re-upgraded to 2.9.0, and the problem is still gone.
[01:27] <wgrant> Maybe the previous 2.9.0 installation got broken when X died half way through.
[01:27] <wgrant> bryce: You can't write to distro branches yet.
[01:27] <wgrant> bryce: They are the exclusive domain of james_w's robot at the moment.
[01:27] <bryce> okie
[01:28] <bryce> wgrant, I would bet the regression was more due to mesa or libdrm (or the kernel) than to the ddx -intel driver
[01:29] <wgrant> bryce: That was what I initially suspected, but mesa/libdrm was all from xorg-edgers at the time, and the problem remained once I downgraded to the karmic versions.
[01:29] <bryce> any diff in your Xorg.0.log or glxinfo between the working and broken cases?
[01:31] <wgrant> I don't have the Xorg.0.log from the broken cases, as I presumed I'd be able to reproduce it.
[01:31] <wgrant> Sadly not.
[07:32] <tjaalton_> bryce: ok great, xserver looks fine. modedebug can stay on, since it's only helpful, and a few (hundred?) extra lines on the logfile is not that bad
=== tjaalton_ is now known as tjaalton
[09:57] <eagles0513875> hey guys
[09:58] <eagles0513875> i have a question is the nvidia driver going ot be upgraded for karmic as im starting to notice people having alot of random issues such as consoles and in alpha 5 i had no x starting 
[10:13] <tjaalton> updated to what? it's the latest stable version aiui
[10:25] <eagles0513875> the latest version from nvidia
[11:05] <superm1> kees, i think this execstack stuff is killing my install
[11:05] <superm1> this machine has fglrx and just did an apt upgrade and bumped to 8.660-0ubuntu3, the box was unusably slow
[11:05] <superm1> downgraded to 8.660-0ubuntu2 and it was usable again
[11:12] <tormod> superm1, maybe you should try the open-source driver :P
[11:13] <superm1> tormod, on a radeon HD 3450?  I don't think this card would be nearly as usable
[11:14] <tormod> superm1, it's getting there, 2D should work fine, 3D might work
[11:14] <superm1> tormod, yeah 2D is fine, but I need 3D, so that's a negatory.
[11:16] <superm1> kees, here's a bug for it: bug 447901
[11:16] <ubottu> Launchpad bug 447901 in fglrx-installer "execstack is causing fglrx to be unusably slow" [Undecided,New] https://launchpad.net/bugs/447901
[11:35] <tjaalton> eagles0513875: that's beta, so no
[11:37] <tormod> tjaalton, jcristau: I think the Section's in libdrm/debian/control could need some love
[11:47] <tjaalton> tormod: which ones?
[11:47] <tjaalton> nouveau is all ours
[11:48] <tormod> yes libdrm-nouveau1-dbg, and libdrm-radeon1
[11:52] <tjaalton> they both are only on our package
[11:52] <tjaalton> too scary?
[11:59] <tormod> right, the Debian version is fine
[12:06] <albert23> tormod: are you aware of bug 447181 and bug 447427? The loss of UMS in xorg-edgers on jaunty seems to cause problems.
[12:06] <ubottu> Launchpad bug 447181 in xserver-xorg-video-intel "Video driver error: No kernel modesetting driver detected" [Undecided,New] https://launchpad.net/bugs/447181
[12:06] <ubottu> Launchpad bug 447427 in xserver-xorg-video-intel "[i945] No screens found / none have usable configuration on Intel 945GM" [Undecided,New] https://launchpad.net/bugs/447427
[12:09] <tormod> albert23, thanks, I was wondering if there would be people running it with old kernels :)
[12:10] <albert23> I guess it's a preview of what we may see with hardy -> lynx updates next year
[12:28] <tormod> albert23, I could add a /etc/modprobe.d/i915-kms.conf to the -intel package, but maybe it is more educational to leave that to the user
[12:31] <albert23> tormod: yeah, maybe just a warning on the ppa page that KMS is now mandatory would be good
[12:35] <tormod> albert23, good idea
[13:52] <eagles0513875> tjaalton: that isnt beta btw from the nvidia site there is a newer version of the driver out  and it seems like im seeing more and more people wiht nvidia issues :( 
[13:58] <tjaalton> eagles0513875: the latest non-beta version is 185.18.36, and that's in karmic
[13:59] <tjaalton> mine is working just fine
[13:59] <eagles0513875> tjaalton: was that in alpha 5?
[13:59] <tjaalton> I don't know
[13:59] <eagles0513875> cuz back in alpha 5 the repo one wasnt working which i dont think was .36 but an older version the one that was in jaunty
[13:59] <eagles0513875> strange tjaalton i am not sure if i should send people in here who are having nvidia issues or not
[14:00] <tjaalton> Sun, 23 Aug 2009, so yes it was in alpha5
[14:01] <eagles0513875> interesting i dunno but there was a bug in it where x wouldnt start up at all 
[14:01] <eagles0513875> would be dropped into a tty console 
[14:01] <eagles0513875> with the nv driver and the 185 driver that is in repos 
[14:01] <eagles0513875> downloaded it from nvidia and it worked just fine
[14:02] <tjaalton> without a logfile it's impossible to tell
[14:02] <tjaalton> could be just the kernel module missing
[14:03] <eagles0513875> tjaalton: true. alpha 6 it was fixed and nv worked out of the box
[14:03] <eagles0513875> and has been since
[14:03] <tjaalton> nv is different
[14:04] <abhinav> Hi .. suspend/hibernate with karmic is failing due to an error pointing to nvidia.
[14:04] <eagles0513875> tjaalton: maybe so but it wasnt working in alpha 5 
[14:04] <abhinav> filed 415211 on launchpad - in case anyone wants to take a look. Guess quite a few users have seen this
[14:04] <abhinav> this is with the latest updates on karmic beta
[14:05] <tjaalton> eagles0513875: but not because of the driver, but something else
[14:06] <eagles0513875> was worried till alpha 6 came out that i would have had to recompile x from source with a newer version
[14:08] <tjaalton> unless you were bit by bug 385658
[14:08] <ubottu> Launchpad bug 385658 in xserver-xorg-video-nv "'nv' is selected when no xorg.conf is present even if it doesn't support the nvidia hardware" [High,Fix released] https://launchpad.net/bugs/385658
[14:08] <tjaalton> eh, not that one then :)
[14:08] <tjaalton> or maybe..
[14:09] <eagles0513875> tjaalton: i think i was 
[14:09] <eagles0513875> cuz it would just drop right into console
[14:14] <eagles0513875> hey guys im trying to remix my own distro using karmic as my basis how can i rebrand it instead of using  the karmic debootstrap use debootstrap with my own naming convention for what im developing
[14:15] <tjaalton> hardly the place to ask
[14:15] <eagles0513875> whoops thought i was in ubuntu+1
=== ripps_ is now known as ripps
[14:25] <amx109> updated karmic today and X is now borked. i get nothing but gibberish along the very centre of the screen. 2.6.31-13 doesnt work. nor does 2.6.31-12, but 2.6.31-11 drops me to a terminal login (still no X)
[14:25] <amx109> i have an ati 2850. can anyone help?
[14:26] <tjaalton> using fglrx?
[14:26] <eagles0513875> tjaalton: amx109 is having a similar issue that i was having back in alpha 5 with 11 kernel
[14:27] <tjaalton> but totally different hw
[14:27] <tjaalton> and driver
[14:41] <amx109> tjaalton,  yeah, im using fglrx
[14:54] <amx109> ive got X back
[14:55] <amx109> there was a missing file that fglrx was complaining about
[14:55] <amx109> i restored it from a backup
[14:55] <amx109> i get into X, and gnome now
[14:55] <amx109> but theres an amd logo in bottom right corner with 'testing use only. unssupported hardware' below it
[14:57] <amx109> im going to remove fgrlx and hope that improves things