No sound device detected after updating

Bug #200384 reported by apopovas
14
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Ubuntu
Incomplete
Undecided
Unassigned

Bug Description

After installing latest updates via update manager (restart was requested), no sound drivers were detected. When trying to launch volume control, this message appears: "No volume control GStreamer plugins and/or devices found."
When trying to test sound in sound preferences this message appears: "audiotestsrc wave=sine freq=512 ! audioconvert ! audioresample ! gconfaudiosink: Failed to connect stream: Invalid argument"

I use Toshiba Satellite Pro L100-121, Ubuntu Hardy Heron Alfa 5

Revision history for this message
Greg Grossmeier (greg.grossmeier) wrote :

Could you please paste the output when you type "uname -a" in the terminal?

Revision history for this message
iKs (iks279) wrote :

I get the exact same bug and this is the output of uname -a :
$ uname -a
Linux xlaptop 2.6.24-12-generic #1 SMP Sat Mar 8 01:30:36 UTC 2008 x86_64 GNU/Linux

I also noticed first that all applications using Gstreamer were freezing and not responding anymore (totem, rhythmbox, etc.). After restarting the computer, these worked but I had no sound at all and those error messages apopovas gave.

If you need any other information please feel free to ask.

Revision history for this message
iKs (iks279) wrote :

By the way, `sudo alsa reload` gives :
$ sudo alsa reload
Unloading ALSA sound driver modules: (none loaded).
Loading ALSA sound driver modules: (none to reload).

And System >> Preferences >> Sound >> Default Mixer Tracks >> Device lists no sound device. I'm editing the description accordingly to "No sound device detected after updating via update manager".

Revision history for this message
Rhaegar (rhaegartargaryen) wrote :

Same problem here, I get absolutely the same errors / output.
When I try to test audio in the audio settings windows, I get the following error message:
audiotestsrc wave=sine freq=512 ! audioconvert ! audioresample ! gconfaudiosink: Failed to connect stream: Invalid argument

Revision history for this message
Lafa (luis-alves) wrote :

I see the same problem, on my hardy box

Revision history for this message
Sylvain_Lermen (s-lermen) wrote :

Same goes with me. I updated about an hour ago ... no sound! When trying "sudo alsa reload" I'm getting the same message as iKs ... same is with the audiotest.

I'm running ubuntu hardy alpha 6 on a Shuttle XPC with onboard sound chip

Revision history for this message
Sylvain_Lermen (s-lermen) wrote :

Update:

The Bug seems to be solved by a new update now. Obviously this was the same problem as it has occurred in Gutsy, depending on the "linux-backports-modules". The new update installed this module (linux-backports-modules-generic in my case) and ... voila: everything is fine now!

Revision history for this message
Narayan S S (rocknarayan) wrote :

I installed Hardy Beta 1 today and find that this problem is persisting. No sound card has been identified. When I ran the "lspci -v" command the card was shown in the device list as follows.

00:11.5 Multimedia audio controller: VIA Technologies, Inc. VT8233/A/8235/8237 AC97 Audio Controller (rev 60)
 Subsystem: ASUSTeK Computer Inc. Unknown device 810d
 Flags: medium devsel, IRQ 5
 I/O ports at bc00 [size=256]
 Capabilities: <access denied>

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.