Bug 1370791 - GTK3 windows appear with a black flash
Summary: GTK3 windows appear with a black flash
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: gtk3
Version: 28
Hardware: x86_64
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Matthias Clasen
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-08-27 10:11 UTC by Clemens Eisserer
Modified: 2019-05-28 19:06 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-05-28 19:06:53 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Clemens Eisserer 2016-08-27 10:11:02 UTC
Description of problem:

All GTK3-based applications first show up with a black window, before they are able to draw themself. It gives the distracting illusion of black flashing.

Evince print dialog (gtk3): https://www.youtube.com/watch?v=53JyFZMxjE0
Firefox file save dialog (gtk3): https://www.youtube.com/watch?v=3WDy-bI_-Qg

For comparison - a slow-motion video of an older version of Firefox still using GTK2 - where everthing works as expected:

Old Firefox file dialog (gtk2): https://www.youtube.com/watch?v=N-fjknZPPcU


Also when the window is resized, the new area by which the window has grown is also rendered black: https://www.youtube.com/watch?v=fhzENp3rkOo

The problem only seems to manifest when not using a compositor (e.g. xfwm)


Version-Release number of selected component (if applicable):


How reproducible:
Very, I am able to reproduce it on my Intel based laptop (fedora 24, SNA) as well as my mothers AMD netbook (fedora 23, glamor).


Steps to Reproduce:
1. Disable compositor
2. Use GTK3 with default theme
3. open a new dialog

Actual results:
The window first appears black

Expected results:
As with GTK2, the window should appear with correct background color


Additional info:

Comment 1 carstenmattner 2016-09-20 11:42:47 UTC
I can confirm, but it happens with a compositor (compton) here, and also under Weston and Sway, both being Wayland compositors. Where this happens the most, even under Wayland compositors, is when in Gtk3 X11 mode.

Where it doesn't seem to happen if it's a Wayland compositor and a proper Gtk3 Wayland invocation of an application. However, such Gtk3 Wayland apps have the issue that things like file dialogs are scaled and all widgets are zoomed out or zoomed in instead of proper resizing of widgets according to the grid.

This regression is disruptive enough that I cannot use stable Firefox and have to resort to Firefox ESR for Gtk2.

Comment 2 carstenmattner 2016-09-20 11:44:30 UTC
Clemens, do you mind re-submitting this upstream at https://bugzilla.gnome.org/? I see this on any Linux distro with 3.20.

Comment 3 carstenmattner 2016-09-20 11:51:04 UTC
Nevermind, I've filed a ticket with your report copied and referenced plus my comments because this is preventing me from using Gtk 3.20. Hope you don't mind: https://bugzilla.gnome.org/show_bug.cgi?id=771708

Comment 4 jeremy9856 2017-09-10 14:17:02 UTC
It happen for me with when I use the modesetting driver instead of the intel one.

Comment 5 Fedora End Of Life 2017-11-16 19:04:38 UTC
This message is a reminder that Fedora 25 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 25. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '25'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 25 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged  change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

Comment 6 Christian Stadelmann 2017-11-16 23:24:44 UTC
Still present on Fedora 27. I *think* this only affects XWayland windows, but no pure wayland windows.

Comment 7 Clemens Eisserer 2017-11-17 07:22:27 UTC
still there when using xfce+xorg in Fedora 26

Comment 8 carstenmattner 2017-11-17 08:07:36 UTC
Upstream bug: https://bugzilla.gnome.org/show_bug.cgi?id=771708

Comment 9 carstenmattner 2017-11-17 08:08:41 UTC
(In reply to Christian Stadelmann from comment #6)
> Still present on Fedora 27. I *think* this only affects XWayland windows,
> but no pure wayland windows.

It affects plain Xorg and XWayland.

Comment 10 Fedora End Of Life 2018-05-03 08:33:02 UTC
This message is a reminder that Fedora 26 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 26. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '26'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 26 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged  change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

Comment 11 Christian Stadelmann 2018-05-21 19:15:37 UTC
This issue is still present on Fedora 28 and can be easily reproduced using Firefox (which is using XWayland). Please update the version info accordingly.

Comment 12 Ben Cotton 2019-05-02 21:43:34 UTC
This message is a reminder that Fedora 28 is nearing its end of life.
On 2019-May-28 Fedora will stop maintaining and issuing updates for
Fedora 28. It is Fedora's policy to close all bug reports from releases
that are no longer maintained. At that time this bug will be closed as
EOL if it remains open with a Fedora 'version' of '28'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 28 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 13 Christian Stadelmann 2019-05-04 23:13:58 UTC
I think this issue is gone, I am unable to reproduce it on latest Fedora 29.

Comment 14 teppot 2019-05-06 20:53:12 UTC
Still happens on Fedora 30 at least with Firefox.

Comment 15 Ben Cotton 2019-05-28 19:06:53 UTC
Fedora 28 changed to end-of-life (EOL) status on 2019-05-28. Fedora 28 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.