Summary: | media-video/totem-2.16.5 with xine-lib 1.1.3/1.1.4 doesn't play ogg files | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Brian Beardall <brian> |
Component: | Current packages | Assignee: | Gentoo Linux Gnome Desktop Team <gnome> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | gstreamer, kubrick, m.kristian, pacho |
Priority: | High | ||
Version: | 2006.1 | ||
Hardware: | All | ||
OS: | Linux | ||
URL: | http://bugzilla.gnome.org/show_bug.cgi?id=405883 | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
patch from upstream
patched ebuild using the upstream patch |
Description
Brian Beardall
2007-01-10 18:47:36 UTC
I had the same problem after upgrading to xine-lib 1.1.3 and after downgrading to media-libs/xine-lib-1.1.2-r3 it works again. the xine-ui plays ogg files with both versions. still reproduced on totem 2.16.5 and xine-lib-1.1.4. *** Bug 167004 has been marked as a duplicate of this bug. *** Searched on gnome bugzilla and there's an open bug for this. Posted on URL. Created attachment 114696 [details]
patch from upstream
Created attachment 114698 [details]
patched ebuild using the upstream patch
since this patch is applied by the gnome folks only on version 2.17/2.18, please consider to put the attached ebuild and patch into portage to fix that bug for users of gnome-2.16.
it works for me on Portage 2.1.2.2 (default-linux/x86/2006.1/desktop, gcc-4.1.1, glibc-2.5-r0, 2.6.16-gentoo-r6 i686)
Since totem 2.18.3 is current stable, this isn't a problem anymore. disagree !! so I just write my personal view of things !! * gentoo is the only linux distribution which I found which does not support the xine backend in totem 2.18.x anymore * people are unhappy about not having the xine backend in totem 2.18.x (have a look in the forum) * maybe I did look at the wrong places, but I could not find any official statement from upstream that the xine backend gets droppend somewhen in the future - maybe someone put such a link in the upgrade gnome docu !! looking at these points, than an ebuild which supports xine would be really nice to have. for me personally totem without xine is just an audio player !! well I have my own overlay ebuild now, with xine support. Then help us fix bugs instead of waving your hands high up in the air. sorry if I sounded a bit harsh. please find my ebuild for totem 2.18.3 with xine-lib support in https://bugs.gentoo.org/show_bug.cgi?id=191120 Just putting the xine backend into the totem build is trivally easy. It's fixing bugs in that backend (which neither the gnome herd nor the xine maintainers want to support) that's hard. I'm not sure how to move forward at this point... Maybe some gnome herd member is willing to proxy maintain for you? More likely, someone should just create an overlay that has the support, and maintain it there, unless some gentoo dev wants to take ownership of it. (In reply to comment #8) > disagree !! so I just write my personal view of things !! > > * gentoo is the only linux distribution which I found which does not support > the xine backend in totem 2.18.x anymore Gentoo is also one of the few distributions that installs the source files as well and has file collission protections. We want gstreamer to be the default - so do other distributions, and they have it. What other distributions do, is provide two binaries - default (named totem) using gstreamer and another (named totem-xine) using xine-lib. The catch is that they can just have a package that contains the totem-xine binary and call it a day - we have to handle other things, such as avoiding file collissions for header files, while others don't even install headers by default, but we need to as things do depend on totem and this is the custom. That said, I'm willing to proxy maintain a xine backend in totem 2.20.x, provided that a clean patch for upstream bug http://bugzilla.gnome.org/show_bug.cgi?id=459539 is provided as well. Having said patch would allow to make the backend runtime-chooseable so we can provide only one binary, yet have both supported and switchable to a non-default xine-lib backend by an argument to totem. Then a totem-xine symlink to totem --backend=xine can also be provided. Without this, it is a hack and I'm not willing to put any xine support in portage tree for totem, as a) it would either be a big totem-xine binary hack with ebuilds; or b) xine would be the default and we can't support that. > * people are unhappy about not having the xine backend in totem 2.18.x (have a > look in the forum) They can be pointed to the above bug if they want a solution in portage, which has to be a clean solution. > * maybe I did look at the wrong places, but I could not find any official > statement from upstream that the xine backend gets droppend somewhen in the > future - maybe someone put such a link in the upgrade gnome docu !! I removed such a statement in the upgrade guide a while back. I had a chat with Bastien Nocera (upstream maintainer) at the GNOME Conference (GUADEC) this July and indeed the xine backend is supported by upstream by him personally only until gstreamer can provide a good DVD playing solution. In discussions with him back then we also came to the agreement that the above described method is the best and cleanest solution for Gentoo Linux and he intended to provide help in how to achieve it in totem backend choosing code - it should be about 2-4 hours of work, but he hasn't provided the described help yet and I haven't personally had time to dig into this so deep to poke around in the totem codebase without some guidelines from him. I'm not accusing him of anything, however, we are all busy people. > looking at these points, than an ebuild which supports xine would be really > nice to have. for me personally totem without xine is just an audio player !! > well I have my own overlay ebuild now, with xine support. Good for you :) We however need a clean solution for portage purposes. now I start to understand the underlying problems. in the end I just want to use totem for playing my dvds (with menu support), whether with xine or with gstreamer. since the upstream bug http://bugzilla.gnome.org/show_bug.cgi?id=459539 needs to be fixed first, I am happy to see if I can help here. but I would appreciate to get the hints from Bastien Nocera, before I start. so please either post them here (which triggers an email to me) or sent them directly to me. thanx. (In reply to comment #13) > but I would appreciate to get the hints from Bastien Nocera, before I start. It appears he posted them on the upstream bug two days ago already and you should have seen them on the upstream bug. I hadn't noticed the e-mail noting that and thought he hadn't done it yet as I couldn't check at the time (gnome bugzilla had a SQL corruption at the time). So all's there now to get started :) Appears someone is trying to tackle it already too. |