Red Hat Bugzilla – Bug 466851
HDA Intel/STAC92xx Analog, Default mixer initialization incorrect, volume very low
Last modified: 2009-12-18 01:34:17 EST
Description of problem:
On a system (which I've upgraded from Fedora 9 to latest rawhide), totem refuses to play any kind of file (despite the fact I've erased and reinstalled it completely via yum).
When double-clicking a media file, the error message is: "An error has occured: Failed to connect stream: Invalid argument".
I've tried to open:
- ogg files
- oga files
- mp3 files
- mpg files
The corresponding files play with no problem using other players (mainly vlc).
I've discovered this after noting that SoundJuicer ripper now produces .oga files instead of .ogg and I've tried to play an .oga file.
Version-Release number of selected component (if applicable):
Always (on my system).
Steps to Reproduce:
1. Install the above totem packages
2. Double-click a multimedia file (free or non-free).
Totem doesn't play multimedia files.
Free multimedia files should play out of the box. Non-free multimedia files should play if the corresponding non-free codecs are installed (livna-supplied packages, via yum).
I've only enabled the official rawhide and livna-development yum repositories - in order to keep the soon-to-be Fedora 10 updated online, without package conflicts.
Launch totem from the command-line, you'll see that the error comes from pulseaudio itself.
Sounds like no audio device could be configured.
Which driver do you use?
Does "pavucontrol" show any output devices?
In the mean time, it works - after the latest online updates.
The device is HDA Intel - STAC92xx Analog (on a Dell Inspiron 1520 laptop):
Thanks forthe update. Closing this bug then.
Sorry, I was too optimistic about that - reopening bug.
I get the same error in SOME applications - for example, I cannot play CDs in rhytmbox or in sound juicer, while it works OK in gnome-mplayer.
Still sounds something is blocking your audio device when PA tries to open it. Does "pavucontrol" show any audio device for you?
Yes - as I said, it shows HDA Intel - STAC92xx Analog. I'm running on a Dell Inspiron 1520 laptop.
The audio device used to work with no problem since Fedora 8 - no special drivers required, just the software from the Fedora official DVD.
Can you please open pavucontrol, make sure the device exists and the try to reproduce the issue in Totem?
I am pretty sure that some other app is simply blocking acecss to the audio device which will then result in the error message you encountered because PA has not audio device to output data to.
Created attachment 322212 [details]
pavucontrol - tab 1
Here are a few screenshots that shows how the various multimedia applications behave.
Created attachment 322213 [details]
pavucontrol - tab2
Created attachment 322214 [details]
pavucontrol - tab 3
Created attachment 322215 [details]
pavucontrol - tab 4
Created attachment 322216 [details]
An audio CD is just inserted...
Created attachment 322217 [details]
Rythmbox doesn't play
In rythmbox, selecting a CD track and pressing Play leads to no result (nothing happens).
Created attachment 322218 [details]
VLC plays at very low volume
VLC plays normally, but the sound volume is quite low (despite the fact that all other controls, both hardware and software, are set to maximum).
Created attachment 322219 [details]
Totem's option to play CDs is deactivated
Totem menu options for playing CDs is deactivated; it seems some plugin is needed, but none offered/found.
Created attachment 322220 [details]
Sound Juicer says invalid stream
Trying to play the CD with the Play option in Sound Juicer leads to the error in the image.
Please suggest other test to perform and I'll be pleased to experiment with them.
Thanks a lot,
Ripping a CD with SoundJuicer now produces .oga files instead of .ogg files.
Some players - for example XMMS - don't seem to know to open them.
However, players that do know play .ogg files at normal volume level.
You can change the volume of each playback stream (like the one from VLC) in pavucontrol.
.oga is the standardized name for OGG audio files. Many older programs called that .ogg before.
Hmm, if you type "pacat /dev/urandom" in a terminal. Do you hear any noise?
Even if sliders in pavucontrol are set to maximum (please see comment #11 above), volume is very low. Since this is a laptop, there are no cables to check... ;-)
Of course, I know .ogg -> .ogg is just an extension change. But this simple change seems to confuse some players, according to my tests. Please try to open/play an .oga file by double-clicking it, when it is associated with various players installed on a Fedora system... The situation is similar on a Windows system.
Typing "pacat /dev/urandom" leads to:
[root@mazarin ~]# pacat /dev/urandom
Stream error: Invalid argument
For another example why renaming .ogg files to .oga still induces collateral problems (even if technically correct), please see bug #468464.
Multimedia-related problems were present on my Dell Inspiron 1520 laptop since I've upgraded from Fedora 9 to rawhide (with daily updates) - as seen in comments above. IMHO, this is a regression.
For the moment, the most a annoying fact is that volume is very low, even if both hardware & software controls are set to maximum.
Could you please suggest a systematic way to double check all settings ?
This is the actual hardware profile of the laptop (smolt):
Thanks a lot,
This bug appears to have been reported against 'rawhide' during the Fedora 10 development cycle.
Changing version to '10'.
More information and reason for this action is here:
Is this issue still current? Have you played around with "alsamixer -c0" to get the mixer initialized correctly?
Hello and thanks,
Yes, this still happens. Sound is *very* low in *some* cases, especially on YouTube, despite the fact both software and hardware controls are set to maximum.
I didn't played with "alsamixer -c0"; I'll do this today and let you know ASAP.
Hmm, I am pretty sure this is just another mixer initialization issue. Reassigning to alsa-libs, since it is now ALSA's job to come up with good default volumes.
Also, attach output from 'alsa-info.sh --no-upload'.
This message is a reminder that Fedora 10 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 10. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora
'version' of '10'.
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version prior to Fedora 10's end of life.
Bug Reporter: Thank you for reporting this issue and we are sorry that
we may not be able to fix it before Fedora 10 is end of life. If you
would still like to see this bug fixed and are able to reproduce it
against a later version of Fedora please change the 'version' of this
bug to the applicable version. If you are unable to change the version,
please add a comment here and someone will do it for you.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
The process we are following is described here:
Fedora 10 changed to end-of-life (EOL) status on 2009-12-17. Fedora 10 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.
If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version.
Thank you for reporting this bug and we are sorry it could not be fixed.