Red Hat Bugzilla – Bug 247927
Deluge do not start
Last modified: 2007-11-30 17:12:10 EST
Description of problem:
Since i have update Deluge from updates-testing, it do not start.
Version-Release number of selected component (if applicable):
It is happened every time.
Steps to Reproduce:
1. launch Deluge from the menu or enter deluge in the shell
Deluge do not start
The launch of Deluge
Created attachment 159026 [details]
Result of the shell
Hello; and thank you for the bug report.
Your backtrace looks nearly identical to one I had posted on the forums:
Please remove your $HOME/.config/deluge/persistent.state file (e.g., "rm
/home/username/.config/deluge/persistent.state" from a terminal, or similar) and
see if that works around the issue. (Removing this file should be harmless, as
it contains only some torrent-specific activity data that will be automatically
regenerated by Deluge the next time the torrent in question is active.)
If you're curious of the details, I've hunted this down to the following cause:
This is an unfortunate incompatibility introduced by upstream which hurts
because it uses the Python pickle module to store various activity data across
session, which stores a hardcoded module name in the configuration files it
writes. With Deluge 0.5 and earlier, this was a submodule within the global
'deluge' module. This has changed in 0.5.1+, which means that there is no module
registered with the pickle loader to handle the usage of the activity data.
Please let me know if this fixes your issue; and, if so, I will add some
upgrading-specific documentation to the package. Unfortunately, arbitrarily
removing files in a user's home directory is not feasible as a package scriptlet
for various reasons, so it cannot be an automatic feature.
I have remove $HOME/.config/deluge/persistent.state file and now i can launch
If it is not possible to remove the file with package, maybe it is possible with
Hmm. I think patching the inital startup script might do the job. I'll see what
I can devise...
Maybe it's could be good to have something like :
#pickle module loading
#remove $HOME/.config/deluge/persistent.state file and try again
Hmm. I delved through it a bit more deeply and found that you can keep the
persistence data so long as the the old module name is replaced. (In fact, this
is probably the preferred method, so that the running data of the user is kept
across the upgrade and he or she does not need to restart any torrents they had
E.g., a simple "sed -i -e 's/^(ideluge.deluge/(ideluge.core/g' persistent.state"
should take care of it. That shouldn't be too hard with file.readline() and
re.sub() kung-fu so I'll whip up a patch for this first thing tomorrow. :)
Okey dokey. After some mucking with the re module a bit, I've got a 55-line
patch that should take care of fixing this issue. I'm updating my F-7 virtual
machine now and will test it there. Once that's done successfully I'll commit it
as an update. (Should be another few hours....man I really need to update this
VM far more often. T_T)
deluge-0.5.2-2.fc7 has been pushed to the Fedora 7 testing repository. If problems still persist, please make note of it in this bug report.
deluge-0.5.2-2.fc7 has been pushed to the Fedora 7 stable repository. If problems still persist, please make note of it in this bug report.