[02:10] <bryce_> heya
[06:01] <bryce_> hi soren
[06:21] <bryce_> heya james
[06:22] <bryce_> james_w: after dinner tonight I caught up with soeren and started peppering him with xrandr gui questions
[06:22] <bryce_> james_w: he answered them sort of non-committally and then edged away from me very quickly!  :-P
[08:45] <ubotu> New bug: #219069 in xorg (main) "FUJITSU SIEMENS Lifebook: VGA out cannot enabled (Hardy)" [Undecided,New] https://launchpad.net/bugs/219069
[09:03] <seb128> hey james_w
[09:03] <james_w> hi seb128 
[09:04] <seb128> james_w: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/219014, have you seen similar issues during your testing? does the change drop you suggested will fix this one?
[09:04] <ubotu> Launchpad bug 219014 in gnome-control-center "screen resolution pictures are connected" [Undecided,New] 
[09:05] <james_w> I'm not really sure what the problem is in the first part, do you know?
[09:05] <james_w> "The two images don't look correct touching like in the picture attached."
[09:06] <james_w> what does he mean by "not correct?"
[09:06] <seb128> look at the screenshot
[09:06] <james_w> the 19" is smaller than the 15"?
[09:07] <seb128> I think the complain is that the rectangle are touching
[09:07] <seb128> where he expects some space between the drawings
[09:07] <seb128> I've to agree it doesn't look really good this way
[09:07] <seb128> there is lot of empty space
[09:08] <seb128> so the monitors could use some rather than conflicting in the same corner
[09:09] <james_w> I was under the impression that they were supposed to be touching.
[09:10] <seb128> ah, maybe
[09:10] <james_w> I suppose they don't have to be, but I though the aim was the screen would span the two monitors.
[09:10] <seb128> the screenshot looks weird to be honest
[09:10] <james_w> yeah, it's not great
[09:11] <james_w> the second part of his problem should probably be filed as a separate bug against the driver by the sounds of it.
[09:13] <seb128> james_w: not sure, is there anything detecting the screens plugged and doing dynamic change?
[09:13] <seb128> it should run xrand --auto which is mapped to the screen switching key
[09:14] <james_w> I don't think there is anything that detects it.
[09:15] <james_w> hitting the "Detect displays" button and then applying may fix it up.
[09:15] <seb128> ok, so that's not a driver bug, he just needs to press the key
[09:15] <james_w> I guess it's a wishlist bug to have hotplug support wherever it needs to go for this.
[09:15] <seb128> right
[09:49] <mvo> is it known that xorg sometimes uses vesa instead of nv? I have a fresh altnernative install and get vesa on a nvidia 7600
[09:52] <tjaalton> mvo: what's the pci-id of the card?
[09:53]  * mvo checks
[09:53] <tjaalton> basically all the id's that the nv source lists should load nv
[09:54] <mvo> 10de:00f1
[09:54] <mvo> (its a 6600, sorry)
[09:55] <tjaalton> hmm, not in nv.ids
[09:55] <tjaalton> I'll check teh source
[09:55] <tjaalton> the
[09:56] <tjaalton> nope, not listed.. try forcing it on the xorg.conf
[09:57] <tjaalton> oh right.. I guess it wont load
[09:57] <tjaalton> since the driver should refuse to load if the id is not listed there
[09:57] <mvo> oh
[09:59] <tjaalton> so, either it's a mistake or left out intentionally
[10:00] <mvo> ok, thanks
[10:00] <mvo> should I file a bug?
[10:00] <tjaalton> you could build the driver with the id added in nv_driver.c
[10:00] <tjaalton> yes
[10:00] <tjaalton> static SymTabRec NVKnownChipsets[]
[10:02] <mvo> LP or upstream bugtracker?
[10:02] <tjaalton> why not both :)
[10:02] <mvo> because I'm lazy :P
[10:03] <tjaalton> let me check the nv bugs first
[10:03] <tjaalton> hehe
[10:04] <tjaalton> see bug 207428
[10:04] <ubotu> Launchpad bug 207428 in xserver-xorg-video-nv "GF 7050 not supported" [Low,Confirmed] https://launchpad.net/bugs/207428
[10:05] <tjaalton> a similar case
[10:07] <tjaalton> mvo: file on LP for now
[10:14] <mvo> I filed #219101
[10:14] <mvo> is it worth just adding the pci id to see what happens?
[10:20] <tjaalton> mvo: yes, add it like the rest and compile
[10:21] <mvo> ok
[10:26] <ubotu> New bug: #210526 in linux-source-2.6.22 "The touchpad freezes everytime I restore system from standby (dup-of: 59867)" [Undecided,Incomplete] https://launchpad.net/bugs/210526
[10:26] <ubotu> New bug: #219101 in xserver-xorg-video-nv (main) "nvidia 6600 not supported" [Undecided,New] https://launchpad.net/bugs/219101
[10:30] <ubotu> New bug: #209477 in linux-restricted-modules-2.6.24 (restricted) "trigger crashed with SIGSEGV" [Undecided,New] https://launchpad.net/bugs/209477
[10:37] <mvo> look fine
[10:37] <mvo> looks fine when adding the pci id
[10:38] <tjaalton> oh, nice
[10:46] <tjaalton> new lrm (fglrx 8.4) uploaded to my PPA (https://edge.launchpad.net/~tjaalton/+archive)
[10:48] <tjaalton> mvo: could you attach the Xorg.0.log from the patched nv to the bug. I'll forward it upstream
[11:07] <mvo> tjaalton: added, thanks!
[15:41] <ubotu> New bug: #219232 in linux-restricted-modules-2.6.24 (restricted) "KDE4 hangs (black screen) on logout with fglrx driver" [Undecided,New] https://launchpad.net/bugs/219232
[16:11] <ubotu> New bug: #216279 in tasks "Translation template is not being generated (dup-of: 188690)" [Undecided,New] https://launchpad.net/bugs/216279
[16:21] <ubotu> New bug: #218489 in xorg (main) "X freeze when switching between OpenOffice and Firefox" [Undecided,New] https://launchpad.net/bugs/218489
=== dennda_ is now known as dennda
[17:55] <ubotu> New bug: #219285 in xorg (main) "Hardy Heron: screen turns off, Xorg 100%" [Undecided,New] https://launchpad.net/bugs/219285
[18:14] <ubotu> New bug: #66478 in flashplugin-nonfree (multiverse) "Crash when viewing flash sites (dup-of: 14911)" [Undecided,New] https://launchpad.net/bugs/66478
[18:16] <ubotu> New bug: #63257 in flashplugin-nonfree (multiverse) "Firefox, shutdowns automatically when using a flash player...  (dup-of: 14911)" [Undecided,New] https://launchpad.net/bugs/63257
[18:18] <ubotu> New bug: #67806 in firefox (universe) "Firefox crash on gmail (dup-of: 14911)" [Undecided,Confirmed] https://launchpad.net/bugs/67806
[18:19] <ubotu> New bug: #67242 in flashplugin-nonfree (multiverse) "firefox crashes on flash content (dup-of: 14911)" [Undecided,New] https://launchpad.net/bugs/67242
[18:21] <ubotu> New bug: #219294 in xterm (main) "xterm segfaults if more than 9999 scroll lines" [Undecided,New] https://launchpad.net/bugs/219294
=== bryce_ is now known as inkscape_bryce
[19:36] <ubotu> New bug: #219321 in xorg-server (main) "package xserver-xorg-core 2:1.3.0.0.dfsg-12ubuntu8.3 [modified: usr/lib/xorg/modules/extensions/libglx.so] failed to install/upgrade: " [Undecided,New] https://launchpad.net/bugs/219321
[20:05] <tjaalton> mvo: that ^^ bug is strange, because it happens during upgrade from gutsy to hardy, but the version that fails is from gutsy. so the upgrade process updates x-x-c twice and fails (obviously because of diversions..). theres a dupe somewhere too
[20:06] <inkscape_bryce> heya tjaalton
=== inkscape_bryce is now known as bryyce
[20:08] <tjaalton> bryyce: howdy, how's XDC today?
[20:08] <tjaalton> no fglrx-8.4 for 8.04 btw, but maybe for .1
[20:08] <tjaalton> (or whatever the version might be at the time)
[20:09] <bryyce> ok
[20:09] <bryyce> XDC going pretty well.  So far today was Tinderbox for X, XCB, and now Wine & X
[20:10] <bryyce> I'm going to try to show/share some of my earlier Crucible/X test framework stuff with Chris Bell
[20:11] <tjaalton> ok cool
[20:13] <tjaalton> ask someone if TTM is going to make it in 2.6.26 :)
[20:13] <tjaalton> I guess it's the one Intrepid will use
[20:14] <tjaalton> k, dinner & some random movie, bbl ->
[20:15] <mvo> tjaalton: hm, maintainer scripts are meant to be idempotent - still, strange problem
[20:20] <mvo> tjaalton: I asked him for the upgrade logs, that should give us a apt/dpkg terminal log
[20:32] <bryyce> tjaalton: keithp says TTM will go in "after I rewrite it"
[20:32] <bryyce> tjaalton: which he thinks will be about 1 month
[20:48] <bryyce> tjaalton: what was the issue with getting fglrx 8.4 in?  just too late in the cycle, or were there bugs?
[21:03] <mvo> it seems like 855 give problem with video playback under compiz, do we know anything about this? or do we have hardware to confirm this?
[21:10] <seb128> mvo: my old laptop has an intel 855 card I think, I can try things tomorrow if you want, what is the issue?
[21:15] <bryyce> mvo, I've not been aware of further issues with 855, but jesse said there's probably more.
[21:17] <mvo> someone reported that video playback is broken with compiz for them, and I only have a 830 system for testing
[21:18] <mvo> seb128: yeah, that would be cool, just check if totem video playback works
[21:32] <seb128> mvo: ok, I will do that tomorrow after upgrading
[21:47] <mvo> thanks
[22:05] <tjaalton> bryyce: too late..
[22:06] <bryyce> tjaalton: ah ok
[22:07] <tjaalton> mvo: bug 217867 is a dupe
[22:07] <ubotu> Launchpad bug 217867 in xorg-server "package xserver-xorg-core 2:1.3.0.0.dfsg-12ubuntu8.3 failed to install/upgrade: " [Undecided,New] https://launchpad.net/bugs/217867
[22:08] <tjaalton> bryyce: ah, so there's hope for TTM after all :)
[22:09] <bryyce> tjaalton: keithp didn't elaborate but his tone had a disgruntled aspect to it that made me think there's a story behind it
[22:11] <tjaalton> it would also mean that .27 is a more probable target for TTM
[22:11]  * bryyce nods
[22:11] <ubotu> New bug: #215465 in xscreensaver (main) "[fglrx amd64] queens crashed with SIGSEGV (dup-of: 181121)" [Medium,Incomplete] https://launchpad.net/bugs/215465
[22:11] <bryyce> keithp didn't commit to a particular kernel version
[22:17] <ubotu> New bug: #214255 in xscreensaver (main) "[nvidia] glmatrix crashed with SIGSEGV (dup-of: 110125)" [Medium,Incomplete] https://launchpad.net/bugs/214255
[22:17] <ubotu> New bug: #218018 in xscreensaver (main) "[nvidia] The queens screensaver crashed in preview mode (dup-of: 110125)" [Undecided,Incomplete] https://launchpad.net/bugs/218018
[22:17] <tjaalton> I wonder if we could pull the latest stable drm to .26 when .27 is released
[22:17] <tjaalton> speculation..
[22:31] <munckfish> Hi all
[22:31] <munckfish> I've just managed to upgrade my PS3 gutsy install to Hardy
[22:31] <munckfish> and I'm about to start trying to get the backtrace stuff
[22:31] <munckfish> for the crash I was experience
[22:31] <munckfish> I want to 
[22:32] <munckfish> generate a pristine xorg.conf using the newly installed dexconf
[22:32] <munckfish> what do I have to do to ensure what's generated is exactly as would be generated by the live CD on boot?
[22:32] <munckfish> is it safe to just run dexconf? Or do I need to 
[22:32] <tjaalton> munckfish: ok, just run 'dpkg-reconfigure -phigh xserver-xorg'
[22:32] <munckfish> clean out the debconf db somehow?
[22:32] <tjaalton> dexconf should work too
[22:33] <tjaalton> there's not much to clean
[22:33] <munckfish> so just accepting the defaults in dpkg-reconfigure will do it?
[22:33] <munckfish> ok
[22:33] <tjaalton> should be fine
[22:33] <tjaalton> -phigh doesn't ask any questions IIRC
[22:33] <munckfish> ok thx
[22:34] <munckfish> btw, I can at least get X to run now using my gutsy xorg.conf
[22:34] <munckfish> and I didn't notice the invalid pointer problem yet
[22:34] <munckfish> but I'll see how it goes
[22:34] <tjaalton> ok
[22:34] <munckfish> I did have X spontaneously restart though
[22:34] <munckfish> only evidence I could find was in .xsession-errors
[22:35] <munckfish> I'll raise something in LP later
[22:39] <munckfish> tjaalton: does dexconf rely on there being at least a bare bones xorg.conf?
[22:39] <tjaalton> nope
[22:39] <munckfish> I just ran it, and it's failed
[22:39] <tjaalton> use -o
[22:39] <tjaalton> -o foo
[22:39] <tjaalton> mv foo /etc/X11/xorg.con
[22:40] <tjaalton> f
[22:40] <munckfish> xorg.conf no such file .......
[22:40] <munckfish> then FATAL: Module battery not found.
[22:40] <tjaalton> dexconf -o foo works
[22:40] <tjaalton> at least here
[22:42] <ubotu> New bug: #219377 in xorg (main) "Can't install Ubuntu using the liveCD because the radeonhd driver is not on the cd" [Undecided,New] https://launchpad.net/bugs/219377
[22:49] <bryyce> tjaalton: for r500/r600 what driver do we pick on the cd?  fglrx?
[22:50] <tjaalton> bryyce: ati
[22:50] <tjaalton> fglrx is not on the cd, neither is nvidia*
[22:50] <bryyce> ok
[22:57] <bryyce> tjaalton: btw alex just gave me a bunch of patches he says we should really have for 6.8 (all breakages discovered right after the release)
[22:58] <tjaalton> bryyce: excellent..
[22:59] <tjaalton> bryyce: although I'd prefer a new release if there were such issues..
[22:59] <tjaalton> didn't ajax point out that "releases are cheap" :)
[23:00] <bryyce> yeah but the current git tree is full of a lot of feature work he says is really not stable enough for us yet
[23:00] <bryyce> so he's cherrypicked these patches for us.
[23:01] <bryyce> (I agree, a point release would have been nice)
[23:01] <tjaalton> yeah, point-releases are cheap..
[23:06] <munckfish> Hi again guys, I've uploaded the backtrace now to LP 217647
[23:06] <munckfish> https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/217647
[23:07] <munckfish> has anyone got a moment to help analyse it a little?
[23:07] <bryyce> tjaalton: http://paste.ubuntu.com/7445/
[23:09] <munckfish> Sort of as I expected the invalid pointer is the 'idsdir' handle
[23:09] <munckfish> idsdir = (DIR *) 0x101f0000
[23:10] <bryyce> munckfish: mmm
[23:12] <munckfish> so simple stuff out the way first the directory it's trying to access /usr/share/xserver-xorg/pci/ does exist
[23:14] <bryyce> good backtrace...  looking at src
[23:14] <munckfish> ok cool
[23:14] <munckfish> would a strace help any?
[23:14] <munckfish> or ltrace
[23:14] <munckfish> ?
[23:15] <bryyce> hmm, probably not
[23:15] <bryyce> you could step through the function in gdb... that's probably what I'd do next
[23:16] <bryyce> set a break on chooseVideoDriver, then step through and see how the pointers are getting used
[23:16] <munckfish> can I do that without the source?
[23:16] <tjaalton> bryyce: a nice bunch of patches
[23:17] <munckfish> I mean just with the debug syms?
[23:17] <bryyce> munckfish: actually even that's not really necessary...  seems like it's narrowed down sufficiently
[23:17] <munckfish> I'm guessing not
[23:17] <bryyce> munckfish: one sec
[23:17] <munckfish> bryce: nae problem
[23:18] <munckfish> wow, there's two of you! are you both the same person?
[23:19] <tjaalton> multibryce!
[23:19] <tjaalton> we need'em both ;)
[23:19] <munckfish> bry[y]?ce
[23:19] <munckfish> well, I guess two's more powerful that one!
[23:20] <munckfish> bryce cloning
[23:20] <bryyce> try this patch:  http://bryceharrington.org/files/closedir.patch
[23:20] <bryyce> munckfish: yuup :-)
[23:21] <munckfish> k bryyce I'll rebuild and be back to report
[23:23] <bryyce> tjaalton: should we roll those into a package for testing?  Or...  it would be nice to tie the patches to specific bugs.  I may spend some time tonight to try to link them to bug reports.
[23:23] <tjaalton> bryyce: both, yes
[23:25] <tjaalton> at least if it should get in before release, I doubt it will
[23:26] <bryyce> yeah not unless we could tie the patches to extremely bad bugs
[23:26] <tjaalton> right
[23:26] <bryyce> but shooting for sru's or 8.04.1 might be more realistic
[23:42] <tjaalton> night folks ->
[23:47] <bryyce> night
[23:57] <munckfish> so ... bryyce what's the real reason for your clone?
[23:59] <bryyce> munckfish: 'bryce' is my login at home, 'bryyce' is my laptop here at the X dev conference
[23:59] <munckfish> oh i c
[23:59] <munckfish> you're at the X conf cool