Bug 1368921 - System "hangs" until the mouse is moved
Summary: System "hangs" until the mouse is moved
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: xorg-x11
Version: 24
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: X/OpenGL Maintenance List
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-08-22 06:39 UTC by Stefan Neufeind
Modified: 2017-08-08 16:39 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-08-08 16:39:40 UTC
Type: Bug


Attachments (Terms of Use)

Description Stefan Neufeind 2016-08-22 06:39:27 UTC
I lately experience problems that the system "hangs" until you move the mouse-cursor. This happen in the "konsole" (KDE) as well as when entering text in an application. During typing the screen is not updated. This happens for both an external USB-keyboard as well as the internal laptop-keyboard. As soon as you move the mouse-cursor some pixels the screen updates immetiately. Using a continously updating application like "top" I see that it's not just the keyboard-input that hangs but that also top does not update the screen until you move the mouse-cursor.

This occured sometime during the updates of the last few weeks. I'm using Fedora 24 with testing-updates enabled and runing KDE / Plasma.
I can't say if this is related to kernel (graphics driver for Intel onboard), Xorg or maybe Plasma.

Comment 1 Stefan Neufeind 2016-08-22 07:24:39 UTC
Maybe related to xorg-drv-intel issue #1367831?

Comment 2 aaronsloman 2016-09-26 21:34:18 UTC
I have noticed this for several months on a Dell Latitude E6410 running Fedora 22, though I have not tried an external keyboard.

Sometimes while typing text it seems that the input is held in a queue until I use a finger on the touchpad.

I had assumed that it had something to do with the settings of the synclient or syndaemon programs. The latter monitors keyboard activity and disables the touchpad when the keyboard is being used. I have not been able to work out good settings to fix the problem.

Comment 3 Fedora End Of Life 2017-07-25 22:33:25 UTC
This message is a reminder that Fedora 24 is nearing its end of life.
Approximately 2 (two) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 24. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '24'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 24 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged  change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

Comment 4 Stefan Neufeind 2017-07-26 06:31:03 UTC
I have *not* seen this happen recently on my system, updated Fedora 26 meanwhile.

Comment 5 Fedora End Of Life 2017-08-08 16:39:40 UTC
Fedora 24 changed to end-of-life (EOL) status on 2017-08-08. Fedora 24 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.