[b4sh]

Do I really need to install hald? I thoughts is has gone in latest ubuntu distro.

Yes, without hald xbmc not shutdown your machine.

[wgandhi]

I am not sure if you have to install hald. I think it is gone from ubuntu 10.04 as well. I can double check when I get home if I have it installed.
Just to be sure, what is the version of XBMC you are using?
Can you goto System->Info within XBMC and report it back.
Its weird that the .bashrc change does not work. Can you post your .bashrc?
Can you also post the /etc/PolicyKit/PolicyKit.conf file? You should have added the user xbmc to that file.

[hrizzy]

Well, the issue with bashrc is pretty weird for me as well.
Its a usual bashrc from fresh install, I've put nothing there

XBMC ver:
~$ apt-cache policy xbmc
xbmc:
Installed: 1:9.11+svn28042-lucid1
Candidate: 1:9.11+svn28042-lucid1

Seems I didn't install policykit using how-to install xbmc on minimal ubuntu - its also deprecated. There is policykit-1 in place.
Should I?

So far I have edited
/var/lib/polkit-1/localauthority/50-local.d/custom-actions.pkla
and added

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

Well. After some research I've installed upower,
added org.freedesktop.upower* to /var/lib/polkit-1/localauthority/50-local.d/custom-actions.pkla

Still the same...

[vote4schow]

I am not sure if you have to install hald. I think it is gone from ubuntu 10.04 as well. I can double check when I get home if I have it installed.
Just to be sure, what is the version of XBMC you are using?
Can you goto System->Info within XBMC and report it back.
Its weird that the .bashrc change does not work. Can you post your .bashrc?
Can you also post the /etc/PolicyKit/PolicyKit.conf file? You should have added the user xbmc to that file.

Definitely install hal, acpi-support, and upower. After installing hal and rebooting for good measure, suspend/shutdown worked without having to do anything else. AFAIK, Lucid works just as well as Karmic for XBMC.

For the n00bs, run:
$ apt-get -y install upower acpi-support hal

[vikjon0]

Do I really need to install hald? I thought is has gone in latest ubuntu distro.

Well, the idea behind installing it is, wait for it, that it is not included in the distro.

AFAIK, Lucid works just as well as Karmic for XBMC.
$ apt-get -y install upower acpi-support hal

So far I have not seen a fix for usb disk mount. For me thats reason enough to wait.

[vote4schow]

So far I have not seen a fix for usb disk mount. For me thats reason enough to wait.

That's too bad. I run a diskless solution (iSCSI boot, files on NFS) so I didn't run into that problem.

[Hannes The Hun]

Well, the idea behind installing it is, wait for it, that it is not included in the distro.

does the installation of HAL prolong the boot process? also, as far as I understand it, suspend&shutdown will work afterwards from within XBMC but it won't help much with the autostart problem, right?

ah well... shoulda gone with karmic instead

[vikjon0]

it won't help much with the autostart problem, right?

It autostarts fine for me. I dont follow the "new" xbmcbuntu guide, perhaps thats makas a difference. I dont do any of the extra steps in the guide. Just install mini ubuntu with user xbmc and then install xbmc & live.

[einhänder]

want to tell you my solution/setup. i experienced the same/similar behaviour after switching to upower and banning hald from my system. at first i thought it was related to permissions or sth in that direction until i found out it is a hardware / maybe kernel driver issue in my case.
suspending the machine was working fine at the first try, but it didn't work for a second time. after waking the system from a successful first suspend i inspected the kernel logs and discovered the following:

Code:

[   83.609062] btusb_intr_complete: hci0 urb f4504900 failed to resubmit (1)
[   83.610054] btusb_bulk_complete: hci0 urb f4504300 failed to resubmit (1)
[   83.611052] btusb_bulk_complete: hci0 urb f4504080 failed to resubmit (1)

and

Code:

[   84.038707] pm_op(): usb_dev_suspend+0x0/0xf returns -16
[   84.038712] PM: Device usb3 failed to suspend: error -16

a quick research gave me a proper solution. i simply had to disable wakeup on the usb device/hub, IN MY CASE (you might have a problem with another device. inspect your logs. /var/log/pm-suspend.log is also helpful) the bluetooth dongle and enable it again on resume. thus i created a little script for pm-suspend (permissions set to 755):

Code:

cat /etc/pm/sleep.d/100WiiUse_WiiRemote
#!/bin/bash

. "${PM_FUNCTIONS}"

suspend_wiiuse-wiiremote()
{
    kill -ABRT $(pidof WiiUse_WiiRemote) && \
    sleep 1 && \
        echo disabled > /sys/bus/usb/devices/3-6/power/wakeup
}

resume_wiiuse-wiiremote()
{
        echo enabled > "/sys/bus/usb/devices/3-6/power/wakeup" && \
    /bin/su - xbmc -l -c "/usr/local/bin/WiiUse_WiiRemote >/dev/null 2>&1 &"
}

case $1 in
    suspend)
        suspend_wiiuse-wiiremote
        ;;

    resume)
        resume_wiiuse-wiiremote
        ;;

    *)
        echo "FAIL SHISSL SUSPEND"
    ;;
esac

the above gave me a working suspend/resume functionality.
below you are going to find my software/hardware setup and general config.

hardware:
- asus at3n7a-i
- moneual 312 case
- wiimote
- nothing unusal

software:
- gentoo linux
- 2.6.33-r2
- NO hald
- xorg-server-1.8.1-r1 with udev support/NO hal support
- udev-154
- udisks-1.0.1
- upower-0.9.4
- pm-utils-1.3.0-r3
- polkit-0.96-r1
- NO policykit package
- consolekit-0.4.1

config:
- NO custom rules in "/etc/polkit-1/*"
- autologin via /etc/inittab:

Code:

c6:2345:respawn:/usr/bin/openvt -fwec 7 -- /bin/su - xbmc -l -c "/bin/bash --login -c /usr/bin/startx >/dev/null 2>&1"

- added a global xsession called xbmc-gentoo, no .xinitrc or anything like that:

Code:

cat /etc/env.d/90xsession
XSESSION="/usr/local/bin/xbmc-gentoo"

Code:

cat /usr/local/bin/xbmc-gentoo
#!/bin/bash
/usr/bin/xsetroot -cursor /opt/.modResources/xcursor/emptyCursor.xbm /opt/.modResources/xcursor/emptyCursor.xbm &
/usr/local/bin/WiiUse_WiiRemote >/dev/null 2>&1 &
/usr/bin/xbmc-standalone

- no need to start xbmc with ck-launch-session, afaik startx/xinit should assign a session:

Code:

ck-list-sessions
Session1:
    unix-user = '1000'
    realname = '(null)'
    seat = 'Seat1'
    session-type = ''
    active = TRUE
    x11-display = ':0'
    x11-display-device = '/dev/tty6'
    display-device = '/dev/tty7'
    remote-host-name = ''
    is-local = TRUE
    on-since = '2010-05-19T12:52:27.770586Z'
    login-session-id = ''
Session2:
    unix-user = '1000'
    realname = '(null)'
    seat = 'Seat2'
    session-type = ''
    active = FALSE
    x11-display = ''
    x11-display-device = ''
    display-device = '/dev/ssh'
    remote-host-name = 'XXXXXXXXXXXXXX'
    is-local = FALSE
    on-since = '2010-05-19T12:54:21.266920Z'
    login-session-id = ''

that's it.