=== mvo_ is now known as mvo [14:42] Hi. [14:44] I'm looking for someone who knows anything about 107_fedora_dont_backfill_bg_none.patch [14:44] I suspect it's only there to help with Xgl, which is largely unused nowadays [14:44] Pretty much every driver provides its own texture_from_pixmap implementation [14:45] This patches introduces graphical corruption with compositing enabled; we've had quite a bit of users complaining about it [14:46] s/patches/patch [14:46] Plagman, I can't comment on the patch particularly, but the people who would be responding to it later would probably ask, we being Ubuntu users? [14:47] Plagman: it's still shipped by fedora, and was added to the package a long time ago, so no-one here knows the details why it was added [14:48] we equals NVIDIA X driver team [14:49] People like to say it's our bug as well. :/ [14:50] Plagman: any way to reproduce with 177.80? [14:50] sure [14:50] you'll need a compositing manager running [14:50] check [14:51] basically, any newly created window should briefly flash black [14:51] (or random colorful corruption if you're using InitialPixmapPlacement=2) [14:51] if you start firefox, you should get a black square before the first expose [14:51] i've seen that particularly with bigger windows like FF on my nvidia cards but never thought much of it [14:52] right, me too with FF [14:52] people don't usually complain about it with default IPP settings [14:52] but with InitialPixmapPlacement=2, the graphics memory isn't initialized so they get whatever was there at the time [14:53] whereas the contents of the backing pixmap should really be initialized to whatever is behind it [14:53] using that block that's removed by the patch I'm talking about [14:54] it was added to the fedora xserver version 1.0.99.2-1 [14:54] by krh [14:55] oh, okay [14:55] I'll just email him then [14:56] tjaalton, but it didn't actually land upstream? [14:56] superm1: nope [14:56] of course not :/ [14:56] it removes functionality [14:56] as I see it, it's mostly an ugly hack to make Xgl faster at the cost of correctness [14:56] actually, I did drop it from 2:1.2.0-3ubuntu1, but re-enabled because people complained about performance regressions [14:57] with what drivers did they see regressions? [14:57] heh, can't remember.. it was 1,5 years ago [14:58] and the changelog entry doesn't help either [14:59] munckfish: hey, the daily ps3 image doesn't work :) [14:59] perhaps it will be worthwhile to test via an SRU for regressions against a handful of drivers then after Gold [15:00] tjaalton: the desktop one doesn't nope - I just tested it this weekend [15:00] but the alternate one does [15:00] and if perfromance regressions are still present just drop the SRU. [15:00] munckfish: damn, another 2h download it is then :) [15:00] I'll contact Kristian about the original intent of the patch and its meaningfulness as of today [15:00] usplash is knackered for some reason and the desktop installer didn't have it disabled [15:00] last time it was built [15:00] Plagman: that would help [15:00] If we agree that it doesn't make sense to keep it, who do I copy here to make what you said happen? [15:01] munckfish: but shouldn't "install" run the text-mode installer? [15:01] tjaalton: other than that once it's up and running it's really quite nice [15:01] tjaalton: no it runs ubiquity I think [15:01] Plagman: me and bryce for instance [15:01] munckfish: bah [15:02] sounds good [15:02] thanks for the quick feedback [15:02] np [15:19] damn, krh is off on vacation [15:23] you could try ajax then [15:24] I guess I could [15:28] I'm not really familiar with the Ubuntu release/update management process; even if this patch was proved to be harmful, would there be a realistic hope of the X server in final 8.10 not having it? Or maybe in a subsequent update? I realize it's pretty late for that right now. [15:29] no chance to get in the final release [15:29] but an update is possible if dropping it doesn't break anything [15:31] I see. [15:31] afk for 4h -> [16:03] heya [16:12] well, ajax doesn't want the patch gone [16:13] apparently most drivers suffer from this [16:14] it's not a performance problem on our side, though; we'll discuss options internally [16:14] thanks for the help === james_w` is now known as james_w [18:41] tjaalton: welcome :) [21:56] Hrmm. X doesn't like having key repeat settings set with HAL managing devices. [22:27] jcristau: thanks :)