#1531: gtk ui not working after upgrade
----------------------+-----------------------------------------------------
 Reporter:  matthieu  |       Owner:       
     Type:  bug       |      Status:  new  
 Priority:  major     |   Milestone:  1.3.x
Component:  gtkui     |     Version:  1.3.5
 Keywords:            |  
----------------------+-----------------------------------------------------
Changes (by uus):

 * cc: uus1@… (added)
  * version:  1.3.1 => 1.3.5


Comment:

 Replying to [comment:7 Cas]:
 > As I said before with no information to go on and being unable to
 reproduce ourselves it is impossible for us to debug this.
 >
 > You will need try testing different scenarios with the config. For
 example setting up a clean config, check clients connect then copy the
 state folder over that contains all your torrent info and try again.
 >
 > Are you connecting locally or over network to deluged?

 Hi! I have the same issue.
 I try to connect over the network to deluged.
 Systems are:
 Linux ustor 3.0.0-17-server #30-Ubuntu SMP Thu Mar 8 22:15:30 UTC 2012
 x86_64 x86_64 x86_64 GNU/Linux (deluged)(172.16.0.10)
 Linux uusx 3.0.0-17-generic #30-Ubuntu SMP Thu Mar 8 20:45:39 UTC 2012
 x86_64 x86_64 x86_64 GNU/Linux  deluge-gtk(172.16.0.2)
 windows 7 corporate x32 (172.16.0.6)
 deluge version:1.3.5
 server is a new installation of deluged. Yesterday it worked fine, but
 afer adding several(~50) torrents from http://tracker.hdclub.com.ua and
 rebooting i have what i have.

 deluge_win is when windows laptop tried to connect; deluge_lin is from the
 moment linux PC tried to connect.
 as i can assume the main point of the logs is
 [INFO    ] 17:48:35 rpcserver:203 Deluge Client connection made from:
 172.16.0.2:48259
 [INFO    ] 17:48:35 rpcserver:223 Deluge client disconnected: Connection
 was closed cleanly.

 creating new profile for deluge helps to resolve the issue but you loose
 all the torrents states(((
 I also do next(on server):
 '''stop deluged;[[BR]]
 mv .config/deluge/state .config/deluge/state_old;[[BR]]
 start deluged; <- at this point remote client was already able to connect
 to deluged[[BR]]
 stop deluged; [[BR]]
 rm -rvf .config/deluge/state[[BR]]
 mv  .config/deluge/state_old/ .config/deluge/state'''[[BR]]


 so it helped:remote clients are able to connect to deluged without loosing
 torrents state.

-- 
Ticket URL: <http://dev.deluge-torrent.org/ticket/1531#comment:8>
Deluge <http://deluge-torrent.org/>
Deluge project

-- 
You received this message because you are subscribed to the Google Groups 
"Deluge Dev" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/deluge-dev?hl=en.

Reply via email to