Bug 443263

Summary:	totem always uses xine backend!!!
Product:	[Fedora] Fedora	Reporter:	Hans de Goede <hdegoede>
Component:	totem	Assignee:	Bastien Nocera <bnocera>
Status:	CLOSED DUPLICATE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	medium	Docs Contact:
Priority:	high
Version:	rawhide	CC:	ma
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2008-04-21 17:49:50 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Hans de Goede 2008-04-19 21:00:01 UTC

Description of problem:
Totem always uses the xine-backend, running "totem-backend -b gstreamer" as root
does not change this.

The only way I've found to run totem using the gstreamer backend is by invoking:
totem-backend -b gstreamer totem as normal user.

This can be a rather nasty F-9 surprise for people like me who have spend a lot
of time to create a good gstreamer setup / have written lots of gstreamer
patches to get good multimedia support!

I would _really_ like to see this fixed before F-9, let me know if there is
anything I can do to help achieve that.

To reproduce:
start totem, or a website with embedded media which will start the totem plugin.
Goto the about bix, it will always say: "using xine-lib version 1.1.11.1",
independent of how you've configured things through totem-backend.

Comment 1 Martin Jürgens 2008-04-19 21:11:38 UTC

I am running into the same issue and additionally think that this is a F9blocker. 

Actually, I did not even note that Totem switched to Xine, as I explicitly was
running Gstreamer some time earlier in the F9 cycle.

Comment 2 Bastien Nocera 2008-04-21 17:49:50 UTC

That's because the alternatives file gets removed in the postun on upgrade.

*** This bug has been marked as a duplicate of 442895 ***