[SOLVED] Deluged not compatable with current python packages

piratebill · 2026-07-13 23:26:51

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-08-11 15:44:59)

mpan · 2026-07-14 01:35:37

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.

piratebill · 2026-07-14 02:29:17

I'll see if I can delete the other one

EDIT:
I can't.

Last edited by piratebill (2026-07-14 02:32:07)

seth · 2026-07-14 05:41:48

https://gitlab.archlinux.org/archlinux/ … rk_items/8
You can report it for the dustbin.

piratebill · 2026-07-14 14:45:33

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)

Jhackler · 2026-07-31 14:34:02

I am surprised how many weeks now I have not been able to use deluge lol I am confident it will be fixed though

mpan · 2026-07-31 18:04:44

It feels Deluge devs are lacking help nowadays. It’s hard to respond quickly, if you’re some random person in Nebraska thanklessly maintaining it since 2003. I myself could only offer reporting the issue through #deluge@Libera in a hope the news of breakage reach the right ears. I see another user reported it on their forum too.

Of course anybody may just patch the offending section. It’s literally a no longer supported key getting passed to libtorrent. But I don’t know enough of Deluge’s internals to ensure the change isn’t going to break anything further down the stream. So I’m not going to make a pull request.

If you wish to donate the effort and make the change, together with understanding its consequences (for 2.0 libtorrent version too!), it would be very much appreciated.

loqs · 2026-07-31 23:11:23

@jhackler @mpan have either of you tried the upstream PR for cryptography or my patch for libtrorrent-raster 2.1? If so any issues with them?

mpan · 2026-08-06 17:56:50

Loqs, I didn’t and I can’t. But what patches are you referencing? You didn’t link any, so I don’t think people can test them.

seth · 2026-08-06 19:41:16

https://gitlab.archlinux.org/archlinux/ … rk_items/8
Might also wanna test whether it's fixed now

piratebill · 2026-08-11 15:43:54

Everything appears to be fixed now.

mpan · 2026-08-11 16:02:47

“Circumvented” is a better word. The packages (deluge, deluge-gtk) now rely on vendoring in an outdated version of libtorrent. It buys us some time, allows deluged and the GTK frontend to start, but the core issue remains unfixed. That has to be addressed upstream.

And the upstream could use some help, not face more demands to fix things.

loqs · 2026-08-14 00:00:30

mpan wrote:

And the upstream could use some help, not face more demands to fix things.

Not all issue reports are demands. Preventing issues on the projects github and new registrations on its trac may well leave the project unaware there even is an issue to fix. Without mentioning being unable to report security issues.

mpan · 2026-08-14 00:49:43

loqs wrote:

Not all issue reports are demands.

Not necessarily in this thread, but across the community there are some entitled and angry voices. And in general, not only with Deluge, this tone is also not uncommon.

loqs wrote:

Preventing issues on the projects github (…)

Deluge’s GitHub accepts pull requests just fine.

loqs wrote:

(…) and new registrations on its trac may well leave the project unaware there even is an issue to fix. Without mentioning being unable to report security issues.

That an issue can’t be opened using an automated ticket system is not preventing reporting. The world, including software development, lived with no tickets for most of its existence and with no trouble. The issue has been reported within hours of Arch deploying the libtorrent-rasterbar update, and only with a minor delay on Deluge’s forum.

In either case reporting is not a problem, Deluge is not short of people listing things “somebody” should fix. Writing and properly testing patches is where the help may be needed.

loqs · 2026-08-14 01:27:42

mpan wrote:

In either case reporting is not a problem

Can you point me to the bug report for the issue in the projects current cipher spec?

mpan wrote:

That an issue can’t be opened using an automated ticket system is not preventing reporting. The world, including software development, lived with no tickets for most of its existence and with no trouble.

Which requires registering on another platform. Why not make it easy? If you are wondering what I have against registering on other platforms see https://gitlab.gnome.org/World/pika-bac … _items/689. If projects want help projects may need to make receiving help easier.

mpan wrote:

The issue has been reported within hours of Arch deploying the libtorrent-rasterbar update, and only with a minor delay on Deluge’s forum.

Reported where? No one involved in https://gitlab.archlinux.org/archlinux/ … rk_items/8 was aware of any upstream report.

mpan wrote:

Writing and properly testing patches is where the help may be needed.

So what is stopping you or the rest of the userbase?

Last edited by loqs (2026-08-14 02:00:21)

seth · 2026-08-14 07:08:48

f projects want help projects may need to make receiving help easier.

… like switching to a probably broken SSO gitlab infrastructure … /scnr

Reported where?

Probably https://forum.deluge-torrent.org/viewtopic.php?t=57703
Maybe https://bbs.archlinux.org/viewtopic.php … 0#p2304530
That's however not a "bug report" - which isn't happening because: see above.
We broke the internet

