Possible shutdown fix for Xbmcfreak livecd Natty Dharma v1

The following instructions could solve the Natty Dharma v1 livecd shutdown problem. Make sure the following packages are installed:

sudo apt-get install policykit-1 upower acpi-support

Create a new file custom-actions.pkla on the following location:

sudo nano /var/lib/polkit-1/localauthority/50-local.d/custom-actions.pkla

Copy paste the contents below to the file. Make sure the xbmc user is set correctly!

[Actions for xbmc user]
Identity=unix-user:xbmc
Action=org.freedesktop.upower.*;org.freedesktop.consolekit.system.*;org.freedesktop.udisks.*
ResultAny=yes
ResultInactive=no
ResultActive=yes

Please let me know if this fixes your problem. More info can be obtained from: http://wiki.xbmc.org/index.php?title=Ubuntu_Suspend_/_Wake

If a file /var/lib/polkit-1/localauthority/50-local.d/20-xbmclive.pkla already exist make sure the content looks like:

[XBMC-Live user permissions]
Identity=unix-user:xbmc
Action=org.freedesktop.upower.*;org.freedesktop.consolekit.system.*;org.freedesktop.udisks.*
ResultAny=yes
ResultInactive=no
ResultActive=yes

Comments

  1. Steven says:

    Hier doethet helaas niets.
    Pakketjes waren al geinstalleerd.

    nieuw bestand is “custom-actions.pkla”
    [Actions for xbmc user]
    Identity=unix-user:steven
    Action=org.freedesktop.upower.*;org.freedesktop.consolekit.system.*;org.freedesktop.udisks.*
    ResultAny=yes
    ResultInactive=no
    ResultActive=yes

    oot@XBMCLive:/var/lib/polkit-1/localauthority/50-local.d# cat 20-xbmclive.pkla
    in dezelfde dir stond al een bestand “20-xbmclive.pkla”:

  2. Steven says:

    bestaande bestand:

    cat 20-xbmclive.pkla

    # Policy to allow the livecd user to bypass policykit. Should be installed at /var/lib/polkit-1/localauthority/50-local.d/20-xbmclive.pkla
    [XBMC-Live user permissions]
    Identity=unix-user:steven
    Action=*
    ResultAny=no
    ResultInactive=no
    ResultActive=yes

  3. Steven says:

    Fixed, I had to do one more thing which is also mentioned on http://wiki.xbmc.org/index.php?title=Ubuntu_Suspend_/_Wake

    “NOTE: You may have to comment out the existing 20-xbmclive.pkla as well until this issue is resovled”

    After commenting out all lines, shutdown seems to work again, great!
    Thanks!

  4. Steven says:

    I was a bit too fast. Pushing on shutdown via remote seems to let the system resume (go to standby).
    After resuming (pushing once on the power buttom) the system comes back but remote isn’t working any more

  5. adgr says:

    Steven :I was a bit too fast. Pushing on shutdown via remote seems to let the system resume (go to standby).After resuming (pushing once on the power buttom) the system comes back but remote isn’t working any more

    Did you see the part “Fix the Lirc Device Increment Bug” in the wiki and did you create the /etc/pm/sleep.d/90_lirc sleep as instructed in that same wiki?

  6. cobradevil says:

    was idd even zoeken.
    heb de oplossing in het ticket gezet en monkeyman heeft het verwerkt in git.

    Groeten William

  7. cobradevil says:

    @Steven
    Hoi Allen,

    Ik had vorige week hetzelfde issue maar dan op een minimal install.

    http://cobradevil.org/index.php?title=XBMC_GIT_Eden_natty_Zotac-id31
    Het probleem heb ik in het ticket gemeld en is reeds verwerkt.

    William

  8. t11r says:

    I have the same problem as Steven, I have the the /etc/pm/sleep.d/90_lirc file.
    I edited the wiki entry because there was a typo in the url for the LIRC.STOP command. I also added ‘NOTE: You have to enable control of XBMC via HTTP for this to work.’

    Calling
    wget “http://127.0.0.1:9019/xbmcCmds/xbmcHttp?command=ExecBuiltIn&parameter=LIRC.Stop”
    Gives this response:

    OK

    Calling
    wget “http://127.0.0.1:9019/xbmcCmds/xbmcHttp?command=ExecBuiltIn&parameter=LIRC.Start”
    Gives no response

    Is this correct? Or has it something to do with the fact that the HTTP API is deprecated since Dharma?

    So in the end everything works except for the remote after suspend :s

  9. t11r says:
  10. t11r says:

    I seem to have found the culprit:

    $ sudo /etc/init.d/lirc stop
    * Stopping remote control daemon(s): LIRC
    …done.
    $ sudo /etc/init.d/lirc start
    * Loading LIRC modules
    …done.
    * Unable to load LIRC kernel modules. Verify your
    * selected kernel modules in /etc/lirc/hardware.conf

    adding:

    DRIVER=”"
    DEVICE=”"
    MODULES=”lirc_mceusb”

    to /etc/lirc/hardware.conf doesn’t help it.
    Will look in to it tonight, but suggestions would be nice :)

  11. BiTRiP says:

    Try this /etc/lirc/hardware.conf

    # /etc/lirc/hardware.conf
    #

    #Dont start irexec
    START_IREXEC=false

    #Chosen Remote Control
    REMOTE=”Nuvoton Transceivers/Remotes”
    REMOTE_MODULES=”lirc_dev nuvoton-cir”
    REMOTE_DRIVER=”default”
    REMOTE_DEVICE=”/dev/lirc0″
    REMOTE_SOCKET=”"
    REMOTE_LIRCD_CONF=”remotes/mceusb”
    REMOTE_LIRCD_ARGS=”"

    #Chosen IR Transmitter
    TRANSMITTER=”None”
    TRANSMITTER_MODULES=”"
    TRANSMITTER_DRIVER=”"
    TRANSMITTER_DEVICE=”"
    TRANSMITTER_SOCKET=”"
    TRANSMITTER_LIRCD_CONF=”"
    TRANSMITTER_LIRCD_ARGS=”"

    #Enable lircd
    START_LIRCD=”true”

    #Don’t start lircmd even if there seems to be a good config file
    #START_LIRCMD=”false”

    #Try to load appropriate kernel modules
    LOAD_MODULES=”true”

    # Default configuration files for your hardware if any
    LIRCMD_CONF=”"

    #Forcing noninteractive reconfiguration
    #If lirc is to be reconfigured by an external application
    #that doesn’t have a debconf frontend available, the noninteractive
    #frontend can be invoked and set to parse REMOTE and TRANSMITTER
    #It will then populate all other variables without any user input
    #If you would like to configure lirc via standard methods, be sure
    #to leave this set to “false”
    FORCE_NONINTERACTIVE_RECONFIGURATION=”false”
    START_LIRCMD=”"

    Also be sure this line is in /etc/lirc/lird.conf:

    include “/usr/share/lirc/remotes/mceusb/lircd.conf.mceusb”

  12. john-cord says:

    on Ubuntu 10.10 Maverick, Kernel 2.6.35-* You Should enable sysfs based wakeup on Remote Control device,

    on my system it is done by

    echo enabled > /sys/bus/usb/devices/2-4/power/wakeup

    You can find which is Your device by grepping dmesg, for me it is mceusb

    dmesg |grep mceusb

  13. tech242 says:

    BiTRiP :
    Try this /etc/lirc/hardware.conf

    Thanks BiTRiP, that config did it for me! Remote wasn’t working after resume, but after switching my hardware.conf for yours remote works nicely after resume as well!

  14. Mitch says:

    Ik zag op github xbmcfreak het volgende :
    xbmcfreak pushed to master at xbmcfreak/xbmcfreak-natty
    7e83c32 shutdown and web reference to php remote fixed

    Betekent dit dat er snel een nieuwe versie komt van xbmc livecd Natty Dharma ?

Leave a Comment

*