Created attachment 565964 [details] emerge --info output Trying to emerge x11-misc/zim-0.70_rc1 produces the following errors: >>> Install zim-0.70_rc1 into /var/tmp/portage/x11-misc/zim-0.70_rc1/image/ category x11-misc python3.6 setup.py install --root=/var/tmp/portage/x11-misc/zim-0.70_rc1/image * ACCESS DENIED: open_wr: /proc/self/oom_score_adj * ACCESS DENIED: open_wr: /proc/self/oom_score_adj * ACCESS DENIED: open_wr: /proc/self/oom_score_adj * ACCESS DENIED: open_wr: /proc/self/oom_score_adj [...] [31;01m*[0m --------------------------- ACCESS VIOLATION SUMMARY --------------------------- [31;01m*[0m LOG FILE: "/var/log/sandbox/sandbox-4.log" [31;01m*[0m 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: /proc/self/oom_score_adj A: /proc/self/oom_score_adj R: /proc/57/oom_score_adj C: /usr/bin/dbus-daemon --syslog-only --fork --print-pid 5 --print-address 7 --session F: open_wr S: deny P: /proc/self/oom_score_adj A: /proc/self/oom_score_adj R: /proc/57/oom_score_adj C: /usr/bin/dbus-daemon --syslog-only --fork --print-pid 5 --print-address 7 --session F: open_wr S: deny P: /proc/self/oom_score_adj A: /proc/self/oom_score_adj R: /proc/64/oom_score_adj C: /usr/bin/dbus-daemon --config-file=/usr/share/defaults/at-spi2/accessibility.conf --nofork --print-address 3 F: open_wr S: deny P: /proc/self/oom_score_adj A: /proc/self/oom_score_adj R: /proc/64/oom_score_adj C: /usr/bin/dbus-daemon --config-file=/usr/share/defaults/at-spi2/accessibility.conf --nofork --print-address 3 [31;01m*[0m --------------------------------------------------------------------------------
Please attach the entire build log to this bug report.
Created attachment 565972 [details] build.log as requested
Not sure what is happening there. Does not appear to be related to bug #567192 but it might be in some way.
Today I was able to successfully emerge x11-misc/zim-0.70_rc3. I attached the list of packages from last unsuccessful emerge and the successful emerge for analysis if anyone is interested. Both (attached) emerges were done with gcc-8.3.0. The emerges before these two were done with gcc-8.2.0. If you have any questions or need any more information don't hesitate to ask.
Created attachment 569084 [details] last failed emerge log
Created attachment 569086 [details] successful emerge log
Hello Recently this started to happen on one of my machines, for various unrelated packages (kbd, pip, vim). I don't think is related to any of the actual packages directly. Is it possible opening some kind of session to build in triggers starting dbus for portage? I'm adding my own emerge --info, in case it is somehow useful.
Created attachment 587038 [details] Another emerge --info
It seems that something is being inherited from the environment somehow. Running `emerge' through `env -i` works around the problem. I did a diff, but I can't figure out what's causing the problem. diff -u <(sudo env | sort) <(env -i sudo env | sort) --- /proc/self/fd/11 2019-12-10 22:24:41.682648203 +0300 +++ /proc/self/fd/12 2019-12-10 22:24:41.685648157 +0300 @@ -1,7 +1,4 @@ -COLORTERM=truecolor -DISPLAY=:0 HOME=/root -LANG=en_US.utf8 LOGNAME=root MAIL=/var/mail/root PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin:/opt/bin:/usr/lib/llvm/8/bin @@ -10,6 +7,5 @@ SUDO_GID=1000 SUDO_UID=1000 SUDO_USER=wgh -TERM=xterm-kitty +TERM=unknown USER=root -XAUTHORITY=/home/wgh/.Xauthority
Clearing DISPLAY seems enough.
If unsetting DISPLAY fixes it, then it was clearly bug 700830 So now with current versions of portage it should be properly cleaned, don't hesitate to reopen if it is not fixed (we may then need a fix like in bug 692178)
