| Summary: | www-client/midori-0.4.4 w/ webkit-gtk:3 unable to load (some) plugins | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Klaus Kusche <klaus.kusche> |
| Component: | Current packages | Assignee: | XFCE Team <xfce> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | mk |
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
|
Description
Klaus Kusche
2012-04-05 08:06:06 UTC
*** This bug has been marked as a duplicate of bug 374057 *** You can't replace a *working* gtk2 version with an *non-working* gtk3 version. A browser where all the plugins work upsteam and none of them works in gentoo is a "critical" bug. Either * provide a gtk2 version or * rename the bug to provide a *working* gtk3 version (which means all browser plugins which work in gtk2 must also work in gtk3) (In reply to comment #2) I migrated to epiphany due to the ideological bias of XFCE maintainers such as evident in this bug (experimental gtk3 support is turned on unconditionally, bugs about gtk3 are closed upstream on first opportunity, etc.). You might want to discuss this issue on gentoo-dev mailing list, although I wouldn't hold my breath towards maintainers accounting for users' opinion (they apparently failed with gtk2 migration in the past, and are now eager to brush migration issues under the carpet). Actually, I do have a mixed gtk2 / gtk3 XFCE installation on my primary machine, and up to now, the upstream XFCE team (not gentoo's) was very responsive on the several gtk2/gtk3 issues I reported. I'm happy with it, but I use firefox on my box, not midori... Midori is intended for several computer science classroom PC's here where firefox would kill the machines. But gtk3 midori is not yet ready for prime time at all, and the machines I intend it to run on are one order of magnitude smaller than my primary machine, and are gtk2 only (and that's exactly why I want to run gentoo + XFCE + midori on them). Stop reopening the bug and messing with the bug Importance: field. I've read it, reconsidered and won't be changing the ebuild. I'm a satisfied midori on a GTK+-3 user. *** This bug has been marked as a duplicate of bug 374057 *** The bug still contains no solution or even hint for the original problem, and that's absolutely required to close the bug. The original problem is not gtk2 vs gtk3 (gtk2 was just a proposed solution), the original problem is that all plugins don't work in gentoo's midori and do work in the upstream version. The dupped bug 374057 also provides no help concerning this plugin problem. Could you please at least tell me if plugins work for you (i.e. if I'm the only one having troubles with plugins in gtk3 midori) or if gtk3 midori doesn't support flash, java etc in general? (In reply to comment #4) > and up to now, the upstream XFCE team (not gentoo's) was very responsive > on the several gtk2/gtk3 issues I reported. I meant Gentoo maintainers, of course (you can see the attitude here). Midori is not part of the XFCE project otherwise. > Midori is intended for several computer science classroom PC's here > where firefox would kill the machines. Epiphany is based on the same WebKit-GTK backend, and I didn't notice much difference in resource consumption. It also seems more mature than Midori. If that matters, I am using unstable epiphany with gtk3. The Gentoo maintainers in charge of epiphany also seemed much more helpful to me. according to upstream flash is supported through nspluginwrapper (due to limitation of adobe-flash to gtk+-2) and the rest natively for GTK+-3 midori local testing seems to indicate that accurate and working *** This bug has been marked as a duplicate of bug 374057 *** Wrong, very wrong: 1.) It's not just flash: * The icedtea-bin java plugin, which is the recommended and default java plugin in Gentoo, is gtk2 only. * The Acrobat is gtk2 only. * The Libreoffice plugin is gtk2 only. * Gnash is gtk2 only. * Most good media plugins like VLC or Xine are gtk2 only. 2.) Nspluginwrapper only works on 64 bit *multilib* systems, because it needs a bunch of 32 bit libs. All systems here, both mine and the ones in the classrooms, are pure 64 bit (no multilib), so nspluginwrapper doesn't apply. And it would be brain-damaged to make *small* systems where RAM and disk/flash space is limited multilib! yeah, looks like our nspluginwrapper ebuild sucks. it's needlessly restricted for use of 32bit vs. 64bit. however webkit-gtk-1.8.0 gained USE=webkit2 which allows you to run GTK+-2 plugins inside GTK+-3 browser among other things, but midori doesn't support this *yet* so meanwhile waiting for the 'webkit2' support in midori, i've added USE=deprecated to midori's ebuild to enable GTK+-2 builds fixed in 0.4.5, and 9999 |
