Custom Query (2447 matches)

When I insist adding a magnet after it encounters the warning "unable to download files for this magnet", the magnet gets added to the list but is dropped after restarting deluge, prompting me to add the magnet again. Is this the intended behavior?

I assume it is not. Previous versions did not have this behavior, which I find to be better, since the situation for the magnet may later change when a better internet connection is achieved.

If this is the intended behavior, please reconsider on account of the preceeding logic.

I narrowed issue down to commit #bcaaeac, specifically last change of menubar.py, breaking this i.e.:

-            item = Gtk.RadioMenuItem(group=maingroup, label=username)
+            item = Gtk.RadioMenuItem.new_with_label(maingroup, username)

So reverting that, makes the menu/context-menu entries return for said option, which otherwise got hidden from called error-callback function. Strange as looks in line with documentation, but obviously no expert myself.

Issue reported on forum by darcmandeluge here: ​https://forum.deluge-torrent.org/viewtopic.php?p=237035#p237035

Thanks in advance!

When you set a config directory path (-c) on the command line, and only when, a file named logging.conf is read to set fine grained log levels. This allows to have per module/plugin log levels.

The file is parsed and the log levels are set in the deluge.log.tweak_logging_levels. This function set the appropriate logger to the desired level. Despite the log level is changed, log levels less than ERROR are still not logged.

The reason is that the log level check is done twice, in the logging.Logger class and in the logging.Handler class.

Fix proposed: ​https://github.com/deluge-torrent/deluge/pull/428