Deluge disappears a few seconds after launch

[wateronmars]

Deluge worked great for a while, but now whenever I try to launch it, the .exe disappears after a few seconds. A reinstall did fix it, until I next restarted my computer. There's no apparent crash or anything visibly happening at all - I have to open task manager to see that the .exe does start, then just vanishes.
It's whitelisted and not getting quarantined by internet security (MWB) or firewall (windows). I don't have a clue what's causing it, and my attempts to search for answers have only returned unrelated results.

Version Information: 1.3.15
Operating System: Win10
Installation method: deluge-1.3.15-win32-py2.7.exe from https://ftp.osuosl.org/pub/deluge/windows/

[ambipro]

https://archive.org/details/deluge-1.3.15-win32-py2.7

I've uploaded the original 1.3.15 to archive.org, that installer is not on the link you provided, only 2.1.1.

I'm not sure why you'd want 1.3.15 these day, 2.1.1 is much more solid and performant.

[wateronmars]

Thanks, I'll try reinstalling from that. I'm using that version because a private tracker I'm on will only give you support if you use specific clients - "Deluge 1.3.x or 2.0.x (1.3.15 Recommended)". I remember there was a reason I went for 1x over 2x, but I can't remember what it was.

[wateronmars]

Unfortunately, did not fix it - as soon as I restarted, it resumed disappearing instead of launching. Also, weirdly, I couldn't get any connections in the time between reinstalling and restarting when it did actually run... I think my torrent clients may actually be cursed.

Just tried installing 2.0 over it and that didn't appear to change anything, either.

[ambipro]

try turning on logging. You can find the arguments (and using debug executable may help too in a command prompt so it doesn't just close...)

https://man.archlinux.org/man/deluged.1.en

the arguments are the same for windows. You can use them with deluge-debug as well.

[wateronmars]

Please forgive my ignorance, but how do I do that?

[ambipro]

what do you mean?

There's a deluge-debug.exe in program files\deluge.....

open a command prompt and go to that folder and run run "deluge-debug -l c:\deluge.log -L debug"

There will be a log file. You will see output. It will tell us what's causing it to exit if it's even starting.

[wateronmars]

Okay, I tried running like you said, and the first go didn't work, but the second one let it actually start up, which makes me think there's something it doesn't like about not being installed on the C drive?

Code: Select all

E:\Programs\Deluge>deluge-debug -l c:\deluge.log -L debug
Traceback (most recent call last):
  File "<string>", line 6, in <module>
  File "__main__.py", line 128, in <module>
  File "__main__deluge-debug__.py", line 11, in <module>
  File "deluge\ui\ui_entry.py", line 62, in start_ui
  File "deluge\ui\baseargparser.py", line 226, in parse_known_ui_args
  File "deluge\ui\baseargparser.py", line 255, in _handle_ui_options
  File "deluge\log.py", line 146, in setup_logger
  File "logging/__init__.py", line 913, in __init__
  File "logging/__init__.py", line 945, in _open
  File "codecs.py", line 896, in open
IOError: [Errno 13] Permission denied: 'c:\\deluge.log'

E:\Programs\Deluge>deluge-debug -l e:\deluge.log -L debug

It appears to be running normally, but again with no connections...