[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#565344: Found a second workaround



On Fri, 2010-02-12 at 16:50 +0100, Bruno Kleinert wrote: 
> Am Dienstag, den 02.02.2010, 16:08 +0100 schrieb Bruno Kleinert: 
> > A further experiment to collect information:
> > 
> > On the Intel notebook I tried blindly to restore gamma values from the
> > KMS framebuffer text console with DISPLAY=:0.0 xgamma -gamma 1.0 but
> > that didn't bring back neither the framebuffer console nor the X session
> > when I tried to switch to it.
> > 
> > Only Blindly unlocking the GNOME screensaver and issuing the xgamma
> > command restores the gamma values for the X session and also the KMS
> > framebuffer text. Btw.: Also at the framebuffer console when I issued
> > the xgamma command before, xgamma claimed that the gamma settings
> > already were all set to 1.0 for R, G and B.
> And some other news from tests:
> 
> After installing xserver-xorg-video-radeon and mesa 7.7, both from
> experimental, the AMD/ATI machine is able to run compiz (Works really
> surprisingly stable - but that's off topic here ;).
> 
> I installed compiz packages also on the Notebook with Intel GPU. To my
> surprise *both* machines could suspend and resume without any black
> screen at all! I don't have too many suspend/resume cycles until now,
> but ATM it seems as if both machines resume reliably when they're
> running compiz.

That might explain why I haven't seen the problem, as I run compiz
almost exclusively. :)


> * Software - that likely is - involved: Metacity, configured as
>         compositing manager (Use gconf-editor to
>         set /apps/metacity/general/compositing_manager to 'true') and
>         GNOME screensaver 

Does the problem also occur with Metacity with compositing disabled?
What about other window managers?


> My conclusion: It's hardware and driver independent, so it's likely to
> be a bug in the core xserver. ...and somehow the usage of AIGLX by
> compiz works around that issue.

If DRI2 is enabled on the Intel machine, compiz probably isn't using
AIGLX. I think it's more likely related to some kind of colourmap
related interaction unique to compiz or Metacity.


-- 
Earthling Michel Dänzer           |                http://www.vmware.com
Libre software enthusiast         |          Debian, X and DRI developer




Reply to: