Bug 995703

Summary: [abrt] gdm-3.8.3-2.fc19: __strlen_sse2: Process /usr/libexec/gdm-session-worker was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: Milan Bouchet-Valat <nalimilan>
Component: gdmAssignee: Ray Strode [halfline] <rstrode>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 19CC: m, rstrode
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:c3160189693ec1c6ccdb481088fc1d03e3a2196f
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-02-17 16:41:34 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace
none
File: cgroup
none
File: core_backtrace
none
File: dso_list
none
File: environ
none
File: exploitable
none
File: limits
none
File: maps
none
File: open_fds
none
File: proc_pid_status
none
File: var_log_messages none

Description Milan Bouchet-Valat 2013-08-10 08:41:30 UTC 
Description of problem:
Happens on every boot, but login still works.

Version-Release number of selected component:
gdm-3.8.3-2.fc19

Additional info:
reporter:       libreport-2.1.6
backtrace_rating: 4
cmdline:        'gdm-session-worker [pam/gdm-fingerprint]'
crash_function: __strlen_sse2
executable:     /usr/libexec/gdm-session-worker
kernel:         3.10.3-300.fc19.x86_64
runlevel:       N 5
uid:            0

Truncated backtrace:
Thread no. 1 (9 frames)
 #0 __strlen_sse2 at ../sysdeps/x86_64/strlen.S:31
 #1 __strdup at strdup.c:41
 #2 pam_sm_authenticate at pam_ecryptfs.c:161
 #3 _pam_dispatch_aux at pam_dispatch.c:110
 #4 _pam_dispatch at pam_dispatch.c:407
 #5 pam_authenticate at pam_auth.c:34
 #6 gdm_session_worker_authenticate_user at gdm-session-worker.c:1159
 #7 do_authenticate at gdm-session-worker.c:2179
 #8 state_change_idle at gdm-session-worker.c:2392
Comment 1 Milan Bouchet-Valat 2013-08-10 08:41:35 UTC 
Created attachment 785120 [details]
File: backtrace
Comment 2 Milan Bouchet-Valat 2013-08-10 08:41:39 UTC 
Created attachment 785121 [details]
File: cgroup
Comment 3 Milan Bouchet-Valat 2013-08-10 08:41:43 UTC 
Created attachment 785122 [details]
File: core_backtrace
Comment 4 Milan Bouchet-Valat 2013-08-10 08:41:46 UTC 
Created attachment 785123 [details]
File: dso_list
Comment 5 Milan Bouchet-Valat 2013-08-10 08:41:49 UTC 
Created attachment 785124 [details]
File: environ
Comment 6 Milan Bouchet-Valat 2013-08-10 08:41:52 UTC 
Created attachment 785125 [details]
File: exploitable
Comment 7 Milan Bouchet-Valat 2013-08-10 08:41:56 UTC 
Created attachment 785126 [details]
File: limits
Comment 8 Milan Bouchet-Valat 2013-08-10 08:42:04 UTC 
Created attachment 785127 [details]
File: maps
Comment 9 Milan Bouchet-Valat 2013-08-10 08:42:07 UTC 
Created attachment 785128 [details]
File: open_fds
Comment 10 Milan Bouchet-Valat 2013-08-10 08:42:11 UTC 
Created attachment 785129 [details]
File: proc_pid_status
Comment 11 Milan Bouchet-Valat 2013-08-10 08:42:14 UTC 
Created attachment 785130 [details]
File: var_log_messages
Comment 12 Milan Bouchet-Valat 2013-09-30 08:04:27 UTC 
Happens on every boot, but the crash is not visible.

reporter:       libreport-2.1.7
backtrace_rating: 4
cmdline:        'gdm-session-worker [pam/gdm-fingerprint]'
crash_function: __strlen_sse2
executable:     /usr/libexec/gdm-session-worker
kernel:         3.11.2-201.fc19.x86_64
package:        gdm-3.8.4-2.fc19
reason:         Process /usr/libexec/gdm-session-worker was killed by signal 11 (SIGSEGV)
runlevel:       unknown
type:           CCpp
uid:            0
Comment 13 Ray Strode [halfline] 2013-09-30 20:26:20 UTC 
probably fixed by:

https://git.gnome.org/browse/gdm/commit/?h=gnome-3-8&id=87a3663d1734915efefb2bea29c8ed4488441364
Comment 14 Fedora End Of Life 2015-01-09 19:23:13 UTC 
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.
Comment 15 Fedora End Of Life 2015-02-17 16:41:34 UTC 
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.