Summary: | Display corruption when using iceWM | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Product: | xorg | Reporter: | Jaime Velasco Juan <jsagarribay> | ||||||||||
Component: | Driver/nouveau | Assignee: | Nouveau Project <nouveau> | ||||||||||
Status: | RESOLVED WORKSFORME | QA Contact: | Xorg Project Team <xorg-team> | ||||||||||
Severity: | normal | ||||||||||||
Priority: | medium | ||||||||||||
Version: | 7.3 (2007.09) | ||||||||||||
Hardware: | x86-64 (AMD64) | ||||||||||||
OS: | Linux (All) | ||||||||||||
Whiteboard: | |||||||||||||
i915 platform: | i915 features: | ||||||||||||
Attachments: |
|
Description
Jaime Velasco Juan
2008-01-09 09:58:47 UTC
Created attachment 13621 [details]
Xorg.log when running iceWM
Created attachment 13622 [details]
Screenshot which shows the problem
Created attachment 13623 [details]
Screenshot of the expected result (with nv)
Only IceWM has this problem? Does it also occur when randr12 is disabled? Yes, it only happens with icewm (well, I've never seen it with anything else) and yes, it happens with and without RandR12 Perhaps we should first debug why NoAccel causes a crash, please submit a xlog of that. Created attachment 14114 [details] [review] Fix NoAccel (and ShadowFB) I bisected the NoAccel issue, the problem was introduced with commit 2af4a28ae1df46686e264bcda417a896b7cfa59a Author: Ben Skeggs <skeggsb@gmail.com> Date: Fri Nov 16 09:18:33 2007 +1100 Hook up DMA funcs to channels/grobjs etc etc With this patch, NoAccel works again. Regarding the original bug with iceWM, I'm not able to test/do anything now, but hopefully will be the next week. Regards I pushed that patch. I'll keep an eye on this bugreport. I finally got to testing this again after reinstalling my OS and now I can't reproduce it. I've tried downgrading the xserver and using an old nouveau version, but it works fine now. I don't know where could be the problem, so I'll close the bug with WORKSFORSOME, sorry for the noise. |
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.