| View previous topic :: View next topic |
| Author |
Message |
urcindalo
l33t
Joined: 08 Feb 2005
Posts: 623
Location: Almeria, Spain
|
 Posted: Sun Jul 01, 2018 11:30 am Post subject: crossover-bin fails to emerge: ACCESS DENIED: open_wr |
 |
|
Hi and thanks for reading this!
I've had crossover-bin-15.2.0 installed for a long time. Then, like a month ago or so, it got updated in the tree and new versions were also added. Since then, I find it impossible to update it, or even re-emerge the old 15.2.0 version installed, on any of my boxes (a mixture of intel or amd cpu's with NVIDIA or ATI cards). Here is the error I get (the same no matter the version I try):
| Code: | >>> Emerging (10 of 10) app-emulation/crossover-bin-17.5.0-r1::gentoo
* install-crossover-17.5.0.bin BLAKE2B SHA512 size ;-) ... [ ok ]
>>> Unpacking source...
>>> Unpacking install-crossover-17.5.0.bin to /var/tmp/portage/app-emulation/crossover-bin-17.5.0-r1/work
warning [/var/tmp/portage/app-emulation/crossover-bin-17.5.0-r1/distdir/install-crossover-17.5.0.bin]: 867913 extra bytes at beginning or within zipfile
(attempting to process anyway)
>>> Source unpacked in /var/tmp/portage/app-emulation/crossover-bin-17.5.0-r1/work
>>> Preparing source in /var/tmp/portage/app-emulation/crossover-bin-17.5.0-r1/work ...
* Fixing shebang in ./bin/cxinstaller.
* Fixing shebang in ./bin/cxfix.
* Fixing shebang in ./bin/cxregister.
* Fixing shebang in ./bin/cxprefs.
* Fixing shebang in ./bin/cxwait.
* Fixing shebang in ./bin/crossover.
* Fixing shebang in ./bin/cxtie.
* Fixing shebang in ./bin/cxreset.
* Fixing shebang in ./bin/cxmessage.
* Fixing shebang in ./bin/cxrun.
* Fixing shebang in ./bin/cxupdatecheck.
>>> Source prepared.
>>> Configuring source in /var/tmp/portage/app-emulation/crossover-bin-17.5.0-r1/work ...
>>> Source configured.
>>> Compiling source in /var/tmp/portage/app-emulation/crossover-bin-17.5.0-r1/work ...
>>> Source compiled.
* Skipping make test/check due to ebuild restriction.
>>> Test phase [disabled because of RESTRICT=test]: app-emulation/crossover-bin-17.5.0-r1
>>> Install crossover-bin-17.5.0-r1 into /var/tmp/portage/app-emulation/crossover-bin-17.5.0-r1/image/ category app-emulation
QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/var/tmp/portage/app-emulation/crossover-bin-17.5.0-r1/temp/runtime-root'
QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/var/tmp/portage/app-emulation/crossover-bin-17.5.0-r1/temp/runtime-root'
* ACCESS DENIED: open_wr: /root/.cache/mesa_shader_cache/index
* ACCESS DENIED: fopen_wr: /root/.dbus/session-bus/772ff2e7b22d37eb759c47170000001c-0
>>> Completed installing crossover-bin-17.5.0-r1 into /var/tmp/portage/app-emulation/crossover-bin-17.5.0-r1/image/
* Final size of build directory: 496008 KiB (484.3 MiB)
* Final size of installed tree: 496420 KiB (484.7 MiB)
* --------------------------- ACCESS VIOLATION SUMMARY ---------------------------
* LOG FILE: "/var/log/sandbox/sandbox-4108.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: /root/.cache/mesa_shader_cache/index
A: /root/.cache/mesa_shader_cache/index
R: /root/.cache/mesa_shader_cache/index
C: konqueror --version
F: fopen_wr
S: deny
P: /root/.dbus/session-bus/772ff2e7b22d37eb759c47170000001c-0
A: /root/.dbus/session-bus/772ff2e7b22d37eb759c47170000001c-0
R: /root/.dbus/session-bus/772ff2e7b22d37eb759c47170000001c-0
C: dbus-launch --autolaunch 772ff2e7b22d37eb759c47170000001c --binary-syntax --close-stderr
* --------------------------------------------------------------------------------
>>> Failed to emerge app-emulation/crossover-bin-17.5.0-r1, Log file:
>>> '/var/tmp/portage/app-emulation/crossover-bin-17.5.0-r1/temp/build.log' |
Is it just me? Are you able to emerge crossover-bin?
It is pretty annoying having to add "--exclude crossover-bin" every time I perform a world update. |
|
| Back to top |
|
 |
