Thank you for following up. This bug has not come up in Lucid.
My last comment included the instructions on how I fixed this:
Please close this bug...
After doing several more searches I found this website (it's a
RedHat support
forum): https://bugzilla.redhat.com/show_bug.cgi?id=449268
A user on it had similar problems with sound, but only with
certain video formats (Flash). This suggestion was made:
Comment #4 From Bastien Nocera 2008-06-02 05:26:42 EDT
---
Could you please try running gstreamer-properties, and
setting the default output to autodetect?
I then realized that even though every other application on my
computer was playing sound, Totem may be expecting a certain
setting which is preventing it from playing. I also realized
that with other user's sessions, like Root and Guest, that they
have not had the sound properties modified.
I reset the sound properties to autodetect like Bastien Nocera
recommended (I used gnome-sound-properties instead) and tested
Totem again. The sound works fine now.
In my opinion, this is still a bug that Totem does not use the
preferred sound output device as selected in
gnome-sound-properties. It would benefit Totem to have a sound
option which could override the sound properties as well. By
doing so the sound on the computer could work with the preferred
device while Totem could be configured for something completely
different. A scenario would be if you have multiple sound output
devices.
Thank you,
Allan Bogh
On Fri, 2010-07-02 at 15:09 +, Pedro Villavicencio wrote:
Thank you for taking the time to report this bug and helping to make
Ubuntu better. A new version of totem is available in both Lucid and
Maverick and we are wondering if this is still reproducible in any of
those versions, May you please test and give us of feedback about it?
Thanks in advance.
** Changed in: totem (Ubuntu)
Status: New = Incomplete
--
Volume control and sound missing from Totem. All other video/music players work
fine.
https://bugs.launchpad.net/bugs/367718
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
