Summary: | =dev-python/pip-19.2.2: dbus starts during install if dev-python/keyring is installed - sandbox error ACCESS DENIED: open_wr: /proc/self/oom_score_adj | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Nick <nickAristocrates> |
Component: | Current packages | Assignee: | Python Gentoo Team <python> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | da_risk, gentoo, gmt, jj, maksbotan |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
See Also: | https://bugs.gentoo.org/show_bug.cgi?id=700830 | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
pip-19.2.2.build.log
xfce4-screenshooter's build log |
Description
Nick
2019-08-15 05:34:41 UTC
Something is starting an instance of dbus-daemon when the ebuild runs setup.py install. Nothing in dev-python/pip would launch dbus-daemon. Probably some other python package has some code that does this. Could you grep around in /usr/lib/python3.7/site-packages for anything dbus-related? Interestingly, I can reproduce successfully reinstalling =dev-python/pip-19.1 and still =dev-python/pip-19.2.2 fails with the sandbox error. The ebuild and use flags didn't change so regardless of the true underlying cause _something_ must have changed in the source itself to trigger this problem, but I haven't found anything obvious yet from a diff between the two unpacked source directories. emerge -pv1 =dev-python/pip-19.1 These are the packages that would be merged, in order: Calculating dependencies... done! [ebuild R ] dev-python/pip-19.1::gentoo USE="-test -vanilla" PYTHON_TARGETS="python2_7 python3_5 python3_6 python3_7 -pypy -pypy3" 0 KiB Total: 1 package (1 reinstall), Size of downloads: 0 KiB emerge -pv1 dev-python/pip These are the packages that would be merged, in order: Calculating dependencies... done! [ebuild U ~] dev-python/pip-19.2.2::gentoo [19.1::gentoo] USE="-test -vanilla" PYTHON_TARGETS="python2_7 python3_5 python3_6 python3_7 -pypy -pypy3" 0 KiB Total: 1 package (1 upgrade), Size of downloads: 0 KiB Sorry, but I still cannot reproduce this. If you are able to provide more useful information, feel free to re-open. For me it's triggered by dev-python/keyring. I don't know all the details but when the ebuild runs `pip completion --bash` (or the equivalent command) it seems to load/import a lot of python packages. I was able to find this by running this command `python3 -m trace --trace /usr/bin/pip3 completion --bash > /tmp/trace.log` When keyring is installed it imports dbus and probably launch the dbus-daemon. Yes, I have noticed the same, when I uninstall dev-python/keyring, pip emerges perfectly fine. I had dev-python/keyring pulled in due to no longer needed dev-python/oauth2client, I could reproduce successful install of =dev-python/pip-19.2.2 by uninstalling dev-python/keyring and dependencies and then installing =dev-python/pip-19.2.2. Installing dev-python/keyring should reproduce the build failure. Well spotted Frédéric! Dear python team, This seems like it's a legit bug* Until more is known, perhaps pip-19.2.2 should DEPEND-block dev-python/keyring or something like that? If you would like to repro/investigate: (In comment #6 Nick says) > Installing dev-python/keyring should reproduce the build failure. (In comment #4 Frédéric Barthelery says approximately) > the [=dev-python/pip-19.2.2] ebuild runs > > `pip completion --bash` > > [which seems to import dbus if keyring is installed, > which causes a sandbox violation] Thank you kindly for all the amazing work you do! -- * or, at least, a common mis-configuration that gentoo ought to find a way to handle more gracefully. Created attachment 596606 [details]
xfce4-screenshooter's build log
(In reply to Amit Ugol from comment #8) > Created attachment 596606 [details] > xfce4-screenshooter's build log No idea why is removed my text... Not sure if directly related but same symptoms with xfce4-screenshooter, and I don't have keyring installed at all on my system. (In reply to Amit Ugol from comment #9) > (In reply to Amit Ugol from comment #8) > > Created attachment 596606 [details] > > xfce4-screenshooter's build log > > No idea why is removed my text... > Not sure if directly related but same symptoms with xfce4-screenshooter, and > I don't have keyring installed at all on my system. Sorry for the broken messages... long day. To work around it I opened a new terminal (alt+shift_F2 in my case) logged in as root and compiled. So it might not be relevant exactly to this issue after all... The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=0150f444229b0d6ebdd6e44044e1fe436e6c728a commit 0150f444229b0d6ebdd6e44044e1fe436e6c728a Author: Mike Gilbert <floppym@gentoo.org> AuthorDate: 2020-01-17 16:27:06 +0000 Commit: Mike Gilbert <floppym@gentoo.org> CommitDate: 2020-01-17 16:27:23 +0000 dev-python/pip: attempt to prevent dbus auto-launch Closes: https://bugs.gentoo.org/692178 Package-Manager: Portage-2.3.84_p2, Repoman-2.3.20_p24 Signed-off-by: Mike Gilbert <floppym@gentoo.org> dev-python/pip/pip-19.1.ebuild | 4 ++++ dev-python/pip/pip-19.3.1-r1.ebuild | 4 ++++ dev-python/pip/pip-19.3.1-r2.ebuild | 4 ++++ 3 files changed, 12 insertions(+) |