Custom Query (2447 matches)
Results (568 - 570 of 2447)
Ticket | Resolution | Summary | Owner | Reporter |
---|---|---|---|---|
#2015 | Fixed | Progress Bar display issue with extjs 3.4 | ||
Description |
The progress bar has a display issue when the column is sorted. Not sure how far you got in debugging this one damoxc but I had a quick look myself and it seems to be that the wrong width is being supplied to the renderer. The value is smaller than the progress bar column width and it looked related to x-progress-text width. |
|||
#2017 | WorksForMe | WebUI gets into an endless Login loop | ||
Description |
Forwarded from forum (needs verified): http://forum.deluge-torrent.org/viewtopic.php?f=7&t=38327 WebUI and password problems seem to have been discussed a lot here, but still this problem is quite maddening - here is the step-by-step: (1) Start deluge (I use the deluge-gtk, from the desktop, for the moment) (2) Connect to it using a browser - login using the default password (3) Observe it all functioning properly - you can see the torrents, make changes, etc. (4) Click the the Options/Prefs/Configure button and open the pane that lets you change the Password and/or the Timeout and other things (5) Make ANY change there - e.g. set the timeout to something else. (6) Hit Apply and/or OK *** You get into an endless loop of Login Prompts !!! You are asked for your password again and again! If you enter the: (a) Correct password - you just get another login prompt window (b) Incorrect password - you get an "You entered an incorrect password!" message and back to the login prompt. No, I have not and do not wish to change the password! All I want is the WebUI to let me in! It clearly makes a distinction between the right and wrong passwords, but _something_ seems to get into some endless loop of logins when that particular config pane is used. |
|||
#2038 | Fixed | Chrome 17 disconnecting from webui | ||
Description |
A recent update to Chrome 17 has caused the webui to timeout after several minutes. From what I can tell the problem is actually a bug in deluge where a json request 'web.get_events' never gets a response. I don't fully understand this part of the code but my testing has found that returning a callback of None instead of continuing seems to keep Chrome connection alive and has no effect on receiving future plugin enabled events. diff --git a/deluge/ui/web/json_api.py b/deluge/ui/web/json_api.py index 4bbcf9a..cb5e8fc 100644 --- a/deluge/ui/web/json_api.py +++ b/deluge/ui/web/json_api.py @@ -400,7 +400,8 @@ def _get_events(self, listener_id, count, d): if count >= 3000: d.callback(None) else: - reactor.callLater(0.1, self._get_events, listener_id, count + 1, d) + d.callback(None) + #reactor.callLater(0.1, self._get_events, listener_id, count + 1, d) def remove_listener(self, listener_id, event): """ |