[fritsch]

We currently PR the missing mesa patch (crash on stop) into Ubuntu itself. We want to ship xbmcbuntu with "standard ubuntu packages" and only add our xbmc ppa. Kernel 3.15 will have all the patches and can easily be installed via ubuntu mainline. So stay tuned.

Oibaf (fabio, wsnipex and me worked with him at the vdpau beginnings) builds latest and greatest, which does not have to be stable or working at all, depending on upstream - so I cannot suggest it.

[abudabi]

My openssl doesn't want to upgrade past 1.0.1f. "sudo apt-get install --only-upgrade openssl" says it's on the latest version. Anyone else experiencing this?


2nd issue
So to get around the heartbleed bug I thought I'd add a ppa from here : https://launchpad.net/~george-edison55/+...tbleed-fix
but the add-apt command is not there.

Is this normally the case with the xbmcbuntu iso as I've normally just ran the std ubuntu iso with xbmc on top of that and never had this issue before.

[wsnipex]

who told you that trusty's openssl is still vulnerable to the heartbleed bug when you are fully updated?
Those security issues are usually fixed with backported patches instead of releasing a new version.

[nickr]

There is no such command as add-apt. It is add-apt-repository and it is in the package python-software-properties.

---

Having said that, 1.0.1f has a heartbleed patch, read the changelog

http://changelogs.ubuntu.com/changelogs/.../changelog

openssl (1.0.1f-1ubuntu2) trusty; urgency=medium

* SECURITY UPDATE: side-channel attack on Montgomery ladder implementation
- debian/patches/CVE-2014-0076.patch: add and use constant time swap in
crypto/bn/bn.h, crypto/bn/bn_lib.c, crypto/ec/ec2_mult.c,
util/libeay.num.
- CVE-2014-0076
* SECURITY UPDATE: memory disclosure in TLS heartbeat extension
- debian/patches/CVE-2014-0160.patch: use correct lengths in
ssl/d1_both.c, ssl/t1_lib.c.
- CVE-2014-0160

[Kib]

I think he didn't notice they numbered from 1.0.1f-ubuntu1 to 1.0.1f-ubuntu2.
It has also been backported to all still supported ubuntu versions, but usually under a different version number, (eg on saucy it is 1.0.1e-3ubuntu1.2)

[abudabi]

Sorry guys.. everywhere I read said that you need revision g built after 7 April. When I did "openssl version" I get : OpenSSL 1.0.1f 6 Jan 2014 so I took that as an indication that I'm still vulnerable.

@nickr
Thanks for the changelog link. Checked now and I do in fact have the ubuntu2 one installed that has the patch already.

Yeah I didn't type out the whole command when I made my post. sorry man. I definitely don't have any add-apt* commands (tried the tab autocomplete and nothing came up). And I do have the python package installed?

dpkg --list | grep python-software
ii python-software-properties 0.92.35 all manage the repositories that you install software from

[wsnipex]

it moved to software-properties-common

[abudabi]

Thank you sir.. added that package and I now have the add-apt-repository command

Cheers!

[P-I H]

I have some problems with signalling between the receiver and the PC. Sometimes when I switch to a Dolby Digital or DTS audio stream there is no sound.
However PCM and HD streams are always working.
In the attached log, I have paused the video for about 10 minutes and when I start the video again there is no sound. This happened at the time stamp 18:11:20.
If I stop and start XBMC, I get the sound back sometimes. If I switch the receiver off and on, I get sound back in most cases.
http://paste.ubuntu.com/7256723/
http://paste.ubuntu.com/7256756/
http://paste.ubuntu.com/7256776/
http://paste.ubuntu.com/7256778/
http://paste.ubuntu.com/7256782/

[myle]

I have made the jump from xp to Xbmcbuntu

After watching my first movie them it stop. I sour the blue screen with the buntu screen for about a min them it wenr back to xbmc

Also what be cool coming from windows to Xbmcbuntu some where in xbmc where u can set up the gateway mak and ip and if its a dhcp

[fritsch]

@myle: Read the first post and provide what it asks for.

[phear]

Just a quick post to say thanks. Have been using this for the past week.
OSS works great.

[wsnipex]

for AMD users with the crash on stop issue: http://forum.xbmc.org/showthread.php?tid...pid1683472

[fission]

I've been reading most of this thread and have lurked around here for a while trying to figure things out. I understand the Mesa patch most likely won't be included in the next update until after Trusty release. This is fine. I can wait or I can use the link above.

Like Arkim on the previous page I'm using a home built amd e-350 build. Last year I used a guide made by fritsch (I think) to get xbmc working with xvba on this platform. I understand since then AMD has released updates that allow us to utilize vdpau which hopefully makes everything a lot smoother on the developers side and that this has since been integrated into xbmcbuntu and probably xbmc in general.

I was all set to install but got a little confused on the last page during the discussion between waiting for the 3.14 (or 3.15 kernel) and various improvements that seem will come along with it like 24p and 23.976/23.8.

The majority of my media is 720p/1080p and has been working fine with XBMC I'm running now. Are there known things not working (see above) that will affect me at this point. Is it better to wait? Or will I be able to get hardware decoding and have things generally work. I also read through this guide (http://forum.xbmc.org/showthread.php?tid=174854) which seems to indicate everything is working as it should.

Basically, just trying to figure out if I should hold off on installing on this hardware due to missing things on AMD's end or if everything is working as expected. I'm not afraid of getting my hands dirty and am anxious to get a hold of all the improvements in Gotham and all the other fixes that I'm certain have come with the open source implementation of the amd driver and kernel fixes since 12.04.

[fritsch]

I have another idea for you: Test one of those: http://snapshots.openelec.tv from an USB stick. Here you see how far AMD with vdpau is currently.

Wait perhaps some days until new images are available, cause I pushed some other code some hours back.