The error message occurred during the first time if I emerge dev-java/oracle-jdk-bin-1.7.0.1-r2, on multiple computers at the same package. Since the error messages appear on every emerge. Downgrade to dev-java/oracle-jdk-bin-1.7.0.1-r1 does not help. Reproducible: Always Actual Results: Error messages appears.
Created attachment 296627 [details] emerge --info
Created attachment 296629 [details] emerge oracle-jdk-bin-1.7.0.1-r2
Created attachment 296631 [details] emerge actual example
What's the content of /etc/sandbox.d/20oracle-jdk-bin-1.7?
(In reply to comment #4) > What's the content of /etc/sandbox.d/20oracle-jdk-bin-1.7? on 2 computers: SANDBOX_PREDICT="/dev/random:/proc/self/coredump_filter" on 3 computers: SANDBOX_PREDICT="/dev/random /proc/self/coredump_filter"
After a new emerge-webrsync I have upgraded portage to version 2.1.10.41 and the error seems to be gone on all 5 computers!
(In reply to comment #5) > (In reply to comment #4) > > What's the content of /etc/sandbox.d/20oracle-jdk-bin-1.7? [...] > on 3 computers: > SANDBOX_PREDICT="/dev/random /proc/self/coredump_filter" This would explain the issue. (In reply to comment #6) > After a new emerge-webrsync I have upgraded portage to version 2.1.10.41 and > the error seems to be gone on all 5 computers! The error went away without reinstalling oracle-jdk-bin?
(In reply to comment #7) > (In reply to comment #5) > > (In reply to comment #4) > > > What's the content of /etc/sandbox.d/20oracle-jdk-bin-1.7? > [...] > > on 3 computers: > > SANDBOX_PREDICT="/dev/random /proc/self/coredump_filter" > > This would explain the issue. > > (In reply to comment #6) > > After a new emerge-webrsync I have upgraded portage to version 2.1.10.41 and > > the error seems to be gone on all 5 computers! > > The error went away without reinstalling oracle-jdk-bin? Yes, without reinstalling oracle-jdk-bin, and I have tested before with ":" but without success.
(In reply to comment #8) > Yes, without reinstalling oracle-jdk-bin, and I have tested before with ":" > but without success. Guess it won't easily be possible anymore to figure out what happened and chances are high it's not related to oracle-jdk-bin but a sandbox glich. Closing. If someone runs into the same issue please reopen or file a new bug referencing this one. Hope this is fine with you.