Red Hat Bugzilla – Bug 972530
[abrt] lightdm-gtk-1.3.1-4.fc18: start_authentication: Process /usr/sbin/lightdm-gtk-greeter was killed by signal 11 (SIGSEGV)
Last modified: 2014-01-27 08:46:47 EST
Version-Release number of selected component:
Thread no. 1 (7 frames)
#0 start_authentication at lightdm-gtk-greeter.c:189
#1 g_cclosure_marshal_VOID__VOIDv at gmarshal.c:115
#2 _g_closure_invoke_va at gclosure.c:840
#5 handle_end_authentication at greeter.c:380
#6 from_server_cb at greeter.c:460
#7 g_io_unix_dispatch at giounix.c:167
#12 gtk_main at gtkmain.c:1160
Created attachment 758966 [details]
Created attachment 758967 [details]
Created attachment 758968 [details]
Created attachment 758969 [details]
Created attachment 758970 [details]
Created attachment 758971 [details]
Created attachment 758972 [details]
Created attachment 758973 [details]
Created attachment 758974 [details]
Created attachment 758975 [details]
This message is a reminder that Fedora 18 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 18. 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 WONTFIX if it remains open with a Fedora
'version' of '18'.
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 prior to Fedora 18's end of life.
Thank you for reporting this issue and we are sorry that we may not be
able to fix it before Fedora 18 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 to Fedora 18's end of life.
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.
*** This bug has been marked as a duplicate of bug 922599 ***