Custom Query (2447 matches)
Results (388 - 390 of 2447)
Ticket | Resolution | Summary | Owner | Reporter |
---|---|---|---|---|
#292 | Fixed | clicking the tray icon fails to restore the main window | ||
Description |
Deluge 0.6.0.0r3270 when you enable "Start in tray" the next time you restart deluge, when you click the tray icon to restore the window it fails with: Traceback (most recent call last): File "/usr/lib/python2.4/site-packages/deluge/ui/gtkui/systemtray.py", line 249, in on_tray_clicked self.window.present() File "/usr/lib/python2.4/site-packages/deluge/ui/gtkui/mainwindow.py", line 99, in present self.config["window_x_pos"] = self.window_x_pos AttributeError: MainWindow instance has no attribute 'window_x_pos' right clicking the tray icon and selecting "Show Deluge" fails with: Traceback (most recent call last): File "/usr/lib/python2.4/site-packages/deluge/ui/gtkui/systemtray.py", line 267, in on_menuitem_show_deluge_activate self.window.present() File "/usr/lib/python2.4/site-packages/deluge/ui/gtkui/mainwindow.py", line 99, in present self.config["window_x_pos"] = self.window_x_pos AttributeError: MainWindow instance has no attribute 'window_x_pos' |
|||
#872 | Fixed | Client disconnects from daemon because daemon stops | ||
Description |
Using Deluge 1.1.5 on Ubuntu Hardy I experience regular disconnections of the client caused by the daemon quitting. When I go to the connection manager the daemon is 'red' and restarting and connecting gets everything started again. It looks like the problem described in http://forum.deluge-torrent.org/viewtopic.php?f=12&t=14425&p=70655&hilit=disconnect#p70655 but on my system the daemon seems to have stopped. My connections limit is set to 1000. Every time the number of open connections had reached 1000 the server bails out. However when I set my maximum number of connections to 600 the problem does not occur. |
|||
#2555 | Fixed | Client unable to connect with recent openSSL library / disable SSLv3 usage | ||
Description |
Because of CVE-2014-3566 (POODLE) OpenSSL 1.0.1j has option to build without SSLv3 support (The Debian unstable distribution now has a version which does this). This breaks the rpcserver ssl connections. The WebUI was switched to TLSv1_METHOD in 1.3.10. But the RPCserver still has SSLv3_METHOD. Not sure if compatibility of the TLS version between a deluge client and server is a big issue (or if you would want to limit it to TLSv1 only). Here's a quick patch I applied, which also supports TLS 1.1 and TLS 1.2 |