Bug 1397586 - Display not refreshing properly on nvidia 680M
Summary: Display not refreshing properly on nvidia 680M
Keywords:
Status: CLOSED DUPLICATE of bug 1397623
Alias: None
Product: Fedora
Classification: Fedora
Component: mutter
Version: 25
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Florian Müllner
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-11-22 21:34 UTC by Julian Sikorski
Modified: 2016-11-23 19:04 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-11-23 19:04:51 UTC
Type: Bug

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)


Links
System ID Private Priority Status Summary Last Updated
GNOME Bugzilla 774882 0 None None None 2016-11-22 21:56:53 UTC

Description Julian Sikorski 2016-11-22 21:34:25 UTC 
Description of problem:
Since I upgraded to Fedora 25 the gnome has become unusable. It appears there are serious problems with refreshing the display, with previous frames being displayed interchangeably with current ones. This happens with both wayland and x.

Version-Release number of selected component (if applicable):
gnome-desktop3-3.22.1-1.fc25.x86_64
xorg-x11-server-Xorg-1.19.0-0.8.rc2.fc25.x86_64
libwayland-server-1.12.0-1.fc25.x86_64
libwayland-server-1.12.0-1.fc25.i686

How reproducible:
always

Steps to Reproduce:
1. Install Fedora 25 x86_64 on a Clevo P150HM with nvidia 680M GPU
2. Start gnome session

Actual results:
screen flickers and old frames are shown interchangeably with new ones

Expected results:
desktop is shown without issues

Additional info:
I have made some videos to show the problem:
https://www.youtube.com/watch?v=5kbExMvORss
https://www.youtube.com/watch?v=L0xtR4-tLQc

In the first video, observe how current and previous frames swap with each press of the keyboard.
Comment 1 Julian Sikorski 2016-11-22 21:50:17 UTC 
I started LXDE and the problem is gone, so it looks like the problem is somewhere in the gnome stack.
Comment 2 FishFace 2016-11-23 11:39:54 UTC 
I believe bug 1397623 is a duplicate of this.
Comment 3 Julian Sikorski 2016-11-23 19:04:51 UTC 

*** This bug has been marked as a duplicate of bug 1397623 ***
Note You need to log in before you can comment on or make changes to this bug.