Date: prev next · Thread: first prev next last
2014 Archives by date, by thread · List index

Hi :)
On the Pi it might be possible to use a command-line to open the torrenting
client.  This is likely to give you more feedback after the torrrenting
crashes.  (Unless the whole Pi is crashing but that's unlikely.)

Also has anyone posted this to the devs mailing-list or tried their irc
channel or something to see if they have any ideas why it might be
happening?  So far we seem to be assuming it's the Pi end but maybe
something about the packaging or something the devs might have more
understanding of?

I take it that the normal download works fine?
Regards from
Tom :)

On 14 April 2014 09:03, Tim Lloyd <> wrote:


although I don't have any solutions, here are a few Pi related thoughts
which might help.

Where do you download to? Originally I used a powered USB drive to a hub
connected to the Pi. I found that rapid transfer from ethernet to Pi to USB
drive posed problems and locked up the Pi. This is not the same as your
problem but I now download to the SD card. There is a setting in
transmission which allows you to download to SD card and then copy the
finished file to another drive. This might be worth a try if you are not
currently doing this. It cuts out a few "hops" in the initial transfer

As the download seems to be pretty well progressed when it crashes maybe
there is a general mismatch between what has been transferred and what is
actually at the download location? As the download is pretty swift how
about pausing a couple of times? Say after 35% and 70% - let the storage
catch up with what has been downloaded?

Neither of these actually solve your problem but may ease the pain. At
some point it is worth raising a bug report to see whether any of the devs
can shed some light on this.

Let us know how you go


On 14/04/14 14:31, minos wrote:

Deluge client on Windows 7 64 sp1 :
- starting the crash time by a cpu core 100%... when I click on the Deluge
window, Windows ask to close the crashed app... nothing more to do.
- RPi with Transmission daemon : from another LAN computer, you can be
Transmission is crashing by webinterface not responding, no way to connect
to. If you ssh on the RPi, it's very very long to connect, if you can
connect... generally I reboot it by unplug/plug the power cable, and
delete the LibreOffice torrent !

It usually crash near 99% of the complete download. Sometimes 60%,
randomly... no rule here.
On Windows as the RPi, no logs are written; so no way to investigate :'(
Only LibreOffice I've tried is crashing both clients I have on my LAN
(behind a wrt54gl router, last Tomato by Shibby firmware). Other files are
ok and download is 100% complete, sharing is ok too.

Thx for help.

(or is it possible to have a pb with tracker communication... I don't know

View this message in context:
Sent from the Users mailing list archive at

To unsubscribe e-mail to:
Posting guidelines + more:
List archive:
All messages sent to this list will be publicly archived and cannot be

To unsubscribe e-mail to:
Posting guidelines + more:
List archive:
All messages sent to this list will be publicly archived and cannot be deleted


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.