Description of problem: Had just suspend and reload my computer when the error message appeared. Version-Release number of selected component: gdm-3.8.3-2.fc19 Additional info: reporter: libreport-2.1.5 backtrace_rating: 4 cmdline: 'gdm-session-worker [pam/gdm-password]' crash_function: vasprintf executable: /usr/libexec/gdm-session-worker kernel: 3.9.8-300.fc19.i686 runlevel: N 5 uid: 0 var_log_messages: Jul 5 00:02:36 ulis-desktop abrt[2487]: Saved core dump of pid 2482 (/usr/libexec/gdm-session-worker) to /var/tmp/abrt/ccpp-2013-07-05-00:02:36-2482 (19091456 bytes) Truncated backtrace: Thread no. 1 (10 frames) #3 vasprintf at /usr/include/bits/stdio2.h:210 #4 g_vasprintf at gprintf.c:314 #5 g_strdup_vprintf at gstrfuncs.c:517 #8 gdm_session_worker_process_pam_message at gdm-session-worker.c:804 #9 gdm_session_worker_pam_new_messages_handler at gdm-session-worker.c:849 #10 pam_vprompt at pam_vprompt.c:83 #11 pam_prompt at pam_vprompt.c:111 #12 _unix_read_password at support.c:825 #13 pam_sm_authenticate at pam_unix_auth.c:160 #14 _pam_dispatch_aux at pam_dispatch.c:110 Potential duplicate: bug 876729
Created attachment 769024 [details] File: backtrace
Created attachment 769025 [details] File: cgroup
Created attachment 769026 [details] File: core_backtrace
Created attachment 769027 [details] File: dso_list
Created attachment 769028 [details] File: environ
Created attachment 769029 [details] File: limits
Created attachment 769030 [details] File: maps
Created attachment 769031 [details] File: open_fds
Created attachment 769032 [details] File: proc_pid_status
Tomas, has there been any heap corruption bugs in pam_unix recently? This bug and bug 983024 seem to show memory corruption after pam_unix is loaded.
(In reply to Ray Strode [halfline] from comment #10) > Tomas, has there been any heap corruption bugs in pam_unix recently? This > bug and bug 983024 seem to show memory corruption after pam_unix is loaded. No, there are no such known bugs and I don't see any reports where such corruption would be seen with other services than gdm.
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 bug. Thank you for reporting this bug and we are sorry it could not be fixed.