Bug 6299 - wrong output plugin selected by default
Summary: wrong output plugin selected by default
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: xmms
Version: 6.1
Hardware: i386
OS: Linux
medium
low
Target Milestone: ---
Assignee: Bill Nottingham
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 1999-10-24 08:42 UTC by rh-devel
Modified: 2015-12-15 15:33 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2000-02-22 22:54:00 UTC
Embargoed:


Attachments (Terms of Use)

Description rh-devel 1999-10-24 08:42:58 UTC
The xmms mp3/etc player packaged with RH6.1 comes configured
to use the Disk Writer output plugin by default -- which
writes its output to a .wav file in the user's home
directory, rather than playing it to an audio device.  More
ideally the initial selection should be either the esound or
OSS output plugins (presumably the latter given the GNOME
environment).

Comment 1 Bill Nottingham 1999-10-25 16:07:59 UTC
I don't see this here; removing the ~/.xmms directory,
and then starting xmms, I get the esound plugin...

Comment 2 rh-devel 1999-10-29 00:41:59 UTC
Sofar I've been able to reproduce this only on two RH6.0 workstations
running xmms as installed from xmms.org's 0.9.5 RPMs (which did not
include the WAV output plugin IIRC), which makes it a fairly narrow
issue for xmms rather than RH.

Comment 3 Bill Nottingham 2000-02-22 22:54:59 UTC
fixed in xmms-1.0.1-4.
if ~/.xmms/config references an output plugin that doesn't exist,
it grabs the first one in the list (i.e., the disk writer).
Changed to also look for the same filename in .xmms/config, but
in a different directory...

Comment 4 openshift-github-bot 2015-12-15 15:33:08 UTC
Commit pushed to master at https://github.com/openshift/origin

https://github.com/openshift/origin/commit/20a78d196e35ccbb2e1ea388d435e15b66a029a8
Merge pull request #6309 from gabemontero/issue6299-fixforcepull

Merged by openshift-bot


Note You need to log in before you can comment on or make changes to this bug.