[00:12] <tseliot> bryce: you're right, I didn't pay enough attention to your patch. I guess it's because it's 1:11 AM here ;)
[00:22] <bryce> ah, no prob.  I'll get it built and stuff, maybe we can test and/or commit tomorrow
[00:36] <tseliot> bryce: ok, great
[00:36] <tseliot> and good night
[01:45] <bryce> tjaalton: I've updated notes on http://bryceharrington.org/X/PkgList/versions_current.html; let me know if you disagree with any of it
[05:51] <dholbach> hi guys
[05:51] <dholbach> what would you think about running a session at Ubuntu Developer Week?
[05:52] <dholbach> https://wiki.ubuntu.com/UbuntuDeveloperWeek/Prep still has some free slots and I'm sure people would be interested in learning more about what you do
[06:49] <bryce> dholbach: I did one last time
[06:49] <dholbach> bryce: how did it work out? are you guys interested in running another one?
[06:50] <bryce> dholbach: well, we didn't get any helpers, mostly people were just asking about X status, and for help with their X problems
[06:51] <bryce> so, I don't have an interest in doing another myself, but maybe someone else would
[06:51] <dholbach> ah I see - did you pimp your TODO section enough and talk a bit about stuff that people could get involved with?
[06:52] <bryce> certainly, and explained how to get involved, pointed out low hanging fruit that'd be easy for newbs to make a difference at, etc.
[06:53] <dholbach> OK... I'm not going to pester you much more :)
[06:53] <dholbach> in my sessions I'm going to point to harvest a lot, I hope that people will drive fixes toward you guys that way :)
[06:54] <bryce> I think mostly people were just interested in what upcoming features there were going to be in the next release, so I think they got useful info out of it, but that could be taken care of with just a blog post or two ;-)
[06:54] <bryce> yeah I've not been able to make much use of harvest so far
[06:56] <bryce> by default it displays too much data - I think what I'd love to see is a variant that displays only the several dozen Xorg packages
[06:56] <dholbach> hang on
[06:57] <dholbach> bryce: do you have a team that is bug contact for the X packages?
[06:57] <bryce> yep, it's 'x-swat' iirc
[06:57] <dholbach> ubuntu-x-swat?
[06:57] <bryce> https://bugs.edge.launchpad.net/~ubuntu-x-swat/+packagebugs
[06:58] <bryce> ubuntu-x-swat
[06:58] <dholbach> just a sec
[06:58] <dholbach> bryce: http://6b62lx
[06:58] <dholbach> err
[06:58] <dholbach> bryce: http://tinyurl.com/6b62lx
[06:59] <bryce> ah perfect, thanks
[07:13] <tjaalton> wow, that looks nice
[07:16] <dholbach> bryce: you could run a session called "the perfect contributor" :-)
[07:17] <bryce> I'd just point to tjaalton and be done, I think
[07:18] <dholbach> ok ok, I said I'd stop pestering you :)
[07:18]  * dholbach hugs bryce
[07:18]  * dholbach hugs tjaalton too
[07:18]  * bryce hugs dholbach
[07:18] <bryce> thanks for the harvest help, I was thinking I'd need to do some major hacking, this'll be extremely handy
[07:19] <dholbach> bryce: I wrote a small script that generates the "harvest url" from the +packagebugs page: https://lists.ubuntu.com/archives/ubuntu-devel/2008-August/026118.html
[07:20] <dholbach> that's not perfect or anything - the long term plan is to use seeds, but I'm just so busy right now that I didn't manage to start hacking on that
[07:20] <tjaalton> bryce: :D
[07:20]  * bryce nods
[07:20] <dholbach> you could add that tinyurl to your GettingInvolved page
[07:21] <dholbach> so people triage the page every now and then
[07:21] <bryce> yeah, although the first place I'll slot it in is at http://bryceharrington.org/X/Reports/status_current.html
[07:21] <dholbach> ok... works for me :)
[07:22] <bryce> bbl
[07:23] <dholbach> sleep tight
[07:23] <dholbach> see you
[09:27] <tjaalton> bryce: btw, now that evdev is used for keyboards and mice, we could be able to drop kbd and mouse from -input-all
[09:28] <tjaalton> hm, that doesn't buy us a lot of diskspace after all
[09:28] <tjaalton> :)
[09:28] <tjaalton> joystick and evtouch are just as small
[09:42] <bryce> well, every bit helps
[09:42] <bryce> but will people need them perhaps, if evdev proves problematic?
[09:43] <tjaalton> they can install those afterwards
[09:44] <tjaalton> I think it's safe to say that evdev just works
[09:45] <tjaalton> merging intel
[09:46] <tjaalton> jcristau: was there a proper patch for the Xv issue on G45?
[10:07]  * Ng perks up at mention of G45 ;)
[10:08] <tjaalton> Ng: 2.4.1 aka 2.4.2 on the way
[10:08] <Ng> \o/
[10:08] <Ng> I'm getting a weird thing where the display drops out every so often (in that my tv blinks and shows the signal information again, like it switched video modes)
[10:09] <Ng> it happens more on DVI than HDMI, but other than that I have no useful information about it, there's certainly no log entries anywhere
[10:09] <crevette> hi there
[10:09] <Ng> I'm worried that it might be something with the northbridge itself, when I was installing the board I picked it up by the thing's heatsink and I may have disloged it a bit :/
[10:10] <tjaalton> Ng: nah, those things should be robust
[10:11] <Ng> tjaalton: the heatsink definitely had more movement in it after I'd done that. I'm worried I might have cracked a solder joint or something ;)
[10:12] <crevette> is there some known corruption problem with intel latest driver on intrepid?
[10:14] <tjaalton> crevette: probably
[10:14] <crevette> the chipset is 945
[10:15] <bryce> crevette: bug #?
[10:15] <bryce> crevette: what sort of corruption?  got a screenshot/photo?
[10:19] <crevette> I can do that tonight when I'll be at home
[10:19] <tjaalton> hm, enabling greedy migrationheuristic doesn't help anymore
[10:19] <crevette> I didn't opened a bug yet
[10:23] <tjaalton> bryce: the greedy patch for intel hasn't been applied since 1.5 came along (it crashes), and setting the option by hand doesn't seem to help improving the performance at all. so, what about dropping the patch from the diff?
[10:24] <bryce> tjaalton: I figured we'd need to drop it eventually, so yeah
[10:24] <tjaalton> I've forgot already; why don't we use XAA?
[10:24] <bryce> EXA is the future!
[10:25] <tjaalton> heh
[10:25] <bryce> well, there were some bugs / mis-features which intel said they'd not support on XAA anymore
[10:25] <tjaalton> well, EXA performance doubled with backported EXA changes from xserver master
[10:25] <tjaalton> ah right
[10:25] <bryce> wasn't it video compositing stuff or something?
[10:26] <tjaalton> something like that
[10:29]  * crevette keeps with ubuntu defaut config to support the future
[10:29] <crevette> :)
[10:29] <crevette> but the performances are not here :)
[10:32] <jcristau> +   pI830->TexturedXvEnabled = xf86ReturnOptValBool(pI830->Options, OPTION_TEXTURED_VIDEO, FALSE);
[10:32] <jcristau> tjaalton: just add || OVERLAY_NOEXIST(pI830) there
[10:33] <jcristau> tjaalton: and, updating the patch description and the manpage to say this option defaults to off would be nice
[10:33] <tjaalton> jcristau: heh, right. Now that I tried with the default settings (textured video on) on my i965, I didn't notice any problems
[10:34] <tjaalton> but I should probably get a more demanding clip
[10:41] <tjaalton> right. no problem running an episode of Fifth Gear
[10:41] <tjaalton> what the hell made it work this good?-)
[10:45] <tjaalton> so I guess that patch could be dropped as well
[10:45] <tjaalton> at least disabled for now to see if people complain
[10:56] <tjaalton> jcristau: so; +   pI830->TexturedXvEnabled = xf86ReturnOptValBool(pI830->Options, OPTION_TEXTURED_VIDEO || OVERLAY_NOEXIST(pI830), FALSE); ?
[10:57] <jcristau> no
[10:57] <tjaalton> argh :)
[10:57] <jcristau> pI830->TexturedXvEnabled = OVERLAY_NOEXIST(pI830) || xf86ReturnOptValBool(stuff);
[10:58] <tjaalton> makes more sense. anyway, I'll leave it disabled for now
[12:47] <Q-FUNK> howdy!
[12:47] <Q-FUNK> isn't today archive day?
[13:08] <tjaalton> Q-FUNK: AIUI mon, wed, fri are
[13:11] <Q-FUNK> ah
[13:11] <Q-FUNK> was wondering what was going on with -geode sync from debian
[13:24] <tjaalton> no idea..
[17:06] <tedg> Hey guys, can you tell me about fast-user switching on Intrepid.
[17:06] <tedg> I'm getting an X error from GDM.
[17:07] <tedg> And from the log it looks like the nVidia driver can't initialize the kernel module?
[17:07] <tedg> Seems odd that it could once, but not the second time.
[17:07] <tedg> In general, is fast-user switching working in current Intrepid?
[17:47] <tseliot> bryce: can you upload this, please? https://bugs.launchpad.net/ubuntu/+source/envyng-core/+bug/260862
[17:48] <tseliot> bryce: so that I can ask an archive admin about envyng-core and screen-resolution-extra?
[18:23] <bryce> sure
[18:37] <tseliot> bryce: thanks, let me know when it's done so that I can bug an admin before feature freeze ;)
[18:47] <crevette> hey
[18:47] <crevette> new intel driver seems to be better
[18:47] <crevette> better performances at least
[18:53] <crevette> hey, there is not comosited launch animation on gnome-panel
[18:53] <crevette> composited
[21:22] <tormod> bryce, are you interested in imagemagick?
[21:22] <bryce> sure
[21:26] <tormod> I was wondering if I should try to merge 6.4 which fixes some Ubuntu bugs
[21:26] <tormod> but there are diffs not described in the changelog :(
[21:27] <tormod> would you review it if try? before FF?
[21:29] <bryce> certainly
[21:29] <bryce> tseliot: btw envyng-core is uploaded
[21:30] <tseliot> bryce: thanks a lot
[21:35] <tormod> bryce, you had something to merge changelogs, right?
[21:37] <bryce> yep
[21:38] <bryce> http://bryceharrington.org/ubuntu/merge_changelog
[21:38] <tormod> thanks!
[22:28] <james_w> bryce: sorry, but I very much doubt I'll be able to review anything before feature freeze
[23:25] <bryce> yay, mesa 7.1 released
[23:33] <bryce> tseliot: found a problem in the screen-resolution-extra stuff - email sent
[23:35] <tseliot> bryce: thanks for reporting. I'll have a look at it
[23:38] <tseliot> bryce: does it solve the problem if you replace time.time() with str(time.time()) ? line 259
[23:39] <tseliot> in screenresolution-mechanism.py
[23:39]  * bryce tries
[23:40] <bryce> that solved the error
[23:40] <bryce> let's see if it updated things correctly
[23:41] <tormod> bryce: Imagemagick got messy. Found out a sync was probably better, but it needs some changes to BFS. Don't understand while my PPA build failed during dh_install.
[23:41] <tormod> s/while/why
[23:43] <bryce> ok looks like it worked and updated xorg.conf correctly.  Rebooting to see if the Screen Resolution settings take too
[23:43] <bryce> tormod: ah too bad
[23:43] <tseliot> bryce: great
[23:44] <bryce> hmm
[23:44] <tormod> bryce: see bug #188773
[23:45] <tormod> it's a bit awkward that I don't have intrepid myself...
[23:49] <tormod> the most important bug fix here was for bug #178575
[23:49] <tormod> exif data is lost on image transformation
[23:51] <bryce> hmm
[23:52] <bryce> tormod: yeah I agree getting that patch upstream is probably the best way to go
[23:52] <bryce> tormod: I don't think you can sync it otherwise
[23:53] <bryce> tseliot: I put up some additional screenshots 8a-10
[23:53] <tormod> bryce: we have to wait for the patch to go upstream before syncing?
[23:55] <bryce> tormod: unless there is a reason why that patch is unimportant, yes the folks that do syncs would probably require it to be a merge
[23:56] <bryce> tseliot: and http://bryceharrington.org/ubuntu/ScreenRes/screens-11.png
[23:56] <tormod> because it's cosmetic? typo in documentation?
[23:56] <bryce> right
[23:56] <bryce> tseliot: sweetness :-)
[23:56] <tormod> I'll add that.
[23:57] <tseliot> bryce: the fact that it outputs the "Error" word is just the output of the logging library, nothing to worry about
[23:57] <tseliot> bryce: I'm glad to see that it works
[23:57] <bryce> tseliot: notice that in the console output there's info msgs that are labeled Errors which really aren't - is there a way to clean that up?
[23:57] <bryce> ok, so it seems to generally work
[23:58] <tseliot> bryce: yes, I think it's in the mechanism. Let me have a look
[23:58] <bryce> tseliot: it's a bit irritating that the Screen Resolution tool has to block until the python tool completes, and I think some users may get confused about that, but I don't think there's an easy way around that
[23:59] <bryce> but something we may want to think about
[23:59] <bryce> anyway, once you get that time.time bug fix in, I think this is good to go