Upgrade to Hardy, Many Sound Woes

WARNING I needed a place to take notes while debugging sound issues after upgrading my desktop from Gutsy to Hardy, so here they are. This is probably a pretty boring read, so continue at your own risk.

Upgraded to Hardy today. Got some indistinct error message at the end, so I made sure and ran aptitude update && aptitude -y full-upgrade && dpkg --configure -a a few times before and after rebooting. Then, when I fired up Firefox (fired up... Firefox... get it...?) and went to youtube I realized I didn't have flash anymore. I aptitude installed flashplugin-nonfree, restarted Firefox, and videos worked. Yay!

Then I went away for a while. When I came back youtube videos had no sound. This is actually a problem that I was having before the upgrade. Not even a reboot helped. I fired up Amarok to see if mp3s still played. Nope, it froze. I googled a bit and found some pulse audio help which led me to believe that maybe I needed to add myself to the pulse audio groups. I did so, tried Amarok again, and the whole system froze. No magic keys or anything could save me. I hit the reset button on my case, and when it came back up, still no youtube sound. I started Amarok and it took forever to start, and then I made sure it was configured to use pulseaudio for its output plugin (I'm using the xine engine), and it didn't freeze, but it didn't play music either. Frustrating. First I had sound problems with Gutsy, and now seemingly worse problems with Hardy. Ubuntu, you've been so good to me in the past. What gives?

Pressing on, I tried changing the output plugin for Amarok and the whole app froze again. I tried watching video with totem, no sound. It froze after a bit too and I had to kill it. This is getting quite scary.

Reading some more here and here I discover this thing called libflashsupport. Aptitude tells me it's not installed and the description reads:

Due to various bugs in the Flash 9 plugin sound output of Flash 9 through the pulseaudio soundserver doesn't work properly. This library adds a clutch to make Flash 9 sound output in pulseaudio possible.

After installing this I shut off my computer completely (I'm in full belt-and-suspenders paranoia mode now), waited a few seconds and then turned it back on.

Taking a more conservative route this time, I started Totem first. No KDE or flash weirdness there. It worked, sound and video played without any problems. Next I tried Amarok with the xine engine output plugin set to autodetect. It worked, no hang. Next, youtube. No sound. Totem and Amarok still worked even after trying flash. I don't know if this result is any different from before, unfortunately. Maybe everything works better as long as you don't do flash first. I don't know.

I'm not sure what to try next. Apparently there might be a newer version of libflashsupport that I could try. This advice is not well explained, but it might be worth a try as well. Overall, I'm getting the impression that this is more the fault of flash than anyone else. Cursed closed-source crap!

I decided to try compiling libflashsupport from source as suggested on the pulse audio wiki. I aptitude removed libflashsupport first. After compiling and installing and restarting firefox there was still no youtube sound. Amarok and Totem were still good though. I rebooted. Still no youtube sound.

And then I saw it. There is a volume control on the little video controls under the youtube video. And it was turned all the way down. Oh. my. gosh. Sure enough, when I turned it up, sound played. How long has that been the problem!?!?!?

I decided to undo what I'd done a bit. I uninstalled libflashsupport as compiled from source and re-installed the ubuntu package. After restarting Firefox youtube and totem both worked, at the same time even. I think I'll leave things like that for now. Don't you love Linux? I do. I really do.

Comments

Post a Comment

Popular posts from this blog

SystemVerilog Fork Disable "Gotchas"

This is a long post with a lot of SystemVerilog code. The purpose of this entry is to hopefully save you from beating your head against the wall trying to figure out some of the subtleties of SystemVerilog processes (basically, threads). Subtleties like these are commonly referred to in the industry as "Gotchas" which makes them sound so playful and fun, but they really aren't either. I encourage you to run these examples with your simulator (if you have access to one) so that a) you can see the results first hand and better internalize what's going on, and b) you can tell me in the comments if this code works fine for you and I'll know I should go complain to my simulator vendor. OK, I'll start with a warm-up that everyone who writes any Verilog or SystemVerilog at all should be aware of, tasks are static by default. If you do this: module top; task do_stuff ( int wait_time); #wait_time $display ( "waited %0d, then did stuff" , wa
Read more

'git revert' Is Not Equivalent To 'svn revert'

I just learned that if you have some changes in your working tree that you want to get rid of, you don't type 'git revert' like you might guess. No, that's what cvs, subversion, mercurial, and bazaar (to name a few) use revert to mean, but not git. With git, revert is used to undo actual commits. Thankfully, you can undo your revert with another 'git revert', I just learned. So let me repeat to be clear, if you have changes to your working files that you want to abandon, DO NOT do this: git revert HEAD That will undo your last commit. Do this instead: git reset --hard HEAD I'm glad I have that straightened out now. I'm wondering if /etc was really a good place for me to start out playing with git. UPDATE: Nearly two years later and I'm still getting comments on this. I'm glad I've been able to help people out this way. The discussion in the comments is good, and one thing I'd like to point out is that I now always use
Read more

Git Rebase Explained

Image
Introduction Rebase is a helpful git command that can be used to turn a branchy two-headed version history into an easy to follow linear one. A linear history is much easier for a human eye to follow and a human brain to understand. Rebase is a very safe command to use, despite some fear that people have about it. This post should explain how rebase works and clear up any misunderstandings about it. Rebase Basics The short summary of rebase is that it cuts commits out of the git history and reconnects them somewhere else. Let's say the common scenario comes up: you commit a change to the main branch of a repository, you then run  git fetch , and in come a couple changes that other people made on the main branch. If your commit is version 46f and the others that just came in on the fetch are versions ef9 and 4a2, your version history might look like this: The main branch now has two heads, 46f and 4a2. You can run  git rebase  to disconnect your commit from version d88 and connect i
Read more