Red Hat Bugzilla – Bug 1254296
[abrt] gnome-shell: meta_launcher_new(): gnome-shell killed by SIGSEGV
Last modified: 2016-12-20 09:25:41 EST
Description of problem:
Version-Release number of selected component:
cmdline: /usr/bin/gnome-shell --wayland --display-server
runlevel: N 5
Thread no. 1 (7 frames)
#0 meta_launcher_new at backends/native/meta-launcher.c:300
#1 meta_backend_native_init at backends/native/meta-backend-native.c:332
#2 g_type_create_instance at gtype.c:1870
#3 g_object_new_internal at gobject.c:1774
#6 meta_create_backend at backends/meta-backend.c:566
#7 meta_clutter_init at backends/meta-backend.c:626
#8 meta_init at core/main.c:358
Created attachment 1063950 [details]
Created attachment 1063951 [details]
Created attachment 1063952 [details]
Created attachment 1063953 [details]
Created attachment 1063954 [details]
Created attachment 1063955 [details]
Created attachment 1063956 [details]
Created attachment 1063957 [details]
Created attachment 1063958 [details]
Created attachment 1063959 [details]
Created attachment 1063960 [details]
Created attachment 1063961 [details]
Description of problem:
After a new installation of Fedora-Workstation-netinst-x86_64-23_Alpha I've tried to log into Gnome 3 Wayland. After I entered the password it goes back to the login screen.
It looks like taking control over session fails, but the error is not set (thus the segfault).
Can you reproduce it? If so, could you attach journalctl output after the crash? The one taken by ABRT is kinda useless.
Unfortunately, I cannot reproduce the bug because there is another wayland issue (https://bugzilla.redhat.com/show_bug.cgi?id=1253249). This issue I can reproduce.
In that case we could try to get the logs from the day the crash occured, something like:
$ journalctl --since=15-08-17 --until=15-08-18 _COMM=gnome-session
The bug #1253249 frequently occurs after previous crash, so you can try to look into logs after that crash and if you'll see segfault before #1253249 then the log would be valuable too (best after fresh restart - when #1253249 happens for the first time)
Created attachment 1065129 [details]
It seems there were more gnome-session's errors in the journal that day and I don't know which is related to this bugzilla so I attach full report from that day.
Unfortunately, the logs begin at 13:42 but the crash occurred at 12:08, so there are not any details about this crash. However, the logs reveal the cause of bug #1253249 (in your case, people might experience it from other reasons)
This bug should be fixed upstream now (commit 1845bfe1b6235). It fixes the segfault only though. The issue that causes mutter take the error path (on which it got the SIGSEGV) may still be there.
This message is a reminder that Fedora 23 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 23. 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 23 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 23 changed to end-of-life (EOL) status on 2016-12-20. Fedora 23 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.