SABnzbd Forums

I recently upgraded OpenElec to 4.0.0 and reinstalled the SANnzbd suite; it can no longer suspend the system after completing the queued downloads. I ran the debug logging last night and it provided this:

INFO::[__init__:1600] Queue has finished, launching: <function system_standby at 0x117c320> (None)
2014-05-11 05:06:03,753::INFO::[__init__:1600] Performing system standby
2014-05-11 05:06:03,763::INFO::[__init__:1600] DBus not reachable (org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.UPower was not provided by any .service files)
2014-05-11 05:06:03,763::INFO::[__init__:1600] DBus not reachable (org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.DeviceKit.Power was not provided by any .service files)
2014-05-11 05:06:03,764::INFO::[__init__:1600] DBus does not support Suspend (standby)

Any suggestions on how to fix this? Thanks.

A completely fresh install of OE 4.0.1 hasn't fixed this problem and it definitely isn't the hardware as XBMC can suspend the system without a problem (as could previous versions of SAB). Does anyone have a clue how this works?

I can't find which code SAB executes to suspend, but some googling lead me to this command:
So if you run that as normal user on your OE 4, what do you get?
FWIW, my Ubuntu laptop went to suspend immediatly:

@HTJ did you try this?

Hmmm .. no response from the OP. Quite disappointing. I will unsubscribe from this thread and put HTJ on my ignore list.

I wasn't free during the week to test it. It produces the same type of error:

Error org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.UPower was not provided by any .service files

I've tested this on a completely clean install of OpenElec 4.0.1 and the same thing happens.

Is "dbus" support installed?