Wayland compositor causes window to be transparent
Categories
(Core :: Graphics: WebRender, defect, P3)
Tracking
()
Tracking | Status | |
---|---|---|
firefox94 | --- | disabled |
People
(Reporter: pgmmm, Assigned: stransky, NeedInfo)
References
(Blocks 2 open bugs)
Details
Attachments
(2 files, 1 obsolete file)
User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:94.0) Gecko/20100101 Firefox/94.0
Steps to reproduce:
Create fresh nightly profile with 'gfx.webrender.compositor.force-enabled' set to true
Actual results:
Initial window stays transparent until it is resized or moved
Comment 3•3 years ago
|
||
The Bugbug bot thinks this bug should belong to the 'Core::Widget: Gtk' component, and is moving the bug to that component. Please revert this change in case you think the bot is wrong.
Updated•3 years ago
|
Comment 4•3 years ago
|
||
(In reply to pgmmm from comment #0)
Initial window stays transparent until it is resized or moved
Do I understand correctly that, once moved or resized, things work as expected? Also, just to be sure, this is on a recent version of Gnome, correct?
(In reply to Robert Mader [:rmader] from comment #4)
Do I understand correctly that, once moved or resized, things work as expected? Also, just to be sure, this is on a recent version of Gnome, correct?
That's both correct, opening Gnome's 'Activities' also seems to work.
This is using the standard Gnome (40.4) package on Arch.
Comment 6•3 years ago
|
||
I can reproduce this on Fedora 35 (GNOME 41) with Intel gen 9 graphics. Resizing or moving the window, or using the Activites view workarounds as expected.
Comment 7•3 years ago
|
||
The severity field is not set for this bug.
:jimm, could you have a look please?
For more information, please visit auto_nag documentation.
Updated•3 years ago
|
Comment 8•2 years ago
|
||
The bug has a release status flag that shows some version of Firefox is affected, thus it will be considered confirmed.
Updated•7 months ago
|
Assignee | ||
Comment 9•12 days ago
|
||
Looking at it right now as I see it too. Looks like caused by compositor enable timing.
Assignee | ||
Comment 10•11 days ago
|
||
It's caused by VSync. When switched to SW it works. Also scale change unblock it.
Assignee | ||
Comment 11•11 days ago
|
||
The bug is at NativeLayerRootWayland::RequestFrameCallback(). If it's called early and there aren't any layers yet (mSublayersOnMainThread is empty), we don't register any frame callback so Vsync is not running.
Assignee | ||
Updated•11 days ago
|
Assignee | ||
Updated•11 days ago
|
Description
•