Summary: | Konqueror crash on opening site with embedded webm <video> | ||
---|---|---|---|
Product: | [Frameworks and Libraries] Phonon | Reporter: | Syam <get.sonic> |
Component: | Xine backend | Assignee: | Harald Sitter <sitter> |
Status: | RESOLVED DUPLICATE | ||
Severity: | crash | CC: | adawit, info, martin.sandsmark, myriam |
Priority: | NOR | ||
Version: | 4.4.3 (KDE 4.6.x) | ||
Target Milestone: | --- | ||
Platform: | Fedora RPMs | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: | |||
Attachments: | Backtrace of konqueror crash |
Description
Syam
2011-03-20 16:18:09 UTC
I can confirm this bug here also. Fedora 14 (32-bit), but with Nouveau driver. Trying to access the above page causes a crash in konqueror. backtrace ? Which rendering engine khtml ? The rendering engine is khtml indeed. However in the meantime I have found other similar reports which suggest this is not a konqueror problem but a phonon problem, particularly with the xine backend. I just tried this again: - System Settings -> Multimedia - Set xine as preferred backend - Then use konqueror to visit the website in the original report => Crash I'll attach the backtrace. If on the other hand you set the preferred phonon backend to gstreamer and repeat the test, it works fine. Created attachment 59722 [details]
Backtrace of konqueror crash
(In reply to comment #4) > Created an attachment (id=59722) [details] > Backtrace of konqueror crash (In reply to comment #3) > The rendering engine is khtml indeed. However in the meantime I have found > other similar reports which suggest this is not a konqueror problem but a > phonon problem, particularly with the xine backend. > > I just tried this again: > - System Settings -> Multimedia > - Set xine as preferred backend > - Then use konqueror to visit the website in the original report > => Crash > I'll attach the backtrace. > > If on the other hand you set the preferred phonon backend to gstreamer and > repeat the test, it works fine. Ok. Let us assign it to the correct location then. *** This bug has been marked as a duplicate of bug 227837 *** |