[00:49] <mdeslaur> pwnguin: you want me to try nv?
[00:59] <mdeslaur> pwnguin, jcristau: nice try, but I have the exact same problem with the nv driver
[02:43] <pwnguin> mdeslaur: actually i wa thinking nvidia
[02:43] <pwnguin> err nouveau
[05:23] <mdeslaur> pwnguin: same problem with the nouveau driver
[17:16] <lesshaste> something odd has happened to my X display with the simplest symptom being that the display runs over to the right of the screen so I can't see it all. Also in /var/log/Xorg.0.log I see http://pastebin.com/f7daea46b
[17:16] <lesshaste> this followed a standard update 
[20:02] <directhex> argh. wifey's netbook fails to initialize DRM on cold-boot
[20:21] <lesshaste> hi all
[20:21] <lesshaste> bryce: just reported https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/442395 . Anything more specific needed?
[20:26] <albert23> lesshaste: If you have a second PC available, you could try and make a full stacktrace
[20:27] <albert23> lesshaste: see https://wiki.ubuntu.com/X/Backtracing
[21:19] <lesshaste> albert23: I'll see if I can find one
[21:20] <lesshaste> actually can you use screen to this somehow?
[21:55] <lesshaste> I am suffering from this bug it seems http://bugs.freedesktop.org/show_bug.cgi?id=19643
[21:55] <lesshaste> the attached patch says "If the screen has no modes defined, can lead to a null pointer
[21:55] <lesshaste> dereference in VidModeGetFirstModeline().
[21:55] <lesshaste> "
[21:55] <lesshaste> so would a sensible workaround be to define some modes in xorg.conf somehow?