Bug 167284

Summary: [GTK] Black screen or freeze when I opened several tabs
Product: WebKit Reporter: Charles-Antoine Couret <cacouret.renault>
Component: WebKitGTKAssignee: Nobody <webkit-unassigned>
Status: RESOLVED WORKSFORME    
Severity: Normal CC: aperez, bugs-noreply, clopez, mcatanzaro
Priority: P2    
Version: WebKit Nightly Build   
Hardware: Unspecified   
OS: Unspecified   
See Also: https://bugzilla.redhat.com/show_bug.cgi?id=1415337
Attachments:
Description Flags
waylandes2info output none

Charles-Antoine Couret
Reported 2017-01-21 09:59:11 PST
I used Epiphany 3.23.4-1.fc26 on GNOME Shell and Wayland with my Elitebook 8560w (nVidia Quadro 1000M NVC1). If I open some tabs, the screen began black entirely. I can see only the cursor. Or sometimes the computer freezes. But I can't move the cursor, I can't open a TTY session or other things. I need to reboot my computer in both cases. I don't have this bug with Firefox for example. I use webkitgtk4.x86_64 2.15.2-1.fc26 It's Michael Catanzaro who asked me to report this bug here (https://bugzilla.redhat.com/show_bug.cgi?id=1415337) I'm available if you need more information.
Attachments
waylandes2info output (3.25 KB, text/plain)
2017-01-23 10:51 PST, Charles-Antoine Couret 		no flags
Details
View All Add attachment proposed patch, testcase, etc.
Carlos Alberto Lopez Perez
Comment 1 2017-01-23 07:27:18 PST
What graphics drivers are you using? Nouveau/Mesa or Nvidia/propietary ? Can you paste here the output of this utility? git clone https://github.com/clopez/waylandeglinfo cd waylandeglinfo ./buildme.sh ./waylandes2info &> output.txt # upload output.txt here
Charles-Antoine Couret
Comment 2 2017-01-23 10:50:50 PST
I use the driver nouveau/mesa
Charles-Antoine Couret
Comment 3 2017-01-23 10:51:26 PST
Created attachment 299526 [details] waylandes2info output
Adrian Perez
Comment 4 2018-05-03 04:51:55 PDT
Hi Charles-Antoine! Sorry for getting back to you on this bug report with such a big delay. We have had many Wayland-related bugs solved in the few last releases of WebKitGTK+, and many fixes have gone into GNOME Shell itself as well. Would you be so kind as to check whether this issue is still present with recent versions of WebKitGTK+, Epiphany and GNOME? If you could test the latest stable releases (WebKitGTK+ 2.20.1, GNOME/Epiphany 3.28.1) that would be awesome. Thanks a lot in advance!
Adrian Perez
Comment 5 2019-09-28 14:03:32 PDT
Wayland support has been working well, so I'll close this for now. Feel free to reopen it if the problem persists (or reappears) with current versions of WebKitGTK.
Note You need to log in before you can comment on or make changes to this bug.