Search found 31 matches

by ApexDE
December 17th, 2022, 10:33 am
Forum: Feature Requests
Topic: New option "On queue finish"
Replies: 24
Views: 9097

Re: New option "On queue finish"

is there a way to make them persistent again?

EDIT: found it, sorry ;)

("queue_complete_pers" must be true)
by ApexDE
February 3rd, 2022, 3:40 am
Forum: Bug Reports
Topic: Bug: once a Script is set for a job, it can't be reset to "do nothing" - 3.2.1
Replies: 8
Views: 10814

Re: Bug: once a Script is set for a job, it can't be reset to "do nothing" - 3.2.1

with 3.5.0 i can‘t even set a custom script on the main-webpage „when done“ same behavior as described above: when i select a custom script it jumps back to the previous selected one. Maybe it‘s a safari issue, as i updated to 15.3 recently. macOS Catalina latest security update. It works on mobile ...
by ApexDE
May 23rd, 2021, 1:45 am
Forum: Bug Reports
Topic: Bug: once a Script is set for a job, it can't be reset to "do nothing" - 3.2.1
Replies: 8
Views: 10814

Re: Bug: once a Script is set for a job, it can't be reset to "do nothing" - 3.2.1

It happens with Firefox too. I found out that i can switch between the other scripts, but NOT back to "nothing". So i simply made script "nothing.sh" as a workaround which does - nothing ;) I didn't see anything special when i did open the console and inspected the element regard...
by ApexDE
May 15th, 2021, 11:28 am
Forum: Bug Reports
Topic: Bug: once a Script is set for a job, it can't be reset to "do nothing" - 3.2.1
Replies: 8
Views: 10814

Re: Bug: once a Script is set for a job, it can't be reset to "do nothing" - 3.2.1

I tried it with 3.3.0RC1 but it's still not possible to revert back to "do nothing" once a script is set for a certain job.

Setting a script for "on queue finish" works. I prefer job-based scripts, though.
by ApexDE
May 14th, 2021, 2:20 am
Forum: Bug Reports
Topic: Bug: once a Script is set for a job, it can't be reset to "do nothing" - 3.2.1
Replies: 8
Views: 10814

Bug: once a Script is set for a job, it can't be reset to "do nothing" - 3.2.1

I often use the option to run a script when a certain job is finished (e.g. last one in the queue). Since at least sabNZB 3.2.0 you can't revert to "do nothing" instead of the chosen script. Reproducable all the time on macOS 10.15.7
by ApexDE
January 26th, 2017, 4:18 pm
Forum: Beta Releases
Topic: 1.1.1/1.2.0RC1 : Sleep-when-finished broken on macOS Sierra
Replies: 17
Views: 14561

Re: 1.1.1/1.2.0RC1 : Sleep-when-finished broken on macOS Sie

... but: it hadn't "#!/bin/bash" in the first line. The script is executed fine now from sabnzbd also.
by ApexDE
January 21st, 2017, 3:16 am
Forum: Beta Releases
Topic: 1.1.1/1.2.0RC1 : Sleep-when-finished broken on macOS Sierra
Replies: 17
Views: 14561

Re: 1.1.1/1.2.0RC1 : Sleep-when-finished broken on macOS Sie

Yes, it has. It is executable from Terminal just fine also.
by ApexDE
January 20th, 2017, 4:12 pm
Forum: Beta Releases
Topic: 1.1.1/1.2.0RC1 : Sleep-when-finished broken on macOS Sierra
Replies: 17
Views: 14561

Re: 1.1.1/1.2.0RC1 : Sleep-when-finished broken on macOS Sie

I put some echo output to be written in a text file. The script works when called from terminal and logs to the text file, but not when called from sabnzb. The script isn't executed at all. I can get the system to sleep if i ssh into it and execute "pmset sleepnow" mybe you can add this co...
by ApexDE
January 20th, 2017, 10:25 am
Forum: Beta Releases
Topic: 1.1.1/1.2.0RC1 : Sleep-when-finished broken on macOS Sierra
Replies: 17
Views: 14561

Re: 1.1.1/1.2.0RC1 : Sleep-when-finished broken on macOS Sie

I put some debug output in the script. Problem is: the script does NOT run on postprocess-finish, even though the log says it did. Thats why the machine won't got to sleep mode. 2017-01-20 16:21:32,200::INFO::[postproc:815] Queue has finished, launching: <function run_script at 0x55cc530> (sleep-now...
by ApexDE
January 15th, 2017, 11:10 am
Forum: Bug Reports
Topic: 1.20: Postprocessing Scripts not executed correctly
Replies: 2
Views: 1693

Re: 1.20: Postprocessing Scripts not executed correctly

Ah, OK. Thanks.

But shouldn't the stay-awake-module stop and allow the sleep script to launch after the queue has finished?

Is it possible to disable the stay-awake-module somewhere in the settings?
by ApexDE
January 15th, 2017, 10:35 am
Forum: General Help
Topic: SABNZB not calling post-proc scripts at all
Replies: 2
Views: 1498

Re: SABNZB not calling post-proc scripts at all

Do have a logfile entry?

I have the same issue and posted a bug report.
by ApexDE
January 15th, 2017, 10:24 am
Forum: Bug Reports
Topic: 1.20: Postprocessing Scripts not executed correctly
Replies: 2
Views: 1693

1.20: Postprocessing Scripts not executed correctly

I'm on macOS Sierra. I made a rock-solid sleep script for commandline. It works perfect in every condition, but not with sabnzb. It isn't spwaned correctly, see here: <USERNAME> should be mine (ds) 2017-01-15 16:00:06,418::INFO::[postproc:85] Saving postproc queue 2017-01-15 16:00:06,419::INFO::[__i...
by ApexDE
January 15th, 2017, 10:20 am
Forum: Beta Releases
Topic: 1.1.1/1.2.0RC1 : Sleep-when-finished broken on macOS Sierra
Replies: 17
Views: 14561

Re: 1.1.1/1.2.0RC1 : Sleep-when-finished broken on macOS Sie

I guess the bug lies here. I made a rock-solid sleep script for commandline. It works perfect in every condition, but not with sabnzb. It isn't spwaned correctly, see here: USERNAME should be mine (ds) 2017-01-15 16:00:06,418::INFO::[postproc:85] Saving postproc queue 2017-01-15 16:00:06,419::INFO::...