Deep Standby prevented when a background is running.

[ccs]

Minor issue but annoying none the less. - I know it's unlikely to happen, but I've seen it twice in the last week!

I set most timers to go to deep standby when finished - particularly the last ones of the day. This ensures the box is not left on when not being used.

If a background job is running when the timer ends, in particular autotimer, a dialogue pops up which requires user intervention.

"Backgound job running, autotimer, 47% complete - really shut down now? Yes/No" or something similar.

This remains until I spot it, which could be 18 hours later.

Any chance of this changing to a count down popup, defaulting to yes (bearing in mind autotimer will more than likely have finished after 120 seconds anyway)?

[ccs]

This commit was written to prevent deep standby when not wanted, and very handy it is, now I'm after deep standby when it is wanted.

https://github.com/OpenViX/enigma2/c...16fb864dbcf746

[birdman]

This commit was written to prevent deep standby when not wanted, and very handy it is, now I'm after deep standby when it is wanted.

https://github.com/OpenViX/enigma2/c...16fb864dbcf746

Hmmm....that was me.
I'll take a look, but can't test anything for ~a week.

[birdman]

Any chance of this changing to a count down popup, defaulting to yes (bearing in mind autotimer will more than likely have finished after 120 seconds anyway)?

It really needs a short(ish) timeout, but a repeat on "no response" (so that at some point it runs again and, that time, hopefully succeeds).

[birdman]

Hmmmm.... This is all to do with TryQuitMainLoop. I seem to recall fixing(?) some code somewhere because this returned when the code wasn't expecting it to. But I can't find it (so may be wrong).

However, in the meantime you can disable the pop-up in such circumstances (and hence enable the shutdown) by disabling the Task warning on shutdown option in the Customize settings menu.
It presumably can't do any harm, as if the box is already in Standby it shuts down with no prompt anyway.

[birdman]

Hmmmm.... This is all to do with TryQuitMainLoop. I seem to recall fixing(?) some code somewhere because this returned when the code wasn't expecting it to. But I can't find it (so may be wrong).

No, I was right:
https://github.com/OpenViX/enigma2/pull/187
Not sure it helps here, though.

[ccs]

Hmmmm.... This is all to do with TryQuitMainLoop. I seem to recall fixing(?) some code somewhere because this returned when the code wasn't expecting it to. But I can't find it (so may be wrong).

However, in the meantime you can disable the pop-up in such circumstances (and hence enable the shutdown) by disabling the Task warning on shutdown option in the Customize settings menu.
It presumably can't do any harm, as if the box is already in Standby it shuts down with no prompt anyway.

Thanks, I hadn't noticed that option before.
I assume that autotimer runs when the box is in standby, and it certainly appears to be be robust enough not to corrupt the xml file if terminated unexpectedly.
Plenty of my timers will have run in standby, and I've never seen any problems with autotimer.

I assume that "a recording is about to start/due soon" (or whatever the wording is) is not classed as a "pending background job" ??

[birdman]

I assume that "a recording is about to start/due soon" (or whatever the wording is) is not classed as a "pending background job" ??

From a quick look and a bit of guessing, what happens there is that the default answer for the pop-up is False.
(the code is in Screens/Standby.py).
It seems to me that this piece of code needs 3 options, Yes, No and retry in <n> mins.

[ccs]

Disabling the Task warning on shutdown option has the desired effect for autotimer.

Warnings are still given for recordings about to start/running, which is what you'd want.

A warning is still given if you're in timeshift - I never use it, but once in a while finger trouble starts it off, so I get the same issue with failure to go into deep standby when timers finish unattended.

Is this avoidable?

[birdman]

A warning is still given if you're in timeshift - I never use it, but once in a while finger trouble starts it off, so I get the same issue with failure to go into deep standby when timers finish unattended.

Is this avoidable?

Only by changing the code (there's no configurable option).

I'm not sure why being in timeshift should ever prevent such a shutdown (surely it's no different to manually switching to Deep Standby?)
But then I never use timeshift, so may be missing something (and I don't mean missing a programme because of not using timeshift!).

[ccs]

..... manually switching to Deep Standby produces the same timeshift dialogue (4 options, I think) as a recording finishing and going to deep standby.