Bug 108932 - not able to use to sound devices on inspiron 8500
not able to use to sound devices on inspiron 8500
Status: CLOSED WORKSFORME
Product: Red Hat Linux
Classification: Retired
Component: gnomemeeting (Show other bugs)
9
All Linux
medium Severity medium
: ---
: ---
Assigned To: Daniel Reed
David Lawrence
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2003-11-03 10:14 EST by John Artley
Modified: 2007-04-18 12:59 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2004-11-06 13:02:41 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)

  None (edit)
Description John Artley 2003-11-03 10:14:30 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686) Gecko/20030807 Galeon/1.3.5

Description of problem:
get error message 

The selected audio device (/dev/dsp) was successfully opened but it is
impossible to write data to this device. Please check your audio setup.

When using the configuration druid. 

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

How reproducible:
Always

Steps to Reproduce:
1. Start gnomemeeting
2. run configurationDruid
3. test sound
    

Actual Results:  get error message 

The selected audio device (/dev/dsp) was successfully opened but it is
impossible to write data to this device. Please check your audio setup.


Expected Results:  I have never seen it work, so I dont know

Additional info:

This was tried on a Dell inspiron 8500 laptop using 2.4.22-6.ll.rh90
Comment 1 Daniel Reed 2004-10-08 22:51:44 EDT
I can not reproduce the error on the hardware I have available, and do
not have access to your hardware. If this is still a problem for you I
can migrate the bug to the upstream developers.
Comment 2 Daniel Reed 2004-11-06 13:02:41 EST
Please feel free to reopen this if you are still having issues.

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