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