RESOLVED INVALID41154
QtWebkit doesn't paint the flash content on RHEL4/CentOS4 using flash player 9 
https://bugs.webkit.org/show_bug.cgi?id=41154
Summary QtWebkit doesn't paint the flash content on RHEL4/CentOS4 using flash player 9
qt-info
Reported 2010-06-24 05:48:45 PDT
Firefox plays the flash well, but QtWebkit shows only a gray window for the flash ( seems to be not painted at all). Tested and reproduced in RHEL4 and CentOS4.6, Qt4.5.3 and Qt4.6.3
Attachments
screenshot (39.52 KB, image/jpeg)
2010-06-24 05:52 PDT, qt-info 		no flags
Details
View All Add attachment proposed patch, testcase, etc.
qt-info
Comment 1 2010-06-24 05:51:02 PDT
I traced a little bit into the source but didn't find anything strange. The plugin loads fine and the PluginView is created without any problem. need to trace deeper. since the newer distribution like SuSE10, Ubuntu 10 doesn't have the problem, it's possible to be related to the system libs.
qt-info
Comment 2 2010-06-24 05:52:03 PDT
Created attachment 59647 [details] screenshot
qt-info
Comment 3 2010-06-24 07:57:20 PDT
The problem is that the m_tempFileHandle is invalid in src/3rdparty/webkit/WebCore/plugins/PluginStream.cpp PluginStream::didReceiveResponse Need to debug more to find the reason.
qt-info
Comment 4 2010-06-24 09:03:04 PDT
should correct that it's not because of the temp file. on a normal system, didReceiveData is kept getting called, but on CentOS it is called for only once.
Simon Hausmann
Comment 5 2010-06-25 05:50:41 PDT
Could you go to http://www.adobe.com/software/flash/about/ with your working firefox installation and add a comment here mentioning the flash version that you're using on CentOS4?
qt-info
Comment 6 2010-06-25 05:54:28 PDT
Firefox tells me that I have version 9,0,277,0 installed.
Jocelyn Turcotte
Comment 7 2014-02-03 03:50:46 PST
=== Bulk closing of Qt bugs === If you believe that this bug report is still relevant for a non-Qt port of webkit.org, please re-open it. If you believe that this is still an important QtWebKit bug, please fill a new report at https://bugreports.qt-project.org and add a link to this issue. See http://qt-project.org/wiki/ReportingBugsInQt for additional guidelines.
Note You need to log in before you can comment on or make changes to this bug.