Raspbmc’s RC5 Not So Smooth Update

Raspbmc logoSo, Raspbmc‘s RC5 update was rolled out and seeing as how I have automatic updating turned on, my Raspbmc got the update. But…things didn’t go as smoothly as expected which sent my Raspbmc installation into an infinite loop with messages stating that XBMC was 100% downloaded, and that I should just “relax” while it completed. Or something.

Well, 10 minutes of relaxing was more than enough. It was time to fix it.

I ssh’d over to my pi installation and looked in /var/log/messages.

Voila. Look at that error:

Oct  3 21:58:08 raspbmc xbmc: /home/pi/.xbmc-current/xbmc-bin/lib/xbmc/xbmc.bin: error while loading shared libraries: libtag.so.1: cannot open shared object file: No such file or directory

Upon further investigation (and Googling) and finding that other people had the same problem with the same error, adding the following symlink resolved the issue:

cd /lib
sudo ln /opt/xbmc-bcm/xbmc-bin/lib/xbmc/system/libshairport.so.0 .
sudo ln -s /opt/xbmc-bcm/xbmc-bin/lib/xbmc/system/libtag.so.1 .

Once done, reboot and you should be good.

RC5 has a whole bunch of new fixes and features. I’ll get into that tomorrow. No, Friday. No wait, I have a thing on Friday. Ok ok, I’ll talk about all the new features in Raspbmc RC5 next week.


Update: Yet another update over at raspbmc. It’s still RC5, and the update appears to still be giving some people headaches by the looks of some of the comments over there. For myself it took 2 reboots/auto updates before XBMC would download/extract/install and boot properly. The update hung for about 30 minutes, but another reboot re-initialized the raspbmc installation process and XBMC started as it should. Now the test: does it work as expected?

More soon.

Update 2: I let Auto Update do its thing on October 20 and everything went smoothly. As mentioned over here the XBMC Android remote may not work, which appears to be the case. Mine kind of half works now. No big deal as I suspect it’ll catch up eventually (remember, this stuff is all still fairly new!) My regular TV remote still works.

Update 3: Took Jarno’s suggestion and tried Yatse Widget aka XBMC remote for Android and was pleasantly surprised by it. Yatse is much more complete than the “official” XBMC Android remote and played very nicely with OpenELEC on the Raspberry Pi.



3 comments on “Raspbmc’s RC5 Not So Smooth Update

  1. Stephan Raue says:

    you can always try OpenELEC (http://www.openelec.tv), the builds are updated regulary, all of the new and fixed functions in Raspbmc RC5 we have included since weeks and the updates are more stable. See also http://wiki.openelec.tv/index.php?title=Installing_OpenELEC_on_Raspberry_Pi and http://wiki.openelec.tv/index.php?title=Updating_OpenELEC

  2. mike o says:

    @Stephan Raue
    Thanks Stephan! I’ve actually got an OpenELEC image ready to go on my 2nd SD card and have been sort of comparing the two. I’ll be swapping it back in again now that more advances have been made.

  3. Jarno says:


    If you still have issues with your Android XBMC remote you can use another Android remote called Yatse. It works perfectly for me and I’ve been using it since the last update.
    Jarno´s last blog post ..Lördagslåten vecka 45

Leave a Reply