After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 545341 - Cannot test sound preferences
Cannot test sound preferences
Status: RESOLVED DUPLICATE of bug 471364
Product: GStreamer
Classification: Platform
Component: gstreamer (core)
0.3.4
Other Linux
: Normal normal
: git master
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on:
Blocks:
 
 
Reported: 2008-07-29 16:37 UTC by Robert Kochis
Modified: 2008-07-29 18:05 UTC
See Also:
GNOME target: ---
GNOME version: 2.19/2.20


Attachments
Setting audio preferences to physical hardware (92.02 KB, image/png)
2008-07-29 16:38 UTC, Robert Kochis
Details
Setting audio preferences to Alsa driver (96.12 KB, image/png)
2008-07-29 16:39 UTC, Robert Kochis
Details
Soundcard detection window, I hear sound fine from here. (33.60 KB, image/png)
2008-07-29 16:41 UTC, Robert Kochis
Details

Description Robert Kochis 2008-07-29 16:37:30 UTC
I open System->Preferences->Hardware->Sound.  When I select my soundcard SiS7012 and then press test I get an internal error.  

See attached screenshots
Comment 1 Robert Kochis 2008-07-29 16:38:50 UTC
Created attachment 115503 [details]
Setting audio preferences to physical hardware
Comment 2 Robert Kochis 2008-07-29 16:39:38 UTC
Created attachment 115505 [details]
Setting audio preferences to Alsa driver
Comment 3 Robert Kochis 2008-07-29 16:41:47 UTC
Created attachment 115506 [details]
Soundcard detection window, I hear sound fine from here.
Comment 4 Sebastian Dröge (slomo) 2008-07-29 18:05:31 UTC
Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.


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