Comment 1 for bug 777684

Thanks for taking the time to report this. It's true that when SABnzbd is started, it is not paused automatically, even if it had been paused in the previous session. This is in contrast to a setting like the download speed limit, which is preserved across sessions.

LottaNZB is usually started because the user has the intention to download something. So, if SABnzbd is started as a result of starting LottaNZB, preserving the pausing state does not seem that intuitive and I'd rather not like to make that the default behavior.

However, in your case, SABnzbd appears to be started silently in the background when the computer is started (correct me if this assumption is wrong). It seems more appropriate to preserve the pausing state here. Since SABnzbd is started independently from LottaNZB, LottaNZB has no control over whether SABnzbd should be paused from the beginning.

I thus see the following solutions:

- Suggest the SABnzbd developers to add a setting that will cause the pausing state to be preserved across sessions.
- In the script that starts SABnzbd (usually /etc/default/sabnzbdplus), add the extra command line option -pause so that SABnzbd is always paused on startup. While you'll need to resume SABnzbd, it will at least not start downloading automatically.