Red Hat Bugzilla – Bug 1012756
[abrt] mutter-wayland-3.9.92-1.fc20: xserver_died: Process /usr/bin/mutter-wayland was killed by signal 5 (SIGTRAP)
Last modified: 2015-06-29 08:28:23 EDT
Description of problem:
$ mutter-wayland --wayland
mutter-Message: forked X server, pid 4344
(mutter-wayland:4339): mutter-ERROR **: Spurious exit of X Wayland server
Trace/breakpoint trap (core dumped)
Version-Release number of selected component:
cmdline: mutter-wayland --wayland
var_log_messages: Sep 27 05:27:21 F20rc4 kernel: [ 949.103659] traps: mutter-wayland trap int3 ip:3aa36505a9 sp:7fff40464e90 error:0
Thread no. 1 (5 frames)
#2 xserver_died at wayland/meta-xwayland.c:292
#3 g_child_watch_dispatch at gmain.c:5047
#8 meta_xwayland_start at wayland/meta-xwayland.c:424
#9 meta_wayland_init at wayland/meta-wayland.c:965
#10 meta_init at core/main.c:428
Created attachment 803723 [details]
Created attachment 803724 [details]
Created attachment 803725 [details]
Created attachment 803726 [details]
Created attachment 803727 [details]
Created attachment 803728 [details]
Created attachment 803729 [details]
Created attachment 803730 [details]
Created attachment 803731 [details]
*** Bug 1013023 has been marked as a duplicate of this bug. ***
Created attachment 804623 [details]
[PATCH] wayland: make xwayland optional
The bug is caused by mutter-wayland trying to load XWayland,
which is not built on most distros (including F20). This patch
adds a runtime option for xwayland. With this change a user
needs to explicitly specify --xwayland otherwise mutter-wayland
will not try loading it.
No. mutter will not work without XWayland until we do some serious rearchitecting. We need to package XWayland in F20.
So what is going on with Gnome 3.10 + Wayland on Fedora 20? I installed first time in my life Fedora, Gnome 3.* because of preview of Wayland. I wanted to be one of the early adopter of Wayland. I wanted test it. Are there any information about progress in Gnome3.10/Wayland/Fedora20?
XWayland is packaged in F20 ( http://pkgs.fedoraproject.org/cgit/xorg-x11-server.git/commit/?h=f20&id=15e2ab311cc3e0fed7b99d98536fde395d38b502 ), so it should be working. Can you post your ~/.cache/xwayland.log ?
I don't have that file. I tried commands:
1. gnome-session --session gnome-wayland
2. mutter-launch -- mutter-wayland --wayland
1. Normal environment in emulator of terminal
2. In other vt when I was logged in as normal user
3. In other vt when I was logged as a root.
Some commands don't started or rest started program but this program immidiatel crashed.
Examples my crash reports:
This message is a reminder that Fedora 20 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 20. 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'
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 20 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 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 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
Thank you for reporting this bug and we are sorry it could not be fixed.