<html>
<head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<br>
<div class="moz-cite-prefix">On 05/02/2014 12:07 PM, Daniel J Walsh
wrote:<br>
</div>
<blockquote cite="mid:5363D0EA.60805@redhat.com" type="cite">
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
<br>
<div class="moz-cite-prefix">On 05/01/2014 06:26 PM, Chris
Kottaridis wrote:<br>
</div>
<blockquote cite="mid:5362CA02.5000608@quietwind.net" type="cite">
<meta content="text/html; charset=UTF-8"
http-equiv="Content-Type">
<br>
<div class="moz-cite-prefix">On 05/01/2014 05:08 PM, Rick
Stevens wrote:<br>
</div>
<blockquote cite="mid:5362C5EB.8060708@alldigital.com"
type="cite">On 05/01/2014 01:40 PM, Andrew Azores issued this
missive: <br>
<blockquote type="cite">On 05/01/2014 04:27 PM, Chris
Kottaridis wrote: <br>
<blockquote type="cite"> <br>
On 05/01/2014 02:11 PM, Deepak Bhole wrote: <br>
<blockquote type="cite">* Chris Kottaridis <a
moz-do-not-send="true" class="moz-txt-link-rfc2396E"
href="mailto:chriskot@quietwind.net"><chriskot@quietwind.net></a>
[2014-05-01 13:25]: <br>
<blockquote type="cite">I have an F19 and an F20 host
and when I try to start a webex on the <br>
F20 host it doesn't work right. It works fine on the
F19 machine. <br>
<br>
The symptom is that when I start the webex in F20 it
sends up a <br>
message about wanting to run an applet and I tell it
yes it's OK to <br>
run the applet. That doesn't come up on the F19 host.
On the F19 the <br>
icedtea icon pops up for a short time and then I get
connected. I <br>
don't see the icedtea icon pop up in F20. <br>
<br>
I did notice that icedtea is at 1.5 in F20, but at 1.4
for F19 and <br>
there is some policy control added in 1.5. I set the
policy to allow <br>
all applets to do everything for the time being in the
<br>
.config/icedtea-web/security/java.policy file which
the icedtea-web <br>
man page says is the default policy file. <br>
<br>
Any ideas on what the difference might be between F19
and F20 would <br>
be appreciated or pointer to a different group that
could help. <br>
<br>
Sorry that I only have rather high level usage info,
but so far <br>
other then this issue with starting a webex everything
seems OK that <br>
I have tried so far. <br>
<br>
</blockquote>
Hi Chris, <br>
<br>
Is it possible for us to reproduce this? If so, what are
the steps? <br>
</blockquote>
You'd need a webex account. <br>
</blockquote>
<br>
Hmm, there's no way to reproduce it with the test meeting
[0] ? <br>
<br>
<blockquote type="cite"> <br>
After some more playing it seems the issue is when I try
to share my <br>
desktop it doesn't get shared in F20, but does in F19. <br>
</blockquote>
<br>
So the Webex applet is successfully starting with both,
then? <br>
<br>
<blockquote type="cite"> <br>
That is what's so weird is it works like a champ in F19. I
assume <br>
there is just something missing, maybe something I need to
install or <br>
some permission or configuration setting. I haven't found
anything in <br>
any log files yet to help point to what the problem might
be. <br>
<br>
When I connect to webex to start a session if I click on
Activities I <br>
see a webex icon of a ball that is half green and half
blue and the <br>
name is "sun-applet-PluginMain" on the activites list.
After I click <br>
on share desktop I see a second icon like that which says
Atasjni on <br>
the F19, but still only have the one on F20. So, it seems
some app is <br>
having trouble getting started when I click to share
desktop. So, far <br>
I haven't found any complaint in any log file though. <br>
<br>
Thanks <br>
Chris Kottaridis <br>
</blockquote>
<br>
Do you have any log files at all to share? You can also try
launching <br>
your browser from terminal (assuming this is starting
through a browser <br>
at all), and capture the output with a redirect or tee
there. <br>
<br>
Also, just a note that IcedTea-Web 1.5 is available for
Fedora 19 as <br>
well. Although if you appear to be having problems after the
1.5 update, <br>
I wouldn't recommend you update to it yet - not until we
figure out <br>
what's going on here! With 1.5 on both Fedora 19 (native)
and 20 (VM), <br>
Webex works fine, but I haven't tried this 'share desktop'
functionality. <br>
<br>
[0] <a moz-do-not-send="true" class="moz-txt-link-freetext"
href="http://www.webex.com/test-meeting.html">http://www.webex.com/test-meeting.html</a>
<br>
</blockquote>
<br>
Also check to see if there's perhaps a SELinux alert going
along with <br>
this. There may be changes to selinux configs that block
sharing the <br>
desktop. <br>
</blockquote>
<br>
I don't know a lot about selinux, but I used the SELinux
management tool to just disable SELinux.<br>
<br>
<img src="cid:part3.07060000.05000508@quietwind.net" alt=""><br>
<br>
So, I assume SELinux is out of the picture for now.<br>
<br>
But, I think it is probably some local configuration issue like
that.<br>
<br>
Thanks<br>
Chris Kottaridis<br>
<blockquote cite="mid:5362C5EB.8060708@alldigital.com"
type="cite">----------------------------------------------------------------------
<br>
- Rick Stevens, Systems Engineer, AllDigital <a
moz-do-not-send="true" class="moz-txt-link-abbreviated"
href="mailto:ricks@alldigital.com">ricks@alldigital.com</a>
- <br>
- AIM/Skype: therps2 ICQ: 22643734 Yahoo:
origrps2 - <br>
-
- <br>
- We have enough youth, how about a fountain of
SMART? - <br>
----------------------------------------------------------------------
<br>
</blockquote>
<br>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
</blockquote>
Putting SELinux into permissive mode, would have been plenty.
Setting the machine to disabled will only take place on the next
reboot.<br>
<br>
If SELinux is blocking the web browser from sharing desktop you
could turn off one of these booleans, which would probably fix
your problem.<br>
<br>
unconfined_chrome_sandbox_transition --> on<br>
unconfined_mozilla_plugin_transition --> on<br>
setsebool -P unconfined_chrome_sandbox_transition 0<br>
setsebool -P unconfined_mozilla_plugin_transition 0<br>
<br>
You would need to restart the browser.<br>
</blockquote>
<br>
I have rebooted many times after disabling SELinux, it was getting
in the way of other issues and so for the time being I just want to
get it out of the way. Thanks for the pointers though. Once I get
things right I'll re-enable it and make sure to make the changes you
recommend.<br>
<br>
Thanks<br>
Chris Kottaridis<br>
<br>
<blockquote cite="mid:5363D0EA.60805@redhat.com" type="cite"> <br>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
</blockquote>
<br>
</body>
</html>