Version-Release number of selected component: gdm-3.8.3-2.fc20 Additional info: reporter: libreport-2.1.6 backtrace_rating: 4 cmdline: /usr/libexec/gdm-simple-slave --display-id /org/gnome/DisplayManager/Displays/_0 crash_function: _IO_vfprintf_internal executable: /usr/libexec/gdm-simple-slave kernel: 3.11.0-0.rc2.git3.1.fc20.x86_64 runlevel: 3 5 uid: 0 Truncated backtrace: Thread no. 1 (4 frames) #0 _IO_vfprintf_internal at vfprintf.c:257 #1 buffered_vfprintf at vfprintf.c:2328 #2 _IO_vfprintf_internal at vfprintf.c:1289 #3 __stpcpy_chk at ../sysdeps/x86_64/strcpy_chk.S:118
Created attachment 780919 [details] File: backtrace
Created attachment 780920 [details] File: cgroup
Created attachment 780921 [details] File: core_backtrace
Created attachment 780922 [details] File: dso_list
Created attachment 780923 [details] File: environ
Created attachment 780924 [details] File: exploitable
Created attachment 780925 [details] File: limits
Created attachment 780926 [details] File: maps
Created attachment 780927 [details] File: open_fds
Created attachment 780928 [details] File: proc_pid_status
Created attachment 780929 [details] File: var_log_messages
Bambang, do you know why your backtrace has this at the top of it: warning: core file may not match specified executable file. ? Have you been building gdm from source or so?
(In reply to Ray Strode [halfline] from comment #12) > Bambang, do you know why your backtrace has this at the top of it: > > warning: core file may not match specified executable file. > > ? Have you been building gdm from source or so? Hi Ray, I configured ABRT to report automatically. So, sorry, I do not know the backtrace has the one that you mentioned. I did not build gdm from the source. I just use rawhide (for my experience), and hopefully can contribute to the community. I guess, this happened yesterday when I logged out from the system, and the gdm crashed (probably, that was a stage which the abrt reported the errors). Then I logged in into text mode and then powered off the system (since it was after work hour and I need to go home...). Sorry, I can only give you this tiny information, but I will also look at these reported files. Thanks.
This bug appears to have been reported against 'rawhide' during the Fedora 20 development cycle. Changing version to '20'. More information and reason for this action is here: https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora20
Another user experienced a similar problem: I was trying to exit out of Keepass running under Mono I think is what triggered it. reporter: libreport-2.2.3 backtrace_rating: 4 cmdline: /usr/libexec/gdm-simple-slave --display-id /org/gnome/DisplayManager/Displays/_0 crash_function: _IO_vfprintf_internal executable: /usr/libexec/gdm-simple-slave kernel: 3.16.7-200.fc20.x86_64 package: gdm-3.10.0.1-1.fc20 reason: gdm-simple-slave killed by SIGSEGV runlevel: unknown type: CCpp uid: 0
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' of '20'. 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 bug. Thank you for reporting this bug and we are sorry it could not be fixed.