Custom Query (2449 matches)
Results (571 - 573 of 2449)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #2368 | Invalid | All torrents dissapear after a crash | ||
| Description |
After a crash all torrents have disappeared in deluge. It seems that in torrentview.state the information of the torrents is still there. I'm using 1.3.6 version of Deluge for Windows. |
|||
| #2367 | Fixed | [win32] Private Flag not showing as ticked/checked in DelugeStart theme | ||
| Description |
Due to the private flag option being permanently greyed out the DelugeStart Windows theme is not showing whether the private flag is set or not. Forum thread: http://forum.deluge-torrent.org/viewtopic.php?f=7&t=45803 |
|||
| #2366 | Duplicate | Location of deluge pid file | ||
| Description |
Currently, the deluge pid file is located under $XDG_CONFIG_DIR, which may force the user to manually delete the pid file on unclean exits, eg power failure. If the location of the pid file was to use the $XDG_RUNTIME_DIR specification, this situation would be remedied. Exerpt of the standard according to http://standards.freedesktop.org/basedir-spec/basedir-spec-latest.html "The lifetime of the directory MUST be bound to the user being logged in. It MUST be created when the user first logs in and if the user fully logs out the directory MUST be removed. If the user logs in more than once he should get pointed to the same directory, and it is mandatory that the directory continues to exist from his first login to his last logout on the system, and not removed in between. Files in the directory MUST not survive reboot or a full logout/login cycle." The specification ensures that a pid file will not survive on a reboot or login/logout cycle. Thus, using $XDG_RUNTIME_DIR remedies this situation. |
|||
