Red Hat Bugzilla – Bug 1468796
[abrt] gnome-shell: _g_log_abort(): gnome-shell killed by signal 5
Last modified: 2017-08-12 23:42:41 EDT
Description of problem:
I had an install of Fedora 25 that started to behave erratically before and after I attempted to use dnf system-upgrade to 26 Beta.
I downloaded a new ISO and wiped everything except my Home directory. I rebooted after a successful installation and tried to log in and gnome got stuck with the cursor in the middle of the screen on the black screen that generally shows before the wallpaper and shell pops up. No input from the keyboard or mouse worked, including attempts to switch to another tty.
I rebooted and before logging in switched to another tty and ran updates, which also completed without a hitch. I rebooted and exactly the same thing.
I can provide more details if needed but I'm not really sure what's going on so I'm not certain what information would be helpful.
Version-Release number of selected component:
runlevel: N 5
Thread no. 1 (8 frames)
#0 _g_log_abort at gmessages.c:549
#1 g_log_default_handler at gmessages.c:3036
#4 xserver_died at wayland/meta-xwayland.c:397
#5 g_task_return_now at gtask.c:1145
#6 complete_in_idle_cb at gtask.c:1159
#12 meta_xwayland_start at wayland/meta-xwayland.c:569
#13 meta_wayland_init at wayland/meta-wayland.c:352
#14 meta_init at core/main.c:574
Potential duplicate: bug 1413346
Created attachment 1295426 [details]
Created attachment 1295427 [details]
Created attachment 1295428 [details]
Created attachment 1295429 [details]
Created attachment 1295430 [details]
Created attachment 1295431 [details]
Created attachment 1295432 [details]
Created attachment 1295433 [details]
Created attachment 1295434 [details]
Created attachment 1295435 [details]
Created attachment 1295436 [details]
Using the GNOME Classic desktop appears to work just fine.
GNOME on Xorg works as well.
Installing proprietary nvidia graphics drivers through negativo17 repository fixed this issue.
I'm still not certain what the cause of this issue is.
*** Bug 1480941 has been marked as a duplicate of this bug. ***