Bug 115859 – After install, xmms fails to start.

Bug 115859 - After install, xmms fails to start.

Summary:	After install, xmms fails to start.

Status:	CLOSED DUPLICATE of bug 112864

Aliases:	None

Product:	Fedora
Classification:	Fedora
Component:	xmms (Show other bugs)
Sub Component:
Version:	rawhide
Hardware:	i386 Linux

Priority	medium Severity high
Target Milestone:	---
Target Release:	---
Assigned To:	Bill Nottingham
QA Contact:
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2004-02-16 13:08 EST by Jack Thompson
Modified:	2014-03-16 22:42 EDT (History)
CC List:	1 user (show)

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2006-02-21 14:01:19 EST
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description Jack Thompson 2004-02-16 13:08:19 EST

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6)
Gecko/20040207 Firefox/0.8

Description of problem:
Having installed FC 2 test 1 I tried to run xmms. This resulted in
segmentation fault.

Version-Release number of selected component (if applicable):
xmms-1.2.8-3

How reproducible:
Always

Steps to Reproduce:
1. Install FC 2 test 1
2. Try to execute xmms
3.
    

Actual Results:  Segmentation fault.

Expected Results:  xmms should have started without errors.

Additional info:

Comment 1 Scott Sloan 2004-02-16 13:18:47 EST

copy over the .xmms folder from the user home previous home directory.
This worked for me. Note all OSS drivers were removed from the kernel,
so make sure you change your output plugin to Alsa.

Comment 2 Bill Nottingham 2004-02-16 14:07:01 EST


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

Comment 3 Red Hat Bugzilla 2006-02-21 14:01:19 EST

Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.

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