[01:18] <cwillu> Well, I put out a donation request, and it looks like there's 18 different machines I can have by monday 
[01:35] <cwillu> ... and all but two are amd
[01:49] <cwillu> bryce, should I be able to mark bugs as triaged now?
[01:49] <cwillu> https://bugs.launchpad.net/xserver-xorg-video-intel/+bug/339781 is upstream
[01:49] <cwillu> with a patch
[01:53] <cwillu> (dupe of 339233, but I'd still like to know if I'm missing something :p)
[03:43] <cwillu> yay, I'm sick of confirming incomplete bugs!  \o/
[03:44] <cwillu> bryce, http://pastebin.com/f707dff7b
[05:11] <bryce> cwillu: yes you should be able to set Triaged now; let me know if not
[05:12] <bryce> cwillu: hey you're in Canada?  where abouts?
[05:14] <bryce> cwillu: wow you've had a busy day! http://people.ubuntu.com/~brian/complete-graphs/xserver-xorg-video-intel/plots/xserver-xorg-video-intel-week-incomplete.png
[08:09] <cwillu> bryce, heh, well, the scale exaggerates the slope a little :p
[08:10] <cwillu> planning on opening the umbrella bugs tomorrow, linking them up and putting the boilerplate on the statuses
[08:11] <cwillu> which will basically consist of going through all the confirmed bugs listed on the hugday paeg
[08:14] <cwillu> I'm from saskatoon saskatchewan
[08:17] <cwillu> re: triaged, I still can't.  I get the feeling that there was some inconsistency introduced, I don't think it's subscribing me to new bugs unless I actually subscribe to them by hand (although it was for a few hours)
[15:52] <BUGabundo> is bug 355671 known?
[16:04] <mnemo> not sure... but I have a vague probably that DRI has been disabled on one of the early intel chipsets as a workaround for SEGV in x.org start
[16:04] <mnemo> bryce or timo would probably have a better answer
[16:05] <BUGabundo> for ibex too?
[16:05] <BUGabundo> or just jaunty?
[16:05] <BUGabundo> this user is on ibex, I think
[16:05] <mnemo> oh, in that case I have no idea
[16:05] <mnemo> im talking about jaunty
[16:06] <BUGabundo> yeah, that I know
[16:07] <mnemo> bryce uploaded a new intel driver for intrepid on 30th of march
[16:07] <mnemo> fixing bug #320893
[16:07] <mnemo> according to "aptitude changelog xserver-xorg-video-intel"
[16:09] <BUGabundo> but that isn't even the card that alfatec has
[16:09] <mnemo> look at the diff, maybe this bugfix introduced a regression for alfatec's card?
[16:10] <BUGabundo> maybe
[16:11] <mnemo> sounds like he just updated one of the patch files in the package though
[16:11] <mnemo> "Update 104_i830-vbt-timing-hack.patch to final version taken upstream"
[16:11] <mnemo> etc
[16:12] <BUGabundo> alfatec: can you pastebin your changelogs?
[16:12] <BUGabundo> /usr/share/doc/xserver-xorg
[16:13] <jcristau> ym /u/s/d/xserver-xorg-video-intel/
[16:13] <BUGabundo> eh... since I don't have intel... don't have that path.. lol
[16:13] <BUGabundo> alfatec: can you ?
[16:14] <alfatec> yes, just a minute
[16:15] <BUGabundo> just open that path with nautilus
[16:15] <BUGabundo> then open the changelog file, and then paste the content to http://paste.ubuntu.com
[16:15] <BUGabundo> and give us the link alfatec
[16:15] <BUGabundo>  !pastebin
[16:19] <alfatec> http://paste.ubuntu.com/144967/
[16:19] <alfatec> is that correct ?
[16:20] <mnemo> hmm so you dont have the most recent intrepid version
[16:20] <mnemo> and bryce's upload from 30th march was a fix some an issues that some update caused
[16:20] <mnemo> i'd say it's worth a shot to install the latest version and see if that works
[16:21] <BUGabundo> afaik alfatec has every update availble to him on ibex
[16:21] <BUGabundo> unless he is on an old mirror
[16:21] <BUGabundo> alfatec: what mirror are you using?
[16:22] <mnemo> BUGabundo: this is what I see inside "aptitude changelog xserver-xorg-video-intel" for ibex --> http://paste.ubuntu.com/144971/
[16:23] <alfatec> https://neacm.fe.up.pt/ubuntu
[16:23] <BUGabundo> that would mean he has at least 4 updates lacking
[16:23] <BUGabundo> it can't be...
[16:24] <BUGabundo> alfatec: can you please pastebin your /etc/apt/sources.list
[16:24] <alfatec> ok
[16:24] <mnemo> alfatec: also pastebin the output of "dpkg -l | grep intel" please
[16:25] <alfatec> http://paste.ubuntu.com/144973/
[16:25] <mnemo> heh, what is "http://ppa.launchpad.net/intel-gfx-testing/ppa/ubuntu jaunty main
[16:25] <BUGabundo> deb http://ppa.launchpad.net/intel-gfx-testing/ppa/ubuntu jaunty main
[16:25] <mnemo> " ?
[16:25] <BUGabundo> jaunty?????
[16:26] <BUGabundo> mnemo: ehehe
[16:26] <BUGabundo> alfatec: come on.... you did it again?????
[16:26] <alfatec> http://paste.ubuntu.com/144974/
[16:26] <mnemo> we've all been newbies ;)
[16:27] <BUGabundo> 2:2.4.1-1ubuntu10.4
[16:27] <BUGabundo> that's not the version you mentioned in the bug
[16:27] <alfatec> O:-)
[16:27] <BUGabundo> mnemo: he keeps doing it... did the same mistkare yesterday
[16:27]  * BUGabundo alfatec needs a good head smack
[16:27] <mnemo> i have "2:2.4.1-1ubuntu10.4" on my intel+ibex box
[16:28] <alfatec> sorry
[16:28] <alfatec> a give my self a head smack
[16:29] <BUGabundo> fix that, and revert the upgrade
[16:29] <alfatec> ok 
[16:29] <BUGabundo> then reboot, and re-run update-manager
[16:29] <BUGabundo> let us know how it went, so we can close the bug as invalid if that is the cause
[16:40] <alfatec> i have done that 
[16:40] <alfatec> i change my sources 
[16:40] <BUGabundo> does compiz works now?
[16:41] <alfatec> re run update-manager
[16:41] <alfatec> nop
[16:41] <alfatec> not working yet
[16:41] <alfatec> :
[16:41] <alfatec> :S
[16:42] <BUGabundo> what driver version do you have now?
[16:43] <alfatec> 2:2.5.1
[16:43] <BUGabundo> now its newer?
[16:43] <BUGabundo> $ compiz --replace
[16:43] <BUGabundo> works?
[16:43] <alfatec> i will try 
[16:44] <alfatec> hangs at the same place
[16:44] <jcristau> restarted X after update-manager?
[16:45] <BUGabundo> yeah that too
[16:47]  * albert23 thinks (EE) intel(0): Cannot support DRI with frame buffer width > 2048 explains the trouble
[16:48] <BUGabundo> alfatec: are you using dual monitor?
[16:52] <alfatec> i have to restart the X
[16:52] <alfatec> yesterday e try the dual monitor 
[16:56] <alfatec> could be the reason ?
[16:56] <BUGabundo> it shouldn't
[16:57] <BUGabundo> unless you saved it to xorg.conf
[16:57] <BUGabundo> pastebin that too
[16:57] <albert23> alfatec: the problem is the virtual setting in xorg.conf
[16:58] <alfatec> http://paste.ubuntu.com/144990/
[16:59] <BUGabundo> 		Virtual	2640 800
[16:59] <BUGabundo> I would run XFIX from recovery console
[16:59] <BUGabundo> just to be sure
[17:06]  * cwillu hides
[17:06] <BUGabundo> hey cwillu
[17:06] <cwillu> wassup?
[17:07] <BUGabundo> did you get a reply from bryce?
[17:07] <BUGabundo> he emailed me the other day, and I told him about your tests
[17:07] <cwillu> yep, that's why I'm here :)
[17:07] <BUGabundo> alfatec: ping
[17:07] <alfatec> i'm here
[17:08] <BUGabundo> alfatec: did you reconfigured X yet?
[17:08] <BUGabundo> cwillu: bryce aint here, I think
[17:08] <alfatec> i have a backup of xorg.conf 
[17:09] <alfatec> i will replace them 
[17:10] <BUGabundo> no need
[17:10] <BUGabundo> just let dpgk make one new
[17:19] <alfatec> it works :>
[17:19] <alfatec> yes
[17:19] <BUGabundo> nice
[17:19] <alfatec> recovery mode fix x
[17:19] <BUGabundo> lets close your bug
[17:19] <alfatec> then compiz --replace
[17:19] <BUGabundo> it was user action
[17:20] <alfatec> yep
[17:20] <alfatec> I am grateful for your help, I am of the first steps, but a great desire to learn. Thanks for the compliments patience
[17:20] <BUGabundo> you can enable it permenatenly on Appearance
[23:02] <cwillu-maemo> '''Two bugs can have identical symptoms, and still be unrelated.  Check that you have exactly the same chipset _before_ commenting (lspci -nn |grep -i vga).  An issue that isn't isolated to a particular chip usually can't be upstreamed, and so can't be fixed!'''
[23:02] <cwillu-maemo> bryce, thoughts on that wording?
[23:03] <mnemo> "bryce has been idle 17hrs 49mins 35secs"
[23:05]  * cwillu-maemo pokes him anyway
[23:05]  * cwillu-maemo pokes anyone else who is interwsh
[23:05] <cwillu-maemo> stupid touscreen...
[23:06]  * cwillu-maemo pokes anyone else who is interested too
[23:07] <mnemo> maybe it should say: run "lspci --n | grep -i vga" in a terminal
[23:07] <mnemo> -nn
[23:07] <mnemo> not --n
[23:08] <mnemo> and what are they going to compare that "lspci -nn" output with?
[23:09] <mnemo> bugs have chipset specified in different ways
[23:09] <mnemo> since we don't have a specific "chipset: blah" field
[23:09] <mnemo> im probably nitpicking though
[23:09] <cwillu-maemo> the lspci thay's already on the bug report in the cases i care about
[23:09] <mnemo> aah, you mean its listed as "lspci: blah"
[23:09] <cwillu-maemo> i'm trying to get them as consistent as possible
[23:10] <mnemo> thats great
[23:10] <mnemo> i've seen that on some of them
[23:11] <cwillu-maemo> most of the lspci's are from bryce, i'm just following his lead
[23:11] <mnemo> mmkay
[23:12] <cwillu-maemo> is there a syntax to bold stuff in launchpad descriptions?
[23:12] <mnemo> not that I know of
[23:14]  * cwillu-maemo starts hunting for injection attacks ;p
[23:15] <mnemo> I found a pango injection attack in a filename passed to eye of gnome once
[23:15] <mnemo> http://bugzilla.gnome.org/show_bug.cgi?id=555940
[23:16] <mnemo> thats when you know you got too much time on your hands ;P
[23:21]  * cwillu-maemo pokes mnemo with copious free time