gienah
Developer
Joined: 24 Nov 2010
Posts: 212
Location: AU
|
| Posted: Sun Jul 01, 2018 1:37 pm Post subject: |
|
|
I don't use crossover-bin. Looking at the errors you might be able to work around it by hacking the ebuild and adding:
to |
|
| Back to top |
|
|
khayyam
Watchman
Joined: 07 Jun 2012
Posts: 6227
Location: Room 101
|
| Posted: Sun Jul 01, 2018 3:08 pm Post subject: |
|
|
| gienah wrote: | | Looking at the errors you might be able to work around it by hacking the ebuild [...] |
gienah ... the access violations are the result 'open_wr' and 'fopen_wr' using XDG/dbus environment variables ...
@urcindalo ... you should be able to resolve the issue by clearing the environment using 'env --ignore-environment'
| Code: | | # env -i emerge =app-emulation/crossover-bin-17.5.0-r1 |
HTH & best ... khay |
|
| Back to top |
|
|
urcindalo
l33t
Joined: 08 Feb 2005
Posts: 623
Location: Almeria, Spain
|
| Posted: Sun Jul 01, 2018 6:16 pm Post subject: |
|
|
| khayyam wrote: | @urcindalo ... you should be able to resolve the issue by clearing the environment using 'env --ignore-environment'
| Code: | | # env -i emerge =app-emulation/crossover-bin-17.5.0-r1 |
HTH & best ... khay |
Yeah, thanks! It worked. |
|
| Back to top |
|
|
urcindalo
l33t
Joined: 08 Feb 2005
Posts: 623
Location: Almeria, Spain
|
| Posted: Mon Jul 02, 2018 8:09 am Post subject: |
|
|
| urcindalo wrote: | | khayyam wrote: | @urcindalo ... you should be able to resolve the issue by clearing the environment using 'env --ignore-environment'
| Code: | | # env -i emerge =app-emulation/crossover-bin-17.5.0-r1 |
HTH & best ... khay |
Yeah, thanks! It worked. |
BTW, I saw these messages: | Code: | PORTAGE_BZIP2_COMMAND setting is invalid: 'bzip2'
PORTAGE_BZIP2_COMMAND setting from make.globals is invalid: 'bzip2' |
Could they be the cause?
I didn't set them up manually. Which package is responsible for them[/quote]? |
|
| Back to top |
|
|
khayyam
Watchman
Joined: 07 Jun 2012
Posts: 6227
Location: Room 101
|
| Posted: Mon Jul 02, 2018 1:25 pm Post subject: |
|
|
| urcindalo wrote: | BTW, I saw these messages:
| Code: | PORTAGE_BZIP2_COMMAND setting is invalid: 'bzip2'
PORTAGE_BZIP2_COMMAND setting from make.globals is invalid: 'bzip2' |
Could they be the cause? |
urcindalo ... no, those are unrelated. The actual problem is that XDG and dbus set environment variables telling programs where they should write 'cache' and other sorts of data. This location is outside the containment of the sandbox used to build/install packages and so an "access violation" is triggered when something tries to read/write there. By clearing those variables from the 'root' environment the problem is averted ... keep that in mind, because it will no doubt happen again with some other package if you don't do something about it (ie, by unsetting them in ~/.profile ... or having 'if [[ $UID > "0" ]] ; then' as a test, if set via some system wide config ... or who-knows-what dbus/xdg do (I refuse to endorse crappy standards/sotware).
| urcindalo wrote: | | I didn't set them up manually. Which package is responsible for them? |
The 'make.globals' is as part of sys-app/portage:
| Code: | % equery -NC files sys-apps/portage | grep 'make.globals'
/usr/share/portage/config/make.globals |
best ... khay |
|
| Back to top |
|
|
urcindalo
l33t
Joined: 08 Feb 2005
Posts: 623
Location: Almeria, Spain
|
| Posted: Tue Jul 03, 2018 7:59 am Post subject: |
|
|
| Thanks for your detailed explanation. |
|
| Back to top |
|
|
|
Portage & Programming
