Red Hat Bugzilla – Bug 982457
kernel-3.9.9-301.fc19 and adobe flash-plugin do not cooperate
Last modified: 2013-07-19 00:05:55 EDT
Description of problem:
When I use this kernel, I am unable to view flash videos from youtube, news sites, etc. The video plays, without sound and the video stops playing after about 10 seconds, just locking up, with the last image frozen. When one closes the tab in firefox that the video is frozen in, firefox freezes for a good minute or three, before responding again. A number of AVC denials appear, asking me to restorecon on about 5 files, but this does not resolve the issue. Not even setsebool unconfined_mozilla_plugin_transition 0 works. Not even running selinux in permissive mode will work. It does not appear to be selinux, but the kernel. When I reboot and use 3.9.5-301.fc19, everything works fine.
Version-Release number of selected component (if applicable):
Run the system using the aforementioned kernel and navigate to youtube and play a video. Try it on cbc.ca/thenational/watch: same result. Video freezes, during the advertisement, even!
Steps to Reproduce:
Well, I am mystified! I just rebooted, yet again, back into the 'defective' kernel, and now it actually works. I have had this problem for the last 2 days, but suddenly, it appears to be gone, with this kernel! There were some updates earlier... perhaps there was something among them?
I spoke too soon. It's back! The problem still exists.
I am beginning to suspect that this is the same problem I had in fedora 17 or fedora 18. I had been in discussion with Dan Walsh about it.
The issue, if it indeed is the same one we had discussed, is related to suspend/resume. I don't know the right lingo for it, but some property of the files that are causing selinux to block the sound and video of flash movies is changed after the resume.
At the time, Dan had suggested that the systemd folks, I believe he said, need to straighten this out.
I think this is a selinux problem after all. I have made a new bug report under selinux to address this issue, so I am closing this bug report.