Bug 1314208
Summary: | GTK3 Popover menu cause screen flicking on Wayland with intel | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Tommy He <lovenemesis> |
Component: | mutter | Assignee: | Florian Müllner <fmuellner> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | medium | Docs Contact: | |
Priority: | unspecified | ||
Version: | 23 | CC: | ajax, fedora, fmuellner, ofourdan, otaylor, walters, xgl-maint |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2016-03-15 04:16:23 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | |||
Bug Blocks: | 1277927 |
Description
Tommy He
2016-03-03 08:51:21 UTC
Note this issue does not only happens on Gedit but any other apps which utilizing GTK3 Popover menu. Unlikely the X11 ddx being the problem in Wayland, either a gtk bug or a clutter/mutter issue (more likely because it occurs after gedit is closed) (In reply to Olivier Fourdan from comment #2) > Unlikely the X11 ddx being the problem in Wayland, either a gtk bug or a > clutter/mutter issue (more likely because it occurs after gedit is closed) Thanks for pointing it out. Do you think I need to file a separate bug in GNOME Bugzilla? Or the one here is sufficient? Are you sure this is an issue in Gtk/X11/Wayland? I'm just asking because the 4.4.x kernels before 4.4.4 which is due to be build probably today have a regression on intel GPUs that leads to flicker. See bug #1313318 for details. Well, like I said, the problem does not happen if specifying GDK_BACKEND=x11. Anyway, I'm pulling kernel 4.4.4 from updates-testing to give another try. This issue is no longer present after following two updates: mutter-3.18.3-1.fc23.x86_64 kernel-4.4.4-301.fc23.x86_64 Whatever fixes in mutter or kernel issue, it's gone now. |