Red Hat Bugzilla – Bug 1026983
[abrt] gdm-3.8.4-2.fc19: poll: Process /usr/sbin/gdm was killed by signal 6 (SIGABRT)
Last modified: 2015-02-17 14:04:45 EST
Description of problem:
1. Start with standard Fedora 19 installation
2. Uninstall Plymouth (this shouldn't matter, a similar issue existed with plymouth installed, possibly related to bug #967521, although in that case gdm didn't even get to start)
3. Regenerate initramfs using dracut to eliminate plymouth bits from initramfs
4. Reboot system until gdm hangs on startup
Once gdm hangs on startup, I switched to VT2, logged in as root, and ran "pkill -SIGABRT gdm" to generate a core dump. This had a side effect of causing gdm to restart successfully.
Version-Release number of selected component:
runlevel: N 5
Thread no. 3 (6 frames)
#0 poll at ../sysdeps/unix/syscall-template.S:81
#1 g_main_context_poll at gmain.c:3995
#3 g_main_context_iteration at gmain.c:3762
#4 glib_worker_main at gmain.c:5427
#5 g_thread_proxy at gthread.c:798
#7 clone at ../sysdeps/unix/sysv/linux/x86_64/clone.S:113
Created attachment 819976 [details]
Created attachment 819977 [details]
Created attachment 819978 [details]
Created attachment 819979 [details]
Created attachment 819980 [details]
Created attachment 819981 [details]
Created attachment 819982 [details]
Created attachment 819983 [details]
Created attachment 819984 [details]
Created attachment 819985 [details]
This message is a notice that Fedora 19 is now at end of life. Fedora
has stopped maintaining and issuing updates for Fedora 19. It is
Fedora's policy to close all bug reports from releases that are no
longer maintained. Approximately 4 (four) weeks from now this bug will
be closed as EOL if it remains open with a Fedora 'version' of '19'.
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 19 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 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 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.