[02:15] <ubotu> New bug: #165093 in linux-restricted-modules-2.6.22 (restricted) "[nvidia-glx-new] Xorg crashes with /usr/bin/X(FontFileCompleteXLFD+0x1e1)" [Undecided,New] https://launchpad.net/bugs/165093
[05:42] <tjaalton> soren: oh, glad that it worked
[05:42] <tjaalton> soren: btw, you seem to have the same keyboard/mouse as I do (bought it this Saturday) :)
[07:26] <ubotu> New bug: #165117 in xserver-xorg-video-intel (multiverse) "Broken Image/Road Overlays on Google Earth" [Undecided,New] https://launchpad.net/bugs/165117
[15:26] <ubotu> New bug: #165189 in xorg (main) "cannot switch VTs from bulletproof-X" [Undecided,New] https://launchpad.net/bugs/165189
[17:01] <ScislaC> tjaalton: was it your xorg-driver-fglrx debs that ended up hitting the repos for Hardy?
[17:06] <ScislaC> I still get the watermark in the bottom right corner, and for the most part everything in my Xorg.0.log looks fine... the only things I wonder about are the lines that say "No signature file" and "AMD Video Driver is unsigned".
[17:06] <ScislaC> btw... hi all :)
[17:39] <bryce> heya ScislaC
[17:40] <ScislaC> hi bryce! how goes in X land?
[17:41] <bryce> I've been thanksgiving-ing the past few days so am not sure myself
[17:42] <ScislaC> hehehe
[17:42]  * ScislaC nods
[17:42] <ScislaC> yeah, I think I've hit my turkey quota for the rest of the year
[17:45] <bryce> we tossed the rest in the freezer yesterday
[18:21] <ubotu> New bug: #165002 in xorg (main) "Installing new PCI device breaks X" [Undecided,New] https://launchpad.net/bugs/165002
[19:47] <tjaalton> hey dudes
[19:47] <tjaalton> ScislaC: maybe the driver is just buggy
[19:57]  * bryce waves
[20:01] <tjaalton> hey bryce
[20:01] <bryce> http://news.launchpad.net/general/inkscape-moving-to-launchpad
[20:03] <tjaalton> yeah, xcb-1.1 built already
[20:04] <tjaalton> and radeonhd, nv synced
[20:09] <ScislaC> tjaalton: well, if you get bored in the coming weeks and want to give the newer one (Catalyst 7.11) a shot, I'd be happy to test it before you up it to the repo
[20:10] <tjaalton> maybe when hardy gets a new kernel
[20:12] <tjaalton> "catalyst 7.11" is just marketing, the driver itself is 8.43 :)
[20:15] <ScislaC> tjaalton: New kernel makes sense... as for version numbering, yeah, I know... but I want to roll with what it's officially called :)
[20:59] <ScislaC> tjaalton: fyi, the following got rid of the watermark for me. http://ubuntuforums.org/showpost.php?p=3843078&postcount=3
[21:02] <bryce> yeah, I think there might also be a build option that turns it off
[21:02] <bryce> I was thinking we should incorporate that into our build scripts
[21:02] <bryce> tjaalton: btw, did you commit the lrm changes into the kernel team's git?
[21:06] <ScislaC> bryce: so now I know the driver works :)   Now to see if I can get XGL working again :D (since aiglx doesn't work with that driver and the newest xserver)
[21:08] <bryce> cool
[21:22] <tjaalton> bryce: it's not in the git
[21:23] <tjaalton> ScislaC: it should work
[21:24] <ScislaC> tjaalton: I'll be the judge of that ;) just unpacking a large tar, then I will restart X
[21:26] <tormod> hi, is https://wiki.ubuntu.com/X/Patches originally meant for backports to 1.4 (Hardy) or 1.3 (Gutsy) as well?
[21:28] <tormod> maybe we should have a Gutsy field and a Hardy field? Or some way to tag where the patch is nominated for?
[21:35] <bryce> good idea
[21:35] <bryce> heya tormod btw, good to see ya
[21:36] <tormod> hi bryce
[21:36] <bryce> yeah that page was set up originally just for Gutsy backports, but it certainly can be extended if you'd like
[21:36] <tormod> well I see some patches are well commented about SRUs
[21:36] <bryce> yeah I'm going to try pushing on those a bit today
[21:37] <bryce> I'd like to clear out that page, I don't think there's as much pressure for gutsy backports of the fixes as I anticipated
[21:43] <tjaalton> bryce: your merge-status page isn't updating, it shouldn't have separate apps anymore ;)
[21:44] <bryce> hrm
[21:44] <tjaalton> ScislaC: doesn't work?
[21:44] <ScislaC> nope... xgl is a no go here... going to look at logs
[21:44] <tjaalton> oh, I meant aiglx
[21:45] <ScislaC> ah, no... aiglx does not work with the newest xserver according to many reports on phoronix and my own experience of it not doing what it should (yes I whitelisted fglrx for compiz and all that jazz)
[21:45] <ScislaC> or... let me say
[21:45] <tjaalton> do you have a link?
[21:46] <ScislaC> FGLRX 8.42 does not use AIGLX correctly with the new version
[21:46] <ScislaC> give me a couple mins to dig up
[21:46] <bryce> hmm, you're right - last update was the 20th.  I'll start capturing logs on it.  meanwhile I'm doing a manual update now
[21:46] <tjaalton> ok, nice to know that it's the driver failing :)
[21:46] <bryce> bbiab (lunch)
[21:49] <tjaalton> ScislaC: btw, I misread your original issue.. I thought you had some corruption on the screen or similar
[21:49] <ScislaC> no no... it was just the watermark originally :)
[21:49] <ScislaC> tjaalton: here's a thread that discusses it http://forum.compiz-fusion.org/showthread.php?p=37328
[21:49] <tjaalton> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=449117
[21:49] <ubotu> Debian bug 449117 in fglrx-driver "fglrx-driver: Corruption in the lower right corner with 8.42.3" [Important,Open] 
[21:50] <tjaalton> that's why it sounded familiar
[21:50] <tjaalton> thanks, I'll read
[21:50] <ScislaC> I've seen a few threads on phoronix mention the aiglx and xserver-xorg version issue too... so the compiz thread isn't alone
[21:51] <ScislaC> tjaalton: as for that bug, yes, I have seen the corruption twice there... once when I had the watermark, and the other today after I removed the watermark
[22:01] <tjaalton> ScislaC: ok, let's wait for the next release then
[22:02]  * ScislaC nods
[22:02] <ScislaC> tjaalton: I've seen mixed reports of 8.43 fixing the aiglx issue
[22:02] <ScislaC> I'll keep you posted either way, just because it's good to have more info rather than less :)
[22:06] <tjaalton> well, if there is going to be a 2.6.24rc kernel for the alpha, we are forced to update fglrx :/
[22:07] <tjaalton> or :)
[22:13] <tjaalton> I wonder if libx11 needs a rebuild because of the new libxcb
[22:14] <jcristau> eh? there's no soname change
[22:15] <ScislaC> tjaalton: just curious, with stuff like xserver-xgl, is that just the automatic merge from debian, or is the ubuntu X team doing stuff like that?
[22:25] <tjaalton> jcristau: oh, right
[22:26] <tjaalton> ScislaC: could you rephrase that?
[22:31] <tjaalton> ScislaC: you mean if xserver-xgl is packaged by ubuntu?
[22:32] <tjaalton> seems to be the case
[22:37] <ScislaC> tjaalton: let me ask the real question... :)   In Gutsy, if XGL was installed, gdm would automatically start a session with it. I'm just wondering if that was part of the xserver-xgl package or a gdm thing, or what. Mainly I wonder because it doesn't start an XGL session (even though it's still installed) with all the new xorg/xserver stuff.
[22:38] <tjaalton> see /etc/X11/Xsession.d/98xserver-xgl_start-server
[22:39] <tjaalton> which is from xserver-xgl
[22:39] <tjaalton> I'd just get rid of xgl ;)
[22:39] <tjaalton> like, completely
[22:40] <bryce> tjaalton: hmm, versions page updated, but the old packages haven't dropped off
[22:40] <bryce> http://people.ubuntu.com/~bryce/Xorg/versions_current.html
[22:40] <tjaalton> is it because of gutsy still being listed?
[22:41] <bryce> hmm, it shouldn't.  let me poke a bit
[22:42] <bryce> appres is one that should be disappeared now, yes?
[22:43] <bryce> aha, found the issue
[22:45] <bryce> (the chroot wasn't getting apt-get update'd)
[22:45] <tjaalton> hehe
[22:45] <bryce> ok regenning.  thanks for catching the problem
[22:45] <ubotu> New bug: #165282 in xserver-xorg-video-intel (main) "laptop freezes after log out with Intel 855GM graphic chip" [Undecided,New] https://launchpad.net/bugs/165282
[22:47] <tjaalton> there should be a couple of apps left which are not in x11* bundles, and are probably worth dropping completely
[22:47] <tjaalton> although there is a debian bug about adding beforelight
[22:48]  * bryce nods
[22:48] <bryce> page is refreshed now
[22:48] <bryce> I bet we could drop beforelight and no one would care
[22:49] <bryce> woow, look at all the green :-)
[22:50] <tjaalton> yeah :)
[22:50] <tjaalton> apps are still listed though :)
[22:51] <bryce> do you know if the -evdev package pre-1.2.0, or post-1.2.0?
[22:51] <bryce> er ^is^
[22:51] <tjaalton> pre, but new enough
[22:54] <tjaalton> actually, 1.2.0 breaks all evdev setups that doesn't use input-hotplug
[22:54] <bryce> hmm, there doesn't seem to be much recent activity on -avivo.  I wonder if it's still relevant, or if we should think of deprecating it?
[22:55] <tormod> I don't think avivo makes any sense any longer.
[22:55] <tjaalton> right
[22:55] <tjaalton> soon radeonhd faces the same destiny :)
[22:56] <bryce> what's going to replace radeonhd?
[22:56] <tormod> what about -mga, should we file a sync request?
[22:56] <tjaalton> stuff being merged in -ati
[22:56] <tjaalton> atombios stuff
[22:56] <bryce> tjaalton: ahhhh nice
[22:56] <bryce> tormod: not a bad idea
[22:56] <tjaalton> you mean 1.9.100?
[22:56] <bryce> yeah
[22:56] <tormod> tjaalton: yes
[22:56] <bryce> I see it's in experimental
[22:57] <tjaalton> check the bugs first :)
[22:57] <bryce> maybe it'll sync over on its own once it's out of experimental?
[22:57] <tjaalton> yes
[22:57] <tormod> bryce: yes
[22:57] <bryce> ah
[22:58] <ScislaC> where can I find a list of cards that -ati currently supports? (the version in the repo)
[22:58] <bryce> any interesting stories with -sis?  
[22:58] <bryce> ScislaC: I'm not sure there's a published list, but if you apt-get the source, you could look in the pci id file to check what's advertised as supported
[22:59] <tormod> bryce: I think 0.9.3-6 is almost as good as 0.9.4
[22:59] <bryce> anyway, that short list of outstanding merges is pretty dang short!  I'm impressed
[23:00] <ScislaC> maybe I'll just break my stuff real quick to test instead ;)
[23:00] <ScislaC> brb
[23:01] <tjaalton> too fast :)
[23:01] <tjaalton> his X1xx surely isn't supported
[23:02] <tormod> :) he could have just asked
[23:05] <tjaalton> yeah
[23:08] <bryce> nah, he loves testing this stuff
[23:11] <bryce> what's the difference between -dbg and -dbgsym?
[23:12] <jcristau> the latter is ubuntu-specific and exists for all packages, aiui
[23:12] <tormod> bryce: I think -dbg is when the source package makes it and -dbgsym when it's built separately
[23:13] <tormod> but I think packages should be fixed to not build -dbg.
[23:13] <tormod> hmm I asked about this here or somewhere else but don't remember the answer :)
[23:14] <bryce> ah interesting
[23:15] <bryce> I kind of like it when packages have -dbg's -- makes it simpler to build both versions for testers
[23:16] <tormod> yes but there is just a package to install that will always make dbgsym's using a hook in debian/rules
[23:17] <tjaalton> https://lists.ubuntu.com/archives/ubuntu-mozillateam/2007-March/000215.html
[23:18] <tjaalton> so there are no user-installable packages called $pkg-dbgsym
[23:18] <tjaalton> but some have $pkg-dbg
[23:18] <tormod> I found https://wiki.ubuntu.com/HardyDebugPackageRemoval
[23:19] <bryce> huh, interesting
[23:20] <bryce> ok, in any case, that's enough to answer the user's question, thanks.
[23:21] <ScislaC> well... no -ati for me... but radeonhd works okay. All that matters is that I have a semi-working driver that doesn't peg one of my cores (as the new fglrx does)
[23:22] <bryce>  brb
[23:22] <bryce> <-- ScislaC has quit ("Leaving.")
 too fast :)
