[00:01] <bryce> tjaalton: would you mind doing an upload for me when you get a chance?  Here's a patch to add a quirk for an upcoming laptop model - http://people.ubuntu.com/~bryce/Uploads/xserver-xorg-video-intel_2.2.0.90-2ubuntu3.dsc
[00:07] <tjaalton> bryce: uploaded
[00:07] <bryce> rockin' thanks
[00:07] <tjaalton> bryce: how come you still don't have core-dev powers?-)
[00:07] <bryce> laziness
[00:07] <tjaalton> heh
[00:08] <bryce> actually I've written up the app, fixed up my wiki page, and everything, I just need to send the mail. 
[00:29] <tjaalton> ok, hopefully I'm done with lrm for the day
[00:30] <tjaalton> night
[00:42] <bryce> tjaalton: night
[00:43] <bryce> tjaalton: btw I've added this quirk patch to our xorg-server:  http://gitweb.freedesktop.org/?p=xorg/xserver.git;a=commitdiff;h=fc092334ac0a323b80a9602cb8bf60ca9dee3bfa
[00:43] <bryce> tjaalton: it adds several kinds of quirks for dealing with buggy EDID
[00:44] <bryce> I've compiled xorg-server with the patch to verify it applies, and it looks good
[01:33] <jcristau> bryce: what's the diff between patches 150 and 43?
[01:34] <bryce> oh, good catch
[01:35] <jcristau> (i'm wondering how you got that to apply :))
[01:36] <bryce> oh I have another patch (maybe two) and then was going to test.
[02:14] <bryce> tjaalton: another dell quirk to upload when you have a chance:  http://people.ubuntu.com/~bryce/Uploads/xserver-xorg-video-intel_2.2.0.90-2ubuntu4.dsc
[02:45] <ubotu> New bug: #192024 in xserver-xorg-video-intel (main) "java applications don't start giving a backtrace on ground of locking assertion failure" [Undecided,New] https://launchpad.net/bugs/192024
[04:34] <ubotu> New bug: #175647 in linux-restricted-modules-2.6.24 (restricted) "Compiz-fusion with seperate x screen doenst work properly, gtk menus slow" [Undecided,Incomplete] https://launchpad.net/bugs/175647
[05:20] <tjaalton> bryce: ok, intel uploaded
[05:36] <tjaalton> bug 187855
[05:36] <ubotu> Launchpad bug 187855 in xorg "keyboards events generated wrongly create issues" [Undecided,Incomplete] https://launchpad.net/bugs/187855
[05:38] <tjaalton> ah that one
[05:38] <tjaalton> daniels said that it would be a kernel issue, but I'm not sure how serious he was
[06:43] <tjaalton> mmm, compiz eats 869MB RES
[07:27] <bryce> yum
[07:31] <tjaalton> bryce: btw, did we decide to sync ati from experimental? alex said he's preparing a release soon
[07:33] <bryce> tjaalton: let's wait for the release
[07:34] <tjaalton> ok
[07:35] <bryce> if it comes in time, and brings needed features and is sufficiently stable, we can consider pulling it in
[07:36] <bryce> but from what you described before, it sounds like the features that have gone in are maybe not as well tested as we'd like
[07:36] <tjaalton> we need to either get r5/6xx support in ati or figure out how to fix vesa for them again
[07:47] <bryce> yup
[07:52] <bryce> 'night
[07:53] <tjaalton> night, I'll do some uploads in the meantime ;)
[08:02] <ubotu> New bug: #137828 in linux-restricted-modules-2.6.24 "Dell Latitude nVidia card not handled correctly" [Undecided,Fix released] https://launchpad.net/bugs/137828
[08:06] <ubotu> New bug: #147133 in ubuntu "ACX driver working badly (dup-of: 58384)" [Undecided,New] https://launchpad.net/bugs/147133
[08:26] <ubotu> New bug: #144984 in linux-restricted-modules-2.6.22 "Gutsy 9/25 Update broke nvidia-glx-new" [Undecided,Invalid] https://launchpad.net/bugs/144984
[11:00] <ubotu> New bug: #192087 in xorg (main) "Feisty - Gusty - Hardy Gnome Lock (not sure xorg related)" [Undecided,New] https://launchpad.net/bugs/192087
[11:05] <ubotu> New bug: #192088 in xserver-xorg-video-intel (main) "[hardy] X freezes system after cold boot on i830M using DRI" [Undecided,New] https://launchpad.net/bugs/192088
[12:31] <ubotu> New bug: #192107 in xorg (main) "xorg fails to start i Hardy with ATI X1400 " [Undecided,New] https://launchpad.net/bugs/192107
[13:31] <ubotu> New bug: #191851 in totem (main) "error while playing a ogg file (dup-of: 39050)" [Undecided,New] https://launchpad.net/bugs/191851
[16:07] <tedg> Okay, just to give more data... I got the mysterious white screen thing this morning.
[16:07] <tedg> xrandr was happy.
[16:07] <tedg> nothing in the logs.
[16:07] <tedg> When I asked xrandr to switch modes, then things go REALLY unhappy.
[16:08] <tedg> Before I could always switch to a VT, but after asking xrandr to switch modes the display flickered.
[16:08] <tedg> And then no more VTs.
[16:08] <tedg> But, they were still responsive, I was able to shutdown the machine.
[16:08] <tedg> And upon reboot, all better.
[16:30] <tjaalton> tedg: did you file a bug already?
[16:31] <tjaalton> I'm wondering if it's just dodgy hardware..
[16:42] <tedg> No, I haven't.  I didn't feel like I could file a bug that was anything other than "Incomplete".
[16:42] <tedg> I can do that though.
[18:17] <ScislaC> anyone know if the fglrx that's in the repo will be what you guys stick with for hardy? (it sounds like there were some slight performance improvements and compatibility with xserver-xorg 1.4 was added in 8.02)
[18:22] <tjaalton> ScislaC: 8-02 is the latest in hardy
[18:22] <tjaalton> pretty fresh though
[18:23] <ScislaC> tjaalton: not showing in the repo after I just did a reload in synaptic...
[18:24] <tjaalton> ScislaC: it'll get there in time
[18:25] <ScislaC> tjaalton: either way... woohoo! :)
[18:26] <ScislaC> I can finally upgrade to the hardy kernel and xserver!!!! (I've had those packages and fglrx locked in synaptic since gutsy)
[18:28] <bryce> heya ScislaC
[18:29] <ScislaC> hi bryce! I'm gonna be a happy boy. :)
[18:31] <ScislaC> bryce: btw, just so I can be prepared, do I need to do anything magical after my xserver upgrades (will I need to dpkg-reconfigure xserver-xorg)? will my current xorg.conf cause issues?
[18:33] <bryce> not as far as I know
[18:34] <bryce> timo might know differently tho
[19:04] <tjaalton> it _should_ work
[19:18] <bryce> hrm, I don't know what to think about redhat's xrandr gui work
[19:19] <bryce> sort of steals wind from the sails, but I'm not sure if it's something we'd want to deploy for hardy
[19:19] <bryce> (and I've not yet been able to get it to actually work)
[19:25] <tjaalton> must be fun :/
[19:35] <bryce> tjaalton: q's for you on #ubuntu-devel
[19:36] <tjaalton> k
[19:41] <ScislaC> bryce: hopefully you find it as amusing as I did... I just backed up my xorg.conf just in case it would be necessary for later, and saw a ton of backups from the past... they were suffixed with stuff like "-iwishitworked", "-pleasedontbreak", "-Ihatefglrx", etc. :)
[19:42] <bryce> lol
[20:32] <ScislaC> upgrade worked well :)
[20:35] <bryce> nice
[21:17] <ubotu> New bug: #178648 in linux-restricted-modules-2.6.24 (restricted) "sysctl table check failed: /dev/ath .7.9 Unknown sysctl binary path" [Medium,Fix released] https://launchpad.net/bugs/178648
[22:27] <ScislaC> bryce: if there is a bug that prevents a gnome/kde session from ending if a program is running (it's keytouch and I confirmed it on launchpad)... if it's not a "regular" package is it not a priority to fix it?
[22:28] <bryce> hmm, not sure
[22:28] <bryce> ScislaC: maybe ask bdmurray?
[22:28] <ScislaC> fair enough
[22:29] <ScislaC> bdmurray: do you happen to know the answer to the question I just asked bryce? :)
[22:30] <ubotu> New bug: #192253 in xorg (main) "xorg glx module is missing" [Undecided,New] https://launchpad.net/bugs/192253
[22:31] <bdmurray> ScislaC: it'd probably depend on the release - is this on Hardy?
[22:31] <ScislaC> bdmurray: yes
[22:32] <bdmurray> and so if keytouch is running you can not log out of your desktop session is that right?
[22:32] <ScislaC> correct
[22:33] <ScislaC> but if you kill it before you choose to log out or shut down, everything is fine
[22:33] <bdmurray> Without having seen the bug that sounds like something worth fixing.
[22:34] <ScislaC> https://bugs.launchpad.net/ubuntu/+source/keytouch/+bug/186713
[22:34] <ubotu> Launchpad bug 186713 in keytouch "[hardy] keytouch blocks logout" [Undecided,Confirmed] 
[22:34] <ScislaC> btw, is it not kosher that I marked it as confirmed?
[22:36] <bdmurray> A bug can be / should be confirmed in multiple situations and this seems to meet 2 of them.
[22:37] <bdmurray> So yes it is kosher
[22:39] <ScislaC> bdmurray: excellent :)
[22:42] <bdmurray> You can learn a bit more about how we use statuses at http://wiki.ubuntu.com/Bugs/Status
[22:46] <ScislaC> bdmurray: thanks for the reference link :)
[22:49] <bdmurray> no problem
[22:52] <bdmurray> ScislaC: How do I know if keytouch is running?
[22:52] <bdmurray> Is it just keytouchd running that screws it up?
[22:53] <ScislaC> bdmurray: you need to start it via preferences or session management...
[22:53] <ScislaC> and yes... keytouchd
[23:02] <bdmurray> It'd be interesting to know if there is a debian bug about it since we autosync with them
[23:09] <bdmurray> Come to find out there isn't so that might be worth forwarding to them.
[23:10] <ScislaC> I have to run right now, but will do so tomorrow :)
[23:10] <ScislaC> thanks for the wonderful X work guys :D