xbmc.abortRequested not set

Apparently, in my Dharma SVN 35648 running on Jaunty, the flag xbmc.abortRequested is not set at shutdown.

This simple script:


logs "Abort Requested: False" even after XBMC has been requested to exit, still after the "NOTICE: stop python" notification in the log, and then the script is interrupted by the system abruptly.

Is it a known bug? Perhaps fixed in recent releases?

I'm seeing the same in 10.1. Did you ever find out why this happens?
I'm also running the last build of dsplayer, and there it's working as expected.

I don't think was available in Dharma. It should be available in Eden-pre though(ie Nightly) As the 'service' module is only meant for Eden..

Is this event only sent when shutting down xbmc, or is it also sent when loggin out? Or is there another event that gets sent when logging off?

It is sent when shutting down XBMC, as the scripts that will use it, script.service... , will automatically start when XBMC starts.

sereende Wrote:Apparently, in my Dharma SVN 35648 running on Jaunty, the flag xbmc.abortRequested is not set at shutdown.

This simple script:

Code:

import time
import xbmc

xbmc.log("Started")

while 1:
    print "Abort Requested: "+str(xbmc.abortRequested)
    if (xbmc.abortRequested):
        xbmc.log("Aborting...")
        break
    time.sleep(1)

xbmc.log("Exiting")

logs "Abort Requested: False" even after XBMC has been requested to exit, still after the "NOTICE: stop python" notification in the log, and then the script is interrupted by the system abruptly.

Is it a known bug? Perhaps fixed in recent releases?

Hi,

Is there a solution for this problem?
I have the same issue, I would like to do one Python action when XBMC is shutdown.
But the xbmc.abortRequested seems not te be set when this happens.

Thanx in advance

FYI ... i'm on it ... see https://github.com/xbmc/xbmc/pull/690 (still discussing)