[03:21] tjaalton: btw I've added links to dsc files at http://bryceharrington.org/X/PkgList/versions_current.html [09:58] bryce: xorg-server rc1 already has the patches you added/modified, and it's the next version that'll be uploaded :) [10:07] tjaalton: well maybe 155 but not 156 [10:08] bryce: yes, you're right [10:09] I had to sort out 155 to understand 156, so wasn't a complete waste of time ;-) [10:14] good :) [10:27] btw, I also looked at 107 some more and reviewed all the comments around it in the upstream tracker [10:27] and I'm much less convinced now that we're going to be able to leave it disabled [10:27] still, it'll be worth the experiment just in case [10:27] (ajax's commentary in particular) [10:37] yeah.. [10:37] what's the upstream bug again? [10:41] LP: #254468, http://bugs.kde.org/show_bug.cgi?id=170462 [10:41] KDE bug 170462 in compositing "Video garbage when drawing new object (Comment #54)" [Normal,Reopened] [10:41] right, I remember that discussion :) [11:10] yes, the problem is solved by removing a patch [11:13] tseliot: what you missed was: [11:13] 12:27 < bryce> btw, I also looked at 107 some more and reviewed all the comments around it in the upstream tracker [11:13] 12:27 < bryce> and I'm much less convinced now that we're going to be able to leave it disabled [11:13] 12:27 < bryce> still, it'll be worth the experiment just in case [11:13] 12:28 < bryce> (ajax's commentary in particular) [11:14] tjaalton: ah, ok so it's likely that we'll leave the patch in the package, right? [11:15] tseliot: could be, yes.. the next upload will disable it though [11:15] ok, let's experiment a bit then [11:15] to see what the performance hit is [11:15] right [13:55] tjaalton: any chance of those X packages today? [13:57] Alexia_Death: not before alpha3 is released [13:58] tjaalton: ok :) [14:00] jcristau: thinking about adding linux-libc-dev to the xserver-xorg-dev Deps, since that's where the drm headers are going in Debian too (sometime)? [14:17] bryce: thanks for bumping the importance of the drm header issue .) [14:17] :) [15:08] heh, so now the intel pageflipping support is being removed from mesa, and AIUI it's closely related to the drm header mess.. I'll try to see if the patch makes mesa build against current headers [15:13] and if it really is broken old code, it should be removed from the ddx driver too.. [15:16] oh, and there's a patch sent to intel-gfx@ [16:37] bryce, you had an autofire off on bug 315588. i wont be able to get lspci, but all the information you would get from it should be available elsewhere in the bug [16:37] Launchpad bug 315588 in xserver-xorg-video-vesa "Hardware w/ 1600x900 LCD does not boot up using vesa" [High,Incomplete] https://launchpad.net/bugs/315588 [16:39] anyone know where to get the updated synaptics driver to use an elantech touchpad? [16:40] seems like a resounding no === You're now known as ubuntulog [17:50] hey bryce [18:56] anyone familiar with synaptics around here? [18:57] where is the best place to report bugs or odd behaviour on the nvidia-settings program? [18:58] BUGabundo1: launchpad [18:58] launchpad.net/ubuntu/+source/nvidia-settings likely [18:59] tjaalton! [18:59] solarion: I've no knowledge, sorry :) [18:59] don't have one [19:00] I was just saying hey. :) [19:00] though if you happen to know what version of the synaptics driver supports elantech touchpads, I'd be glad for the knowledge. :) [19:01] ah "You will need Xorg Synaptics driver 0.99.1 or newer (0.99.2, 0.99.3) to interoperate with the 2.6.28 kernel Elantech driver! " [19:01] oh, jaunty still has 0.15 [19:01] 0.15.2 to be precise [19:01] can I has? :) [19:02] * solarion would love to frickin' finally be able to use his touchpad as Asus intended [19:02] not before alpha3 is out [19:03] and the backlog is loong [19:03] aww. :( [19:03] do you know why the mouse (without synaptics support) would be jerky? [19:03] seems to snap to some invisible, non-1-pixel grid [19:04] the xorg backlog in ubuntu, or jaunty backlog in general? [19:04] xorg [19:04] we have a few packages to update [19:04] ah [19:04] libdrm, mesa, intel, xserver ... [19:04] * solarion looks forward to the updates [19:05] is this related to the new intel modesetting(?) code drop in the kernel? [19:05] no, jaunty won't have that [19:05] what's holding things up? [19:05] it needs 2.6.29 [19:05] ah, and jaunty is 2.6.28? [19:05] yes [19:06] and will be [19:06] *remain [19:06] aww. Even though .29 should be released before 9.04? [19:06] still way too late [19:06] yeah, I was 'fraid of that [19:06] what's the holdup on the packages? [19:07] (i.e. the cause of the aforementioned backlog) [19:08] the drm headers are now provided by the kernel (linux-libc-dev), but the userspace expects to see the latest goo [19:08] so -intel and mesa fail to build [19:08] coding stuff then, not testing [19:08] but in fact the reason seems to be that they both contain stale code that never got in the kernel drm [19:08] yes [19:08] aww [19:09] * solarion has time to maybe do minor testing, but not any coding [19:09] * solarion heads to lunch [19:09] well, these will hopefully fix a few problems [19:11] tjaalton: what does xserver-xorg-dev need that's moving to the kernel? [19:11] jcristau: the drm headers, ie. linux-libc-dev. otherwise the drivers should depend on it [19:12] the drivers that include drm headers should build-dep on it, yeah [19:12] ok, the description is a bit misleading then :) "Unless you are developing or building a driver.." [19:13] I mean, does it hurt to have the drm headers installed, compared to adding the dep to the ones that need them= [19:13] ? [19:13] I'm fine with either approach, it's a one-time change anyway.. (hopefully) [19:16] it doesn't hurt, no. i just find it ugly :) [19:17] ugly to put in x-x-dev?-) [19:17] ah, yes [19:19] or maybe libdrm-dev should depend on it [19:20] since it #includes drm.h [19:20] that would be Clean :) [19:30] hey bryce_ [19:31] jbarnes confirmed that the correct approach to make intel & mesa to build again is to drop the pageflipping code from both [19:31] ok [19:31] yeah I saw th ebug. I assume you know the patch or change he's referring to? [19:32] yep [19:32] it was on intel-gfx@ [19:33] ok cool [19:33] and the mesa patch on mesa3d-dev@ [19:36] hi guys [19:37] are we getting libdrm 2.4.3 in jaunty soon? [19:37] no, but maybe 2.4.4 :) [19:37] when alpha3 is released [19:37] cool :) [19:37] alpha3? today? [19:38] btw, today I'm heya tormod [19:38] :P [19:38] heh [19:39] bryce_: grammar? :P [19:40] I guess after libdrm 2.4.4, there will be intel 2.6.0 ? [19:40] yes [19:41] because the new libdrm basically breaks the current intel [19:41] horse and carriage [19:41] love and marriage [19:44] tormod: sorry was in the middle of saying something else [19:44] today I'm downtown with some canonical/community folks. pdx conclave sort of thing [19:44] bryce_: np, I got that [19:45] so will be focusing on hotkey stuff today [19:45] next week, my dad is unfortunately going to be in the hospital for surgery, so I'm going to be taking some time off [19:46] anyway, so to say I may be semi-AWOL for about the next week or so [19:47] oh, take care.. [19:48] best wishes === mvo__ is now known as mvo [22:18] wgrant: hey, I've merged synaptics in git.. could you check if the modifications in the fdi file were ok? synced that with upstream.. [22:19] tjaalton: Sure, looking now... I'd been meaning to do that myself, but I've been rather tied up with work :( [22:21] I think we'll need to alter the defaults a bit, as they're changed significantly from what we have always had. [22:22] ok.. upstream dropped the "match vendor" bits completely, so it'll need some work if you still want to do that [22:22] That fdi file looks good. [22:23] I mean defaults like disabling edge-scrolling if we can detect multi-finger taps. [22:23] ah, ok [22:25] hrm, mesa build still fails even with the no-pageflipping patch [23:01] :-/ [23:42] btw I spoke with slangasek about hotkey bugs and a default place to put them if we don't know where they actually belong... he suggests filing them against hal [23:48] slangasek says alpha3 is now released