Bug 1654803

Summary: When running kernel 4.19.X, desktop display does not refresh. Works on booting kernel 4.18.X
Product: [Fedora] Fedora Reporter: David Anderson <fedora-packaging2>
Component: kernelAssignee: Kernel Maintainer List <kernel-maint>
Status: CLOSED CURRENTRELEASE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 29CC: airlied, bskeggs, ewk, hdegoede, ichavero, itamar, jarodwilson, jforbes, jglisse, john.j5live, jonathan, josef, kernel-maint, linville, mchehab, mjg59, peter, steved
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-01-29 19:44:32 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:
Attachments:
Description Flags
Xorg.0.log - with the working kernel
none
Xorg.0.log - with the non-working kernel none

Description David Anderson 2018-11-29 17:26:34 UTC
Created attachment 1509890 [details]
Xorg.0.log - with the working kernel

Description of problem:

I have identical symptoms on two machines (which have identical hardware).

After updating to any of the 4.19.x kernels, on the desktop (which is XFCE), it appears that nothing happens when you click. Sometimes, the expected action happens a lot later. However, experimenting shows that it's actually a refresh problem. If you switch to a virtual console and switch back, then what you expected to see is there. If you leave it for the screensaver to start, then the mouse is actually constrained to the xscreensaver dialog even whilst you think you're still looking at the desktop. If you type in the password to unlock the screensaver, you don't see the desktop, but the mouse is released (you'll see it if you switch away and back).

If I reboot on the latest 4.18.18 kernel, it returns to working fine (as it always did - one of these machines began life on Fedora 27; the other is a completely fresh Fedora 29 install).

Version-Release number of selected component (if applicable):

kernel-4.19.4-300.fc29.x86_64 (and the earlier 4.19 kernels too).

How reproducible:

Every time. (And never on the older kernel).

Steps to Reproduce:
1. Log in to desktop.
2. Perform any action that should cause something different to appear on the screen.

Actual results:

In a desktop environment, the amount of time for the screen to update can vary from a few seconds to very many (I gave up waiting after a while). If you force a refresh somehow (e.g. switch to virtual console and return) you'll see what you expected.

Expected results:

Normal screen refresh.

Additional info:

- No errors are logged in ~/.xsession-errors .

- I have attached Xorg.0.log for both the working and non-working scenarios.

- I haven't seen anything like this happen on the greeter screen (lightdm)

- Happens on all logins, including newly-created ones

Comment 1 David Anderson 2018-11-29 17:27:49 UTC
Created attachment 1509891 [details]
Xorg.0.log - with the non-working kernel

Comment 2 Pete Olson 2018-12-06 03:02:37 UTC
I am seeing exactly the same symptoms on an HP laptop.

I am also running XFCE, though I start it from a console with startx.

No problems on any of several other computers running essentially the same apps on different hardware.

Comment 3 Justin M. Forbes 2019-01-29 16:14:06 UTC
*********** MASS BUG UPDATE **************

We apologize for the inconvenience.  There are a large number of bugs to go through and several of them have gone stale.  Due to this, we are doing a mass bug update across all of the Fedora 29 kernel bugs.

Fedora 29 has now been rebased to 4.20.5-200.fc29.  Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel.

If you experience different issues, please open a new bug report for those.

Comment 4 Pete Olson 2019-01-29 18:07:07 UTC
The new kernel seems to have resolved the problem. All is well again.

Comment 5 Justin M. Forbes 2019-01-29 19:44:32 UTC
Thanks for letting us know.