Bug 81298 - warning.wav missing from gnome-audio package
Summary: warning.wav missing from gnome-audio package
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: gnome-audio
Version: 8.0
Hardware: i386
OS: Linux
Target Milestone: ---
Assignee: Havoc Pennington
QA Contact: Jay Turner
Depends On:
TreeView+ depends on / blocked
Reported: 2003-01-07 19:47 UTC by Don Vanco
Modified: 2015-01-08 00:02 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2003-01-14 20:53:27 UTC

Attachments (Terms of Use)

Description Don Vanco 2003-01-07 19:47:55 UTC
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 5.5; Windows NT 5.0; T312461)

Description of problem:
Upon trying to set up event sounds in Gnome I tried to select from the "default 
sounds" - none of them would play, instead I got a pop-up warning me that I 
needed to install gnome-audio.  I did so, and then all but one of the sample 
files would play.  It would appear that warning.wav did not get installed on my 
system.  The rest of the .wav files seem to have installed fine 

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

How reproducible:

Steps to Reproduce:
1. Remove gnome-audio
2. Clean /usr/share/sounds
3. Re-install gnome-audio, look for warning.wav

Actual Results:  file is not there on my system

Expected Results:  the file warning.wav exists in /usr/share/sounds

Additional info:
Intel 815 based mobo (other things acting odd - like XMMS seg faulting; 
wondering if it's a chipset thing, but don't see how that would affect the 
installation of a single file from an rpm)

Comment 1 Michael Lee Yohe 2003-01-07 20:39:59 UTC
Please provide which package you are using (the gnome-audio package).

$ rpm -qf /usr/share/sounds/warning.wav 

Then - provide the contents of the package _after_ you re-install it and verify
that warning.wav does not exist.

$ rpm -ql gnome-audio

Comment 2 Havoc Pennington 2003-01-14 20:53:27 UTC
I do see warning.wav in rawhide gnome-audio package.

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