[04:10]  * greg-g waves and leaves
[04:16] <_stink_> did do-release-upgrade -d from jaunty to karmic.  have intel 82845G graphics.  under karmic, my machine will idle at the gdm prompt forever just fine, and i can switch to a vt and use it just fine, ssh in just fine, etc.  but once i log in via gdm, no matter into GNOME or failsafe xterm, within 5 minutes the machine "locks up".  no mouse/keyboard response (CapsLock won't toggle), can't ssh in anymore.  but sysrq+reisub will get me a 
[04:19] <_stink_> also, a liveusb of karmic always locks up as it's starting the desktop, and i suspect it's the same problem.
[04:20] <rickspencer3> _stink_, was this today?
[04:21] <_stink_> rickspencer3: i did the update Sunday, i think.  the problem has persisted since then
[04:21] <_stink_> er, did the *upgrade* to karmic Sunday.
[04:22] <rickspencer3> _stink_, could you please do a dist upgrade today to get onto the very latest RC bits
[04:22] <rickspencer3> and then do you know how to use ubuntu-bug to log a bug?
[04:22] <rickspencer3> $ubuntu-bug xorg
[04:22] <_stink_> know of it, haven't used it yet
[04:23] <rickspencer3> ok, it's super easy
[04:23] <rickspencer3> so first to get updated do:
[04:24] <rickspencer3> $sudo apt-get update && sudo apt-get dist-upgrade -y
[04:24] <rickspencer3> this will download the latest info about packages available, and then update to those packages
[04:24] <rickspencer3> then if you still see the problem do
[04:24] <_stink_> cool, doing that part now
[04:24] <rickspencer3> $ubuntu-bug xorg
[04:25] <rickspencer3> and this will open launchpad with a bug form, but also include every xorg related file
[04:25] <rickspencer3> so in this way it will get assigned to the write packages, have your config info, etc...
[04:25] <rickspencer3> so substantially increases the chances of someone seeing what is going wrong
[04:25] <rickspencer3> hth
[04:26] <_stink_> rickspencer3: thanks!
[04:26] <rickspencer3> sure, np
[04:27] <rickspencer3> thanks for the bug report :)
[16:55] <hyperair> is anyone around here free to look at a rather popular issue with PM and KMS with intel? bug #417599
[17:18] <tseliot> hyperair: so pm-utils doesn't restore the backlight with KMS. Is this the problem?
[17:18] <hyperair> tseliot: it seems so.
[17:18] <hyperair> tseliot: i don't have a machine i could test with
[17:25] <tseliot> hyperair: I know that KMS broke backlight control with xrandr but that was fixed.  I don't know if this is the reason why they disabled quirks if KMS is on.
[17:25] <tseliot> Maybe there are other problems with KMS
[17:27] <hyperair> hmm
[17:28] <hyperair> i think it was disabled because it was considered unnecessary
[17:28] <hyperair> including the whole chvt hack
[17:33] <tseliot> hmm...
[17:36] <tseliot> maybe it could be patched to override the kms check if passed, say, --quirk-override-kms
[17:38] <jcristau> that would be wrong
[18:29] <steveire> http://dpaste.com/110259/ Hi Trying to set up a dual screen system I get this when I select twinview. Does it mean anything?
[18:29] <steveire> All I get is a X cursoron my second screen. No "desktop"
[18:34] <steveire> http://dpaste.com/110265/
[18:34] <steveire> Does this mean that x only knows about one screen?
[18:48] <bryce__> steveire, depends on the driver
[19:04] <steveire> bryce__: It's an nvidia
[19:04] <steveire> http://img18.imageshack.us/content.php?page=done&l=img18/8399/errrnvidia.png
[20:25] <Amaranth> steveire: xrandr is useless with nvidia, don't pay attention to what it says