Login at Kodi Home

wodska · (This post was last modified: 2013-01-24, 20:06 by artrafael.)

Hi all!

I'm relatively new to Linux/XBMCbuntu so I have a few (probably small) issues. I hope someone here can help me out here, I'm guessing a lot of people must having the same problem?

A month ago I bought myself an Acer Aspire, hooked it on my TV and I installed XBMCbuntu on it. Had a few troubles installing the Frodo RC3 but now it all works like a charm. Bought myself an MCE remote which worked perfectly out of the box. Never had a better media center untill now!

But there is an issue, when I try to power off XBMCbuntu, I see the screen going to the XBMC-logo and the dots moving from left to right. Then all of a sudden this screen freezes. The dots aren't moving and unless I hold my on/off button, XBMCbuntu won't shutdown. Strange thing is: reboot works perfect. I've been searching the web for a while now and I don't seem to find anything that works to fix this issue?

I do have to say, when trying to instal XBMCbuntu I only got a blank screen with a blinking underscore on the top-left corner when selecting 'install xbmcbuntu'. So I set ACPI=off before launching the installer which did the trick. After installing, however, XBMCbuntu wouldn't boot, I only saw a blank screen again. So I edited the GRUB config file (/etc/default/grub) and changed the GRUB_CMDLINE_LINUX_DEFAULT line by adding acpi=off at the end of the line. By that XBMCbuntu boots just fine. Because ACPI (advanced configuration and power interface) is set to off in the GRUB file, this might the reason why he wouldn't shut down.

Anyone has an idea what to do to fix this issue? I've tried to get a log file, but with the 'debug logging' option enabled in XBMC, it looks like it overwrites it's log file everytime when he boots, which makes it difficult to find what is exactly going wrong.

Thanks a lot in advance!

*edit: typo

wodska · 2013-01-22, 08:42

Anyone has an idea? There must at least be another way to get a log file to see where the system 'crashes' on the shutdown?

artrafael · 2013-01-22, 09:15

Look in the xbmc.old.log file, which is the xbmc.log from the previous session.

You might also try the following test: Switch to the XBMCbuntu desktop and see if you can shutdown successfully from there. On the XBMC home page, click the power icon on the lower-left of the display (or press keyboard "s"), select Exit and, when the log-in screen is displayed, enter your username and password and, on the third input field, open the drop-down menu and select XBMCbuntu (instead of XBMC). Click Login and your system should boot to the XBMCbuntu desktop. Wait a few minutes and then select the Shutdown icon on the lower-right of the display and select Shutdown. See if the system is able to shutdown normally this way.

wodska · (This post was last modified: 2013-01-22, 22:46 by wodska.)

(2013-01-22, 09:15)artrafael Wrote: Look in the xbmc.old.log file, which is the xbmc.log from the previous session.

Thanks for the tip, now I can finally see the logging of the shutdown. These are the latest lines I get, maybe someone can see what's going wrong at the shutdown? The multiple 'WARNING' lines don't make any sense to me, but must be the reason why it hangs...?

Code:
03:50 T:3038264000  NOTICE: destroy

03:50 T:3038264000 WARNING: Attempted to remove window 10015 from the window manager when it didn't exist

03:50 T:3038264000 WARNING: Attempted to remove window 10016 from the window manager when it didn't exist

03:50 T:3038264000 WARNING: Attempted to remove window 10017 from the window manager when it didn't exist

03:50 T:3038264000 WARNING: Attempted to remove window 10018 from the window manager when it didn't exist

03:50 T:3038264000 WARNING: Attempted to remove window 10019 from the window manager when it didn't exist

03:50 T:3038264000 WARNING: Attempted to remove window 10021 from the window manager when it didn't exist

03:50 T:3038264000 WARNING: Attempted to remove window 10107 from the window manager when it didn't exist

03:50 T:3038264000 WARNING: Attempted to remove window 10115 from the window manager when it didn't exist

03:50 T:3038264000 WARNING: Attempted to remove window 10104 from the window manager when it didn't exist

03:50 T:3038264000  NOTICE: closing down remote control service

03:50 T:3038264000  NOTICE: unload sections

03:50 T:3038264000   DEBUG: CAnnouncementManager - Announcement: OnClear from xbmc

03:50 T:3038264000   DEBUG: Previous line repeats 1 times.

03:50 T:3038264000   DEBUG: object 0 --> 0 instances

03:50 T:3038264000   DEBUG: object 1 --> 0 instances

03:50 T:3038264000   DEBUG: object 2 --> 0 instances

03:50 T:3038264000   DEBUG: object 3 --> 0 instances

03:50 T:3038264000   DEBUG: object 4 --> 0 instances

03:50 T:3038264000   DEBUG: object 5 --> 0 instances

03:50 T:3038264000   DEBUG: object 6 --> 0 instances

03:50 T:3038264000   DEBUG: object 7 --> 0 instances

