Bug 1151742

Summary: [abrt] xorg-x11-server-Xwayland: _CallCallbacks(): Xwayland killed by SIGABRT
Product: [Fedora] Fedora Reporter: Anonymous <lampshade>
Component: xorg-x11-serverAssignee: X/OpenGL Maintenance List <xgl-maint>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 21CC: lampshade, xgl-maint
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/5370927fd5a2fe7cd36d2b6e7893931f9e851cfe
Whiteboard: abrt_hash:2d158c6deffcf6a75d2503cf8268d085a62b707a
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-12-02 04:14:23 UTC Type: ---
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
File: backtrace
none
File: cgroup
none
File: core_backtrace
none
File: dso_list
none
File: environ
none
File: limits
none
File: maps
none
File: open_fds
none
File: proc_pid_status
none
File: var_log_messages none

Description Anonymous 2014-10-11 09:38:46 UTC
Description of problem:
After boot I changed to vt2 (ctrl-alt-f2) logged as root and: service gdm stop
Then logged in vt3 as user (login: fedora) and: weston-launch &
It launched weston-desktop. I opened weston-terminal. In weston-terminal:
Xwayland :5
then I launched another weston-terminal, when I was using Xwayland and in this terminal I wrote:
steam &
and Xwayland crashed
then I tried all over again but typed glxinfo instead of steam and also crashed
Even glxinfo crashes Xwayland on my PC (laptop with Intel 2000 Sandy Bridge GPU and discrete (disabled I hope) Geforce 620m.

Version-Release number of selected component:
xorg-x11-server-Xwayland-1.16.1-1.fc21

Additional info:
reporter:       libreport-2.2.3
backtrace_rating: 4
cmdline:        Xwayland :5
crash_function: _CallCallbacks
executable:     /usr/bin/Xwayland
kernel:         3.17.0-300.fc21.x86_64
runlevel:       N 5
type:           CCpp
uid:            1002

Truncated backtrace:
Thread no. 1 (6 frames)
 #6 _CallCallbacks at dixutils.c:718
 #7 CallCallbacks at ../include/callback.h:83
 #8 CloseDownClient at dispatch.c:3381
 #9 Dispatch at dispatch.c:444
 #10 dix_main at main.c:296
 #12 _start

Comment 1 Anonymous 2014-10-11 09:38:49 UTC
Created attachment 945930 [details]
File: backtrace

Comment 2 Anonymous 2014-10-11 09:38:50 UTC
Created attachment 945931 [details]
File: cgroup

Comment 3 Anonymous 2014-10-11 09:38:52 UTC
Created attachment 945932 [details]
File: core_backtrace

Comment 4 Anonymous 2014-10-11 09:38:53 UTC
Created attachment 945933 [details]
File: dso_list

Comment 5 Anonymous 2014-10-11 09:38:54 UTC
Created attachment 945934 [details]
File: environ

Comment 6 Anonymous 2014-10-11 09:38:56 UTC
Created attachment 945935 [details]
File: limits

Comment 7 Anonymous 2014-10-11 09:38:57 UTC
Created attachment 945936 [details]
File: maps

Comment 8 Anonymous 2014-10-11 09:38:59 UTC
Created attachment 945937 [details]
File: open_fds

Comment 9 Anonymous 2014-10-11 09:39:00 UTC
Created attachment 945938 [details]
File: proc_pid_status

Comment 10 Anonymous 2014-10-11 09:39:01 UTC
Created attachment 945939 [details]
File: var_log_messages

Comment 11 Anonymous 2014-10-11 09:40:44 UTC
I typed:
DISPLAY=":5" steam
and
DISPLAY=":5" glxinfo
of course

Comment 12 Anonymous 2014-10-24 21:27:17 UTC
Another user experienced a similar problem:

I was using weston-launch, setting DISPLAY=":5" environment variable, running glxinfo, glxgears and empathy on Xwayland in various configurations and Xwayland crashed while I was doing this.

reporter:       libreport-2.3.0
backtrace_rating: 4
cmdline:        Xwayland :5
crash_function: _CallCallbacks
executable:     /usr/bin/Xwayland
kernel:         3.17.1-303.fc21.x86_64
package:        xorg-x11-server-Xwayland-1.16.1-1.fc21
reason:         Xwayland killed by SIGABRT
runlevel:       N 5
type:           CCpp
uid:            0

Comment 13 Anonymous 2014-10-25 10:15:33 UTC
Another user experienced a similar problem:

glxinfo -display ":5" runs fine
DISPLAY=":5" glxinfo -display ":5" crashes Xwayland

reporter:       libreport-2.3.0
backtrace_rating: 4
cmdline:        Xwayland :5
crash_function: _CallCallbacks
executable:     /usr/bin/Xwayland
kernel:         3.17.1-303.fc21.x86_64
package:        xorg-x11-server-Xwayland-1.16.1-1.fc21
reason:         Xwayland killed by SIGABRT
runlevel:       N 5
type:           CCpp
uid:            0

Comment 14 Fedora End Of Life 2015-11-04 14:59:25 UTC
This message is a reminder that Fedora 21 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 21. 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 '21'.

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 21 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 15 Fedora End Of Life 2015-12-02 04:14:26 UTC
Fedora 21 changed to end-of-life (EOL) status on 2015-12-01. Fedora 21 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.