#3201: Create Windows package (Py3-GTK3)
------------------------------+---------------------
  Reporter:  Cas              |      Owner:
      Type:  feature-request  |     Status:  new
  Priority:  major            |  Milestone:  2.1.x
 Component:  Packaging        |    Version:  develop
Resolution:                   |   Keywords:
------------------------------+---------------------

Comment (by mhertz):

 Since Cas's install instructions in this thread results in not being able
 to announce to https trackers, then i'm trying to build libtorrent v1.1.13
 qith openssl, but even without openssl, then it doesn't work right in
 deluge2 for me, even though I can import it fine in a python ierminal
 still outside of deluge2. I can build latest libtorrent v1.2.2 and run in
 deluge2 fine, but just not v1.1.13, and don't get it.

 The strange thing also, is that often then right after building it, then
 when adding it to deluge2 and firering it up, then deluge2 start fine with
 it, but then if disconnecting from daemon and closing deluge2 and starting
 it again, then it never works regardless of how many times trying. Is
 shows an error 10061 of connection actively refused by destination
 computer, and loading it into dependency walker and profiling
 it(deluged.exe), shows this error:
 {{{
 Second chance exception 0xE06D7363 (Microsoft C++ Exception) occurred in
 "KERNELBASE.DLL" at address 0x00007FFB59ED50D8.
 }}}
 In the debug-log of deluge2 it states:
 {{{
 00:59:07 [DEBUG   ][deluge.ui.client                  :302 ]
 sslproxy.disconnect()
 00:59:07 [DEBUG   ][deluge.ui.gtk3.connectionmanager  :319 ] Failed to
 connect: Connection was refused by other side: 10061: Der kunne ikke
 oprettes forbindelse, fordi destinationscomputeren aktivt nægtede det..
 00:59:07 [INFO    ][deluge.ui.gtk3.connectionmanager  :335 ] Retrying
 connection.. Retries left: 1
 00:59:07 [DEBUG   ][deluge.ui.gtk3.connectionmanager  :288 ] Attempting to
 connect to daemon...
 00:59:07 [DEBUG   ][deluge.ui.client                  :286 ]
 sslproxy.connect()
 00:59:07 [DEBUG   ][deluge.ui.client                  :212 ] Connecting to
 daemon at "127.0.0.1:58846"...
 00:59:08 [DEBUG   ][deluge.ui.client                  :219 ] Connection to
 daemon at "127.0.0.1:58846" failed: Connection was refused by other side:
 10061: Der kunne ikke oprettes forbindelse, fordi destinationscomputeren
 aktivt nægtede det..
 00:59:08 [DEBUG   ][deluge.ui.client                  :596 ]
 on_connect_fail: [Failure instance: Traceback (failure with no frames):
 <class 'twisted.internet.error.ConnectionRefusedError'>: Connection was
 refused by other side: 10061: Der kunne ikke oprettes forbindelse, fordi
 destinationscomputeren aktivt nægtede det..
 ]
 00:59:08 [DEBUG   ][deluge.ui.client                  :302 ]
 sslproxy.disconnect()
 00:59:08 [DEBUG   ][deluge.ui.gtk3.connectionmanager  :319 ] Failed to
 connect: Connection was refused by other side: 10061: Der kunne ikke
 oprettes forbindelse, fordi destinationscomputeren aktivt nægtede det..
 }}}
 (The danish part means that there couldn't be made a connection because
 destination computer actively refused it)

 I have tried 5 different boost versions, where most give linking errors,
 which either is online reported to be unresolved or fixed by changing
 boost version. I know using boost over v1.66 needs a patch added to
 jamfile to support python3, but I do add that also, which makes it run,
 but fails later with linking errors. I usually stick to v1.66 because was
 reported by a libtorrent dev to be recommended as didn't need patches, and
 using that, makes it be imported every time in a terminal, but just not in
 deluge2, except often right after the building. I always include runtime
 files needed, and also used b2 option of static runtime linking without
 any change.

 I use python v3.68, and msvc build tools latest version(14.23 = 2019), but
 have tried also v14.16 = 2017), and change setup.py to reflect the proper
 msvc version, which is added to b2 command-line then, and address-model=64
 or whatever it is called I also use, and again, I build libtorrent v1.2.2
 with openssl fine, and doesn't have this issue and always connects, but it
 does however still show a connection error or two of the one posted above,
 but always connects fine anyway, as 5 or 6 of those is supported before
 failing I can see.

 Thanks alot in advance, as this is driving me freakin' crazy soon, as have
 run 100 test of this now I'd guess.

--
Ticket URL: <https://dev.deluge-torrent.org/ticket/3201#comment:44>
Deluge <https://deluge-torrent.org/>
Deluge Project

-- 
You received this message because you are subscribed to the Google Groups 
"Deluge Dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/deluge-dev/057.aabed39efbf8c3796787e14a95f55b42%40deluge-torrent.org.

Reply via email to