Re: Realplayer in Suse 10 error

Hi again,

Marc van Munnen wrote:
> Hi,
>
> Months ago I updated my Suse 9.2 to a kind of Open Suse 10.0 (the one 
> that was included with Linux Magazine some while ago). Now I notice 
> that RealPlay(er) does not work anymore. From the command line with 
> "realplay" it says:
> /usr/bin/realplay: line 70: /usr/bin/aoss: Toegang geweigerd
> Or, in plain English: No Access
> From KDE it fires realplay-kde wich does not show anything usefull. 
> But from the command line it says the same.
>
> So, I downloaded the latest and greatest RealPlayer 10, de-installed 
> what I had and installed what I downloaded. Then Realplay worked like 
> a charm. BUT. But amaroK did not anymore. It needed  rvplayer that my 
> downloaded version of Realplayer did not carry with it, as did the 
> version that came with Suse. I tried to find a decent copy of rvplayer 
> but ended up with al kind of broken dependencies.
>
> So I deinstalled my downloaded RealPlayer 10 and re-installed what 
> came with Suse and now I'm stuck again, because this version keeps 
> giving this annoying message:
> /usr/bin/realplay: line 70: /usr/bin/aoss: Toegang geweigerd.
>
> As a result Mozilla shows uncharacteristic behaviour by disappearing 
> in a whiff when I klick on some links (I assume).
>
> I hope someone can shed some light on my dark path.
>
> Thanks anyway for reading.
> Marc
>
I have solved this problem. It all has to do with settings in AppArmor 
that is enabled by default in Suse 10. Anyone interested can get the 
details.

Marc