Kodi Community Forum
XBMCbuntu / XBMCfreak - Accidentally logged into OpenBox - Printable Version

+- Kodi Community Forum (https://forum.kodi.tv)
+-- Forum: Support (https://forum.kodi.tv/forumdisplay.php?fid=33)
+--- Forum: General Support (https://forum.kodi.tv/forumdisplay.php?fid=111)
+---- Forum: Linux (https://forum.kodi.tv/forumdisplay.php?fid=52)
+---- Thread: XBMCbuntu / XBMCfreak - Accidentally logged into OpenBox (/showthread.php?tid=134483)



XBMCbuntu / XBMCfreak - Accidentally logged into OpenBox - himayv - 2012-06-21

So, I think I did something dumb and I'm not sure how to undo it:

I logged out of XBMC (I am running XBMCfreak / XBMCbuntu on my Acer Aspire Revo 1600), it gave three options, XBMC, XBMCbuntu, and OpenBox, I selected OpenBox.

That gives me a big grey screen and a mouse pointer, but nothing to do / click on.

I can hit Ctrl + F2 and get to a command prompt, but if I type "xbmc" at the command prompt, I get an error about being unable to load the video.

Since my last log in was to OpenBox, it now goes there every time I reboot the machine.

Help! How do I get back to logging in to XBMCbuntu or XBMC?

Thanks in advance!


RE: XBMCbuntu / XBMCfreak - Accidentally logged into OpenBox - lrusak - 2012-06-21

at command promt did you try "logout" or "exit" ?


XBMCbuntu / XBMCfreak - Accidentally logged into OpenBox - himayv - 2012-06-22

Thanks for the response! Yes, I did try both of those. Neither worked. When I logout, it takes me to a command prompt to login again (if I reboot from there, back to openbox)...if I type exit, same thing.

Thoughts? Thanks in advance!
Just fixed it! Right click, exit. Sorry for the silly question!


RE: XBMCbuntu / XBMCfreak - Accidentally logged into OpenBox - Fiery - 2012-06-22

Not really a Linux User, but try killall5, this should end the current session and get you back to the selection screen where you can then select Xbmc and have a working System again.


RE: XBMCbuntu / XBMCfreak - Accidentally logged into OpenBox - artrafael - 2012-06-22

Missed your edit to post #3 stating you'd fixed the problem.