Description of problem: I opened my laptop, it took longer than usual to wake up, then it said some process had to be killed Version-Release number of selected component: xorg-x11-server-Xwayland-1.19.6-5.fc27 Additional info: reporter: libreport-2.9.3 backtrace_rating: 4 cmdline: /usr/bin/Xwayland :0 -rootless -terminate -core -listen 4 -listen 5 -displayfd 6 crash_function: _Uelf64_lookup_symbol executable: /usr/bin/Xwayland journald_cursor: s=a076843b874b4f0c9e0bda8adbf2d1fe;i=537a;b=de5adee6f892423d87f102620642dcba;m=71024228;t=565f75be3b726;x=49f89a5efa89b3c7 kernel: 4.15.3-300.fc27.x86_64 rootdir: / runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 _Uelf64_lookup_symbol at elfxx.c:109 #1 _Uelf64_get_proc_name_in_image at elfxx.c:315 #2 _Uelf64_get_proc_name at elfxx.c:353 #3 get_proc_name at mi/Gget_proc_name.c:93 #4 _ULx86_64_get_proc_name at mi/Gget_proc_name.c:109 #5 xorg_backtrace at backtrace.c:81 #8 XkbGeomRealloc at XKBGAlloc.c:405 #9 _XkbCopyGeom at xkbUtils.c:1439 #10 XkbCopyKeymap at xkbUtils.c:1992 #12 XkbDeviceApplyKeymap at xkbUtils.c:2025
Created attachment 1400326 [details] File: backtrace
Created attachment 1400327 [details] File: cgroup
Created attachment 1400328 [details] File: core_backtrace
Created attachment 1400329 [details] File: cpuinfo
Created attachment 1400330 [details] File: dso_list
Created attachment 1400331 [details] File: environ
Created attachment 1400332 [details] File: exploitable
Created attachment 1400333 [details] File: limits
Created attachment 1400334 [details] File: maps
Created attachment 1400335 [details] File: mountinfo
Created attachment 1400336 [details] File: open_fds
Created attachment 1400337 [details] File: proc_pid_status
*** Bug 1549516 has been marked as a duplicate of this bug. ***
I am getting a similar-looking backtrace, repeatedly. I wrote an analysis of the backtrace which is mostly me going "impossible!". "SIGBUS apparently at first instruction in XkbGeomRealloc(), when resuming from suspend" https://bugzilla.redhat.com/show_bug.cgi?id=1557682 Sadly it looks like xorg_backtrace() is also crashing in different places, this means there's ABRT reports that aren't getting merged correctly. I have followed "https://wiki.ubuntu.com/X/Backtracing#Untrap_signals" to disable xorg_backtrace(). Maybe the next time, a cleaner backtrace will help me analyze better. (DISCLAIMER. The manpage warns about consequences from this. Because X doesn't get to clean up if you do this. However with unprivileged X, _and_ me using XWayland rather than X accessing devices directly, I think it's fine. And if it's not, I should still get the backtrace saved to disk nicely and be able to reboot cleanly enough with sysrqs, because I have enabled sysrq). Google "Xwayland XkbGeomRealloc" is bringing this report up nice and prominently, so I'll mark mine as a duplicate.
*** Bug 1557682 has been marked as a duplicate of this bug. ***
Although, if you would like to click on [edit] next the title of this bug, and change it to refer XkbGeomRealloc() instead of _Uelf54_lookup_symbol(), that might also help highlight the *real* problem. I don't have permission to do that on this bug.
Similar problem has been detected: This happened on resume from suspend. It does not always happen on resume from suspend. AFAIK this is the second time I've seen this backtrace. I have seen one other backtrace more frequently (and reported it). On this occasion I believe it affected my foreground GNOME session. It did not affect gdm, nor the GNOME session I had on a different tty (as a different user). reporter: libreport-2.9.3 backtrace_rating: 3 cmdline: /usr/bin/Xwayland :0 -rootless -terminate -core -listen 4 -listen 5 -displayfd 6 crash_function: _dl_fixup executable: /usr/bin/Xwayland journald_cursor: s=2dfd4bfd0b9c49e7bf8baeec3ec3ffc7;i=4e804b;b=23af529241b647dca1b9b199402b28f6;m=17420cf1d7;t=5681ae2205ed5;x=1e12814d65fea71b kernel: 4.15.10-300.fc27.x86_64 package: xorg-x11-server-Xwayland-1.19.6-5.fc27 reason: Xwayland killed by SIGBUS rootdir: / runlevel: N 5 type: CCpp uid: 1001
I found the elusive developer who's looking at this :). This bug should be marked as a duplicate of the following: https://bugzilla.redhat.com/show_bug.cgi?id=1553979
*** This bug has been marked as a duplicate of bug 1553979 ***