Bug 163484 - [gtk] [wayland] Epiphany starts with a lot of video glitches
Summary: [gtk] [wayland] Epiphany starts with a lot of video glitches
Status: RESOLVED INVALID
Alias: None
Product: WebKit
Classification: Unclassified
Component: WebKitGTK (show other bugs)
Version: WebKit Nightly Build
Hardware: Unspecified Unspecified
: P2 Normal
Assignee: Nobody
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-10-15 04:03 PDT by Márcio
Modified: 2016-10-15 19:36 PDT (History)
2 users (show)

See Also:


Attachments
lsmod, lspci and installed packages (12.40 KB, application/zip)
2016-10-15 04:03 PDT, Márcio
no flags Details
screencapture (1.96 MB, image/png)
2016-10-15 04:04 PDT, Márcio
no flags Details
with GDK_GL=disable option (1.64 MB, image/png)
2016-10-15 04:07 PDT, Márcio
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Márcio 2016-10-15 04:03:32 PDT
Created attachment 291713 [details]
lsmod, lspci and installed packages

When I start epiphany 3.22.1 under wayland there are a lot of video glitches that make impossible to see the window content.

Using the flag GDK_BACKEND=x11 that bug do not happens.
That bug is happen on a desktop with a radeon rx 480 with fully update open source stack, mesa, amdgpu, kernel 4.8, gtk 3.22.1 and webkit2gtk 2.14.1.
It not happens on a notebook ivybridge with intel video driver.
Using the flag GDK_GL=disable just the webview shows that glitches.

I'm using fully updated Arch Linux.

There isn't backtrace on gdb.

Step to reproduce:

1 - open epiphany on gnome 3.22 wayland on amdgpu stack;
Comment 1 Márcio 2016-10-15 04:04:51 PDT
Created attachment 291714 [details]
screencapture
Comment 2 Márcio 2016-10-15 04:07:12 PDT
Created attachment 291715 [details]
with GDK_GL=disable option
Comment 3 Márcio 2016-10-15 04:08:21 PDT
Link to gnome bugzilla report: https://bugzilla.gnome.org/show_bug.cgi?id=772960
Comment 4 Michael Catanzaro 2016-10-15 19:36:06 PDT
OK, Márcio discovered in the GNOME bug that this issue affects Totem, so it's definitely not a WebKit problem.