[00:10] <bryce> personally I'm still not sold on ppa, but I think the concept is probably good
[00:11] <pcjc2> It feels a more official place to push debs for testing than my own webspace
[00:12] <pcjc2> I had a brief scan of the 965 bugs to see if any matched this: https://bugs.freedesktop.org/show_bug.cgi?id=11895
[00:12] <ubotu> Freedesktop bug 11895 in Drivers/DRI/i915 "X crashed on i965" [Blocker,Verified: fixed] 
[00:12] <pcjc2> need some log files
[00:13] <pcjc2> last I looked, our drm.ko didn't have the fix
[00:15]  * bryce nods
[00:16] <bryce> so far I've just been going through and reviewing all the "New" bugs, and either prioritizing them or requesting what other info is needed.  I want to drive New -> 0
[00:17] <bryce> after that I'll go through the xorg and debian bug tracker and look for clear matches
[00:17] <bryce> then it'll just be a matter of going through each bug and figuring out what's going wrong
[00:17] <tepsipakki> so simple :)
[00:18] <bryce> it'll be a breeze
[00:18] <bryce> well, we definitely saw with some of the bugs this last go round that getting more eyes + activity on bugs really seemed to help push them forward
[00:19] <bryce> so I'm hoping just poking at all the -intel bugs, we can stir more people to work on them.  Tasks always seem to go easier when more people are working on them
[00:29] <tepsipakki> gah, what am I doing up so late.. nite all :)
[00:29] <tepsipakki> ->
[00:29] <pcjc2> night
[00:29] <bryce> night tepsipakki
[00:51] <pcjc2> ok... seems I suffer from Compiz + rotation bugs too
[02:35] <ubotu> New bug: #151300 in xorg (main) "[Feisty] livecd safe graphics isn't (safe)" [Undecided,New] https://launchpad.net/bugs/151300
[03:52] <pcjc2> Can't sleep, so debugging
[03:52] <pcjc2> Am I right in thinking gnome-compiz-preferences does not play nicely with Compiz in Gutsy?
[04:15] <pcjc2> Bryce: RE. XV on 965, isn't there an Ubuntu patch applied which fixes that?
[04:39] <ubotu> New bug: #155619 in xorg (main) "I cannot set my screen resolution above 640x480@50hz although my HW supports much better." [Undecided,New] https://launchpad.net/bugs/155619
[05:38] <tepsipakki> bryce: note that I crossposted that email :)
[05:38] <tepsipakki> to: debian-x cc: ubuntu-x
[05:43] <tepsipakki> alioth == alioth.debian.org, aka. git.debian.org
[05:44] <tepsipakki> bryce: also, I had a quick chat with gravity about FOSSCamp etc
[07:05] <ubotu> New bug: #155664 in xserver-xorg-video-ati (main) "radeon 9200 Pro xorg server can't do 1600x1200 resolution in gutsy Gibbon" [Undecided,New] https://launchpad.net/bugs/155664
[08:55] <ubotu> New bug: #155685 in xorg (main) "failsaveXServer fails" [Undecided,New] https://launchpad.net/bugs/155685
[09:31] <ubotu> New bug: #155698 in xorg (main) "gutsy does not autodetect graphic card and screen" [Undecided,New] https://launchpad.net/bugs/155698
[09:55] <ubotu> New bug: #155704 in xserver-xorg-video-intel (main) "Can not play video, totem hangs" [Undecided,New] https://launchpad.net/bugs/155704
[10:11] <ubotu> New bug: #155708 in xserver-xorg-video-ati (main) "ATI Radeon 9250 hangs on boot" [Undecided,New] https://launchpad.net/bugs/155708
[11:20] <ubotu> New bug: #155735 in xserver-xorg-video-ati (main) "gamma setting is lost after suspend/resume" [Undecided,New] https://launchpad.net/bugs/155735
[12:51] <ubotu> New bug: #106087 in scim "Gaim and Firefox can't get input from keyboard. (dup-of: 66104)" [Low,New] https://launchpad.net/bugs/106087
[13:35] <pcjc3> I bounced LP bug #149639 to the linux-source-2.6.22 package as it appears to have kernel panics as the underlying cause. I'm not sure what (if anything) I should edit in the description
[13:35] <ubotu> Launchpad bug 149639 in linux-source-2.6.22 "Xorg crashes very frequently" [High,Confirmed] https://launchpad.net/bugs/149639
=== pcjc3 is now known as pcjc2_
[13:37] <tepsipakki> most likely broken hardware
[13:37] <tepsipakki> testing an older release should tell
[13:40] <pcjc2_> Or it could be a driver bug?
[13:41] <pcjc2_> I'll ask them to test a Feisty LiveCD
[13:44] <pcjc2_> I added that they should check memtest86 and if it crashes, look out for overheating in the BIOS monitoring pages
[14:19] <ubotu> New bug: #155743 in xorg (main) "[Gutsy] Gnome doesn't detect monitor change from landscape to portrait mode, nor does it offer a way to rotate the video output" [Undecided,Confirmed] https://launchpad.net/bugs/155743
[14:45] <ubotu> New bug: #66689 in xorg (universe) "misuses debconf" [Low,Confirmed] https://launchpad.net/bugs/66689
[14:55] <ubotu> New bug: #155780 in language-support-zh (main) "[Gusty] Installation of Chinese language support borks the keyboard (dup-of: 66104)" [Undecided,Confirmed] https://launchpad.net/bugs/155780
[16:23] <ubotu> New bug: #154859 in xserver-xorg-video-intel (main) "xrandr (or X) can't drive 2nd screen at 1920x1200 anymore" [Undecided,Incomplete] https://launchpad.net/bugs/154859
[16:49] <rawler> quick question about ubotu; how exactly should I read the announcements?
[16:49] <rawler> when I follow many of the "new bug"-links, it's not actually a new bug?
[17:59] <bryce> rawler: in the brackets it indicates the state
[17:59] <bryce> if you see [Undecided,New] then it's _usually_ a new bug
[17:59] <bryce> otherwise, it's either been recently moved into x* from 'ubuntu' or other areas, or it's recently had a noteworthy change
[18:18] <ubotu> New bug: #151168 in linux-restricted-modules-2.6.22 (main) "memory leak with ring" [Undecided,New] https://launchpad.net/bugs/151168
[19:49] <ubotu> New bug: #155910 in xorg (main) "screen wont allow resolutions but the highest resolution" [Undecided,New] https://launchpad.net/bugs/155910
[20:29] <_jz> hello
[20:30] <_jz> anyone has an insight on that weird bug : https://bugs.launchpad.net/compizsettings/+bug/108527 Gutsy + radeon + compiz -> repetitive xorg freezes
[20:30] <ubotu> Launchpad bug 108527 in xserver-xorg-video-ati "X freezes when compiz is enabled on ATI cards" [High,Confirmed] 
[20:30] <_jz> i had 7 today :(
[20:30] <_jz> ah :)
[20:30] <_jz> i am available if i can help diagnose anything
[20:30] <_jz> put any debug variable anywhere
[20:31] <tepsipakki> _jz: are you still running 7.04?
[20:31] <_jz> nope
[20:31] <_jz> it happens since i upgraded (yesterday) to 7.10
[20:32] <_jz> it was quite a messy upgrade.. had to manually remove some packages before it accepted to upgrade, but then it went OK and i had to redo the dualhead config, etc. 
[20:32] <_jz> put my old xorg.conf file, maybe i should start tweaking there  ?
[20:32] <_jz> do you want to see it ?
[20:32] <tepsipakki> yes
[20:34] <_jz> http://pastebin.com/m7a089f6
[20:34] <_jz> had the problem using default 16 and default 24 depth
[20:35] <tepsipakki> uh
[20:35] <tepsipakki> why do people play with the options :)
[20:35] <_jz> this is what i had to do to make my dual head work with feisty
[20:35] <_jz> if you have some other config file to suggest i'd be glad
[20:36] <tepsipakki> yes, a clean one
[20:36] <_jz> maybe one could ask to people reporting that bug if they are using a vanilla Gutsy, or if they upgraded from feisty ?
[20:36] <tepsipakki> move it aside to see if it still crashes
[20:36] <_jz> how can i find one (that will work with my dual head) ?
[20:36] <tepsipakki> try without dualhead
[20:36] <_jz> i can't _live_ without dualhead :((
[20:36] <_jz> but if it's for the cause.... 
[20:36] <tepsipakki> besides, the driver in gutsy doesn't support mergedfb anymore
[20:36] <tepsipakki> see the releasenotes
[20:37] <_jz> ho yes i see this
[20:37] <_jz> so i used the xrandr on top of it
[20:37] <_jz> how can i get the plain vanilla gutsy config file ? 
[20:37] <_jz> any dpkg-reconfigure something ?
[20:37] <tepsipakki> dpkg-reconfigure xserver-xorg
[20:37] <tepsipakki> or just running dexconf should do
[20:38] <_jz> it put me a vesa card :(
[20:39] <_jz> i need to put a few things to make it able to use compiz, don't i ?
[20:39] <tepsipakki> no
[20:39] <tepsipakki> just change the driver
[20:39] <_jz> ok
[20:40] <_jz> just this and 1280x1024 and Virtual 2560 x 1024
[20:40] <_jz> (pleaaaase? ;)
[20:40] <tepsipakki> it should calculate the virtual
[20:40] <_jz> it didn't previously
[20:40] <_jz> because it's off my max texture size
[20:40] <_jz> which was fine with previous compiz
[20:40] <tepsipakki> ok
[20:40] <_jz> it just didn't draw a background
[20:40] <_jz> and had to launch it with SKIP_CHECKS=yes
[20:41] <_jz> ok. i'll be back with compiz in a moment and will keep you informed.
[20:51] <_jz> so
[20:51] <_jz> i'm back. 
[20:52] <_jz> i put my keyboard layout to "fr", virtual, and the correct BusID (i think it got my integrated crap GPU instead of my ATI)
[20:52] <tepsipakki> you should disable the other one
[20:52] <tepsipakki> from bios
[20:52] <_jz> now the right monitor is 800x600, do I just have to wait for the crash ? Can I try xrander or something to get my dualhead working ?
[20:52] <tepsipakki> but it probably doesn't matter here
[20:52] <_jz> yes it's true but it's not the cause of the problem i think
[20:52] <tepsipakki> right
[20:53] <tepsipakki> most likely its a DRI bug in mesa for your hardware
[20:53] <tepsipakki> if everything is stable using !compiz
[20:53] <_jz> what horrifies me is that compiz is on by default now :(((
[20:53] <_jz> i _think_ it is
[20:54] <tepsipakki> some hardware is blacklisted
[20:54] <_jz> according to all the reporters... i was using it for one hour when i killed X to start again with compiz
[20:54] <_jz> mine isn't
[20:54] <tepsipakki> have you followed up on that bug?
[20:54] <_jz> it's a 03:00.0 VGA compatible controller: ATI Technologies Inc RV350 AP [Radeon 9600]
[20:54] <_jz> nope. i'm not registered on launchpad
[20:54] <tepsipakki> it will get lost here..
[20:55] <_jz> i'll try with the bugmenot account ;)
[20:55] <tepsipakki> then you can just wait 
[20:55] <_jz> but having my hardware blacklisted wouldn't be such a "solution" for me
[20:55] <tepsipakki> tough :)
[20:55] <_jz> because i can easily launch X without compiz
[20:56] <_jz> i'd rather have compiz working again (now i can't live without the exposé-like Scale plugin :/
[20:57] <tepsipakki> what I said, wait for hardy
[20:57] <tepsipakki> unless someone finds a fix for it
[20:57] <_jz> nono i'm a good citizen, i'll fill in my follow-up ;)
[20:57] <tepsipakki> which won't break anything else
[20:58] <tepsipakki> you could try other distros if you can reproduce it there
[21:00] <tepsipakki> now I need to watch some telly, sorry :) ->
[21:02] <_jz> OK it hang too with that vanilla config file :(
[21:02] <_jz> while ironically trying to configure my monitors
[21:03] <_jz> so it's useless to ask if it only does this with people who installed a brand new gutsy, or just with people who upgraded ?
[21:03] <_jz> i unfortunately don't have much time for testing other distros.. 
[21:03] <_jz> what is weird is that it worked like a breeze with feisty
[21:06] <ubotu> New bug: #155937 in xorg (main) "SHMConfig should be enabled by default, and gsynaptics should be installed by default on laptops" [Undecided,New] https://launchpad.net/bugs/155937
[21:07] <_jz> do you think it's useless / not a good idea for me to go back to my previous config file ?
[21:09] <bryce> hi guys
[21:20] <_jz> I'd love to be able to help diagnose this
[21:21] <_jz> does it come from the driver ? from xorg ? from mesa ? from compiz ?  how can i know ? :
[21:31] <bryce> one sec - reviewing backlog
[21:31] <tepsipakki> _jz: you could try disabling dri by putting 'Option "NoDRI"' for the driver
[21:31] <tepsipakki> hi bryce 
[21:31] <bryce> heya tepsipakki
[21:32] <tepsipakki> "my name is earl" rocks :)
[21:36] <tepsipakki> bryce: apparently the new upstream hal has added support for input-hotplug (ie. includes the fdi-file for it)
[21:36] <bryce> cool, yeah I heard
[21:37] <bryce> what's the implication of that?  anything we need to do to tie into it?
[21:37] <tepsipakki> I'm not sure..
[21:38] <tepsipakki> did try it once, maybe all it needed was to remove the InputDevice sections from the conf
[21:45] <ubotu> New bug: #155954 in xorg (main) "Xorg ATI driver somewhat supports ATI Radeon IGP " [Undecided,New] https://launchpad.net/bugs/155954
[21:55] <bryce> _jz, there are some additional tips for troubleshooting X freezes and crashes at https://wiki.ubuntu.com/DebuggingXorg
[21:55] <bryce> _jz, it sounds like the next step needing to be taken here is to get a backtrace with gdb
[21:56] <bryce> _jz, it's sort of technical to do that, but if you're wishing to assist in diagnosing the issue, that'd be extremely valuable here
[21:57] <_jz> the only problem is i don't have much time for now :/
[21:57] <_jz> maybe you could ask this in the bug report thread ?
[22:02] <bryce> done
[22:02] <bryce> _jz, anyway the issue comes from the driver, and if you wish to help diagnose it, the bug needs people to gdb it.
[22:14] <_jz> not sure it comes from the driver : some people reported about the same with fglrx
[22:14] <pcjc2> hi all.
[22:15] <pcjc2> Reporter for bug #50048 says it works in 7.10, should that be resolved as "Fix released" or "Invalid"?
[22:15] <ubotu> Launchpad bug 50048 in xserver-xorg-video-i810 "Unable to adjust refresh rate.." [Low,Incomplete] https://launchpad.net/bugs/50048
[22:18] <bryce> _jz, it's not uncommon to see identical symptoms on different drivers, but these kinds of problems are generally due to driver code problems
[22:18] <_jz> ok
[22:18] <_jz> but how to explain that it worked on feisty ?
[22:18] <bryce> _jz, in any case, since fglrx is a binary proprietary driver, we wouldn't have any luck running it in gdb since we don't have access to the code anyway
[22:19] <_jz> sure
[22:19] <_jz> fglrx sux big times (like any proprietary driver)
[22:19] <bryce> on feisty we were using the 6.6.x driver
[22:19] <_jz> is there maybe a way i could go back to that driver, so we could see if it comes from here ?
[22:20] <bryce> 6.7.x includes a fairly significant rewrite of some areas, which made many bugs go away, but brought some new ones
[22:20] <bryce> maybe you could test a 6.6.x version of the driver to see if it still works. 
[22:20] <_jz> how could I do this ? i guess that just forcing a dpkg -i of the feisty package wouldn't do it ?
[22:20] <_jz> or would it ?
[22:21] <bryce> possibly; I'd grab one from say Gutsy-tribe-1
[22:21] <bryce> or... hmm
[22:21] <bryce> tepsipakki: do you remember which tribe we put xserver 1.3 in?
[22:22] <_jz> no people reported the problems with early versions of gutsy i think
[22:22] <tepsipakki> bryce: before tribe-1, but its the same ABI anyway so the feisty version should work AIUI
[22:22] <bryce> ah ok
[22:23] <tepsipakki> note that the reporter had this problem with feisty
[22:23] <_jz> but i didn't !
[22:23] <_jz> there is a slight variation in the bug
[22:23] <_jz> mouse moving or not upon freeze
[22:23] <tepsipakki> then it's a different bug
[22:24] <bryce> ah, then sounds like there could be multiple bugs here
[22:24] <_jz> mine is not moving, unlike the first reporter
[22:24] <bryce> it's not uncommon for completely different bugs to have nigh-identical symptoms
[22:24] <_jz> but all other symptoms and conditions are completely identicals... 
[22:24] <bryce> yeah, whether the mouse moves or not is a fairly significant difference for X problems
[22:25] <_jz> well... the not-moving-mouse version of the bug didn't happen here in feisty
[22:25] <bryce> also, whether or not the caps lock key toggles, whether or not you can switch to a tty, and whether or not you can ssh or ping the machine
[22:25] <_jz> i had a very few freezes, but then it was the whole machine freezing, with no ssh, nothing, so it was unrelated
[22:25] <_jz> no tty switch, i didn't test for the caps lock !
[22:27] <bryce> of course, on the other hand, sometimes the same root bug will cause very different symptoms on different hardware
[22:27] <bryce> like, screen corruption for one class of hardware, blank screen for another, etc.
[22:27] <bryce> anyway, I gotta go run and get a haircut.  bbiab
[22:27] <_jz> how can i rollback one xorg version ?
[22:28] <_jz> hehe a haircut is a too rare event for a developper for you to miss ;)
[22:28] <_jz> (crappy syntax, but you see my point ;)
[22:28] <bryce> can't be too shaggy for UDS ;-)
[22:28] <bryce> you can install older versions like this:
[22:28] <bryce>  apt-get install xserver-xorg-core=2:1.3.0.0.dfsg-4ubuntu
[22:29] <bryce> or use dpkg -i
[22:29] <_jz> if you're not you'll get noticed ;))
[22:31] <pcjc2> My launchpad profile pic (short hair) is way out of date
[22:31] <pcjc2> its down to my shoulders now!
[22:31] <_jz> E: Version '2:1.3.0.0.dfsg-4ubuntu' for 'xserver-xorg-core' was not found
[22:32] <_jz> do I have to enable a special repository for this to work ?
[22:32] <pcjc2> If there is an UDS in the UK some time, I'll have to visit
[22:32] <tepsipakki> _jz: gutsy only has one, so yes. or fetch the deb
[22:32] <tepsipakki> one such package
[22:33] <_jz> hmm... it may sound stupid, but i can't find it
[22:35] <tepsipakki> and I don't know what version you were supposed to test:)
[22:35] <_jz> one from feisty
[22:35] <_jz> the last one from feisty should do it 
[22:36] <tepsipakki> you'll find it (1.2) from archive.ubuntu.com
[22:36] <tepsipakki> pool/main/x/..
[22:37] <_jz> OK thanx
[22:37] <tepsipakki> there could be some dependancy problems
[22:37] <tepsipakki> but I bet you'll notice
[22:38] <_jz> ouch :/
[22:38] <_jz>  xserver-xorg-core_1.3.0.0.dfsg-12ubuntu8_i386.deb   is ok ?
[22:38] <tepsipakki> that's what you have
[22:38] <_jz> ha ok ...  xserver-xorg-core_1.2.0-3ubuntu8_i386.deb then ?
[22:39] <tepsipakki> likely
[22:39] <pcjc2> tepsipakki: How should I close #50048
[22:39] <_jz> wow no dependency problem ! amazing ! :)
[22:40] <tepsipakki> pcjc2: "fix released" i guess
[22:40] <tepsipakki> or if it can't be pinpointed "invalid"
[22:41] <tepsipakki> although, since there were others who had the same issue, "fixed" is more appropriate
[22:41] <_jz> I won't relaunch X right now, so i'll keep you informed tomorrow
[22:41] <_jz> thanx for helping me helping you ! (hey sounds like "ubuntu" to me ? ;)
[22:42] <tepsipakki> np
[23:15] <ubotu> New bug: #155985 in xorg (main) "[gutsy] performance regression with i915 xorg driver (glxgears in liveCD or after HD install) " [Undecided,New] https://launchpad.net/bugs/155985