Simply running
deluge -L debug seems to have solved it. I don't think it's a permission issue because new torrents download just fine in that directory.
Edit: If I quit Deluge (force quit because
regular "Quit" freezes the application), then it's stuck. Deluge simply won't quit. Just.. freezes.
Also, if I download something large (like a documentary pack) over some partial matches (same folder, same filenames, etc), and I close it before Deluge can check them, it will get stuck at "Checking 0.00%" next time I start Deluge.
But like I said, this doesn't happen if I run it using
deluge -L debug.
Should I start Deluge this way from now on ? And why does this "debug" feature even affect Deluge this way ?
Edit #2: Just noticed that it says "Paused 10.56%" and it's downloading at the same time. Wow... Just... wow.
Have you ever seen this before ? I remember messing around with the state saves before:
http://forum.deluge-torrent.org/viewtop ... =7&t=36695 But shouldn't uninstalling Deluge, clearing the package cache and reinstalling Deluge fix it ? Because I've already tried it. Hmmm... Silly question. Maybe you're not familiar with pacman, the default package manager in Arch. Pacman is supposed to uninstall it completely using the -Rns argument, everything except files that the packages themselves create (like dot files in the home dir, etc).
And since I've only messed with these two files...
/usr/lib/python2.7/site-packages/deluge/core/torrent.py
/usr/lib/python2.7/site-packages/deluge/ui/gtkui/torrentview.py
I think they're part of the deluge package, not something deluge created post-install. But I'm not sure, when running
pacman -Ql deluge (to see everything the "deluge" package installed), I run out of scrolling space because the list is too long.

Any idea on how I could echo it to a file or something to see the full list ?