Running Boxee and XBMC on a minimal Karmic install
#16
from what it sounds like to me, with my limited experience with linux, that i installed the first version of the xbmc installer script and some how it didn't configure my setup properly. That's why when i exited xbmc from the menu it took me to a command prompt rather than the window manager like it apparently did for prupert. Right now i'm in the middle of completely re-installing everything, including linux, and hopefully a clean install of everything will remedy the problem.

but thanks again prupert for your tireless effort,
d
Reply
#17
great news, i finally got it to work. Took me forever to correct the missing dependencies when installing boxee, but got it up and running none the less. Many thanks to prupert for his time and patience.

There is however one problem that i encountered installing the latest installer script that wasn't there with the original.

When I exit out of xbmc it no longer takes me to the command prompt as before, but takes me to what i assume is the window manager. What i'm looking at when i exit is a black screen with an X in the middle. I am able to move the X cursor around with my mouse, but after about five seconds or so it reboots back into xbmc. It does this no matter which option i choose from the shutdown menu(ie. exit, shutdown, restart). They all lead me back to the same screen, followed by a reboot back into xbmc. The irexec files also does not get called up when this is happening as well.

However when i changed this file:

/usr/local/bin/xbmc-session

to this:
Code:
!/bin/bash

trap "xbmc --standalone" SIGINT SIGHUP EXIT SIGTERM QUIT SIGSEGV
while true
do
#xbmc
#sleep 10
done

essentially commenting out the xbmc and sleep 10 from the script.

When i do this everything works perfectly. I get a window manager with an arrow rather than an X, im able to click and open a terminal, and most importantly both buttons call the things that they were programed to do(start xbmc and boxee). I'm assuming it has to be something in the new script that it is doing it, because it wasn't happening in the first version.

Now dont get me wrong, i'm extremely happy that i finally got this thing running right and I really appreciate the help immensely. However, i'd like to be able to shutdown the computer from xbmc rather than getting up and having to hold down the power button to get the damn thing to turn off.

I dont if you had this problem or not when you did your install prupert, but i figured i'd ask if you know anything since you've been the man so far.

Anyways, once again thanks for all the help and hope to hear from you soon,
D
Reply
#18
Ooh yeah, sorry about not warning you about the first part - where xbmc restarts if you exit it because of the xbmc-session script, I forgot about that. You've commented out exactly the part you needed to, so looks like you are becoming a linux guru yourself!!

As far as shutting down goes, for me, I simply choose shutdown xbmc from the xbmc power menu, which turns off the PC for me. Does that not work for you?

I know that some people with unusual hardware get problems shutting down, but it is just that their linux install needs to be configured correctly.

What PC are you using again? I'm using an Acer Revo 3610 and it worked out of the box.

Glad things are now working better for you, I knew we could you there in the end. Boxee and xbmc working together is so worth it.

My only complaint is that you can't shutdown the PC from boxee, it only has a suspend or logout option. So I have to logout of boxee, load xbmc and then exit - not the best solution....
Reply
#19
I wouldn't think my hardware would be that unusual. Im running a old p.o.s. p4 dell dimension, but hey it was free and it gets the job done(even the high def stuff).

