[ruuk]

Hi Ruuk, thanks for the updates.

I'm getting a window popup each time I restart XBMC before starting Forum Browser saying "enter password to unlock the encrpted keyring"
see Picture
and Log
I think it appeared at V2.1.46. On first press of V2.1.46 from memory It asked me to create a password and confirm password then it went away, but it keeps popping up on each reboot while both V2.1.47 & V2.1.48 are installed

I'm running XBMCbuntu V12.2, Aeon Nox skin, V2.1.48 of Forum Browser.

I like the Youtube addition, you have made a good job of it, but for a long while now, I think I mentioned it that my Youtube links via Forum Browser wont play.
I added "RomanAtwood" channel (Comedy/Pranks) and played a video located at RomanAtwoods original pranks/Epic Purse Prank!!/first video link. FORUMBROWSER: Video ID: xhAcq9yB1fQ but as expected it locked up XBMC, giving me the only option to hard boot. The stand alone Youtube addon plays this video ok, but as I say it's on all links in Forum Browser pointing to Youtube videos. The above log also shows me playing said video right at the end of the log, but I don't think it will help you.

Since there is no keyring on your system, it uses the internal keyring. This requires unlocking for each new session of XBMC (it only asks on startup because you must have some FB notifications going). If you want to get around this, run the 'Password Storage' addon from the programs menu. Click 'Keyring Options' and then you can store the key to disk. This will actually store a random key to disk and encrypt the passwords with that. This is less secure but you won't be asked for a password anymore.

As far as the crashing issue, I played the same video fine. I have the same YouTube version as you and the same CommonFunctions version, so I don't know what's up.

Could it possibly be a low memory issue? Since it plays fine in YouTube normally, the only difference I see is that Forum Browser is also open, therefore more memory is in use. Obviously if you have 8gigs of ram that's not the issue

I'll have to try XBMCbuntu out and see if I get the same problem. I can add that to my list of testing systems which now also includes virtual machines with OSX and OpenElec
Crashes are the worst because there is generally nothing in the log to show what happened

---

By the way, I was already pretty sure you tested this, because of this data in my google API console

3.67k 96.02% US
152 3.98% GB <-- hasselhof