I have to agree it is annoying and just happened to me 5min ago... I think the functionality should change. My initial idea would be to error out if the file was created and is now missing, however using deluge with remote shares or removable storage in a temporary missing state it could be annoying...

to build a new deluge version repeat steps 11-14 but with latest version 1.2.3 and libtorrent 0.14.10 (or 0.15.0)

check the version of deluge-web with --version

I think you are using lt 0.15 which has a known tracker issue. See other posts in this fourm.

You dont need to use a dev build of Deluge to use a patched 0.15, simply use it with the 1.2.3 source. However the current dev version is approaching release (1.3.0) very shortly so I doubt you will find issues with it.

As i said before we really need logs to determine what is happening. We also need to know whether you are using any plugins and how you have setup Deluge i.e. have you setup deluged or are you simply running as standalone

I did not realise you were using lt 0.15, i think this ticket is similar to your issue: http://dev.deluge-torrent.org/ticket/1213

latest version is 1.2.3 and will support that command.

I have seen no issues with Deluge 1.2.3 and Chrome

what version of deluge?