[23:22] <bryce>  his X1xx surely isn't supported
 :) he could have just asked
[23:22] <bryce> ;-)
[23:22] <ScislaC> hehehe
[23:22] <tormod> what card do you have?
[23:22] <ScislaC> mobility X1400
[23:24] <tormod> ScislaC: you could try the atombios branch of -ati git...
[23:24] <tjaalton> 01:21 < ScislaC> well... no -ati for me... but radeonhd works okay
[23:24] <tjaalton> but yeah, why not try that as well :)
[23:24] <tormod> when "okay" is too boring :)
[23:25] <ScislaC> heh... okay is always too boring ;)
[23:25] <tjaalton> "I can see something moving on the screen.. I'll try git head instead"
[23:25] <ScislaC> heh
[23:26] <ScislaC> you want to point me to the url? (also, is there a recommended way to install so that I don't fudge repo updates?)
[23:29] <ScislaC> okay then...
[23:29] <ScislaC> apparently this driver is a little buggy :P
[23:29] <tjaalton> \o/
[23:29] <tjaalton> more fun
[23:30] <ScislaC> I tried to start something that required acceleration, but, it died...
[23:31] <ScislaC> I so wish I had stuck with the intel graphics chip instead of going for the ati... :(
[23:32] <ScislaC> oh well... one more person to help you guys test stuff ;)
[23:32] <ScislaC> oh hey... didn't even notice keescook in here :)
[23:32]  * keescook waves "hi" to ScislaC :)
[23:32] <ScislaC> heya keescook! how goes in security land?
[23:33] <keescook> goes okay.  still need more hours in the day.  :)
[23:33] <keescook> how're you doing?
[23:34] <ScislaC> doing okay... the funny thing? I'm also still having that hours in the day problem. ;)
[23:34] <keescook> hehe
[23:38] <tormod> ScislaC: http://gitweb.freedesktop.org/?p=xorg/driver/xf86-video-ati.git;a=shortlog;h=atombios-support
[23:39] <tormod> ScislaC: for how to make debs out of it, do something like http://wiki.debian.org/XTips
[23:42] <jcristau> or just run autogen.sh && make and copy the resulting radeon_drv.so in /usr/lib/xorg/modules
[23:46] <bryce> heya keescook
[23:46] <keescook> hiya bryce
[23:51] <ScislaC> tormod: pardon my git stupidity... when I do a git clone git://git.freedesktop.org/git/xorg/driver/xf86-video-ati, I don't seem to get the AtomBios stuff with it... (and I don't believe I need everything on a higher level from the git repo either, but may be wrong about that)
[23:52] <tormod> you have to change to the atombios branch
[23:52] <jcristau> ScislaC: you need to checkout the atombios-support branch after the clone
[23:52] <jcristau> git-checkout -b atombios-support origin/atombios-support
[23:57] <ScislaC> hmmm not quite getting it yet (still new to git)... have to run and will try tomorrow...
[23:57] <ScislaC> bbl