Bug 1487954

Summary: Xorg crash in cursor move after few second idle
Product: [Fedora] Fedora Reporter: Virgilio <virgiliovasconcelos>
Component: xorg-x11Assignee: X/OpenGL Maintenance List <xgl-maint>
Status: CLOSED EOL QA Contact:
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 26CC: register, renerask
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-05-29 11:25:49 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
core_backtrace none

Description Virgilio 2017-09-03 18:41:32 UTC
Description of problem:
I'm using Fedora 26, Gnome under Xorg because the lack of support for wacom tablets (https://bugzilla.redhat.com/show_bug.cgi?id=1397898).

After the most recent updates, Xorg crashes almost every time I move my cursor (trackpad or tablet) returning from an idle state. Even a few seconds of inactivity is enough for crashing Xorg in a simple cursor move.

I have reinstalled Fedora with no Gnome themes or extensions to ensure I was on a clean environment. That happens with the most up-to-date install.


Version-Release number of selected component (if applicable):
Name         : xorg-x11-server-Xorg
Version      : 1.19.3
Release      : 4.fc26
Arch         : x86_64


How reproducible:
Well... to me it happens so often it's becoming unusable. As Wayland also is unusable for my work with graphics tablets, I'm not sure what to do

Steps to Reproduce:
1. Log in to Fedora
2. Step back from the computer for a few minutes
3. When you return, the first thing you do is moving the cursor (touchpad or stylus)

Actual results:
Xorg crashes and you lose everything you were working on with.


Expected results:
Happy Fedora user with his/her mouse/touchpad/stylus skills.
Gnome Version 3.24.2


Additional info:
IntelĀ® Haswell Mobile / Gallium 0.4 on NVE7
Name         : xorg-x11-drv-intel
Version      : 2.99.917
Release      : 28.20160929.fc26
Arch         : x86_64


Nvidia GeForce GT750M dedicated card with nouveau driver:
Name         : xorg-x11-drv-nouveau
Epoch        : 1
Version      : 1.0.15
Release      : 1.fc26
Arch         : x86_64


Log from systemd:
Process 20778 (Xorg) of user 1000 dumped core.

Stack trace of thread 20794:
#0  0x00007f019083ffb6 drmmode_set_cursor.isra.17 (modesetting_drv.so)
#1  0x00000000004af913 xf86_set_cursor_position (Xorg)
#2  0x00000000004ba532 xf86MoveCursor (Xorg)
#3  0x00000000005842fb miPointerMoveNoEvent (Xorg)
#4  0x00000000005850c9 miPointerSetPosition (Xorg)
#5  0x000000000044bf6e positionSprite.part.8 (Xorg)
#6  0x000000000044c710 fill_pointer_events (Xorg)
#7  0x000000000044df4f GetPointerEvents (Xorg)
#8  0x000000000044e4f0 QueuePointerEvents (Xorg)
#9  0x00007f019045b8b9 xf86libinput_handle_event (libinput_drv.so)
#10 0x00007f019045c2a0 xf86libinput_read_input (libinput_drv.so)
#11 0x000000000059a983 InputReady (Xorg)
#12 0x000000000059cff1 ospoll_wait (Xorg)
#13 0x000000000059a7ce InputThreadDoWork (Xorg)
#14 0x00007f019407836d start_thread (libpthread.so.0)
#15 0x00007f0193db0bbf __clone (libc.so.6)

Stack trace of thread 20778:
#0  0x00007f0193db1123 epoll_wait (libc.so.6)
#1  0x000000000059cfa4 ospoll_wait (Xorg)
#2  0x000000000059603b WaitForSomething (Xorg)
#3  0x00000000004355e3 Dispatch (Xorg)
#4  0x0000000000439850 dix_main (Xorg)
#5  0x00007f0193cc050a __libc_start_main (libc.so.6)
#6  0x000000000042357a _start (Xorg)

Stack trace of thread 20791:
#0  0x00007f019407e90b pthread_cond_wait@@GLIBC_2.3.2 (libpthread.so.0)
#1  0x00007f018c28d6ab util_queue_thread_func (nouveau_dri.so)
#2  0x00007f018c28d3e7 impl_thrd_routine (nouveau_dri.so)
#3  0x00007f019407836d start_thread (libpthread.so.0)
#4  0x00007f0193db0bbf __clone (libc.so.6)

Comment 1 Virgilio 2017-09-04 16:28:45 UTC
As an update on this. I have downgraded some Xorg related packages and this bug has vanished. So, I presume it is related to one of these packages below, possibly 'libinput':

sudo dnf --allowerasing --releasever=25 downgrade xorg-x11-drv-libinput xorg-x11-drv-wacom xorg-x11-drv-intel xorg-x11-server-Xorg

Comment 2 Blazej Floch 2018-03-11 04:29:38 UTC
I can confirm this problem on Fedora 27, also with a Wacom tablet and X11.

This is where my report ended up: https://retrace.fedoraproject.org/faf/reports/1724223/

I've lost work several times now.

Comment 3 Fedora End Of Life 2018-05-03 08:01:09 UTC
This message is a reminder that Fedora 26 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 26. 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 '26'.

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 26 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 renerask 2018-05-24 13:12:43 UTC
Created attachment 1441055 [details]
core_backtrace

I have had the same problem through at least fedora 26, 27 and now 28.

I have 2 screens attached to a laptop, one DisplayPort and one HDMI screen.
This problem can usually be reproducing within a minute by moving the pointer between the DP and HDMI screens.
I don't use the laptop screen much so I haven't tried to reproduce it with that screen.

This bug may be the same issue https://bugzilla.redhat.com/show_bug.cgi?id=1554026

This is the coredump output in journalctl.
Process 1523 (Xorg) of user 1000 dumped core.

Stack trace of thread 1879:
#0  0x00007f85d15aef01 drmmode_set_cursor.isra.18 (modesetting_drv.so)
#1  0x00000000004af5fe xf86_set_cursor_position (Xorg) 
#2  0x00000000004ba4a6 xf86MoveCursor (Xorg)
#3  0x0000000000584e5b miPointerMoveNoEvent (Xorg)
#4  0x0000000000585c5c miPointerSetPosition (Xorg)
#5  0x000000000044b8be positionSprite.part.8 (Xorg)
#6  0x000000000044c097 fill_pointer_events (Xorg)
#7  0x000000000044d8ff GetPointerEvents (Xorg)
#8  0x000000000044dea4 QueuePointerEvents (Xorg)
#9  0x00007f85d12caa52 xf86libinput_handle_event (libinput_drv.so)
#10 0x00007f85d12cad08 xf86libinput_read_input (libinput_drv.so)
#11 0x000000000059b8b7 InputReady (Xorg)
#12 0x000000000059ded1 ospoll_wait (Xorg)
#13 0x000000000059b6fe InputThreadDoWork (Xorg)
#14 0x00007f85d52a6594 n/a (libpthread.so.0)
#15 0x00007f85d4fd9fdf __clone (libc.so.6)

Stack trace of thread 1523:
#0  0x00007f85d4fda2ff epoll_wait (libc.so.6)
#1  0x000000000059de8b ospoll_wait (Xorg)
#2  0x0000000000596efc WaitForSomething (Xorg)
#3  0x0000000000434c20 Dispatch (Xorg)
#4  0x0000000000438f26 dix_main (Xorg)
#5  0x00007f85d4f0318b __libc_start_main (libc.so.6)
#6  0x000000000042290a _start (Xorg)

Comment 5 Fedora End Of Life 2018-05-29 11:25:49 UTC
Fedora 26 changed to end-of-life (EOL) status on 2018-05-29. Fedora 26
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.