03:50 T:3038264000   DEBUG: object 8 --> 0 instances

03:50 T:3038264000   DEBUG: object 9 --> 0 instances

03:50 T:3038264000  NOTICE: application stopped...

03:50 T:3038264000   DEBUG: PVRManager - destroyed

03:50 T:3038264000   DEBUG: CAnnouncementManager - Announcement: OnClear from xbmc

03:50 T:3038264000   DEBUG: Previous line repeats 1 times.

03:50 T:3038264000   DEBUG: SECTION:UnloadDll(libcurl-gnutls.so.4)

03:50 T:3038264000   DEBUG: Unloading: libcurl-gnutls.so.4

03:50 T:3038264000   DEBUG: LinuxRendererGL: Cleaning up GL resources

03:50 T:3038264000   DEBUG: SECTION:UnloadAll(DLL: special://xbmcbin/system/libcpluff-i486-linux.so)

03:50 T:3038264000   DEBUG: Unloading: libcpluff-i486-linux.so

03:50 T:3038264000   DEBUG: SECTION:UnloadAll(DLL: special://xbmcbin/system/players/dvdplayer/avutil-51-i486-linux.so)

03:50 T:3038264000   DEBUG: Unloading: avutil-51-i486-linux.so

03:50 T:3038264000   DEBUG: SECTION:UnloadAll(DLL: special://xbmcbin/system/players/dvdplayer/swscale-2-i486-linux.so)

03:50 T:3038264000   DEBUG: Unloading: swscale-2-i486-linux.so

03:50 T:3038264000   DEBUG: SECTION:UnloadAll(DLL: special://xbmcbin/system/ImageLib-i486-linux.so)

03:50 T:3038264000   DEBUG: Unloading: ImageLib-i486-linux.so

Quote:You might also try the following test: Switch to the XBMCbuntu desktop and see if you can shutdown successfully from there. On the XBMC home page, click the power icon on the lower-left of the display (or press keyboard "s"), select Exit and, when the log-in screen is displayed, enter your username and password and, on the third input field, open the drop-down menu and select XBMCbuntu (instead of XBMC). Click Login and your system should boot to the XBMCbuntu desktop. Wait a few minutes and then select the Shutdown icon on the lower-right of the display and select Shutdown. See if the system is able to shutdown normally this way.

When I do this, it shows more information. I got about the same result but with the difference that I now see text on the screen which freezes (the '...' are things I left out, because XBMCbuntu stopped it successfully):

Code:
....[ ok ]

....[ ok ]

The system is going down for halt NOW!

acpid: exiting

* stopping remote control daemon(s): LIRC [ fail ] 

Rather then invoking init scripts through /etc/init.d, use the service (8) utility, e.g. service K2smbd stop initctl:Unknown job: K20smbd

Since the script you are attempting to invoke as been converted to an Upstart job, you may asl use the stop (8) utility, e.g. stop K20smbd

* All processes ended within 1 seconds.... [ ok ]

rpcbind: rpcbind terminating on signal. Restart with "rpcbind -w" 

* deactivating swap [ ok ]

umount: /run/lock: not mounted

umount: /run/shm: not mounted

mount: / is busy

*will now halt

[ 1098.697003 ] System halted.

Now I'm not sure if umount is the problem with "mount: / is busy" or the fail message i get by "Stopping remote control daemon(s): LIRC"...

Anyone have a clue about this?

wodska · 2013-01-24, 19:51

I have finally figured it out, hope it will help others as well:
Like I said in my first post, I had to set ACPI=off in the GRUB config file, in order to make my XMBCbuntu boot. And because ACPI is necessary so XMBCbuntu could work with hardware, XMBCbuntu wasn't able to shut down the system. So I've changed ACPI=off to PCI=NOACPI in the GRUB config file. Now my XMBCbuntu boots AND shutsdown without problem. Looks like the logs haven't anything to do with it...

Found the information here: http://ubuntuforums.org/archive/index.ph...31780.html
There are also other arguments mentioned in that post to make ACPI work correctly, so be sure to check it out if you have troubles with ACPI!

artrafael · 2013-01-24, 20:04

Glad you were able to solve this and thanks for sharing your solution. I'm sure this will come in handy for someone else who may encounter the same problem in the future. I've moved this thread to the "Linux and Live support" forum and tweaked the title a bit so it will more likely pop-up in searches.

Isulaiman · 2013-02-26, 19:30

Hi
I'm really new to Linux. I'm having the very same problem as you with shutting down my xbmc. Shutting down from xbmcbuntu seems to be no problem though!

Again a newbie, so pardon my ignorance, but I don't get the GRUB editing you did.
I went into my /etc/default/grub and there was no ACPI after GRUB_CMDLINE_LINUX_DEFAULT .
I don't know if it makes any difference but I'm using a Zotac zbox.
Any help/guidance would've greatly appreciated.

Thanks