>>> Installing (4 of 5) kde-base/plasma-workspace-4.3.3-r1 * Cleaning orphaned Python bytecode from /usr/lib64/python2.6/site-packages/PyKDE4 .. * Cleaning orphaned Python bytecode from /usr/share/apps/plasma_scriptengine_python .. * Compilation and optimization of Python modules for Python 2.6 ... [ ok ] /usr/lib64/portage/bin/ebuild.sh: line 1622: 5673 Segmentation fault "${PORTAGE_BIN_PATH}"/filter-bash-environment.py "${filtered_vars}" * * ERROR: kde-base/plasma-workspace-4.3.3-r1 failed. * Call stack: * misc-functions.sh, line 18: Called source '/usr/lib64/portage/bin/ebuild.sh' * ebuild.sh, line 1776: Called die * The specific snippet of code: * preprocess_ebuild_env || \ * die "error processing environment" * The die message: * error processing environment * * If you need support, post the topmost build error, and the call stack if relevant. * A complete build log is located at '/var/tmp/portage/kde-base/plasma-workspace-4.3.3-r1/temp/build.log'. * The ebuild environment file is located at '/var/tmp/portage/kde-base/plasma-workspace-4.3.3-r1/temp/environment'. * !!! post postinst failed; exiting. !!! FAILED postinst: 1 No further useful info in the build log. ?????
Created attachment 210964 [details] output of emerge --info
Can try installing it again, to see if the segfault occurs again in the same place and report it in this bug?
I was re-emerging the package already. No, the problem is not reproducible. The second time everything worked fine. Some sort of Heisenbug. Let's leave it NEEDINFO for now. I remember seeing this message before once already, but have no idea anymore what package that was...
Exactly. As i've already seen such errors before they were 100% nonreproducible. It looks more like random hardware failure. I'd run memtest to see if it may be RAM problem.
Closing as WORKSFORME.
