Description of problem: Current release lack of systemd user units that allow to run daemons as common user Current release don't allow to access files downloaded from web interface if started from system units Also backport enhancements done by wally to the current spec
RPM: deluge-2.2.0-1.6.mga9 SRPM: deluge-2.2.0-1.6.mga9 And Errata about second point, what I mean is that in current release just deluge user and nobody else can read/write the files downloaded from web interface started with system unit
Assignee: j.alberto.vc => qa-bugs
RH x86_64 installing deluge-2.2.0-1.6.mga9.noarch.rpm from //home/katnatek/qa-testing/x86_64 Preparing... ################################################################################################## 1/1: deluge ################################################################################################## 1/1: removing deluge-2.2.0-1.5.mga9.noarch ################################################################################################## ---------------------------------------------------------------------- More information on package deluge-2.2.0-1.6.mga9.noarch We now provide system and user systemd units for deluge services Choose wich one you want to use. For the system unit for deluge-web you must make sure to have enough space in /var/lib folder ,and you can't select other destination neither select to move files to folders outside /var/lib/deluge in the web interface, but you can move files to other folder from your user session, remember to remove the torrent in web interface before to do that. systemctl start deluge-daemon.service deluge-web.service systemctl status deluge-daemon.service deluge-web.service ● deluge-daemon.service - Deluge Bittorrent Client Daemon Loaded: loaded (/usr/lib/systemd/system/deluge-daemon.service; disabled; preset: disabled) Active: active (running) since Thu 2025-06-12 17:03:27 CST; 18s ago Docs: man:deluged Main PID: 35514 (deluged) Tasks: 4 (limit: 6876) Memory: 42.4M CPU: 1.761s CGroup: /system.slice/deluge-daemon.service └─35514 /usr/bin/python3 /usr/bin/deluged -d jun 12 17:03:27 jgrey.phoenix systemd[1]: Started deluge-daemon.service. ● deluge-web.service - Deluge Bittorrent Client Web Interface Loaded: loaded (/usr/lib/systemd/system/deluge-web.service; disabled; preset: disabled) Active: active (running) since Thu 2025-06-12 17:03:25 CST; 19s ago Docs: man:deluge-web Main PID: 35493 (deluge-web) Tasks: 1 (limit: 6876) Memory: 60.0M CPU: 1.447s CGroup: /system.slice/deluge-web.service └─35493 deluge-web jun 12 17:03:25 jgrey.phoenix systemd[1]: Started deluge-web.service. Open http://localhost:8112/ present the web interface systemctl stop deluge-daemon.service deluge-web.service As common user systemctl --user start deluge-daemon.service deluge-web.service [katnatek@jgrey ~]$ systemctl --user start deluge-daemon.service deluge-web.service [katnatek@jgrey ~]$ systemctl --user status deluge-daemon.service deluge-web.service ● deluge-daemon.service - Deluge Bittorrent Client Daemon Loaded: loaded (/usr/lib/systemd/user/deluge-daemon.service; disabled; preset: disabled) Active: active (running) since Thu 2025-06-12 17:06:55 CST; 23s ago Docs: man:deluged Main PID: 36086 (deluged) Tasks: 6 (limit: 6876) Memory: 41.4M CPU: 1.276s CGroup: /user.slice/user-1000.slice/user@1000.service/background.slice/deluge-daemon.service └─36086 /usr/bin/python3 /usr/bin/deluged -d jun 12 17:06:55 jgrey.phoenix systemd[3937]: Started deluge-daemon.service. ● deluge-web.service - Deluge Bittorrent Client Web Interface Loaded: loaded (/usr/lib/systemd/user/deluge-web.service; disabled; preset: disabled) Active: active (running) since Thu 2025-06-12 17:06:55 CST; 23s ago Docs: man:deluge-web Main PID: 36087 (deluge-web) Tasks: 1 (limit: 6876) Memory: 47.1M CPU: 1.192s CGroup: /user.slice/user-1000.slice/user@1000.service/background.slice/deluge-web.service └─36087 deluge-web jun 12 17:06:55 jgrey.phoenix systemd[3937]: Started deluge-web.service. Open http://localhost:8112/ present the web interface, this time will be using the user folders and configurations Side effect with downloaded files/folder from web interface started as root is even if you can move to common user folder the rights not likes to others torrent clients, need to chmod o-rw -R FolderDownladed of FileDownloaded
Keywords: (none) => advisory
MGA9-64 Plasma Wayland on Compaq H000SB No installation issues. Opened port 8112 in firewall. Test of web interface, same results as katnatek above, so i will not repeat all that all over again. Pushing a bit further (trying to understand the command) $ deluge -v deluge 2.2.0 libtorrent: 2.0.9.0 Python: 3.10.11 OS: Linux Mageia 9 mga9 $ deluge-console "connect localhost <user> <password>" Failed to connect to localhost:58846 with reason: Username does not exist Could not connect to daemon: 127.0.0.1:58846 Username does not exist I tried with deluge as user and with my system user, but the same result, and that port is ???? Using the CLI seems to ask some more configuration, but that is beyond me. If you judge this tested enough, I will agree on the OK.
CC: (none) => herman.viaene
(In reply to Herman Viaene from comment #3) > MGA9-64 Plasma Wayland on Compaq H000SB > No installation issues. > Opened port 8112 in firewall. > Test of web interface, same results as katnatek above, so i will not repeat > all that all over again. > Pushing a bit further (trying to understand the command) > $ deluge -v > deluge 2.2.0 > libtorrent: 2.0.9.0 > Python: 3.10.11 > OS: Linux Mageia 9 mga9 > > $ deluge-console "connect localhost <user> <password>" > Failed to connect to localhost:58846 with reason: Username does not exist > Could not connect to daemon: 127.0.0.1:58846 > Username does not exist > > I tried with deluge as user and with my system user, but the same result, > and that port is ???? > Using the CLI seems to ask some more configuration, but that is beyond me. > If you judge this tested enough, I will agree on the OK. The user is localclient the password can be found in .config/deluge/auth file in the home of the user running the service /var/lib/deluge running from root , just before the :10 string (don't now if is universal) But have other issues will search if is something I can fix
(In reply to katnatek from comment #4) > (In reply to Herman Viaene from comment #3) > > MGA9-64 Plasma Wayland on Compaq H000SB > > No installation issues. > > Opened port 8112 in firewall. > > Test of web interface, same results as katnatek above, so i will not repeat > > all that all over again. > > Pushing a bit further (trying to understand the command) > > $ deluge -v > > deluge 2.2.0 > > libtorrent: 2.0.9.0 > > Python: 3.10.11 > > OS: Linux Mageia 9 mga9 > > > > $ deluge-console "connect localhost <user> <password>" > > Failed to connect to localhost:58846 with reason: Username does not exist > > Could not connect to daemon: 127.0.0.1:58846 > > Username does not exist > > > > I tried with deluge as user and with my system user, but the same result, > > and that port is ???? > > Using the CLI seems to ask some more configuration, but that is beyond me. > > If you judge this tested enough, I will agree on the OK. > > The user is localclient the password can be found in .config/deluge/auth > file in the home of the user running the service /var/lib/deluge running > from root , just before the :10 string (don't now if is universal) > > But have other issues will search if is something I can fix The issu should be fixed but I got it :S https://forum.deluge-torrent.org/viewtopic.php?p=238584&sid=5a9822b51bd17ec21084206bc1a68c2c#p238584 Use deluge-console -d <ip> -p <port> -U <user> -P <password> I did not use port, and get a curses interface to connect We can give this OK
Whiteboard: (none) => MGA9-64-OK
I not put the password here but deluge-console -d localhost -U localclient -P <thepasswod> status Total upload: 0.0 KiB/s Total download: 0.0 KiB/s DHT Nodes: 208 Total torrents: 0 Allocating: 0 Checking: 0 Downloading: 0 Seeding: 0 Paused: 0 Error: 0 Queued: 0 Moving: 0 Its OK as I not have torrents in deluge user now
Validating.
Keywords: (none) => validated_updateCC: (none) => andrewsfarm, sysadmin-bugs
An update for this issue has been pushed to the Mageia Updates repository. https://advisories.mageia.org/MGAA-2025-0061.html
Resolution: (none) => FIXEDStatus: NEW => RESOLVED