Summary: | Xnest crashes in damagePaintWindow() | ||
---|---|---|---|
Product: | xorg | Reporter: | Roland Mainz <roland.mainz> |
Component: | Server/DDX/Xnest | Assignee: | Xorg Project Team <xorg-team> |
Status: | RESOLVED FIXED | QA Contact: | |
Severity: | blocker | ||
Priority: | high | CC: | ago, config, eich, ikaro, keithp, kem, roland.mainz, stuart.kreitman |
Version: | git | ||
Hardware: | x86 (IA32) | ||
OS: | Linux (All) | ||
Whiteboard: | |||
i915 platform: | i915 features: | ||
Bug Depends on: | |||
Bug Blocks: | 351 |
Description
Roland Mainz
2004-07-31 21:10:29 UTC
I have not been able to reproduce this one on an IA-32 box. There have been quite a few changes since the bug report was filed, so I don't know if this still occurs. Please verify that it still happens on your AMD64 box. Keith Packard made a comment in bug 1032 that perhaps DamageSetup was not being called, which might have been happening here as well before Keith checked in his new damage based misprite code (which calls DamageSetup for xnest). That would explain why it failed previously and now seems to work. Xnest seems to work again with 2004-08-11-trunk on IA32, I still have to test AMD64 when I am back... Xnest was initializing the screen in the wrong order. I fixed that and it seems to work fine now. I also fixed Damage to deal with Xnest's lack of pCompositeClip in GCs and the lack of window pixmaps. Xnest will need significant redesign to support Composite though. *** Bug 1292 has been marked as a duplicate of this bug. *** |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.