Created attachment 1156516 [details]
File: Xorg.0.log

Created attachment 1156517 [details]
File: backtrace

Created attachment 1156518 [details]
File: dmesg

Created attachment 1156519 [details]
File: dso_list

Created attachment 1156520 [details]
File: etc_X11_xorg_conf_d.tar.gz

Created attachment 1156521 [details]
File: usr_share_xorg_conf_d.tar.gz

*** Bug 1337567 has been marked as a duplicate of this bug. ***

Similar backtrace in bug #1336177 ? 
I get this crash more often than not on resume (though moving in/out the docking station while the laptop is sleeping may be involved too)

Description of problem:
I was just typing in an input field in Firefox.

Version-Release number of selected component:
xorg-x11-server-Xorg-1.18.3-2.fc23

Additional info:
reporter:       libreport-2.6.4
executable:     /usr/bin/Xorg
kernel:         4.4.9-300.fc23.x86_64
runlevel:       N 5
type:           xorg
uid:            0

Truncated backtrace:
0: /usr/libexec/Xorg (OsLookupColor+0x139) [0x597889]
1: /lib64/libc.so.6 (__restore_rt+0x0) [0x7fe798551aaf]
2: /usr/libexec/Xorg (XkbFlushLedEvents+0xb7) [0x547837]
3: /usr/libexec/Xorg (XkbFlushLedEvents+0x30e) [0x547bbe]
4: /usr/libexec/Xorg (XkbUpdateAllDeviceIndicators+0x70) [0x547cf0]
5: /usr/libexec/Xorg (XkbCompileKeymapFromString+0xa31d) [0x5479dd]
6: /usr/libexec/Xorg (SendErrorToClient+0x2df) [0x436a3f]
7: /usr/libexec/Xorg (remove_fs_handlers+0x453) [0x43aa53]
8: /lib64/libc.so.6 (__libc_start_main+0xf0) [0x7fe79853d580]
9: /usr/libexec/Xorg (_start+0x29) [0x424d99]
10: ? (?+0x29) [0x29]

I have it too very often since like a month... it is really an anoying bug. I though it was vmware related, but actually it seems not.

I have a asus gl552j, if it might add some info (I see XkbFlushLedEvents function, it might be really hardware related...)

Is there no way to have a coredump or abrt working on Xorg user process ?
I tried to attach gdb on Xorg process, inside a screen process from my android... but Xorg still get really instable and I cannot get proper stop on that bug.

I bit more info from that bug on my side

I have it each time I run a vm inside vmware player.
I use the latest vmwareplayer from today, 12.1.1.3770994, but "patched" with unlocker208. well it's a tainted environment
Xorg crash when inputing correct password when back from lock screen.

trace from ~/.local/share/xorg/Xorg.1.log.old :

[  2850.183] (EE) Backtrace:
[  2850.184] (EE) 0: /usr/libexec/Xorg (OsLookupColor+0x139) [0x597889]
[  2850.186] (EE) 1: /lib64/libc.so.6 (__restore_rt+0x0) [0x7fed00f75aaf]
[  2850.186] (EE) 2: /usr/libexec/Xorg (XkbFlushLedEvents+0xb7) [0x547837]
[  2850.187] (EE) 3: /usr/libexec/Xorg (XkbFlushLedEvents+0x30e) [0x547bbe]
[  2850.187] (EE) 4: /usr/libexec/Xorg (XkbUpdateAllDeviceIndicators+0x70) [0x547cf0]
[  2850.188] (EE) 5: /usr/libexec/Xorg (XkbCompileKeymapFromString+0xa31d) [0x5479dd]
[  2850.189] (EE) 6: /usr/libexec/Xorg (SendErrorToClient+0x2df) [0x436a3f]
[  2850.189] (EE) 7: /usr/libexec/Xorg (remove_fs_handlers+0x453) [0x43aa53]
[  2850.191] (EE) 8: /lib64/libc.so.6 (__libc_start_main+0xf0) [0x7fed00f61580]
[  2850.192] (EE) 9: /usr/libexec/Xorg (_start+0x29) [0x424d99]
[  2850.193] (EE) 10: ? (?+0x29) [0x29]

It was attached to gdb, when it crashed :

Program received signal SIGSEGV, Segmentation fault.
XkbFlushLedEvents (dev=dev@entry=0x14f8d20, kbd=kbd@entry=0x14f8d20,
    sli=sli@entry=0x183e9d0, ed=0x7fff6b7d14b0, changes=<optimized out>,
    cause=cause@entry=0x0) at xkbLEDs.c:772