When i choose anything from the shutdown menu(e.g. shutdown, restart, exit, or whatever), it just takes me to the window manger rather than turning the computer off. I'm guessing it has something to do with the script, because the first version of the script allowed me to to turn it off with no problem. I apologize, but i haven't had time to search around, i was too exited that i got it working and was messing with that last night(by the way, you're right it is awesome).

If you happen to know what's happening off hand or can point me where to go, that would be awesome, but don't worry yourself if you don't, you've already more than enough.

Once again I really appreciate all the help and you rock,
D
Reply
#20
Fraid I don't know anything off the top of my head, but I know that sometimes configuring shutdown on Linux can be odd on older machines, which sounds like what you are using. If you just do a search for "shutdown" on this Linux forum, you'll come across quite few posts with some suggestions. It is probably just a case of either installing a specific program or configuring a certain file.

Sorry I can't help more - but glad to have helped so far, it's what the Linux community is all about - helping each other and helping people to learn how to make the most of it. Linux is awesome and I am glad I have helped you learn a little bit about it.
Reply
#21
To all those with the shutdown problem:
i've looked and looked for a solution to the problem, but come up empty handed. There's just something about the last few lines of biptn's script that causes this problem. So until I or someone else can fix this(more likely the latter), i came up with a solution to shut down from within xbmc. It's not pretty but it works until something better comes along.

If you using prupert's irexec idea all you have to do is add a few more lines to get it to shut down and reboot from your remote. I dont know why i didn't think of this earlier

Code:
#shutdown
begin
remote = YOUR_LIRC_REMOTE_NAME
prog = irexec
button = WHAT_EVER_BUTTON_0
config = sudo /sbin/shutdown -P now
end

#reboot
begin
remote = YOUR_LIRC_REMOTE_NAME
prog = irexec
button = WHAT_EVER_BUTTON_8
config = sudo /sbin/reboot
end

hope this helps,
D
Reply
#22
BluechipJ Wrote:Sad

Thought it was an issue with using the XBMC Live LIVE 9.11 Camelot build so I installed a blank minimal Karmic on my Acer AspireRevo 1600.
(Used http://www.springydevelopment.co.uk/2009...mic-koala/)

XBMC runs, but won't suspend, but that's another issue (getting the ?1? and ?0? in the settings).

Main issue is trying to get Boxee running.

./run-desktop-boxee gives the following:
Code:
23/01/10 22:25:19#DEBUG#bxbgprocess.cpp:180(Start)#bg process initialized. [m_lazy=1] so m_maxNumOfWorkingThreads was set to [2]
23/01/10 22:25:19#DEBUG#bxbgprocess.cpp:180(Start)#bg process initialized. [m_lazy=1] so m_maxNumOfWorkingThreads was set to [1]
23/01/10 22:25:19#DEBUG#bxcurl.cpp:93(Initialize)#curl initialized. version <7.19.5>

Running Boxee test...
And the log goes to... /tmp/bluechip-boxee.log
commandline read: Boxee

   ~~~~~~~~~~~~~~~~~~~~~~~~~~| DirectFB 1.2.7 |~~~~~~~~~~~~~~~~~~~~~~~~~~
        (c) 2001-2008  The world wide DirectFB Open Source Community
        (c) 2000-2004  Convergence (integrated media) GmbH
      ----------------------------------------------------------------

(*) DirectFB/Core: Single Application Core. (2009-06-02 06:33)
(!) Direct/Util: opening '/dev/fb0' and '/dev/fb/0' failed
    --> No such file or directory
(!) DirectFB/FBDev: Error opening framebuffer device!
(!) DirectFB/FBDev: Use 'fbdev' option or set FRAMEBUFFER environment variable.
(!) DirectFB/Core: Could not initialize 'system_core' core!
    --> Initialization error!
ERROR: Unable to create application. Exiting
Boxee: asked to stop
Boxee: already stopped
./run-boxee-desktop: 38: /opt/boxee/give_me_my_mouse_back: not found

Bluechip-boxee.log contains:
Code:
17:22:06 T:3078915968 M:715182080 WARNING: Settings file does not exist, defaults assumed, path = special://masterprofile/profiles.xml
17:22:06 T:3078915968 M:715182080  NOTICE: -----------------------------------------------------------------------
17:22:06 T:3078915968 M:715182080  NOTICE: Starting XBMC, Platform: GNU/Linux.  Built on Jan  5 2010 (SVN:10063M)
17:22:06 T:3078915968 M:715182080  NOTICE: special://xbmc/ is mapped to: /opt/boxee
17:22:06 T:3078915968 M:715182080  NOTICE: special://masterprofile/ is mapped to: /home/bluechip/.boxee/UserData
17:22:06 T:3078915968 M:715182080  NOTICE: special://home/ is mapped to: /home/bluechip/.boxee/UserData
17:22:06 T:3078915968 M:715182080  NOTICE: special://temp/ is mapped to: /home/jeremy/.boxee/temp
17:22:06 T:3078915968 M:715182080  NOTICE: special://userhome/ is mapped to: /home/bluechip
17:22:06 T:3078915968 M:715182080  NOTICE: The executable running is: /opt/boxee/Boxee
17:22:06 T:3078915968 M:715182080  NOTICE: Log File is located: /tmp/bluechip-boxee.log
17:22:06 T:3078915968 M:715182080  NOTICE: -----------------------------------------------------------------------
17:22:06 T:3078915968 M:715182080    INFO: No settingsmap.xml to load (/opt/boxee/system/settingsmap.xml). Using default settings.
17:22:06 T:3078915968 M:715182080  NOTICE: Setup SDL
17:22:07 T:3078915968 M:715091968   FATAL: XBAppEx: Unable to initialize SDL: DirectFBCreate: Initialization error!
Apparently reinstalling the Nvidia drivers and setting glxinfo | grep direct is supposed to solve it but running glxinfo gives the following:
Code:
bluechip@media:/opt/boxee$ glxinfo
Error: unable to open display
Any help or info is appreciated.
BluechipJ,

I have exactly the same problem and symptoms you described, except I am using xbmc live. I've looked around the xbmc and boxee forums but I'm not seeing an obvious solution. Did you figure out a solution?

Thanks
Reply
#23
Have you checked you have the most recent version of the driver?

Try:
Code:
sudo apt-get update

then

Code:
apt-cache search  nvidia-glx

And then if there is a higher version available, then
Code:
sudo apt-get install

it.

Also, trying running glxinfo with sudo it might help maybe...

Finally, what version of Boxee are you installing, something from the repos, or one of the more recent Betas?
Reply
#24
Hello everyone. So far I'm running XBMC on a minimal Karmic install (32-bit). I was hoping to get Boxee running as well. I tried installing Boxee Beta 0.9.21.11497 and was getting a lot of issues with dependencies. Is there a Karmic repository that will install all necessary dependencies? Any help would be appreciated.
Reply
#25
adave Wrote:Hello everyone. So far I'm running XBMC on a minimal Karmic install (32-bit). I was hoping to get Boxee running as well. I tried installing Boxee Beta 0.9.21.11497 and was getting a lot of issues with dependencies. Is there a Karmic repository that will install all necessary dependencies? Any help would be appreciated.

I think they are just providing .debs with the Karmic release, and certainly with their most recent alphas and betas, they just provide .debs.

I think you can fix the dependency issue by first installing boxee with

Code:
sudo dpkg -i boxeee.deb

and then doing

Code:
sudo dpkg -f

iirc.
Reply
#26
Thanks for the reply prupert. I went ahead and followed the instructions you provided. After I try and start boxee (using ./boxee command in terminal), I get "Error: Unable to create application. Exiting). Here is the log file:

09:17:42 T:3077511056 M:1668702208 WARNING: Settings file does not exist, defaults assumed, path = special://masterprofile/profiles.xml
09:17:42 T:3077511056 M:1668702208 NOTICE: -----------------------------------------------------------------------
09:17:42 T:3077511056 M:1668702208 NOTICE: Starting XBMC, Platform: GNU/Linux. Built on Apr 14 2010 (SVN:11487M)
09:17:42 T:3077511056 M:1668702208 NOTICE: special://xbmc/ is mapped to: /opt/boxee
09:17:42 T:3077511056 M:1668702208 NOTICE: special://masterprofile/ is mapped to: /root/.boxee/UserData
09:17:42 T:3077511056 M:1668702208 NOTICE: special://home/ is mapped to: /root/.boxee/UserData
09:17:42 T:3077511056 M:1668702208 NOTICE: special://temp/ is mapped to: /root/.boxee/temp
09:17:42 T:3077511056 M:1668702208 NOTICE: special://userhome/ is mapped to: /root
09:17:42 T:3077511056 M:1668702208 NOTICE: The executable running is: /opt/boxee/Boxee
09:17:42 T:3077511056 M:1668702208 NOTICE: Log File is located: /tmp/root-boxee.log
09:17:42 T:3077511056 M:1668702208 NOTICE: -----------------------------------------------------------------------
09:17:42 T:3077511056 M:1668702208 INFO: No settingsmap.xml to load (/opt/boxee/system/settingsmap.xml). Using default settings.
09:17:42 T:3077511056 M:1668702208 NOTICE: Setup SDL
09:17:43 T:3077511056 M:1668448256 ERROR: GLX Error: No Display found
09:17:43 T:3077511056 M:1668448256 FATAL: CApplication::Create: Unable to init windowing system
Reply
#27
adave Wrote:09:17:43 T:3077511056 M:1668448256 ERROR: GLX Error: No Display found
09:17:43 T:3077511056 M:1668448256 FATAL: CApplication::Create: Unable to init windowing system

This is your problem, it is telling you that Boxee couldn't find a Display to use thus it exits.

Also this is worrying:
adave Wrote:09:17:42 T:3077511056 M:1668702208 NOTICE: special://masterprofile/ is mapped to: /root/.boxee/UserData
09:17:42 T:3077511056 M:1668702208 NOTICE: special://home/ is mapped to: /root/.boxee/UserData
09:17:42 T:3077511056 M:1668702208 NOTICE: special://temp/ is mapped to: /root/.boxee/temp
09:17:42 T:3077511056 M:1668702208 NOTICE: special://userhome/ is mapped to: /root

This means you are running Boxee as the root user, which isn't recommended.

I am thus guessing that it is a permissions problem. The user that is running Boxee doesn't have the rights to access the display, since your windows manager is running under a different user...

How exactly are you running Boxee, what command / script are you using to start it?
Reply
#28
I was trying to launch Boxee directly from terminal logged in as root using the "./boxee" command. I'm still a linux noob so trying to figure out how to do everything from command line and terminal. Is this the correct way of launching boxee?
Reply
#29
Do you have a Windows Manager installed?

If you have just installed a Minimal Install of Ubuntu, then although you get a terminal on screen when it boots up, it has no way of showing any Windows or graphics - thus Boxee will fail if you try and run it.

If you successfully installed a Windows manager, as I had talked a but about on the first page of this thread (the links I posted give more detail on doing this), then when your computer starts, it should boot up straight into XBMC. Is this what happens on your computer?
Reply
#30
Yes. Right now my machine boots straight into XBMC. I used Team XCI's XBMC script (https://sourceforge.net/apps/phpbb/xci/v...hp?f=2&t=3). So I'm assuming this script has installed a Windows Manager for me.
Reply

Logout Mark Read Team Forum Stats Members Help
Running Boxee and XBMC on a minimal Karmic install0