Bug 1005253

Summary: [abrt] yum-3.4.3-54.fc18: __strlen_sse2: Process /usr/bin/python2.7 was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: rekaeuqs1
Component: yumAssignee: Packaging Maintenance Team <packaging-team-maint>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 18CC: admiller, ffesti, firas.alkafri, mark.a.sloan, packaging-team-maint, suren, tchollingsworth, tim.lauridsen, zpavlas
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Unspecified   
Whiteboard: abrt_hash:20fae974bd9f3b65a8e3995b3c91d204e8a15fe7
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-09-09 10:16:55 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

Description rekaeuqs1 2013-09-06 14:07:27 UTC 
Description of problem:
This problem happened during a regular yum upgrade

Version-Release number of selected component:
yum-3.4.3-54.fc18

Additional info:
reporter:       libreport-2.1.6
backtrace_rating: 4
cmdline:        /usr/bin/python /bin/yum upgrade -y
crash_function: __strlen_sse2
executable:     /usr/bin/python2.7
kernel:         3.10.6-100.fc18.i686
runlevel:       N 5
uid:            0
var_log_messages: Sep  6 09:53:55 brosef abrt[2438]: Saved core dump of pid 2410 (/usr/bin/python2.7) to /var/tmp/abrt/ccpp-2013-09-06-09:53:50-2410 (100569088 bytes)

Truncated backtrace:
Thread no. 1 (10 frames)
 #0 __strlen_sse2 at ../sysdeps/i386/i686/multiarch/strlen-sse2.S:62
 #1 rpmluaRunScript at rpmlua.c:495
 #2 runLuaScript at rpmscript.c:70
 #3 rpmScriptRun at rpmscript.c:316
 #4 runScript at psm.c:423
 #5 runInstScript at psm.c:455
 #6 rpmpsmStage at psm.c:961
 #7 rpmpsmRun at psm.c:1051
 #8 rpmteProcess at rpmte.c:953
 #9 runTransScripts at transaction.c:1080
Comment 1 rekaeuqs1 2013-09-06 14:07:32 UTC 
Created attachment 794766 [details]
File: backtrace
Comment 2 rekaeuqs1 2013-09-06 14:07:36 UTC 
Created attachment 794767 [details]
File: cgroup
Comment 3 rekaeuqs1 2013-09-06 14:07:41 UTC 
Created attachment 794768 [details]
File: core_backtrace
Comment 4 rekaeuqs1 2013-09-06 14:07:48 UTC 
Created attachment 794769 [details]
File: dso_list
Comment 5 rekaeuqs1 2013-09-06 14:07:53 UTC 
Created attachment 794770 [details]
File: environ
Comment 6 rekaeuqs1 2013-09-06 14:07:57 UTC 
Created attachment 794771 [details]
File: exploitable
Comment 7 rekaeuqs1 2013-09-06 14:08:02 UTC 
Created attachment 794772 [details]
File: limits
Comment 8 rekaeuqs1 2013-09-06 14:08:12 UTC 
Created attachment 794773 [details]
File: maps
Comment 9 rekaeuqs1 2013-09-06 14:08:17 UTC 
Created attachment 794774 [details]
File: open_fds
Comment 10 rekaeuqs1 2013-09-06 14:08:21 UTC 
Created attachment 794775 [details]
File: proc_pid_status
Comment 11 Mark 2013-09-06 17:10:17 UTC 
ran a yum update. 

reporter:       libreport-2.1.6
backtrace_rating: 4
cmdline:        /usr/bin/python /bin/yum update
crash_function: __strlen_sse2
executable:     /usr/bin/python2.7
kernel:         3.10.10-100.fc18.x86_64
package:        yum-3.4.3-54.fc18
reason:         Process /usr/bin/python2.7 was killed by signal 11 (SIGSEGV)
runlevel:       N 5
uid:            0
Comment 12 Suren Karapetyan 2013-09-08 12:11:57 UTC 
I narrowed this down to firefox-23.0.1-4.fc18 (x86_64) from updates-testing. Everything else updates fine.
I can reproduce this on two systems.
firefox-23.0.1-4.fc18.x86_64.rpm can't be installed with rpm either.
Comment 13 T.C. Hollingsworth 2013-09-09 00:05:29 UTC 
*** Bug 1005438 has been marked as a duplicate of this bug. ***
Comment 14 Suren Karapetyan 2013-09-09 10:16:55 UTC 

*** This bug has been marked as a duplicate of bug 1004062 ***