On Tue, Sep 28, 2010 at 4:51 PM, Kristian Lyngstol <[email protected]>wrote:
> On Tue, Sep 28, 2010 at 10:29:34PM -0000, > [email protected] wrote: > > commit 912aac97f000028bda2391edb5b9e5880cef7494 > > > > Don't require both opengl and composite since opengl already requires > > composite. This can cause flicker or momentary black screen with some > > drivers. > > It shouldn't really make a difference when they end up depending on it > implicitly anyway, though. > It shouldn't, but it can which is mostly the drivers fault. It just makes more sense to clarify that opengl is already pulling in composite. The only time you should need to require composite is when you only need composite and do not need opengl. > Did you have a chance to dig into this, by any chance? Is it triggered by > re-ordering of plugins or something similar? What exactly flickers (ie: > startup or continually - I would assume startup, unless they hooks get > mixed up permanently). > No, I did not have a chance to go very far into it. It happens when toggling a plugin in ccsm. > Oh, and what drivers cause this? > I run the entire radeon stack from git, including kernel. It has not been causing black screen as often in the past months with latest driver bits. > I don't mind the walk-around for now, but I'd really like to get to the > bottom of why it's necessary to begin with. Nested and multiple > dependencies shouldn't cause flickering or black screens, so we must be > doing something wrong... > It's not a workaround really, it's more for clarity and to reduce the possibility of displaying any driver bug to the user. (When we eventually get our bug tracker up and running cleanly, stuff like > this needs to go into it so we can backtrace it, but until then that's just > an apropos) > > - Kristian > Yes, we also need to get some form of bug tracker going.
_______________________________________________ dev mailing list [email protected] http://lists.compiz.org/mailman/listinfo/dev
