| View previous topic :: View next topic |
| Author |
Message |
BT
Guru
Joined: 13 Jun 2004
Posts: 318
|
 Posted: Thu Jun 22, 2023 5:09 am Post subject: [SOLVED] dev-libs/openssl-3.0.9 update broke my system |
 |
|
I had a large system update today, mostly KDE Frameworks and KDE Apps, but also OpenSSL which triggered a lot of rebuilds. The update failed right after the OpenSSL merge phase with the following error:
| Code: | >>> Regenerating /etc/ld.so.cache...
>>> Original instance of package unmerged safely.
sort: error while loading shared libraries: libcrypto.so.1.1: cannot open shared object file: No such file or directory
* Running 'openssl rehash /etc/ssl/certs' to rebuild hashes (bug #333069) ...
rehash: warning: skipping ca-certificates.crt,it does not contain exactly one certificate or CRL [ ok ]
sort: error while loading shared libraries: libcrypto.so.1.1: cannot open shared object file: No such file or directory
* ACCESS DENIED: opendir: /usr/local/lib/postinst-qa-check.d
* ACCESS DENIED: opendir: /usr/lib/postinst-qa-check.d
* ACCESS DENIED: opendir: /var/db/repos/gentoo/metadata/postinst-qa-check.d
* ACCESS DENIED: opendir: /usr/lib/portage/postinst-qa-check.d
* ACCESS DENIED: opendir: /usr/lib/portage/python3.11/postinst-qa-check.d
/usr/lib/portage/python3.11/misc-functions.sh: line 322: /dev/fd/63: Permission denied
* ACCESS DENIED: execve: /usr/lib/portage/python3.11/ebuild-ipc
/usr/lib/portage/python3.11/misc-functions.sh: line 692: /usr/lib/portage/python3.11/ebuild-ipc: Permission denied
* ACCESS DENIED: execve: /usr/bin/sort
/usr/lib/portage/python3.11/misc-functions.sh: line 322: /usr/bin/sort: Permission denied
* ----------------------- SANDBOX ACCESS VIOLATION SUMMARY -----------------------
* LOG FILE: "/var/tmp/portage/dev-libs/openssl-3.0.9/temp/sandbox-misc.log"
*
VERSION 1.0
FORMAT: F - Function called
FORMAT: S - Access Status
FORMAT: P - Path as passed to function
FORMAT: A - Absolute Path (not canonical)
FORMAT: R - Canonical Path
FORMAT: C - Command Line
F: opendir
S: deny
P: /usr/local/lib/postinst-qa-check.d/
A: /usr/local/lib/postinst-qa-check.d
R: /usr/local/lib/postinst-qa-check.d
C: bash /usr/lib/portage/python3.11/misc-functions.sh postinst_qa_check
F: opendir
S: deny
P: /usr/lib/postinst-qa-check.d/
A: /usr/lib/postinst-qa-check.d
R: /usr/lib/postinst-qa-check.d
C: bash /usr/lib/portage/python3.11/misc-functions.sh postinst_qa_check
F: opendir
S: deny
P: /var/db/repos/gentoo/metadata/postinst-qa-check.d/
A: /var/db/repos/gentoo/metadata/postinst-qa-check.d
R: /var/db/repos/gentoo/metadata/postinst-qa-check.d
C: bash /usr/lib/portage/python3.11/misc-functions.sh postinst_qa_check
F: opendir
S: deny
P: /usr/lib/portage/postinst-qa-check.d/
A: /usr/lib/portage/postinst-qa-check.d
R: /usr/lib/portage/postinst-qa-check.d
C: bash /usr/lib/portage/python3.11/misc-functions.sh postinst_qa_check
F: opendir
S: deny
P: /usr/lib/portage/python3.11/postinst-qa-check.d/
A: /usr/lib/portage/python3.11/postinst-qa-check.d
R: /usr/lib/portage/python3.11/postinst-qa-check.d
C: bash /usr/lib/portage/python3.11/misc-functions.sh postinst_qa_check
F: execve
S: deny
P: /usr/lib/portage/python3.11/ebuild-ipc
A: /usr/lib/portage/python3.11/ebuild-ipc
R: /usr/lib/portage/python3.11/ebuild-ipc
C: bash /usr/lib/portage/python3.11/misc-functions.sh postinst_qa_check
F: execve
S: deny
P: /usr/bin/sort
A: /usr/bin/sort
R: /bin/sort
C: bash /usr/lib/portage/python3.11/misc-functions.sh postinst_qa_check
* --------------------------------------------------------------------------------
* The ebuild phase 'postinst' has exited unexpectedly. This type of
* behavior is known to be triggered by things such as failed variable
* assignments (bug #190128) or bad substitution errors (bug #200313).
* Normally, before exiting, bash should have displayed an error message
* above. If bash did not produce an error message above, it's possible
* that the ebuild has called `exit` when it should have called `die`
* instead. This behavior may also be triggered by a corrupt bash binary or
* a hardware problem such as memory or cpu malfunction. If the problem is
* not reproducible or it appears to occur randomly, then it is likely to
* be triggered by a hardware problem. If you suspect a hardware problem
* then you should try some basic hardware diagnostics such as memtest.
* Please do not report this as a bug unless it is consistently
* reproducible and you are sure that your bash binary and hardware are
* functioning properly.
!!! post postinst failed; exiting.
sort: error while loading shared libraries: libcrypto.so.1.1: cannot open shared object file: No such file or directory
* ACCESS DENIED: execve: /usr/lib/portage/python3.11/ebuild-ipc
/usr/lib/portage/python3.11/misc-functions.sh: line 692: /usr/lib/portage/python3.11/ebuild-ipc: Permission denied
* ----------------------- SANDBOX ACCESS VIOLATION SUMMARY -----------------------
* LOG FILE: "/var/tmp/portage/dev-libs/openssl-3.0.9/temp/sandbox-misc.log"
*
VERSION 1.0
FORMAT: F - Function called
FORMAT: S - Access Status
FORMAT: P - Path as passed to function
FORMAT: A - Absolute Path (not canonical)
FORMAT: R - Canonical Path
FORMAT: C - Command Line
F: execve
S: deny
P: /usr/lib/portage/python3.11/ebuild-ipc
A: /usr/lib/portage/python3.11/ebuild-ipc
R: /usr/lib/portage/python3.11/ebuild-ipc
C: bash /usr/lib/portage/python3.11/misc-functions.sh die_hooks
* --------------------------------------------------------------------------------
* The ebuild phase 'die_hooks' has exited unexpectedly. This type of
* behavior is known to be triggered by things such as failed variable
* assignments (bug #190128) or bad substitution errors (bug #200313).
* Normally, before exiting, bash should have displayed an error message
* above. If bash did not produce an error message above, it's possible
* that the ebuild has called `exit` when it should have called `die`
* instead. This behavior may also be triggered by a corrupt bash binary or
* a hardware problem such as memory or cpu malfunction. If the problem is
* not reproducible or it appears to occur randomly, then it is likely to
* be triggered by a hardware problem. If you suspect a hardware problem
* then you should try some basic hardware diagnostics such as memtest.
* Please do not report this as a bug unless it is consistently
* reproducible and you are sure that your bash binary and hardware are
* functioning properly.
* FAILED postinst: 1
>>> Regenerating /etc/ld.so.cache...
sort: error while loading shared libraries: libcrypto.so.1.1: cannot open shared object file: No such file or directory
* ACCESS DENIED: execve: /usr/lib/portage/python3.11/ebuild-ipc
/usr/lib/portage/python3.11/misc-functions.sh: line 692: /usr/lib/portage/python3.11/ebuild-ipc: Permission denied
* ----------------------- SANDBOX ACCESS VIOLATION SUMMARY -----------------------
* LOG FILE: "/var/tmp/portage/dev-libs/openssl-3.0.9/temp/sandbox-misc.log"
*
VERSION 1.0
FORMAT: F - Function called
FORMAT: S - Access Status
FORMAT: P - Path as passed to function
FORMAT: A - Absolute Path (not canonical)
FORMAT: R - Canonical Path
FORMAT: C - Command Line
F: execve
S: deny
P: /usr/lib/portage/python3.11/ebuild-ipc
A: /usr/lib/portage/python3.11/ebuild-ipc
R: /usr/lib/portage/python3.11/ebuild-ipc
C: bash /usr/lib/portage/python3.11/misc-functions.sh success_hooks
* --------------------------------------------------------------------------------
* The ebuild phase 'other' has exited unexpectedly. This type of behavior
* is known to be triggered by things such as failed variable assignments
* (bug #190128) or bad substitution errors (bug #200313). Normally, before
* exiting, bash should have displayed an error message above. If bash did
* not produce an error message above, it's possible that the ebuild has
* called `exit` when it should have called `die` instead. This behavior
* may also be triggered by a corrupt bash binary or a hardware problem
* such as memory or cpu malfunction. If the problem is not reproducible or
* it appears to occur randomly, then it is likely to be triggered by a
* hardware problem. If you suspect a hardware problem then you should try
* some basic hardware diagnostics such as memtest. Please do not report
* this as a bug unless it is consistently reproducible and you are sure
* that your bash binary and hardware are functioning properly.
>>> Failed dev-libs/openssl-3.0.9::gentoo
>>> Failed to execute postinst for dev-libs/openssl-3.0.9
>>> Emerging (4 of 232) sys-apps/coreutils-9.3-r2::gentoo
* coreutils-9.3.tar.xz BLAKE2B SHA512 size ;-) ... [ ok ]
* coreutils-9.0_p20220409-patches-01.tar.xz BLAKE2B SHA512 size ;-) ... [ ok ]
sort: error while loading shared libraries: libcrypto.so.1.1: cannot open shared object file: No such file or directory
sort: error while loading shared libraries: libcrypto.so.1.1: cannot open shared object file: No such file or directory
* ACCESS DENIED: open_wr: /dev/null
/usr/lib/portage/python3.11/phase-functions.sh: line 912: /dev/null: Permission denied
* ACCESS DENIED: open_wr: /dev/null
/usr/lib/portage/python3.11/phase-functions.sh: line 914: /dev/null: Permission denied
* ACCESS DENIED: open_wr: /dev/null
/usr/lib/portage/python3.11/phase-functions.sh: line 916: /dev/null: Permission denied
* ACCESS DENIED: open_wr: /dev/null
/usr/lib/portage/python3.11/phase-functions.sh: line 918: /dev/null: Permission denied
* ACCESS DENIED: open_wr: /dev/null
/usr/lib/portage/python3.11/phase-functions.sh: line 920: /dev/null: Permission denied
* ACCESS DENIED: open_wr: /dev/null
/usr/lib/portage/python3.11/phase-functions.sh: line 922: /dev/null: Permission denied
* ACCESS DENIED: open_wr: /dev/null
/usr/lib/portage/python3.11/phase-functions.sh: line 930: /dev/null: Permission denied
* ACCESS DENIED: open_wr: /dev/null
/usr/lib/portage/python3.11/phase-functions.sh: line 941: /dev/null: Permission denied
* ACCESS DENIED: open_wr: /dev/null
/usr/lib/portage/python3.11/phase-functions.sh: line 216: /dev/null: Permission denied
>>> Unpacking source...
* ACCESS DENIED: open_wr: /dev/null
/usr/lib/portage/python3.11/phase-functions.sh: line 216: /dev/null: Permission denied
* ACCESS DENIED: open_wr: /var/tmp/portage/sys-apps/coreutils-9.3-r2/.unpacked
/usr/lib/portage/python3.11/phase-functions.sh: line 271: /var/tmp/portage/sys-apps/coreutils-9.3-r2/.unpacked: Permission denied
* ACCESS DENIED: open_wr: /var/tmp/portage/sys-apps/coreutils-9.3-r2/temp/logging/unpack
/usr/lib/portage/python3.11/isolated-functions.sh: line 265: /var/tmp/portage/sys-apps/coreutils-9.3-r2/temp/logging/unpack: Permission denied
* ERROR: sys-apps/coreutils-9.3-r2::gentoo failed (unpack phase):
* ACCESS DENIED: open_wr: /var/tmp/portage/sys-apps/coreutils-9.3-r2/temp/logging/unpack
/usr/lib/portage/python3.11/isolated-functions.sh: line 265: /var/tmp/portage/sys-apps/coreutils-9.3-r2/temp/logging/unpack: Permission denied
* Failed to create /var/tmp/portage/sys-apps/coreutils-9.3-r2/.unpacked
* ACCESS DENIED: open_wr: /var/tmp/portage/sys-apps/coreutils-9.3-r2/temp/logging/unpack
/usr/lib/portage/python3.11/isolated-functions.sh: line 265: /var/tmp/portage/sys-apps/coreutils-9.3-r2/temp/logging/unpack: Permission denied
*
* ACCESS DENIED: open_wr: /var/tmp/portage/sys-apps/coreutils-9.3-r2/temp/logging/unpack
/usr/lib/portage/python3.11/isolated-functions.sh: line 265: /var/tmp/portage/sys-apps/coreutils-9.3-r2/temp/logging/unpack: Permission denied
* Call stack:
* ACCESS DENIED: execve: /usr/bin/basename
/usr/lib/portage/python3.11/isolated-functions.sh: line 76: /usr/bin/basename: Permission denied
* ACCESS DENIED: open_wr: /var/tmp/portage/sys-apps/coreutils-9.3-r2/temp/logging/unpack
/usr/lib/portage/python3.11/isolated-functions.sh: line 265: /var/tmp/portage/sys-apps/coreutils-9.3-r2/temp/logging/unpack: Permission denied
* , line 780: Called __ebuild_main 'unpack'
* ACCESS DENIED: execve: /usr/bin/basename
/usr/lib/portage/python3.11/isolated-functions.sh: line 76: /usr/bin/basename: Permission denied
* ACCESS DENIED: open_wr: /var/tmp/portage/sys-apps/coreutils-9.3-r2/temp/logging/unpack
/usr/lib/portage/python3.11/isolated-functions.sh: line 265: /var/tmp/portage/sys-apps/coreutils-9.3-r2/temp/logging/unpack: Permission denied
* , line 1072: Called __dyn_unpack
* ACCESS DENIED: open_wr: /var/tmp/portage/sys-apps/coreutils-9.3-r2/temp/logging/unpack
/usr/lib/portage/python3.11/isolated-functions.sh: line 265: /var/tmp/portage/sys-apps/coreutils-9.3-r2/temp/logging/unpack: Permission denied
* phase-functions.sh, line 272: Called die
* ACCESS DENIED: open_wr: /var/tmp/portage/sys-apps/coreutils-9.3-r2/temp/logging/unpack
/usr/lib/portage/python3.11/isolated-functions.sh: line 265: /var/tmp/portage/sys-apps/coreutils-9.3-r2/temp/logging/unpack: Permission denied
* The specific snippet of code:
* ACCESS DENIED: execve: /bin/sed
/usr/lib/portage/python3.11/isolated-functions.sh: line 177: /bin/sed: Permission denied
* ACCESS DENIED: execve: /bin/sed
/usr/lib/portage/python3.11/isolated-functions.sh: line 190: /bin/sed: Permission denied
* ACCESS DENIED: open_wr: /var/tmp/portage/sys-apps/coreutils-9.3-r2/temp/logging/unpack
/usr/lib/portage/python3.11/isolated-functions.sh: line 265: /var/tmp/portage/sys-apps/coreutils-9.3-r2/temp/logging/unpack: Permission denied
*
* ACCESS DENIED: open_wr: /var/tmp/portage/sys-apps/coreutils-9.3-r2/temp/logging/unpack
/usr/lib/portage/python3.11/isolated-functions.sh: line 265: /var/tmp/portage/sys-apps/coreutils-9.3-r2/temp/logging/unpack: Permission denied
* If you need support, post the output of `emerge --info '=sys-apps/coreutils-9.3-r2::gentoo'`,
* ACCESS DENIED: open_wr: /var/tmp/portage/sys-apps/coreutils-9.3-r2/temp/logging/unpack
/usr/lib/portage/python3.11/isolated-functions.sh: line 265: /var/tmp/portage/sys-apps/coreutils-9.3-r2/temp/logging/unpack: Permission denied
* the complete build log and the output of `emerge -pqv '=sys-apps/coreutils-9.3-r2::gentoo'`.
* ACCESS DENIED: open_wr: /var/tmp/portage/sys-apps/coreutils-9.3-r2/.die_hooks
/usr/lib/portage/python3.11/isolated-functions.sh: line 207: /var/tmp/portage/sys-apps/coreutils-9.3-r2/.die_hooks: Permission denied
* ACCESS DENIED: open_wr: /var/tmp/portage/sys-apps/coreutils-9.3-r2/temp/logging/unpack
/usr/lib/portage/python3.11/isolated-functions.sh: line 265: /var/tmp/portage/sys-apps/coreutils-9.3-r2/temp/logging/unpack: Permission denied
* The complete build log is located at '/var/tmp/portage/sys-apps/coreutils-9.3-r2/temp/build.log'.
* ACCESS DENIED: open_wr: /var/tmp/portage/sys-apps/coreutils-9.3-r2/temp/logging/unpack
/usr/lib/portage/python3.11/isolated-functions.sh: line 265: /var/tmp/portage/sys-apps/coreutils-9.3-r2/temp/logging/unpack: Permission denied
* The ebuild environment file is located at '/var/tmp/portage/sys-apps/coreutils-9.3-r2/temp/environment'.
* ACCESS DENIED: open_wr: /var/tmp/portage/sys-apps/coreutils-9.3-r2/temp/logging/unpack
/usr/lib/portage/python3.11/isolated-functions.sh: line 265: /var/tmp/portage/sys-apps/coreutils-9.3-r2/temp/logging/unpack: Permission denied
* Working directory: '/var/tmp/portage/sys-apps/coreutils-9.3-r2/work'
* ACCESS DENIED: open_wr: /var/tmp/portage/sys-apps/coreutils-9.3-r2/temp/logging/unpack
/usr/lib/portage/python3.11/isolated-functions.sh: line 265: /var/tmp/portage/sys-apps/coreutils-9.3-r2/temp/logging/unpack: Permission denied
* S: '/var/tmp/portage/sys-apps/coreutils-9.3-r2/work/coreutils-9.3'
* ACCESS DENIED: execve: /usr/lib/portage/python3.11/ebuild-ipc
/usr/lib/portage/python3.11/isolated-functions.sh: line 233: /usr/lib/portage/python3.11/ebuild-ipc: Permission denied
* ----------------------- SANDBOX ACCESS VIOLATION SUMMARY -----------------------
* LOG FILE: "/var/tmp/portage/sys-apps/coreutils-9.3-r2/temp/sandbox.log"
*
VERSION 1.0
FORMAT: F - Function called
FORMAT: S - Access Status
FORMAT: P - Path as passed to function
FORMAT: A - Absolute Path (not canonical)
FORMAT: R - Canonical Path
FORMAT: C - Command Line
F: open_wr
S: deny
P: /dev/null
A: /dev/null
R: /dev/null
C: bash /usr/lib/portage/python3.11/ebuild.sh unpack
F: open_wr
S: deny
P: /dev/null
A: /dev/null
R: /dev/null
C: bash /usr/lib/portage/python3.11/ebuild.sh unpack
F: open_wr
S: deny
P: /dev/null
A: /dev/null
R: /dev/null
C: bash /usr/lib/portage/python3.11/ebuild.sh unpack
F: open_wr
S: deny
P: /dev/null
A: /dev/null
R: /dev/null
C: bash /usr/lib/portage/python3.11/ebuild.sh unpack
F: open_wr
S: deny
P: /dev/null
A: /dev/null
R: /dev/null
C: bash /usr/lib/portage/python3.11/ebuild.sh unpack
F: open_wr
S: deny
P: /dev/null
A: /dev/null
R: /dev/null
C: bash /usr/lib/portage/python3.11/ebuild.sh unpack
F: open_wr
S: deny
P: /dev/null
A: /dev/null
R: /dev/null
C: bash /usr/lib/portage/python3.11/ebuild.sh unpack
F: open_wr
S: deny
P: /dev/null
A: /dev/null
R: /dev/null
C: bash /usr/lib/portage/python3.11/ebuild.sh unpack
F: open_wr
S: deny
P: /dev/null
A: /dev/null
R: /dev/null
C: bash /usr/lib/portage/python3.11/ebuild.sh unpack
F: open_wr
S: deny
P: /dev/null
A: /dev/null
R: /dev/null
C: bash /usr/lib/portage/python3.11/ebuild.sh unpack
F: open_wr
S: deny
P: /var/tmp/portage/sys-apps/coreutils-9.3-r2/.unpacked
A: /var/tmp/portage/sys-apps/coreutils-9.3-r2/.unpacked
R: /var/tmp/portage/sys-apps/coreutils-9.3-r2/.unpacked
C: bash /usr/lib/portage/python3.11/ebuild.sh unpack
F: open_wr
S: deny
P: /var/tmp/portage/sys-apps/coreutils-9.3-r2/temp/logging/unpack
A: /var/tmp/portage/sys-apps/coreutils-9.3-r2/temp/logging/unpack
R: /var/tmp/portage/sys-apps/coreutils-9.3-r2/temp/logging/unpack
C: bash /usr/lib/portage/python3.11/ebuild.sh unpack
F: open_wr
S: deny
P: /var/tmp/portage/sys-apps/coreutils-9.3-r2/temp/logging/unpack
A: /var/tmp/portage/sys-apps/coreutils-9.3-r2/temp/logging/unpack
R: /var/tmp/portage/sys-apps/coreutils-9.3-r2/temp/logging/unpack
C: bash /usr/lib/portage/python3.11/ebuild.sh unpack
F: open_wr
S: deny
P: /var/tmp/portage/sys-apps/coreutils-9.3-r2/temp/logging/unpack
A: /var/tmp/portage/sys-apps/coreutils-9.3-r2/temp/logging/unpack
R: /var/tmp/portage/sys-apps/coreutils-9.3-r2/temp/logging/unpack
C: bash /usr/lib/portage/python3.11/ebuild.sh unpack
F: open_wr
S: deny
P: /var/tmp/portage/sys-apps/coreutils-9.3-r2/temp/logging/unpack
A: /var/tmp/portage/sys-apps/coreutils-9.3-r2/temp/logging/unpack
R: /var/tmp/portage/sys-apps/coreutils-9.3-r2/temp/logging/unpack
C: bash /usr/lib/portage/python3.11/ebuild.sh unpack
F: execve
S: deny
P: /usr/bin/basename
A: /usr/bin/basename
R: /bin/basename
C: bash /usr/lib/portage/python3.11/ebuild.sh unpack
F: open_wr
S: deny
P: /var/tmp/portage/sys-apps/coreutils-9.3-r2/temp/logging/unpack
A: /var/tmp/portage/sys-apps/coreutils-9.3-r2/temp/logging/unpack
R: /var/tmp/portage/sys-apps/coreutils-9.3-r2/temp/logging/unpack
C: bash /usr/lib/portage/python3.11/ebuild.sh unpack
F: execve
S: deny
P: /usr/bin/basename
A: /usr/bin/basename
R: /bin/basename
C: bash /usr/lib/portage/python3.11/ebuild.sh unpack
F: open_wr
S: deny
P: /var/tmp/portage/sys-apps/coreutils-9.3-r2/temp/logging/unpack
A: /var/tmp/portage/sys-apps/coreutils-9.3-r2/temp/logging/unpack
R: /var/tmp/portage/sys-apps/coreutils-9.3-r2/temp/logging/unpack
C: bash /usr/lib/portage/python3.11/ebuild.sh unpack
F: open_wr
S: deny
P: /var/tmp/portage/sys-apps/coreutils-9.3-r2/temp/logging/unpack
A: /var/tmp/portage/sys-apps/coreutils-9.3-r2/temp/logging/unpack
R: /var/tmp/portage/sys-apps/coreutils-9.3-r2/temp/logging/unpack
C: bash /usr/lib/portage/python3.11/ebuild.sh unpack
F: open_wr
S: deny
P: /var/tmp/portage/sys-apps/coreutils-9.3-r2/temp/logging/unpack
A: /var/tmp/portage/sys-apps/coreutils-9.3-r2/temp/logging/unpack
R: /var/tmp/portage/sys-apps/coreutils-9.3-r2/temp/logging/unpack
C: bash /usr/lib/portage/python3.11/ebuild.sh unpack
F: execve
S: deny
P: /bin/sed
A: /bin/sed
R: /bin/gsed
C: bash /usr/lib/portage/python3.11/ebuild.sh unpack
F: execve
S: deny
P: /bin/sed
A: /bin/sed
R: /bin/gsed
C: bash /usr/lib/portage/python3.11/ebuild.sh unpack
F: open_wr
S: deny
P: /var/tmp/portage/sys-apps/coreutils-9.3-r2/temp/logging/unpack
A: /var/tmp/portage/sys-apps/coreutils-9.3-r2/temp/logging/unpack
R: /var/tmp/portage/sys-apps/coreutils-9.3-r2/temp/logging/unpack
C: bash /usr/lib/portage/python3.11/ebuild.sh unpack
F: open_wr
S: deny
P: /var/tmp/portage/sys-apps/coreutils-9.3-r2/temp/logging/unpack
A: /var/tmp/portage/sys-apps/coreutils-9.3-r2/temp/logging/unpack
R: /var/tmp/portage/sys-apps/coreutils-9.3-r2/temp/logging/unpack
C: bash /usr/lib/portage/python3.11/ebuild.sh unpack
F: open_wr
S: deny
P: /var/tmp/portage/sys-apps/coreutils-9.3-r2/temp/logging/unpack
A: /var/tmp/portage/sys-apps/coreutils-9.3-r2/temp/logging/unpack
R: /var/tmp/portage/sys-apps/coreutils-9.3-r2/temp/logging/unpack
C: bash /usr/lib/portage/python3.11/ebuild.sh unpack
F: open_wr
S: deny
P: /var/tmp/portage/sys-apps/coreutils-9.3-r2/.die_hooks
A: /var/tmp/portage/sys-apps/coreutils-9.3-r2/.die_hooks
R: /var/tmp/portage/sys-apps/coreutils-9.3-r2/.die_hooks
C: bash /usr/lib/portage/python3.11/ebuild.sh unpack
F: open_wr
S: deny
P: /var/tmp/portage/sys-apps/coreutils-9.3-r2/temp/logging/unpack
A: /var/tmp/portage/sys-apps/coreutils-9.3-r2/temp/logging/unpack
R: /var/tmp/portage/sys-apps/coreutils-9.3-r2/temp/logging/unpack
C: bash /usr/lib/portage/python3.11/ebuild.sh unpack
F: open_wr
S: deny
P: /var/tmp/portage/sys-apps/coreutils-9.3-r2/temp/logging/unpack
A: /var/tmp/portage/sys-apps/coreutils-9.3-r2/temp/logging/unpack
R: /var/tmp/portage/sys-apps/coreutils-9.3-r2/temp/logging/unpack
C: bash /usr/lib/portage/python3.11/ebuild.sh unpack
F: open_wr
S: deny
P: /var/tmp/portage/sys-apps/coreutils-9.3-r2/temp/logging/unpack
A: /var/tmp/portage/sys-apps/coreutils-9.3-r2/temp/logging/unpack
R: /var/tmp/portage/sys-apps/coreutils-9.3-r2/temp/logging/unpack
C: bash /usr/lib/portage/python3.11/ebuild.sh unpack
F: open_wr
S: deny
P: /var/tmp/portage/sys-apps/coreutils-9.3-r2/temp/logging/unpack
A: /var/tmp/portage/sys-apps/coreutils-9.3-r2/temp/logging/unpack
R: /var/tmp/portage/sys-apps/coreutils-9.3-r2/temp/logging/unpack
C: bash /usr/lib/portage/python3.11/ebuild.sh unpack
F: execve
S: deny
P: /usr/lib/portage/python3.11/ebuild-ipc
A: /usr/lib/portage/python3.11/ebuild-ipc
R: /usr/lib/portage/python3.11/ebuild-ipc
C: bash /usr/lib/portage/python3.11/ebuild.sh unpack
* --------------------------------------------------------------------------------
* The ebuild phase 'unpack' has exited unexpectedly. This type of behavior
* is known to be triggered by things such as failed variable assignments
* (bug #190128) or bad substitution errors (bug #200313). Normally, before
* exiting, bash should have displayed an error message above. If bash did
* not produce an error message above, it's possible that the ebuild has
* called `exit` when it should have called `die` instead. This behavior
* may also be triggered by a corrupt bash binary or a hardware problem
* such as memory or cpu malfunction. If the problem is not reproducible or
* it appears to occur randomly, then it is likely to be triggered by a
* hardware problem. If you suspect a hardware problem then you should try
* some basic hardware diagnostics such as memtest. Please do not report
* this as a bug unless it is consistently reproducible and you are sure
* that your bash binary and hardware are functioning properly.
sort: error while loading shared libraries: libcrypto.so.1.1: cannot open shared object file: No such file or directory
sort: error while loading shared libraries: libcrypto.so.1.1: cannot open shared object file: No such file or directory
* ACCESS DENIED: open_wr: /var/tmp/portage/sys-apps/coreutils-9.3-r2/.die_hooks
/usr/lib/portage/python3.11/misc-functions.sh: line 647: /var/tmp/portage/sys-apps/coreutils-9.3-r2/.die_hooks: Permission denied
* ACCESS DENIED: execve: /usr/lib/portage/python3.11/ebuild-ipc
/usr/lib/portage/python3.11/misc-functions.sh: line 692: /usr/lib/portage/python3.11/ebuild-ipc: Permission denied
* ----------------------- SANDBOX ACCESS VIOLATION SUMMARY -----------------------
* LOG FILE: "/var/tmp/portage/sys-apps/coreutils-9.3-r2/temp/sandbox-misc.log"
*
VERSION 1.0
FORMAT: F - Function called
FORMAT: S - Access Status
FORMAT: P - Path as passed to function
FORMAT: A - Absolute Path (not canonical)
FORMAT: R - Canonical Path
FORMAT: C - Command Line
F: open_wr
S: deny
P: /var/tmp/portage/sys-apps/coreutils-9.3-r2/.die_hooks
A: /var/tmp/portage/sys-apps/coreutils-9.3-r2/.die_hooks
R: /var/tmp/portage/sys-apps/coreutils-9.3-r2/.die_hooks
C: bash /usr/lib/portage/python3.11/misc-functions.sh die_hooks
F: execve
S: deny
P: /usr/lib/portage/python3.11/ebuild-ipc
A: /usr/lib/portage/python3.11/ebuild-ipc
R: /usr/lib/portage/python3.11/ebuild-ipc
C: bash /usr/lib/portage/python3.11/misc-functions.sh die_hooks
* --------------------------------------------------------------------------------
* The ebuild phase 'die_hooks' has exited unexpectedly. This type of
* behavior is known to be triggered by things such as failed variable
* assignments (bug #190128) or bad substitution errors (bug #200313).
* Normally, before exiting, bash should have displayed an error message
* above. If bash did not produce an error message above, it's possible
* that the ebuild has called `exit` when it should have called `die`
* instead. This behavior may also be triggered by a corrupt bash binary or
* a hardware problem such as memory or cpu malfunction. If the problem is
* not reproducible or it appears to occur randomly, then it is likely to
* be triggered by a hardware problem. If you suspect a hardware problem
* then you should try some basic hardware diagnostics such as memtest.
* Please do not report this as a bug unless it is consistently
* reproducible and you are sure that your bash binary and hardware are
* functioning properly.
>>> Failed to emerge sys-apps/coreutils-9.3-r2, Log file:
>>> '/var/tmp/portage/sys-apps/coreutils-9.3-r2/temp/build.log'
* Messages for package dev-libs/openssl-3.0.9:
* The ebuild phase 'postinst' has exited unexpectedly. This type of
* behavior is known to be triggered by things such as failed variable
* assignments (bug #190128) or bad substitution errors (bug #200313).
* Normally, before exiting, bash should have displayed an error message
* above. If bash did not produce an error message above, it's possible
* that the ebuild has called `exit` when it should have called `die`
* instead. This behavior may also be triggered by a corrupt bash binary or
* a hardware problem such as memory or cpu malfunction. If the problem is
* not reproducible or it appears to occur randomly, then it is likely to
* be triggered by a hardware problem. If you suspect a hardware problem
* then you should try some basic hardware diagnostics such as memtest.
* Please do not report this as a bug unless it is consistently
* reproducible and you are sure that your bash binary and hardware are
* functioning properly.
* FAILED postinst: 1
* The ebuild phase 'other' has exited unexpectedly. This type of behavior
* is known to be triggered by things such as failed variable assignments
* (bug #190128) or bad substitution errors (bug #200313). Normally, before
* exiting, bash should have displayed an error message above. If bash did
* not produce an error message above, it's possible that the ebuild has
* called `exit` when it should have called `die` instead. This behavior
* may also be triggered by a corrupt bash binary or a hardware problem
* such as memory or cpu malfunction. If the problem is not reproducible or
* it appears to occur randomly, then it is likely to be triggered by a
* hardware problem. If you suspect a hardware problem then you should try
* some basic hardware diagnostics such as memtest. Please do not report
* this as a bug unless it is consistently reproducible and you are sure
* that your bash binary and hardware are functioning properly.
* Messages for package sys-apps/coreutils-9.3-r2:
* The ebuild phase 'unpack' has exited unexpectedly. This type of behavior
* is known to be triggered by things such as failed variable assignments
* (bug #190128) or bad substitution errors (bug #200313). Normally, before
* exiting, bash should have displayed an error message above. If bash did
* not produce an error message above, it's possible that the ebuild has
* called `exit` when it should have called `die` instead. This behavior
* may also be triggered by a corrupt bash binary or a hardware problem
* such as memory or cpu malfunction. If the problem is not reproducible or
* it appears to occur randomly, then it is likely to be triggered by a
* hardware problem. If you suspect a hardware problem then you should try
* some basic hardware diagnostics such as memtest. Please do not report
* this as a bug unless it is consistently reproducible and you are sure
* that your bash binary and hardware are functioning properly.
*
* The following 2 packages have failed to build, install, or execute
* postinst:
*
* (dev-libs/openssl-3.0.9:0/3::gentoo, ebuild scheduled for merge) (postinst failed)
* (sys-apps/coreutils-9.3-r2:0/0::gentoo, ebuild scheduled for merge), Log file:
* '/var/tmp/portage/sys-apps/coreutils-9.3-r2/temp/build.log'
* |
Now when I try to continue the update or re-install Portage I get the same sanbox violation which seems to be triggered by:
| Code: | | sort: error while loading shared libraries: libcrypto.so.1.1: cannot open shared object file: No such file or directory |
My system is mostly unusable now. I'm still logged in to my KDE desktop and only the already open applications (Firefox, Dolphin, Konsole) are working. I can't start any new applications. Can someone please help me fix this?
Last edited by BT on Thu Jun 22, 2023 6:45 am; edited 1 time in total |
|
| Back to top |
|
 |
sam_
Developer
Joined: 14 Aug 2020
Posts: 1982
|
| Posted: Thu Jun 22, 2023 5:35 am Post subject: |
|
|
| I have a few guesses but it's going to be easier to try debug this on IRC. Could you hop on to #gentoo at libera.chat? There are web IRC clients available. |
|
| Back to top |
|
|
Boccaccio
Apprentice
Joined: 19 Jul 2005
Posts: 286
|
| Posted: Thu Jun 22, 2023 6:19 am Post subject: |
|
|
I fear that I ran into more or less the same problem. Emerging openssl-3.0.9 failed with the following message
| Quote: |
* Error messages for package dev-libs/openssl-3.0.9:
* The ebuild phase 'postinst' has exited unexpectedly. This type of
* behavior is known to be triggered by things such as failed variable
* assignments (bug #190128) or bad substitution errors (bug #200313).
* Normally, before exiting, bash should have displayed an error message
* above. If bash did not produce an error message above, it's possible
* that the ebuild has called `exit` when it should have called `die`
* instead. This behavior may also be triggered by a corrupt bash binary or
* a hardware problem such as memory or cpu malfunction. If the problem is
* not reproducible or it appears to occur randomly, then it is likely to
* be triggered by a hardware problem. If you suspect a hardware problem
* then you should try some basic hardware diagnostics such as memtest.
* Please do not report this as a bug unless it is consistently
* reproducible and you are sure that your bash binary and hardware are
* functioning properly.
* FAILED postinst: 1
* The ebuild phase 'other' has exited unexpectedly. This type of behavior
* is known to be triggered by things such as failed variable assignments
* (bug #190128) or bad substitution errors (bug #200313). Normally, before
* exiting, bash should have displayed an error message above. If bash did
* not produce an error message above, it's possible that the ebuild has
* called `exit` when it should have called `die` instead. This behavior
* may also be triggered by a corrupt bash binary or a hardware problem
* such as memory or cpu malfunction. If the problem is not reproducible or
* it appears to occur randomly, then it is likely to be triggered by a
* hardware problem. If you suspect a hardware problem then you should try
* some basic hardware diagnostics such as memtest. Please do not report
* this as a bug unless it is consistently reproducible and you are sure
* that your bash binary and hardware are functioning properly.
* Error messages for package sys-apps/coreutils-9.3-r2:
* The ebuild phase 'unpack' has exited unexpectedly. This type of behavior
* is known to be triggered by things such as failed variable assignments
* (bug #190128) or bad substitution errors (bug #200313). Normally, before
* exiting, bash should have displayed an error message above. If bash did
* not produce an error message above, it's possible that the ebuild has
* called `exit` when it should have called `die` instead. This behavior
* may also be triggered by a corrupt bash binary or a hardware problem
* such as memory or cpu malfunction. If the problem is not reproducible or
* it appears to occur randomly, then it is likely to be triggered by a
* hardware problem. If you suspect a hardware problem then you should try
* some basic hardware diagnostics such as memtest. Please do not report
* this as a bug unless it is consistently reproducible and you are sure
* that your bash binary and hardware are functioning properly.
* One or more packages are either masked or have missing dependencies:
*
* dev-libs/openssl:0/1.1= pulled in by:
* (sys-apps/coreutils-9.3-r2:0/0::gentoo, installed)
*
* The resume list contains packages that are either masked or have
* unsatisfied dependencies. Please restart/continue the operation
* manually, or use --skipfirst to skip the first package in the list and
* any other packages that may be masked or have missing dependencies.
*
* The following 2 packages have failed to build, install, or execute
* postinst:
*
* (dev-libs/openssl-3.0.9:0/3::gentoo, ebuild scheduled for merge) (postinst failed)
* (sys-apps/coreutils-9.3-r2:0/0::gentoo, ebuild scheduled for merge), Log file:
* '/var/tmp/portage/sys-apps/coreutils-9.3-r2/temp/build.log'
*
|
Trying to downgrade to 1.1.1u does not work but produces the following message:
| Quote: |
>>> Emerging (1 of 1) dev-libs/openssl-1.1.1u::gentoo
* openssl-1.1.1u.tar.gz BLAKE2B SHA512 size  ... [ ok ]
sort: error while loading shared libraries: libcrypto.so.1.1: cannot open shared object file: No such file or directory
sort: error while loading shared libraries: libcrypto.so.1.1: cannot open shared object file: No such file or directory
* ACCESS DENIED: open_wr: /dev/null
/usr/lib/portage/python3.11/phase-functions.sh: line 912: /dev/null: Permission denied
* ACCESS DENIED: open_wr: /dev/null
/usr/lib/portage/python3.11/phase-functions.sh: line 914: /dev/null: Permission denied
* ACCESS DENIED: open_wr: /dev/null
/usr/lib/portage/python3.11/phase-functions.sh: line 916: /dev/null: Permission denied
* ACCESS DENIED: open_wr: /dev/null
/usr/lib/portage/python3.11/phase-functions.sh: line 918: /dev/null: Permission denied
* ACCESS DENIED: open_wr: /dev/null
/usr/lib/portage/python3.11/phase-functions.sh: line 920: /dev/null: Permission denied
* ACCESS DENIED: open_wr: /dev/null
/usr/lib/portage/python3.11/phase-functions.sh: line 922: /dev/null: Permission denied
* ACCESS DENIED: open_wr: /dev/null
/usr/lib/portage/python3.11/phase-functions.sh: line 930: /dev/null: Permission denied
* ACCESS DENIED: open_wr: /dev/null
/usr/lib/portage/python3.11/phase-functions.sh: line 941: /dev/null: Permission denied
* ACCESS DENIED: open_wr: /dev/null
/usr/lib/portage/python3.11/phase-functions.sh: line 216: /dev/null: Permission denied
>>> Unpacking source...
* ACCESS DENIED: open_wr: /dev/null
/usr/lib/portage/python3.11/phase-functions.sh: line 216: /dev/null: Permission denied
* ACCESS DENIED: open_wr: /var/tmp/portage/dev-libs/openssl-1.1.1u/.unpacked
/usr/lib/portage/python3.11/phase-functions.sh: line 271: /var/tmp/portage/dev-libs/openssl-1.1.1u/.unpacked: Permission denied
* ACCESS DENIED: open_wr: /var/tmp/portage/dev-libs/openssl-1.1.1u/temp/logging/unpack
/usr/lib/portage/python3.11/isolated-functions.sh: line 265: /var/tmp/portage/dev-libs/openssl-1.1.1u/temp/logging/unpack: Permission denied
* ERROR: dev-libs/openssl-1.1.1u::gentoo failed (unpack phase):
* ACCESS DENIED: open_wr: /var/tmp/portage/dev-libs/openssl-1.1.1u/temp/logging/unpack
/usr/lib/portage/python3.11/isolated-functions.sh: line 265: /var/tmp/portage/dev-libs/openssl-1.1.1u/temp/logging/unpack: Permission denied
* Failed to create /var/tmp/portage/dev-libs/openssl-1.1.1u/.unpacked
* ACCESS DENIED: open_wr: /var/tmp/portage/dev-libs/openssl-1.1.1u/temp/logging/unpack
/usr/lib/portage/python3.11/isolated-functions.sh: line 265: /var/tmp/portage/dev-libs/openssl-1.1.1u/temp/logging/unpack: Permission denied
*
* ACCESS DENIED: open_wr: /var/tmp/portage/dev-libs/openssl-1.1.1u/temp/logging/unpack
/usr/lib/portage/python3.11/isolated-functions.sh: line 265: /var/tmp/portage/dev-libs/openssl-1.1.1u/temp/logging/unpack: Permission denied
* Call stack:
* ACCESS DENIED: execve: /usr/bin/basename
/usr/lib/portage/python3.11/isolated-functions.sh: line 76: /usr/bin/basename: Permission denied
* ACCESS DENIED: open_wr: /var/tmp/portage/dev-libs/openssl-1.1.1u/temp/logging/unpack
/usr/lib/portage/python3.11/isolated-functions.sh: line 265: /var/tmp/portage/dev-libs/openssl-1.1.1u/temp/logging/unpack: Permission denied
* , line 780: Called __ebuild_main 'unpack'
* ACCESS DENIED: execve: /usr/bin/basename
/usr/lib/portage/python3.11/isolated-functions.sh: line 76: /usr/bin/basename: Permission denied
* ACCESS DENIED: open_wr: /var/tmp/portage/dev-libs/openssl-1.1.1u/temp/logging/unpack
/usr/lib/portage/python3.11/isolated-functions.sh: line 265: /var/tmp/portage/dev-libs/openssl-1.1.1u/temp/logging/unpack: Permission denied
* , line 1072: Called __dyn_unpack
* ACCESS DENIED: open_wr: /var/tmp/portage/dev-libs/openssl-1.1.1u/temp/logging/unpack
/usr/lib/portage/python3.11/isolated-functions.sh: line 265: /var/tmp/portage/dev-libs/openssl-1.1.1u/temp/logging/unpack: Permission denied
* phase-functions.sh, line 272: Called die
* ACCESS DENIED: open_wr: /var/tmp/portage/dev-libs/openssl-1.1.1u/temp/logging/unpack
/usr/lib/portage/python3.11/isolated-functions.sh: line 265: /var/tmp/portage/dev-libs/openssl-1.1.1u/temp/logging/unpack: Permission denied
* The specific snippet of code:
* ACCESS DENIED: execve: /usr/bin/sed
* ACCESS DENIED: execve: /usr/bin/sed
/usr/lib/portage/python3.11/isolated-functions.sh: line 177: /usr/bin/sed: Permission denied
/usr/lib/portage/python3.11/isolated-functions.sh: line 190: /usr/bin/sed: Permission denied
* ACCESS DENIED: open_wr: /var/tmp/portage/dev-libs/openssl-1.1.1u/temp/logging/unpack
/usr/lib/portage/python3.11/isolated-functions.sh: line 265: /var/tmp/portage/dev-libs/openssl-1.1.1u/temp/logging/unpack: Permission denied
*
* ACCESS DENIED: open_wr: /var/tmp/portage/dev-libs/openssl-1.1.1u/temp/logging/unpack
/usr/lib/portage/python3.11/isolated-functions.sh: line 265: /var/tmp/portage/dev-libs/openssl-1.1.1u/temp/logging/unpack: Permission denied
* If you need support, post the output of `emerge --info '=dev-libs/openssl-1.1.1u::gentoo'`,
* ACCESS DENIED: open_wr: /var/tmp/portage/dev-libs/openssl-1.1.1u/temp/logging/unpack
/usr/lib/portage/python3.11/isolated-functions.sh: line 265: /var/tmp/portage/dev-libs/openssl-1.1.1u/temp/logging/unpack: Permission denied
* the complete build log and the output of `emerge -pqv '=dev-libs/openssl-1.1.1u::gentoo'`.
* ACCESS DENIED: open_wr: /var/tmp/portage/dev-libs/openssl-1.1.1u/.die_hooks
/usr/lib/portage/python3.11/isolated-functions.sh: line 207: /var/tmp/portage/dev-libs/openssl-1.1.1u/.die_hooks: Permission denied
* ACCESS DENIED: open_wr: /var/tmp/portage/dev-libs/openssl-1.1.1u/temp/logging/unpack
/usr/lib/portage/python3.11/isolated-functions.sh: line 265: /var/tmp/portage/dev-libs/openssl-1.1.1u/temp/logging/unpack: Permission denied
* The complete build log is located at '/var/tmp/portage/dev-libs/openssl-1.1.1u/temp/build.log'.
* ACCESS DENIED: open_wr: /var/tmp/portage/dev-libs/openssl-1.1.1u/temp/logging/unpack
/usr/lib/portage/python3.11/isolated-functions.sh: line 265: /var/tmp/portage/dev-libs/openssl-1.1.1u/temp/logging/unpack: Permission denied
* The ebuild environment file is located at '/var/tmp/portage/dev-libs/openssl-1.1.1u/temp/environment'.
* ACCESS DENIED: open_wr: /var/tmp/portage/dev-libs/openssl-1.1.1u/temp/logging/unpack
/usr/lib/portage/python3.11/isolated-functions.sh: line 265: /var/tmp/portage/dev-libs/openssl-1.1.1u/temp/logging/unpack: Permission denied
* Working directory: '/var/tmp/portage/dev-libs/openssl-1.1.1u/work'
* ACCESS DENIED: open_wr: /var/tmp/portage/dev-libs/openssl-1.1.1u/temp/logging/unpack
/usr/lib/portage/python3.11/isolated-functions.sh: line 265: /var/tmp/portage/dev-libs/openssl-1.1.1u/temp/logging/unpack: Permission denied
* S: '/var/tmp/portage/dev-libs/openssl-1.1.1u/work/openssl-1.1.1u'
* ACCESS DENIED: execve: /usr/lib/portage/python3.11/ebuild-ipc
/usr/lib/portage/python3.11/isolated-functions.sh: line 233: /usr/lib/portage/python3.11/ebuild-ipc: Permission denied
* ----------------------- SANDBOX ACCESS VIOLATION SUMMARY -----------------------
* LOG FILE: "/var/tmp/portage/dev-libs/openssl-1.1.1u/temp/sandbox.log"
*
VERSION 1.0
FORMAT: F - Function called
FORMAT: S - Access Status
FORMAT: P - Path as passed to function
FORMAT: A - Absolute Path (not canonical)
FORMAT: R - Canonical Path
FORMAT: C - Command Line
F: open_wr
S: deny
P: /dev/null
A: /dev/null
R: /dev/null
C: bash /usr/lib/portage/python3.11/ebuild.sh unpack
F: open_wr
S: deny
P: /dev/null
A: /dev/null
R: /dev/null
C: bash /usr/lib/portage/python3.11/ebuild.sh unpack
F: open_wr
S: deny
P: /dev/null
A: /dev/null
R: /dev/null
C: bash /usr/lib/portage/python3.11/ebuild.sh unpack
F: open_wr
S: deny
P: /dev/null
A: /dev/null
R: /dev/null
C: bash /usr/lib/portage/python3.11/ebuild.sh unpack
F: open_wr
S: deny
P: /dev/null
A: /dev/null
R: /dev/null
C: bash /usr/lib/portage/python3.11/ebuild.sh unpack
F: open_wr
S: deny
P: /dev/null
A: /dev/null
R: /dev/null
C: bash /usr/lib/portage/python3.11/ebuild.sh unpack
F: open_wr
S: deny
P: /dev/null
A: /dev/null
R: /dev/null
C: bash /usr/lib/portage/python3.11/ebuild.sh unpack
F: open_wr
S: deny
P: /dev/null
A: /dev/null
R: /dev/null
C: bash /usr/lib/portage/python3.11/ebuild.sh unpack
F: open_wr
S: deny
P: /dev/null
A: /dev/null
R: /dev/null
C: bash /usr/lib/portage/python3.11/ebuild.sh unpack
F: open_wr
S: deny
P: /dev/null
A: /dev/null
R: /dev/null
C: bash /usr/lib/portage/python3.11/ebuild.sh unpack
F: open_wr
S: deny
P: /var/tmp/portage/dev-libs/openssl-1.1.1u/.unpacked
A: /var/tmp/portage/dev-libs/openssl-1.1.1u/.unpacked
R: /var/tmp/portage/dev-libs/openssl-1.1.1u/.unpacked
C: bash /usr/lib/portage/python3.11/ebuild.sh unpack
F: open_wr
S: deny
P: /var/tmp/portage/dev-libs/openssl-1.1.1u/temp/logging/unpack
A: /var/tmp/portage/dev-libs/openssl-1.1.1u/temp/logging/unpack
R: /var/tmp/portage/dev-libs/openssl-1.1.1u/temp/logging/unpack
C: bash /usr/lib/portage/python3.11/ebuild.sh unpack
F: open_wr
S: deny
P: /var/tmp/portage/dev-libs/openssl-1.1.1u/temp/logging/unpack
A: /var/tmp/portage/dev-libs/openssl-1.1.1u/temp/logging/unpack
R: /var/tmp/portage/dev-libs/openssl-1.1.1u/temp/logging/unpack
C: bash /usr/lib/portage/python3.11/ebuild.sh unpack
F: open_wr
S: deny
P: /var/tmp/portage/dev-libs/openssl-1.1.1u/temp/logging/unpack
A: /var/tmp/portage/dev-libs/openssl-1.1.1u/temp/logging/unpack
R: /var/tmp/portage/dev-libs/openssl-1.1.1u/temp/logging/unpack
C: bash /usr/lib/portage/python3.11/ebuild.sh unpack
F: open_wr
S: deny
P: /var/tmp/portage/dev-libs/openssl-1.1.1u/temp/logging/unpack
A: /var/tmp/portage/dev-libs/openssl-1.1.1u/temp/logging/unpack
R: /var/tmp/portage/dev-libs/openssl-1.1.1u/temp/logging/unpack
C: bash /usr/lib/portage/python3.11/ebuild.sh unpack
F: execve
S: deny
P: /usr/bin/basename
A: /usr/bin/basename
R: /usr/bin/basename
C: bash /usr/lib/portage/python3.11/ebuild.sh unpack
F: open_wr
S: deny
P: /var/tmp/portage/dev-libs/openssl-1.1.1u/temp/logging/unpack
A: /var/tmp/portage/dev-libs/openssl-1.1.1u/temp/logging/unpack
R: /var/tmp/portage/dev-libs/openssl-1.1.1u/temp/logging/unpack
C: bash /usr/lib/portage/python3.11/ebuild.sh unpack
F: execve
S: deny
P: /usr/bin/basename
A: /usr/bin/basename
R: /usr/bin/basename
C: bash /usr/lib/portage/python3.11/ebuild.sh unpack
F: open_wr
S: deny
P: /var/tmp/portage/dev-libs/openssl-1.1.1u/temp/logging/unpack
A: /var/tmp/portage/dev-libs/openssl-1.1.1u/temp/logging/unpack
R: /var/tmp/portage/dev-libs/openssl-1.1.1u/temp/logging/unpack
C: bash /usr/lib/portage/python3.11/ebuild.sh unpack
F: open_wr
S: deny
P: /var/tmp/portage/dev-libs/openssl-1.1.1u/temp/logging/unpack
A: /var/tmp/portage/dev-libs/openssl-1.1.1u/temp/logging/unpack
R: /var/tmp/portage/dev-libs/openssl-1.1.1u/temp/logging/unpack
C: bash /usr/lib/portage/python3.11/ebuild.sh unpack
F: open_wr
S: deny
P: /var/tmp/portage/dev-libs/openssl-1.1.1u/temp/logging/unpack
A: /var/tmp/portage/dev-libs/openssl-1.1.1u/temp/logging/unpack
R: /var/tmp/portage/dev-libs/openssl-1.1.1u/temp/logging/unpack
C: bash /usr/lib/portage/python3.11/ebuild.sh unpack
F: execve
S: deny
P: /usr/bin/sed
A: /usr/bin/sed
R: /usr/bin/gsed
C: bash /usr/lib/portage/python3.11/ebuild.sh unpack
F:
execve
S: deny
P: /usr/bin/sed
A: /usr/bin/sed
R: /usr/bin/gsed
C: bash /usr/lib/portage/python3.11/ebuild.sh unpack
F: open_wr
S: deny
P: /var/tmp/portage/dev-libs/openssl-1.1.1u/temp/logging/unpack
A: /var/tmp/portage/dev-libs/openssl-1.1.1u/temp/logging/unpack
R: /var/tmp/portage/dev-libs/openssl-1.1.1u/temp/logging/unpack
C: bash /usr/lib/portage/python3.11/ebuild.sh unpack
F: open_wr
S: deny
P: /var/tmp/portage/dev-libs/openssl-1.1.1u/temp/logging/unpack
A: /var/tmp/portage/dev-libs/openssl-1.1.1u/temp/logging/unpack
R: /var/tmp/portage/dev-libs/openssl-1.1.1u/temp/logging/unpack
C: bash /usr/lib/portage/python3.11/ebuild.sh unpack
F: open_wr
S: deny
P: /var/tmp/portage/dev-libs/openssl-1.1.1u/temp/logging/unpack
A: /var/tmp/portage/dev-libs/openssl-1.1.1u/temp/logging/unpack
R: /var/tmp/portage/dev-libs/openssl-1.1.1u/temp/logging/unpack
C: bash /usr/lib/portage/python3.11/ebuild.sh unpack
F: open_wr
S: deny
P: /var/tmp/portage/dev-libs/openssl-1.1.1u/.die_hooks
A: /var/tmp/portage/dev-libs/openssl-1.1.1u/.die_hooks
R: /var/tmp/portage/dev-libs/openssl-1.1.1u/.die_hooks
C: bash /usr/lib/portage/python3.11/ebuild.sh unpack
F: open_wr
S: deny
P: /var/tmp/portage/dev-libs/openssl-1.1.1u/temp/logging/unpack
A: /var/tmp/portage/dev-libs/openssl-1.1.1u/temp/logging/unpack
R: /var/tmp/portage/dev-libs/openssl-1.1.1u/temp/logging/unpack
C: bash /usr/lib/portage/python3.11/ebuild.sh unpack
F: open_wr
S: deny
P: /var/tmp/portage/dev-libs/openssl-1.1.1u/temp/logging/unpack
A: /var/tmp/portage/dev-libs/openssl-1.1.1u/temp/logging/unpack
R: /var/tmp/portage/dev-libs/openssl-1.1.1u/temp/logging/unpack
C: bash /usr/lib/portage/python3.11/ebuild.sh unpack
F: open_wr
S: deny
P: /var/tmp/portage/dev-libs/openssl-1.1.1u/temp/logging/unpack
A: /var/tmp/portage/dev-libs/openssl-1.1.1u/temp/logging/unpack
R: /var/tmp/portage/dev-libs/openssl-1.1.1u/temp/logging/unpack
C: bash /usr/lib/portage/python3.11/ebuild.sh unpack
F: open_wr
S: deny
P: /var/tmp/portage/dev-libs/openssl-1.1.1u/temp/logging/unpack
A: /var/tmp/portage/dev-libs/openssl-1.1.1u/temp/logging/unpack
R: /var/tmp/portage/dev-libs/openssl-1.1.1u/temp/logging/unpack
C: bash /usr/lib/portage/python3.11/ebuild.sh unpack
F: execve
S: deny
P: /usr/lib/portage/python3.11/ebuild-ipc
A: /usr/lib/portage/python3.11/ebuild-ipc
R: /usr/lib/portage/python3.11/ebuild-ipc
C: bash /usr/lib/portage/python3.11/ebuild.sh unpack
* --------------------------------------------------------------------------------
* The ebuild phase 'unpack' has exited unexpectedly. This type of behavior
* is known to be triggered by things such as failed variable assignments
* (bug #190128) or bad substitution errors (bug #200313). Normally, before
* exiting, bash should have displayed an error message above. If bash did
* not produce an error message above, it's possible that the ebuild has
* called `exit` when it should have called `die` instead. This behavior
* may also be triggered by a corrupt bash binary or a hardware problem
* such as memory or cpu malfunction. If the problem is not reproducible or
* it appears to occur randomly, then it is likely to be triggered by a
* hardware problem. If you suspect a hardware problem then you should try
* some basic hardware diagnostics such as memtest. Please do not report
* this as a bug unless it is consistently reproducible and you are sure
* that your bash binary and hardware are functioning properly.
sort: error while loading shared libraries: libcrypto.so.1.1: cannot open shared object file: No such file or directory
sort: error while loading shared libraries: libcrypto.so.1.1: cannot open shared object file: No such file or directory
* ACCESS DENIED: open_wr: /var/tmp/portage/dev-libs/openssl-1.1.1u/.die_hooks
/usr/lib/portage/python3.11/misc-functions.sh: line 647: /var/tmp/portage/dev-libs/openssl-1.1.1u/.die_hooks: Permission denied
* ACCESS DENIED: execve: /usr/lib/portage/python3.11/ebuild-ipc
/usr/lib/portage/python3.11/misc-functions.sh: line 692: /usr/lib/portage/python3.11/ebuild-ipc: Permission denied
* ----------------------- SANDBOX ACCESS VIOLATION SUMMARY -----------------------
* LOG FILE: "/var/tmp/portage/dev-libs/openssl-1.1.1u/temp/sandbox-misc.log"
*
VERSION 1.0
FORMAT: F - Function called
FORMAT: S - Access Status
FORMAT: P - Path as passed to function
FORMAT: A - Absolute Path (not canonical)
FORMAT: R - Canonical Path
FORMAT: C - Command Line
F: open_wr
S: deny
P: /var/tmp/portage/dev-libs/openssl-1.1.1u/.die_hooks
A: /var/tmp/portage/dev-libs/openssl-1.1.1u/.die_hooks
R: /var/tmp/portage/dev-libs/openssl-1.1.1u/.die_hooks
C: bash /usr/lib/portage/python3.11/misc-functions.sh die_hooks
F: execve
S: deny
P: /usr/lib/portage/python3.11/ebuild-ipc
A: /usr/lib/portage/python3.11/ebuild-ipc
R: /usr/lib/portage/python3.11/ebuild-ipc
C: bash /usr/lib/portage/python3.11/misc-functions.sh die_hooks
* --------------------------------------------------------------------------------
* The ebuild phase 'die_hooks' has exited unexpectedly. This type of
* behavior is known to be triggered by things such as failed variable
* assignments (bug #190128) or bad substitution errors (bug #200313).
* Normally, before exiting, bash should have displayed an error message
* above. If bash did not produce an error message above, it's possible
* that the ebuild has called `exit` when it should have called `die`
* instead. This behavior may also be triggered by a corrupt bash binary or
* a hardware problem such as memory or cpu malfunction. If the problem is
* not reproducible or it appears to occur randomly, then it is likely to
* be triggered by a hardware problem. If you suspect a hardware problem
* then you should try some basic hardware diagnostics such as memtest.
* Please do not report this as a bug unless it is consistently
* reproducible and you are sure that your bash binary and hardware are
* functioning properly.
|
|
|
| Back to top |
|
|
sam_
Developer
Joined: 14 Aug 2020
Posts: 1982
|
| Posted: Thu Jun 22, 2023 6:28 am Post subject: |
|
|
OP hopped on IRC and helped confirm my theory quickly. This only happens with FEATURES="-preserve-libs" which is a rare configuration. It's allowed, of course, but it's unusual and not tested very often. It only gives a small speedup to merging and unmerging.
I've pushed a fix for this to prevent it happening to others at https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=161b4e469a0ef4ff533091bf8c820e0371f61f19.
If you've already hit it, you'll need to grab a stage3, extract it to a temporary location, and e.g. run: cp -n /pathtostage3/usr/lib64/lib{ssl,crypto}.so.1* /usr/lib64/. See also https://wiki.gentoo.org/wiki/Fix_my_Gentoo. We can help with this on IRC if needed too. |
|
| Back to top |
|
|
Boccaccio
Apprentice
Joined: 19 Jul 2005
Posts: 286
|
| Posted: Thu Jun 22, 2023 9:49 am Post subject: |
|
|
| Thanks, this helped to get me back to a working system again! |
|
| Back to top |
|
|
curmudgeon
Veteran
Joined: 08 Aug 2003
Posts: 1744
|
| Posted: Thu Jun 22, 2023 11:38 pm Post subject: |
|
|
| Boccaccio wrote: | | Thanks, this helped to get me back to a working system again! |
Ditto.
I actually scanned the forums looking for any posts about problems with the upgrade, but this showed up after I started.
Also, remember that one can use "busybox mount /dev/sdb1 /some/path/" to access files on portable media (instead of having to reboot to a rescue image). |
|
| Back to top |
|
|
netshade
Tux's lil' helper
Joined: 02 Jan 2004
Posts: 88
Location: Sweden
|
| Posted: Fri Oct 25, 2024 1:02 pm Post subject: |
|
|
Just an update if someone finds this thread and is in the same situation~ish.
I had a very similar issue, not sure what made it break but I couldn't update openssl to version 3.3.2 on my system. Lots of coredumps and such and the system generally behaving like I had a differently flavored OS from one of the other "great" suppliers.
I also had lots of similar issues as OP, "ACCESS DENIED" in particular. Looking at the solution posted here put me on the right track and I guess most users out there would've figured it out as well but in case someone doesn't, here's what I had to do differently from the solution posted by @sam_
"If you've already hit it, you'll need to grab a stage 3, extract it to a temporary location and e.g. run: cp -n /pathtostage3/usr/lib64/lib{ssl,crypto}.so.3 /usr/lib64/
Same thing, just different number. (Like I said, I know most people here would've figured it out on their own but someday someone not savvy will need the hint.
_________________
From where the shadows turn into nightmare, netshade greets you... |
|
| Back to top |
|
|
sam_
Developer
Joined: 14 Aug 2020
Posts: 1982
|
| Posted: Fri Oct 25, 2024 2:29 pm Post subject: |
|
|
| I don't understand why you'd need to do that, though. I think that merits debugging in a new thread in its own right. |
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
Portage & Programming