772                 XkbSendExtensionDeviceNotify(dev, cause->client, ed);
Missing separate debuginfos, use: dnf debuginfo-install libevdev-1.4.5-2.fc23.x86_64 mtdev-1.1.5-5.fc23.x86_64 xorg-x11-drv-evdev-2.9.99-2.20150807git66c997886.fc23.x86_64 xorg-x11-drv-intel-2.99.917-19.20151206.fc23.x86_64 xorg-x11-drv-synaptics-1.8.3-1.fc23.x86_64
(gdb) bt
#0  XkbFlushLedEvents (dev=dev@entry=0x14f8d20, kbd=kbd@entry=0x14f8d20,
    sli=sli@entry=0x183e9d0, ed=0x7fff6b7d14b0, changes=<optimized out>,
    cause=cause@entry=0x0) at xkbLEDs.c:772
#1  0x0000000000547a8e in XkbUpdateLedAutoState (dev=dev@entry=0x14f8d20,
    sli=0x183e9d0, maps_to_check=<optimized out>, ed=<optimized out>,
    ed@entry=0x0, changes=<optimized out>, changes@entry=0x0,
    cause=cause@entry=0x0) at xkbLEDs.c:303
#2  0x0000000000547cf0 in XkbUpdateLedAutoState (cause=0x0, changes=0x0,
    ed=0x0, maps_to_check=<optimized out>, sli=<optimized out>,
    dev=0x14f8d20) at xkbLEDs.c:246
#3  XkbUpdateAllDeviceIndicators (changes=changes@entry=0x0,
    cause=cause@entry=0x0) at xkbLEDs.c:321
#4  0x000000000053e1bd in ProcXkbGetKbdByName (client=0x175c870)
    at xkb.c:6019
#5  0x00000000004369bf in Dispatch () at dispatch.c:430
#6  0x000000000043a9c3 in dix_main (argc=14, argv=0x7fff6b7d2938,
    envp=<optimized out>) at main.c:300
#7  0x00007fed00f61580 in __libc_start_main (main=0x424d60 <main>, argc=14,
    argv=0x7fff6b7d2938, init=<optimized out>, fini=<optimized out>,
    rtld_fini=<optimized out>, stack_end=0x7fff6b7d2928) at libc-start.c:289
#8  0x0000000000424d99 in _start () at xkb.c:3504

I'll be digging further, but if someone has a clue already, he's welcome to comment...

Created attachment 1164595 [details]
quickfix for crash

So I've been trying this obvious patch, and yay, no more crash.

Of course, this is not satisfying, as it does not solve the root problem.

Please, as it seems I'm the only one from now that can have this crash consistently, let me know how I can make this crash fixed upstream and with a good fix.

I opened a bug upstream : https://bugs.freedesktop.org/show_bug.cgi?id=96384

*** Bug 1349687 has been marked as a duplicate of this bug. ***

Could someone please have a look at this? It's very frustrating to lose all of you work at random intervals.

Urgh. Whilst trying to build a custom package with the workaround, I noticed this patch in the RPM:

0001-xkb-after-changing-the-keymap-force-an-indicator-upd.patch

And lo' and behold, it calls XkbUpdateAllDeviceIndicators() without a cause:

+    XkbUpdateAllDeviceIndicators(NULL, NULL);

This patch has also been merged upstream.

Adding Peter Hutterer as explicit cc. Could you please have another look at this? :)

Upstream fix proposed here: https://patchwork.freedesktop.org/patch/95375/

xorg-x11-server-1.18.3-5.fc24 has been submitted as an update to Fedora 24. https://bodhi.fedoraproject.org/updates/FEDORA-2016-22243fc23b

xorg-x11-server-1.18.3-5.fc24 has been pushed to the Fedora 24 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2016-22243fc23b

xorg-x11-server-1.18.3-5.fc24 has been pushed to the Fedora 24 stable repository. If problems still persist, please make note of it in this bug report.

Whoops, this is was filed against F23, not F24. Sorry about that, will push the F23 update out in a second

xorg-x11-server-1.18.3-3.fc23 has been submitted as an update to Fedora 23. https://bodhi.fedoraproject.org/updates/FEDORA-2016-10b235c8f0

xorg-x11-server-1.18.3-3.fc23 has been pushed to the Fedora 23 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2016-10b235c8f0

xorg-x11-server-1.18.3-3.fc23 has been pushed to the Fedora 23 stable repository. If problems still persist, please make note of it in this bug report.