After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 358138 - plugin viewer doesn't start with blocked /dev/dsp
plugin viewer doesn't start with blocked /dev/dsp
Status: RESOLVED DUPLICATE of bug 170719
Product: totem
Classification: Core
Component: GStreamer backend
unspecified
Other Linux
: Normal normal
: ---
Assigned To: Maintainer alias for GStreamer component of Totem
Maintainer alias for GStreamer component of Totem
Depends on:
Blocks:
 
 
Reported: 2006-09-28 15:02 UTC by Christian Persch
Modified: 2006-09-28 15:51 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Christian Persch 2006-09-28 15:02:00 UTC 
When something is already using /dev/dsp (e.g. the evil flash plugin), the totem plugin viewer doesn't start up correctly: it just displays an error box saying

The Totem plugin could not startup.
The audio output is in use by another application. Please select another audio output in the Multimedia Systems Selector. You may want to consider using a sound server. [OK]

and exits when you click OK. There's no other way to get it working after /dev/dsp is free again except reload the whole page.

Instead, the viewer should just display a message inline, and stay alive with a "Retry" button.
Comment 1 Bastien Nocera 2006-09-28 15:20:33 UTC 
It should still startup with disabled sound. Reassigning to GStreamer.
Comment 2 Tim-Philipp Müller 2006-09-28 15:51:33 UTC 
This should work now with autoaudiosink from gst-plugins-good CVS (which plugs a fakesink if no usable sound output can be found).

Totem checking for sound stuff at startup no matter what is covered by bug #156576 and bug #170719, hence closing as duplicate.


*** This bug has been marked as a duplicate of 170719 ***