Bug in Deluge 2.1.1

[cesar marcano]

Traceback (most recent call last):

File "deluge-script.pyw", line 33, in <module> File "deluge\ui\ui_entry.py", line 140, in start_ui File "deluge\ui\gtk3\init.py", line 45, in start File "<frozen importlib._bootstrap>", line 1007, in _find_and_load File "<frozen importlib._bootstrap>", line 986, in _find_and_load_unlocked File "<frozen importlib._bootstrap>", line 680, in _load_unlocked File "PyInstaller\loader\pyimod03_importers.py", line 495, in exec_module File "deluge\ui\gtk3\gtkui.py", line 16, in <module> File "<frozen importlib._bootstrap>", line 1007, in _find_and_load File "<frozen importlib._bootstrap>", line 986, in _find_and_load_unlocked File "<frozen importlib._bootstrap>", line 680, in _load_unlocked File "PyInstaller\loader\pyimod03_importers.py", line 495, in exec_module File "gi\init.py", line 45, in <module> File "os.py", line 1111, in add_dll_directory

OSError: 87 The parameter is not correct: 'C:'

[cesar marcano]

After installing Deluge 2.1.1 and then when running the Deluge app of Version 2.1.1, and I discovered the unknown critical bug.

The app does not start on windows 8.1 (may even also on Windows 7 SP1), it led to a critical error.

Using on Windows 8.1

[cesar marcano]

It appears and commented on Stackoverflow, about the error OSError 87 in the Python:

​https://stackoverflow.com/questions/66908593/oserror-winerror-87-the-parameter-is-incorrect

This is a sort-of-a-bug in fabric (as of 2.6.0), see the discussion here:
https://github.com/fabric/fabric/issues/2142

Apparently, it shows up with Python 3.8 or 3.9, but not with 3.6 or 3.7.

To get around it, you can use: c.run("echo hello", replace_env=False)

This is OK for local calls, but can be problematic for remote calls, because it means that the remote session will see all environment variable values (some of which may be sensitive) of your local session.

[cesar marcano]

Another commented in py2exe should be there:

​https://github.com/py2exe/py2exe/issues/117

Good luck to fixing.