Hide Forgot
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
Created attachment 794766 [details] File: backtrace
Created attachment 794767 [details] File: cgroup
Created attachment 794768 [details] File: core_backtrace
Created attachment 794769 [details] File: dso_list
Created attachment 794770 [details] File: environ
Created attachment 794771 [details] File: exploitable
Created attachment 794772 [details] File: limits
Created attachment 794773 [details] File: maps
Created attachment 794774 [details] File: open_fds
Created attachment 794775 [details] File: proc_pid_status
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
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.
*** Bug 1005438 has been marked as a duplicate of this bug. ***
*** This bug has been marked as a duplicate of bug 1004062 ***