Bug 17601 - flicker on new window opening
Summary: flicker on new window opening
Status: RESOLVED NOTOURBUG
Alias: None
Product: xorg
Classification: Unclassified
Component: Driver/nouveau (show other bugs)
Version: git
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: Nouveau Project
QA Contact: Xorg Project Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-09-15 21:47 UTC by Andrey V. Panov
Modified: 2009-01-13 15:44 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments
Xorg log (243.50 KB, text/plain)
2008-09-15 21:47 UTC, Andrey V. Panov
no flags Details
xorg.conf (18.56 KB, text/plain)
2008-09-15 21:49 UTC, Andrey V. Panov
no flags Details

Description Andrey V. Panov 2008-09-15 21:47:33 UTC
Created attachment 18907 [details]
Xorg log

Start of new application window (especially based on gtk-2.14) under KDE 3.5 causes a short flicker stripes on CRT screen.
Comment 1 Andrey V. Panov 2008-09-15 21:49:05 UTC
Created attachment 18908 [details]
xorg.conf
Comment 2 Maarten Maathuis 2008-09-16 01:44:48 UTC
This is caused by gtk calling XRRGetScreenResources() on application start, which probes all outputs. The effect you see is caused by load detect. While it may be possible to avoid load detect, it is not by definition our bug. I'm leaving this to Stuart Bennett, who knows more about the code.
Comment 3 Stuart Bennett 2008-10-10 14:07:54 UTC
I've just pushed a commit that should reduce the load detect side effects "randr12: don't use in use (by another vga output) crtc for load detect (avoids flicker)". Obviously this still leaves the rather stupid behaviour of gtk, but you'll have to get someone else to fix that. So, please try using a updated git checkout and close the bug if the flicker is gone.
Comment 4 Stuart Bennett 2009-01-13 15:44:04 UTC
As noted in comment 2, this is due to a combination of xserver/gtk stupidity that really isn't the driver's fault.


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.