If you are wondering what I have against … https://gitlab.gnome.org/

Nahh… I think everyones aware of those particular problems
(Honest advice: if you want to report something to anything gnome, make the bug report and then mentally abandon it - discussing with them even whether the sun rises in the east, what you'll find yourself doing, is beyond frustrating)

All in all this thread seems a bit unaware of the implications of a rolling release distro - deluge probably focuses on cross-platform and ubuntu
If upstream is aware of the situation and arch bought some time that will hopefully cross the gap.

mpan · 2026-08-14 08:24:17

Loqs, what is your point? Please make a single, clear statement that explains what you are trying to prove by replying to me.

I attach the replies below for post completness only. Without answering the above you may as well ignore them — as I will skip over any further posts, unless I know what is their goal.

loqs wrote:

Can you point me to the bug report for the issue in the projects current cipher spec?

No, and I don’t see a reason I should.

loqs wrote:

mpan wrote:
loqs wrote:
(…) and new registrations on its trac may well leave the project unaware there even is an issue to fix. Without mentioning being unable to report security issues.
That an issue can’t be opened using an automated ticket system is not preventing reporting. The world, including software development, lived with no tickets for most of its existence and with no trouble.
Which requires registering on another platform. (…)

Note: I added a quotation for the context of what I said, and consequently for your response. And in this context I can’t understand what you are complaining about, and I see no connection to what I myself said.

loqs wrote:

mpan wrote:
The issue has been reported within hours of Arch deploying the libtorrent-rasterbar update, and only with a minor delay on Deluge’s forum.
Reported where? No one involved in https://gitlab.archlinux.org/archlinux/ … rk_items/8 was aware of any upstream report.

Maybe they were not. Why would they be, and why are you telling me this?

loqs wrote:

mpan wrote:
Writing and properly testing patches is where the help may be needed.
So what is stopping you or the rest of the userbase?

Userbase: no idea and I don’t see why are you expecting me to give explanations.
Me: stuff in my private life, details of which you don’t need to know.

Strictly speaking not “no idea,” but nothing suitable as an answer to the question in this context, tone, of this kind, in this thread.

seth · 2026-08-14 08:53:07

Why would they be

Because they likely checked upstream bug reports (where this isn't recorded) - the operative term in your statement at the head of this was "forum"
The "other platform" one would now have to register to (since trac doesn't work, github isn't accepted and gitlab not set up yet. I repeat: WE BROKE THE INTERNET!)

If anyone thinks upstream might need help with this, ideally has a communication vector there and is interested in deluge and mildly competent in python the sensible thing for that individual would be to send a patch.
Because that's how these things used to work™.

Otherwise there's nothing to see or discuss here, the downstream situation is momentarily addressed and upstream problems won't be fixed here ever.
Try to enjoy the summer day.

Arch Linux

#1 2026-07-13 23:26:51

[SOLVED] Deluged not compatable with current python packages

#2 2026-07-14 01:35:37

Re: [SOLVED] Deluged not compatable with current python packages

#3 2026-07-14 02:29:17

Re: [SOLVED] Deluged not compatable with current python packages

#4 2026-07-14 05:41:48

Re: [SOLVED] Deluged not compatable with current python packages

#5 2026-07-14 14:45:33

Re: [SOLVED] Deluged not compatable with current python packages

#6 2026-07-31 14:34:02

Re: [SOLVED] Deluged not compatable with current python packages

#7 2026-07-31 18:04:44

Re: [SOLVED] Deluged not compatable with current python packages

#8 2026-07-31 23:11:23

Re: [SOLVED] Deluged not compatable with current python packages

#9 2026-08-06 17:56:50

Re: [SOLVED] Deluged not compatable with current python packages

#10 2026-08-06 19:41:16

Re: [SOLVED] Deluged not compatable with current python packages

#11 2026-08-11 15:43:54

Re: [SOLVED] Deluged not compatable with current python packages

#12 2026-08-11 16:02:47

Re: [SOLVED] Deluged not compatable with current python packages

#13 2026-08-14 00:00:30

Re: [SOLVED] Deluged not compatable with current python packages

#14 2026-08-14 00:49:43

Re: [SOLVED] Deluged not compatable with current python packages

#15 2026-08-14 01:27:42

Re: [SOLVED] Deluged not compatable with current python packages

#16 2026-08-14 07:08:48

Re: [SOLVED] Deluged not compatable with current python packages

#17 2026-08-14 08:24:17

Re: [SOLVED] Deluged not compatable with current python packages

#18 2026-08-14 08:53:07

Re: [SOLVED] Deluged not compatable with current python packages

Board footer