Hide Forgot
abrt version: 1.1.17 architecture: i686 Attached file: backtrace, 61727 bytes cmdline: midori component: midori Attached file: coredump, 388702208 bytes crash_function: g_object_unref executable: /usr/bin/midori kernel: 2.6.35.11-83.fc14.i686 package: midori-0.2.9-4.fc14 rating: 4 reason: Process /usr/bin/midori was killed by signal 11 (SIGSEGV) release: Fedora release 14 (Laughlin) How to reproduce: 1. fullscreen a video inside an <video< tag time: 1300642659 uid: 500
Created attachment 486490 [details] File: backtrace
What page were you looking at the video from? Is it a public page you can note here? If you disable the adobe flash plugin and look does it work without crashing?
It was that website: http://blogs.gnome.org/shaunm/2011/03/20/mallard-can-do-that/ How can I disable the flash plugin?
Interesting. It works ok here, but I am on f15 (newer midori, gstreamer and webkitgtk). You can go to prefs->behavior and uncheck 'enable netscape plugins'. This isn't directly flash, but I did see the flash plugin in your backtrace, so just want to rule it out.
Package: midori-0.2.9-4.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. fullscreen a video
Yes, still the same with disabled plugins. But if it works in the next version that should be fine.
Well, it's unclear if it's: newer midori, newer webkitgtk or newer gstreamer thats causing it to work here. ;( I could make you scratch builds of the first 2 if you like, but I have no idea how to rebuild the gstreamer stack and it's very very unlikely it would get updated in f14. ;( So, where do we go from here? Would you like me to make some scratch builds for f14? Or should we close this since it works in newer releases? Or would you like me to move this over to gstreamer to see if anyone there can figure out how to fix it in f14?
Thanks for the scratch-build offer but I think it's fine to wait for F15. I'll switch with the beta release so no need to spend your time on this. However thanks a lot for your efforts!
ok. Should we leave this open? Close it as wontfix? something else? ;)
Think we can close it. I don't know it wontfix or nextrelease/rawhide makes more sense.
How about upstream? :)
good solution! :D