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
Created attachment 945930 [details] File: backtrace
Created attachment 945931 [details] File: cgroup
Created attachment 945932 [details] File: core_backtrace
Created attachment 945933 [details] File: dso_list
Created attachment 945934 [details] File: environ
Created attachment 945935 [details] File: limits
Created attachment 945936 [details] File: maps
Created attachment 945937 [details] File: open_fds
Created attachment 945938 [details] File: proc_pid_status
Created attachment 945939 [details] File: var_log_messages
I typed: DISPLAY=":5" steam and DISPLAY=":5" glxinfo of course
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
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
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.
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.