Trouble starting webex in F20

Fri May 2 19:13:17 UTC 2014

On 05/02/2014 01:19 PM, Chris Kottaridis wrote:
>
> On 05/02/2014 12:07 PM, Daniel J Walsh wrote:
>>
>> On 05/01/2014 06:26 PM, Chris Kottaridis wrote:
>>>
>>> On 05/01/2014 05:08 PM, Rick Stevens wrote:
>>>> On 05/01/2014 01:40 PM, Andrew Azores issued this missive:
>>>>> On 05/01/2014 04:27 PM, Chris Kottaridis wrote:
>>>>>>
>>>>>> On 05/01/2014 02:11 PM, Deepak Bhole wrote:
>>>>>>> * Chris Kottaridis <chriskot at quietwind.net> [2014-05-01 13:25]:
>>>>>>>> I have an F19 and an F20 host and when I try to start a webex
>>>>>>>> on the
>>>>>>>> F20 host it doesn't work right. It works fine on the F19 machine.
>>>>>>>>
>>>>>>>> The symptom is that when I start the webex in F20 it sends up a
>>>>>>>> message about wanting to run an applet and I tell it yes it's
>>>>>>>> OK to
>>>>>>>> run the applet. That doesn't come up on the F19 host. On the
>>>>>>>> F19 the
>>>>>>>> icedtea icon pops up for a short time and then I get connected. I
>>>>>>>> don't see the icedtea icon pop up in F20.
>>>>>>>>
>>>>>>>> I did notice that icedtea is at 1.5 in F20, but at 1.4 for F19 and
>>>>>>>> there is some policy control added in 1.5. I set the policy to
>>>>>>>> allow
>>>>>>>> all applets to do everything for the time being in the
>>>>>>>> .config/icedtea-web/security/java.policy file which the
>>>>>>>> icedtea-web
>>>>>>>> man page says is the default policy file.
>>>>>>>>
>>>>>>>> Any ideas on what the difference might be between F19 and F20
>>>>>>>> would
>>>>>>>> be appreciated or pointer to a different group that could help.
>>>>>>>>
>>>>>>>> Sorry that I only have rather high level usage info, but so far
>>>>>>>> other then this issue with starting a webex everything seems OK
>>>>>>>> that
>>>>>>>> I have tried so far.
>>>>>>>>
>>>>>>> Hi Chris,
>>>>>>>
>>>>>>> Is it possible for us to reproduce this? If so, what are the steps?
>>>>>> You'd need a webex account.
>>>>>
>>>>> Hmm, there's no way to reproduce it with the test meeting [0] ?
>>>>>
>>>>>>
>>>>>> After some more playing it seems the issue is when I try to share my
>>>>>> desktop it doesn't get shared in F20, but does in F19.
>>>>>
>>>>> So the Webex applet is successfully starting with both, then?
>>>>>
>>>>>>
>>>>>> That is what's so weird is it works like a champ in F19. I assume
>>>>>> there is just something missing, maybe something I need to
>>>>>> install or
>>>>>> some permission or configuration setting. I haven't found
>>>>>> anything in
>>>>>> any log files yet to help point to what the problem might be.
>>>>>>
>>>>>> When I connect to webex to start a session if I click on
>>>>>> Activities I
>>>>>> see a webex icon of a ball that is half green and half blue and the
>>>>>> name is "sun-applet-PluginMain" on the activites list. After I click
>>>>>> on share desktop I see a second icon like that which says Atasjni on
>>>>>> the F19, but still only have the one on F20. So, it seems some
>>>>>> app is
>>>>>> having trouble getting started when I click to share desktop. So,
>>>>>> far
>>>>>> I haven't found any complaint in any log file though.
>>>>>>
>>>>>> Thanks
>>>>>> Chris Kottaridis
>>>>>
>>>>> Do you have any log files at all to share? You can also try launching
>>>>> your browser from terminal (assuming this is starting through a
>>>>> browser
>>>>> at all), and capture the output with a redirect or tee there.
>>>>>
>>>>> Also, just a note that IcedTea-Web 1.5 is available for Fedora 19 as
>>>>> well. Although if you appear to be having problems after the 1.5
>>>>> update,
>>>>> I wouldn't recommend you update to it yet - not until we figure out
>>>>> what's going on here! With 1.5 on both Fedora 19 (native) and 20
>>>>> (VM),
>>>>> Webex works fine, but I haven't tried this 'share desktop'
>>>>> functionality.
>>>>>
>>>>> [0] http://www.webex.com/test-meeting.html
>>>>
>>>> Also check to see if there's perhaps a SELinux alert going along with
>>>> this. There may be changes to selinux configs that block sharing the
>>>> desktop.
>>>
>>> I don't know a lot about selinux, but I used the SELinux management
>>> tool to just disable SELinux.
>>>
>>>
>>>
>>> So, I assume SELinux is out of the picture for now.
>>>
>>> But, I think it is probably some local configuration issue like that.
>>>
>>> Thanks
>>> Chris Kottaridis
>>>> ----------------------------------------------------------------------
>>>> - Rick Stevens, Systems Engineer, AllDigital    ricks at alldigital.com -
>>>> - AIM/Skype: therps2        ICQ: 22643734            Yahoo: origrps2 -
>>>> -                                                                    -
>>>> -         We have enough youth, how about a fountain of SMART?       -
>>>> ----------------------------------------------------------------------
>>>
>>>
>>>
>> Putting SELinux into permissive mode, would have been plenty. 
>> Setting the machine to disabled will only take place on the next reboot.
>>
>> If SELinux is blocking the web browser from sharing desktop you could
>> turn off one of these booleans, which would probably fix your problem.
>>
>> unconfined_chrome_sandbox_transition --> on
>> unconfined_mozilla_plugin_transition --> on
>> setsebool -P unconfined_chrome_sandbox_transition 0
>> setsebool -P unconfined_mozilla_plugin_transition 0
>>
>> You would need to restart the browser.
>
> 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.
>
> Thanks
> Chris Kottaridis
>
>>
>>
>>
>
>
>
If it causes you any problems, please open a bug report or reach out to
the community.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.fedoraproject.org/pipermail/users/attachments/20140502/00906d74/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/png
Size: 18526 bytes
Desc: not available
URL: <http://lists.fedoraproject.org/pipermail/users/attachments/20140502/00906d74/attachment-0001.png>