Bug 1030318

Summary:	xine channels.conf location moved
Product:	[Fedora] Fedora	Reporter:	Paul Finnigan <paul>
Component:	xine-lib	Assignee:	Kevin Kofler <kevin>
Status:	CLOSED NOTABUG	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	low	Docs Contact:
Priority:	unspecified
Version:	20	CC:	kevin, rdieter, xavier
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2013-11-14 20:17:05 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Paul Finnigan 2013-11-14 10:51:46 UTC

Description of problem:

When selecting DVB fromn the UI in xine I get the message "No valid channels.conf found" and the UI locks up, it needs to be killed. Confusing as I had one that looked correct in ~/.xine/

I have found that you need to put the channels.conf file into ~/.config/xine-lib/

This is a problem that needs to be passed upstream I would think. Debian has a similar problem reorted (http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=702580) but this is for a different version of xine-lib

It is not a major issue. Just people need to be aware of the location that channels.conf should be placed.

Version-Release number of selected component (if applicable):
1.2.4-3.fc20

How reproducible:
Every time

Steps to Reproduce:
1. Put channels.conf in ~/.xine/
2. Start xine
3. Select DVB

Actual results:
UI unusable

Expected results:
Watch TV

Additional info:
Move channels.conf file to ~/.config/xine-lib/channels.conf and everything works as expected

Comment 1 Rex Dieter 2013-11-14 12:53:27 UTC

xine-lib is no longer in fedora, please report to bugzilla.rpmfusion.org instead.

Comment 2 Kevin Kofler 2013-11-14 20:17:05 UTC

That, plus I'm sure this is an intentional change (following modern-day freedesktop.org specifications rather than legacy Unix conventions), not a bug at all. 1.2 is a major new version, there are years of development between 1.1 and 1.2.