1. Seems like acct-group/deluge creates the deluge user without a home directory as part of: emerge --ask net-p2p/deluge from the documentation: https://wiki.gentoo.org/wiki/Deluge 2. Next step in the documentation fails: useradd -m -g nogroup -s /bin/nologin deluge saying that the user already exists. 3. Step 4 in the documentation fails: su --shell /bin/bash deluge deluge-console saying that /.config directory does not exist for deluge: as there is no home dir defined for deluge and it is trying to create the config in root, where deluge user has no rights to do that. Reproducible: Always Steps to Reproduce: 1. emerge --ask net-p2p/deluge 2. useradd -m -g nogroup -s /bin/nologin deluge 3. su --shell /bin/bash deluge 4. deluge-console Actual Results: - After emerging deluge user deluge is created with no home directory - config directory for deluge is not documented if it even exists - remote connection to the daemon cannot be enabled according to the documentation https://wiki.gentoo.org/wiki/Deluge Expected Results: Create user with the home dir pointing where deluged will store it's config so that su - deluge will be able to start deluge-console and enable remote connection to the daemon.
In the meantime I found out that: 1. I have to: mkdir /var/lib/deluge chown deluge:deluge /var/lib/deluge Then I can run: deluge-console -c /var/lib/deluge It will start, but later still fail with a python error, but that will already be a different bug report... Let me know if I can actually help to fix the documentation instead of just submitting bugs!
The problem, I think, is that https://wiki.gentoo.org/wiki/Deluge is wrong. That page hasn't been updated since net-p2p/deluge was changed to create the user/group on its own way back in October 2019: https://github.com/gentoo/gentoo/commit/d137de4a30758608c28f2a6880cf91d15816ac2b You should be able to just emerge net-p2p/deluge and be done - no need to manually create/configure a user or group. Hopefully this resolves your issue - if not, please let me know.
