You are not logged in.
After a reboot this morning deluged would not start. Journalctl showed:
deluged fails to start with [ERROR ][deluge.core.daemon_entry :1653] Unable to start deluged: 'unknown name in settings_pack: ignore_resume_timestamps'`deluged -d -L debug` showed:
15:21:40 [INFO ][deluge.core.daemon :1653] Deluge daemon 2.2.0
15:21:40 [DEBUG ][deluge.core.core :1653] Starting session (peer_id: -DE220s-, user_agent: Deluge/2.2.0 libtorrent/2.1.0.0)
15:21:40 [ERROR ][deluge.core.daemon_entry :1653] Unable to start deluged: 'unknown name in settings_pack: ignore_resume_timestamps'
15:21:40 [ERROR ][deluge.core.daemon_entry :1653] 'unknown name in settings_pack: ignore_resume_timestamps' Traceback (most recent call last):
File "/usr/lib/python3.14/site-packages/deluge/core/daemon_entry.py", line 109, in run_daemon daemon = Daemon( listen_interface=options.listen_interface, ...<3 lines>... read_only_config_keys=options.read_only_config_keys.split(','), ) File "/usr/lib/python3.14/site-packages/deluge/core/daemon.py", line 114, in __init__ self.core = Core( ~~~~^ listen_interface=listen_interface,
outgoing_interface=outgoing_interface,
read_only_config_keys=read_only_config_keys,
File "/usr/lib/python3.14/site-packages/deluge/core/core.py", line 122, in __init__ self.session = lt.session(settings_pack, flags=0) ~~~~~~~~~~
^^^^^^^^^^^^^^^^^^^^^^^^ KeyError: 'unknown name in settings_pack: ignore_resume_timestamps' 15:21:40 [INFO ][deluge.core.daemon_entry :1653] Exiting.Took about an hour but I finally found out what was going on, and how to fix it until deluge gets an update. It looks like some stuff got deprecated in python-pyopenssl that deluge relied. on (chatgpt thinks its a call to crypto.X509Req). Steps to get deluge working again:
sudo pacman -U python-pyopenssl-26.2.0-1-any.pkg.tar.zst libtorrent-rasterbar-1:2.0.13-1-x86_64.pkg.tar.zst libtorrent-0.16.7-1-x86_64.pkg.tar.zst python-cryptography-48.0.1-1-x86_64.pkg.tar.zst It looks like deluge closed their system to report bugs, and I don't think this is an Arch package bug (though it could be?). Wasn't sure where else to post this, but I hope it helps anyone else with this issue.
EDIT:
removed link to dustbined thread
Last edited by piratebill (2026-07-14 14:51:10)
Offline
Please don’t cross-post. It’s better to post in a wrong forum than to send to multiple.
I dropped a message about the issue in their IRC channel yesterday. Let’s hope it reaches the right people.
The cause is libtorrent dropping a deprecated feature (`ignore_resume_timestamps` key) in 2.1 release. Deluge still has that in code.
Offline
I'll see if I can delete the other one
EDIT:
I can't.
Last edited by piratebill (2026-07-14 02:32:07)
Offline
https://gitlab.archlinux.org/archlinux/ … rk_items/8
You can report it for the dustbin.
Offline
That is my reported ticket (created it after my first post). Old convo has been dust binned. Thanks!
Last edited by piratebill (2026-07-14 14:54:43)
Offline