/srv/irclogs.ubuntu.com/2010/07/12/#ubuntu-x.txt

TakyojiIs there any further information that I should (and am able to) disclose for this bug report? https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/60419200:12
ubot4Launchpad bug 604192 in xserver-xorg-video-intel (Ubuntu) "Screen goes blank and flashes vertical stripes on 1s interval (affects: 1) (heat: 6)" [Undecided,Confirmed]00:12
RAOFSarvatt: Rock on, dude, thanks!  We've been publically targetting xserver 1.9 since UDS, and it looks like it's going to be in a better state than 1.8 anyway.00:38
RAOFTakyoji: An i845 chip?  Dear lord, I'm surprised it works at all :/00:39
RAOFTakyoji: If you're prepared to do a bunch of work, though, that bug looks like it would be amenable to a regression analysis via bisection.00:40
Takyojiout of curiosity, how would it not be able to work? :P00:44
Takyojialso, is there any specific guide(s) available for regression analysis?00:45
RAOFHm.00:50
RAOFI'm not sure if we've got a bisection howto page on the wiki.  Let me check.00:51
RAOFTakyoji: The basic principle would be to: (a) Check which component is broken (options here are xserver-xorg-video-intel, the kernel, mesa, or libdrm).00:51
RAOF(b) Check out the git source of that component, and run "git bisect" to rebuild it at different points between 9.10 and 10.04 to work out precisely when it broke.00:52
RAOFTakyoji: https://wiki.ubuntu.com/X/Bisecting is a bit of an overview; there's also the bisecting mesa page linked from there.01:04
Takyojiahh, alrighty01:05
TakyojiSo I don't even have to overlook the source code then; just simply find what exact revision broke it?01:07
RAOFRight.01:09
RAOFYou can do that without needing to know anything about the source.01:09
RAOFFirst off, though, you need to know which component broke, so you'll want to try each of the 9.10 components in 10.04, one at a time.01:10
TakyojiSo first I have to verify which component it even is, before going through bisecting, correct?01:16
RAOFTakyoji: Yes.  Because you need to be able to identify a good point and a bad point in the same source.01:35
RAOFThen you can run a bisection over that git history.  If you don't have a good *and* a bad point in the same git source then you can't checkout the commit half way between, work out whether it's good or bad, and then repeat.01:40
=== bryceh is now known as 40FAA7E1T
=== 40FAA7E1T is now known as bryyce
RAOFAlright ladies and gentlemen!  Let your i8xx gpus feast on the joy that is https://edge.launchpad.net/~raof/+archive/aubergine09:31
RAOFEveryone *else* who feels like a test could ensure that it doesn't break your working Intel GPU.09:39
Duke`what's the difference with xorg-edgers?09:41
RAOFThe re-introduction of a legacy, non-GEM UMS codepath.09:44
RAOFie: work around the various longstanding breakages on i8xx cards which were caused by assuming various bits of the hardware actually worked by not using it.09:45
bryyce\o/10:31
vishdo we install the nvidia-settings package by default for all nvidia users?11:37
tseliotvish: the nvidia packages recommend nvidia-settings11:46
tseliotit's treated as a dependency11:47
vishtseliot: ah ok , thanks11:47
tseliotvish: BTW did the gtk guys reply to your request to integrate my patch for that papercut now that we know that Orca would work fine?11:48
vishtseliot: yeah , i'll have to poke ebassi again today..11:49
tseliotvish: ah, good11:49
vishhe was the one who requested review from accessibility folks11:49
tseliotok, let's see if he decides to include the patch now or if he has further requests11:50
=== freeflyi1g is now known as freeflying
scar_what's the most stable 2.6.35 kernel? I've tried the one that comes with mavrick alpha2 and I've tried lucid with linux-image-2.6.35-7-generic-pae. I know this is bit off topic but I'm trying to test xorg-edgers' nouveau driver so I need a 2.6.35 kernel16:17

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!