Bug 1502182

Created attachment 1338694 [details]
File: backtrace

Created attachment 1338695 [details]
File: cgroup

Created attachment 1338696 [details]
File: core_backtrace

Created attachment 1338697 [details]
File: cpuinfo

Created attachment 1338698 [details]
File: dso_list

Created attachment 1338699 [details]
File: environ

Created attachment 1338700 [details]
File: limits

Created attachment 1338701 [details]
File: maps

Created attachment 1338702 [details]
File: open_fds

Created attachment 1338703 [details]
File: proc_pid_status

Created attachment 1338704 [details]
File: var_log_messages

Similar problem has been detected:

Happens constantly with kernel 4.15.3-200.fc26.x86_64 and 4.15.4-200.fc26.x86_64
and just once 4.14.16-200.fc26.x86_64

Problem occurs when logging in on graphical environment
and quickly starting transmission 2.92 (fedora package)
and amule 3.3.1 (rpmfusion package) after eachother.

Does not occur when starting in different order
and when keeping more time in between starting
the mentioned programs.

reporter:       libreport-2.9.1
backtrace_rating: 4
cmdline:        /usr/bin/Xwayland :0 -rootless -noreset -listen 4 -listen 5 -displayfd 6
crash_function: glamor_pixmap_ensure_fb
executable:     /usr/bin/Xwayland
journald_cursor: s=9fe4a9d9dbc24b82b3994a6a7e853149;i=91de7;b=166a78981de44f5ab795d73b7c80f465;m=916f502f;t=56642dc8295ba;x=9526d3190cb02cd5
kernel:         4.15.4-200.fc26.x86_64
package:        xorg-x11-server-Xwayland-1.19.3-4.fc26
reason:         Xwayland killed by SIGABRT
rootdir:        /
runlevel:       3 5
type:           CCpp
uid:            1000

Occurs at same time as BUG 1466948
https://bugzilla.redhat.com/show_bug.cgi?id=1466948

Correction to comment 12 and 13:

-- This problem does not seem to repeat --
-- when following the same steps --

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.

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.