Crashes back to command line as soon as it loads

[flammenwurfer]

I've just installed the new Beta on my boxee box which is running Ubuntu Karmic. I have it set up to run just boxee when I startx. No de or wm loads, just boxee. My .xinitrc file in my home directory contains only "/opt/boxee/run-boxee-desktop". When I execute startx it will get to the main Boxee screen but then it crashes and says

Segmentation Fault
/opt/boxee/run-boxee-desktop: 38: /opt/boxee/give_me_my_mouse_back: not found

I only have a keyboard connected to the box and an ir receiver that I use a windows media center remote with. With the alpha it worked fine with this setup.

I've also tried changing my .xinitrc to contain "/opt/boxee/Boxee" as well. When I do that it still crashes, but I don't get the the give_me_my_mouse_back part. It just crashes and says Segmentation Fault.

[flammenwurfer]

Really? nobody? Interesting. I would really like to use the new Beta but I can't do that if it crashes 5 seconds after I launch it every time.

Is there somewhere else I can go to ask where I might get more resonse?

[judgeschambers]

The forums are hot right now with good, bad and questions in general.

Agentlame is our resident Linux guru. Hopefully he cruises by later tonight.
This is beta, give it time. :D

[cogadh]

The lack of response probably has to do with the rather unique way you are using Boxee. Have you tried just using it "normally" (i.e. within a window manager) to see if it has the same issue?

[agentlame]

"give_me_my_mouse_back" is unrelated to your issue.

Did you make sure to delete your alpha profile, first?


mv ~/.boxee ~/.boxee.alpha


I also run Boxee in just a simple x session. It should work fine.

[flammenwurfer]

Yes, I deleted my alpha profile. Deleted the whole .boxee folder. I've installed the latest nvidia drivers. I have not tried using it in a window manager or anything. The box I have it on has a sole purpose of running boxee so I don't normally have a keyboard and mouse hooked up to it. I will have to scrounge up a keyboard and mouse to test with.

PS. Thanks everybody who has responded. I wasn't trying to be bitchy or anything, just wanting to figure this out and wondered if I was asking in the wrong place.

[flammenwurfer]

Ok, I tried it from icewm and it's doing the same thing. I did notice that if I delete my .boxee folder and start Boxee it will run fine without crashing up until I actually login. It will let me go to and view the network options, control options etc... I can stay in this area as long as I want without it crashing. But once I enter my ID and password and it starts loading the actual boxee interface it will crash within 5 seconds.

From this terminal emulator it's showing three error messages. 2 about "bxbgprocess" and 1 regarding "curl". I'll see if I can get the actual messages themselves and paste them here.

[agentlame]

Can you post the contents of you ~/.boxee directory before and after trying to login?


ls -lR ~/.boxee > ~/stdout.txt #most terminals will not have enough buffer.


Also you:


cat ~/.boxee/UserData/profiles.xml

Both before and after.

Lastly:


cat /tmp/$USER-boxee.log


If you can pastebin all of that. The forums suck for large amounts of text.

[flammenwurfer]

Before: http://pastebin.ca/1717866

After: http://pastebin.ca/1717869

[flammenwurfer]

I stayed up late last night and did a fresh intall of xubuntu karmic. The install finished while I was sleeping and I installed boxee this morning. I didn't play with it very long, but it didn't crash while I was using it for a couple minutes. That's way longer than before!

However, it was SUPER slow. When I push a button to navigate or type or anything it takes it 10 seconds to actually move the cursor after I've pushed a button. I don't think I have restricted drivers enabled yet, could that me causing the sever sluggishness?