[05:16] <ubotu> New bug: #198263 in xserver-xorg-video-ati (main) "firefox 3 displays incorrectly" [Undecided,New] https://launchpad.net/bugs/198263
[05:43] <ubotu> New bug: #198264 in xkeyboard-config (main) "debian/rules patch rule clear file 'rules/base.mlv_s.part'" [Undecided,New] https://launchpad.net/bugs/198264
[06:25] <ubotu> New bug: #198268 in xserver-xorg-video-ati (main) "screen scrambles before or after login" [Undecided,New] https://launchpad.net/bugs/198268
[08:41] <seb128_> bryce: hey
[10:41] <ubotu> New bug: #198309 in xkeyboard-config (main) "sony vaio vgn-sz650n keyboard geometry problem" [Undecided,New] https://launchpad.net/bugs/198309
[11:06] <ubotu> New bug: #198149 in xserver-xorg-video-ati (main) "Using Hardy Alpha live CD, I cannot use Full Graphics mode on any computer with ATI drivers." [Undecided,Confirmed] https://launchpad.net/bugs/198149
[12:00] <ubotu> New bug: #195721 in xserver-xorg-driver-ati "glxinfo crashes after login  ( systemfreeze ) " [Undecided,Confirmed] https://launchpad.net/bugs/195721
[12:17] <ubotu> New bug: #124406 in ubuntu "Keyboard keys get stuck and repeat (Feisty, Gutsy) (dup-of: 194214)" [Undecided,Confirmed] https://launchpad.net/bugs/124406
[12:17] <ubotu> New bug: #158436 in ubuntu "[gutsy] key release events get lost (dup-of: 194214)" [Undecided,Confirmed] https://launchpad.net/bugs/158436
[16:05] <ubotu> New bug: #198393 in xrandr "xrandr fails to output to VGA unless connected at boot" [Undecided,New] https://launchpad.net/bugs/198393
[17:06] <cr3> dpkg-reconfigure xserver-xorg does not seem to prompt for the video driver anymore, is this a known change?
[17:21] <tjaalton> cr3: yes
[17:22] <cr3> tjaalton: is this a bug or is there another way to reconfigure xserver-xorg now?
[17:31] <tjaalton> cr3: what do you mean?
[17:31] <tjaalton> it's not a bug
[17:32] <tjaalton> the xserver uses the best driver available, unless you want to use binary blobs
[17:32] <jcristau> if you want to change it, 'vim' works fine
[17:32] <tjaalton> :)
[17:34] <tjaalton> cr3: for restricted drivers, use the driver manager. soon it'll have cmdline interface as well
[17:47] <bryce> hi seb
[17:47] <bryce> hmm, no seb
[18:01] <seb128> hi
[18:04] <seb128> does anybody sees what is wrong there http://people.ubuntu.com/~seb128/xorgbug?
[18:05] <seb128> that's the xorg conf written by displayconfig-gtk on gutsy when selecting the monitor corresponding to the configuration and the corresponding xorg log because it starts in failsafe mode after using displayconfig-gtk
[18:07] <bryce> no permission to view the xorg.conf
[18:07] <seb128> bryce: fixed
[18:09] <bryce> do you have the Xorg.0.log from the original boot attempt?
[18:09] <seb128> original boot?
[18:10] <bryce> the attempt to launch X prior to the failsafe attempt
[18:10] <bryce> Xorg.0.log.old perhaps
[18:10] <seb128> bryce: http://people.ubuntu.com/~seb128/xorgbug/Xorg.0.log.old
[18:10] <seb128> the box boots correctly after installation
[18:11] <seb128> the problems start happening after using displayconfig-gtk to configure a monitor
[18:12] <seb128> bryce: http://people.ubuntu.com/~seb128/xorgbug/xorg.conf.1 is the stock working config
[18:12] <bryce> ah ok
[18:12] <bryce> well I think we are going to deprecate displayconfig-gtk now
[18:12] <seb128> ok, so not worth debugging ;-)
[18:12] <bryce> probably not
[18:13] <bryce> my guess is that an incorrect monitor configuration got selected
[18:13] <seb128> what will be the recommend wait to configure a CRT monitor when the default resolution is not adapted?
[18:13] <seb128> well, the selected model is the one connected to the PC
[18:14] <seb128> and selecting a generic monitor with a non too high resolution doesn't work either
[18:14] <seb128> I don't have the log for those though
[18:14] <seb128> I've not been on the buggy box, just doing remote debugging
[18:14] <bryce> well, sudo dpkg-reconfigure xorg-server is still the best way to do it (we even recommend it still when displayconfig-gtk fails)
[18:15] <bryce> ideally, I think we know a lot better now how to quirk monitors and update drivers to fix these sorts of issues directly
[18:15] <seb128> well, my fix is "sudo cp xorg.conf.1 xorg.conf" which works fine
[18:15]  * bryce nods
[18:15] <seb128> but I've issue explaining why selecting the right monitor leads to a situation why I need to do command line magic to get a working box again ;-)
[18:16] <seb128> why -> where
[18:17] <bryce> yep, well in such cases we'll just need to apologize and promise to try to sort out why the monitor was not autodetected
[18:18] <bryce> I think we can leave displayconfig-gtk available for people to install and use if they wish; although like you see, it doesn't give a guarantee of a correct config either
[18:19] <ubotu> New bug: #195669 in xorg (main) "pc running at low resolution " [Undecided,Incomplete] https://launchpad.net/bugs/195669
[18:22] <seb128> bryce: and do you see what is wrong in this one? http://people.ubuntu.com/~seb128/xorgbug/Xorg.9.log I think that's another try with a generic monitor which should be no issue
[18:22] <seb128> bryce: would hardy be better? I can give a daily CD to try ;-)
[18:37] <seb128> bryce: https://bugs.edge.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/198450
[18:37] <ubotu> Launchpad bug 198450 in gnome-settings-daemon "gnome-settings-daemon crashed with SIGSEGV" [Medium,New] 
[18:38] <seb128> bryce: this user still get a crash using the new versions
[18:38] <seb128> version rather, I did upload your gnome-desktop update but no gnome-settings-daemon change
[19:15] <bryce> seb128: sorry, I'm feeling ill, and suspect I am going to be taking some sick days
[19:17] <bryce> 198450 probably needs the gnome-settings-daemon change
[19:18] <bryce> seb128: hard to say without knowing the Xorg.0.log and/or driver
[19:19] <bryce> when I looked into this monday, I saw there's two different mechanisms that can lead to the crash at the same spot in the code, so both the gnome-desktop and gnome-settings-daemon fixes are needed to 
[19:20] <bryce> I haven't ruled out that there might be more than those two ways for it to get to that point with an invalid pointer, so we do need to watch for additional crashes.
[19:41] <seb128> bryce: ok, no hurry, get well
[19:41] <seb128> I've to go
[19:41] <seb128> later
[19:56] <ubotu> New bug: #198484 in nvidia-settings (universe) "nvidia-settings FFe" [Undecided,New] https://launchpad.net/bugs/198484
[20:15] <bryce> tjaalton: $ ls -l /var/log/Xorg.0.log
[20:15] <bryce> -rw-r--r-- 1 root root 3841563 Mar  4 09:43 /var/log/Xorg.0.log
[20:15] <bryce> but I think that may be due to all the xrandr fiddling I've been doing
[20:18] <tjaalton> possibly so
[20:18] <bryce> I wonder if the user installed something that is making a lot of xrandr calls or something
[20:19] <tjaalton> I wonder what that might be :)
[20:21] <bryce> do you have an idea?
[20:21] <bryce> (sorry if I'm missing obvious stuff, my brain feels like it's full of fluff right now)
[20:21] <ubotu> New bug: #190821 in nvidia-settings (universe) "nvidia-settings corrupts xorg.conf" [Undecided,Incomplete] https://launchpad.net/bugs/190821
[20:22] <tjaalton> nope.. no I idea :/
[20:22] <tjaalton> hope that he'll reply to the bug soon
[20:31] <ubotu> New bug: #198503 in nvidia-settings (universe) "nvidia-settings doesn't remember window size or default to a decent window size" [Low,Confirmed] https://launchpad.net/bugs/198503
[20:41] <seb128> bryce: gsd update uploaded too, thanks for your work fixing those
[20:41] <bryce> cool thanks
[20:43] <bryce> seb, timo, I'm going to go offline now for a while (feeling pretty crappy).  send me an email if there are emergencies I need to work on, I'll check in as I can.
[20:52] <seb128> bryce: no emergency don't worry
[20:53] <seb128> get better
[20:53] <seb128> later
[20:53] <tjaalton> bryce: ok, get well
[21:06] <ubotu> New bug: #198522 in xorg (main) "X can stop responding when clicking the shutdown button" [Undecided,New] https://launchpad.net/bugs/198522
[21:11] <ubotu> New bug: #192198 in xulrunner-1.9 (main) "rendering problem on firefox 3 (gmail) (dup-of: 186186)" [Undecided,Incomplete] https://launchpad.net/bugs/192198
[21:30] <ubotu> New bug: #183754 in xorg (main) "NV5MGA (RIVA TNT2 MODEL 64 PRO) i can't use it." [Undecided,Incomplete] https://launchpad.net/bugs/183754
[21:30] <ubotu> New bug: #198521 in xorg (main) "Hardy regression: i810 video incorrect size; cursor paints blocks" [Undecided,New] https://launchpad.net/bugs/198521
[21:38] <soren> tjaalton, bryce: What's the current vibe about vmmouse by default?
[21:40] <tjaalton> soren: undecided, but should be fine
[21:40] <soren> tjaalton: Awesome.
[22:52] <ubotu> New bug: #46378 in xkeyboard-config (main) "Bad mapping for Right-Click on PowerPC" [Medium,New] https://launchpad.net/bugs/46378