[olympia]

I have installed XBMC on ubuntu server with only xorg installed.
I start XBMC by running xinit, than from the console: xbmc

When I try to shut down/ suspend the computer I get the following message:
"Is another session active, perhaps over ssh?"

and XBMC stays alive. Could you please help me out on that?

Thanks

[harryzimm]

try starting "xbmc --standalone"

or put this in advancedsettings.xml

<systempowermanagement>true</systempowermanagement>

cheers.

[topfs2]

We have actually moved to completely rely on SystemPowermanagement in svn version.

The error you recieve is because only admins can shutdown a computer that have more than one active session / active tty. This is because is the server nature of linux so person A cant turn of the computer when person B is active.

So if you have ssh connected to the HTPC then exit.

If you dont, then your script that launches XBMC isnt good, it spawns another session (this is not the right word for terminal but I cant recall the right one) so if you post that script Im sure a linux guru could help you.

Cheers,
Tobias

[olympia]

@harryzimm
Thank you the suggestion, but it didn't worked

@topfs2
Indeed you are right. I tested with root and it worked than. But as far I understand XBMC shouldn't run under root priviligies.

To start XBMC I only add "xbmc" to .xinitrc in the home directory. In that way, by running xinit, it starts XBMC automatically, but yes, it opens an other session for X.
(if I run xinit with sudo, than shutdown/suspend works)

So is there anybody know, how to avoid this?

Thank you!

[topfs2]

Im not that great on these things but what works for me is
sudo apt-get install gdm fluxbox

And add xbmc --standalone &
to .fluxbox/startup
(after you have succesfully run fluxbox once)

Then you need to alter gdm to autoboot fluxbox
Should be option session and choose fluxbox and tell it to be default, should be asked about it.
Then start gdmsetup and choose automatic boot and select your user

Cheers,
Tobias

[owagner]

So is there anybody know, how to avoid this?

After a painful excurse into the dbus/hal documentation I resorted to the following kludge (formerly presented here on the forum), which wfm on Ubuntu 8.10:

-- edit /etc/PolicyKit/PolicyKit.conf
-- find the line <match user="root">
-- modify it to read <match user="root|youruserwhichrunsxbmc">

Best Regards,
Olli

[olympia]

After a painful excurse into the dbus/hal documentation I resorted to the following kludge (formerly presented here on the forum), which wfm on Ubuntu 8.10:

-- edit /etc/PolicyKit/PolicyKit.conf
-- find the line <match user="root">
-- modify it to read <match user="root|youruserwhichrunsxbmc">

Best Regards,
Olli

Big thanks owagner! That's made it!
Based on this, I check this file in XBMC Live, if it is solved in the same way, and yes. So I copied PolicyKit.conf from XBMC live to my XBMC Linux installation and it did the trick! Thank you again!