Activity log for bug #229266

Date Who What changed Old value New value Message
2008-05-11 14:50:08 KIAaze bug added bug
2008-05-11 14:50:08 KIAaze bug added attachment 'upgrade.log' (Upgrade log)
2008-05-11 16:05:20 KIAaze description I made some additional upgrades today on Intrepid and suddenly, I don't have sound anymore. Festival gives me this for example: $echo "test" | festival --tts Linux: can't open /dev/dsp Kaffeine tells me "Audio output unavailable. Device is busy. ()" And in sound preferences, trying to test yields this: "audiotestsrc wave=sine freq=512 ! audioconvert ! audioresample ! gconfaudiosink: Failed to connect stream: Invalid argument" Attached is a list of the upgrade (which also removed a lot of packages). I made some additional upgrades today on Intrepid and suddenly, I don't have sound anymore. Festival gives me this for example: $echo "test" | festival --tts Linux: can't open /dev/dsp Kaffeine tells me "Audio output unavailable. Device is busy. ()" And in sound preferences, trying to test yields this: "audiotestsrc wave=sine freq=512 ! audioconvert ! audioresample ! gconfaudiosink: Failed to connect stream: Invalid argument" Attached is a list of the upgrade (which also removed a lot of packages). Update: I restarted selecting the 2.6.24-16-generic kernel instead of the 2.6.24-16-i386 kernel and now I have sound again. :) However, I had the same three error messages at startup about some applets being unable to load: -volume applet: OAFIID:GNOME_MixerApplet -trash applet: OAFIID:GNOME_Panel_TrashApplet -System monitor: OAFIID:GNOME_MultiLoadApplet
2008-05-11 16:05:20 KIAaze title No sound in Intrepid No sound in Intrepid when using 2.6.24-16-i386 kernel
2008-09-13 19:22:17 Felipe Venegas None: status New Incomplete
2008-09-13 19:22:17 Felipe Venegas None: statusexplanation
2008-09-22 20:49:01 Jean-Baptiste Lallement None: status Incomplete Invalid
2008-09-22 20:49:01 Jean-Baptiste Lallement None: statusexplanation We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!