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 120202 - Nautilus 2.3.8 (all?) locks up on sound preview if esd is paused.
Nautilus 2.3.8 (all?) locks up on sound preview if esd is paused.
Status: RESOLVED OBSOLETE
Product: nautilus
Classification: Core
Component: [obsolete] Sound
2.3.x
Other Linux
: High major
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2003-08-19 02:57 UTC by Brian Kerrick Nickel
Modified: 2005-05-17 07:38 UTC
See Also:
GNOME target: ---
GNOME version: 2.9/2.10



Description Brian Kerrick Nickel 2003-08-19 02:57:32 UTC
First off, I plea with you not to say "Oh its another application's fault"
and ignore this. Everyone else has done this with their software, and this
problem will never be solved on any level if that mindset is kept.


If esound is paused (only applications that do this are built on
gstreamer), and you move your mouse over an audio file in nautilus,
nautilus will freeze completely until esound is unpaused.

Steps to repeat:
 Run rhythmbox, start a song, and pause.
 Run nautilus, find an audio file, and mouse over.
 Test nautilus's responsiveness.
 Unpause rhythmbox.

Possible solutions:
 1) Run the audio in a seperate, killable program or thread. The 
    thread/program will then be killed when the mouse leave the icon.
 2) Yell at the rhythmbox team to set audiosink to NULL when pausing.
 3) Yell at the gstreamer team to release esd output when its not in use.

 (2 and 3 are optional, yet recommended)

This problem was bad when it effected non-critical programs, but now its
effecting core applications, and that is unacceptable.
Comment 1 Brian Kerrick Nickel 2003-08-19 03:22:51 UTC
OK, bug 98558 was solved in rhythmbox CVS (many, many thanks to
walters), but the problem will continue to arise in gstreamer software
and should be fixed on all ends.
Comment 2 Elijah Newren 2003-08-19 16:27:32 UTC
I believe Major is a more appropriate severity than critical, so I'm
making the change.  However, I also think priority should be high. 
I'm also going to add the bugsquad keyword.
Comment 3 Sebastien Bacher 2005-05-15 20:33:32 UTC
is that still an issue? 
Comment 4 Brian Kerrick Nickel 2005-05-16 20:32:06 UTC
I don't know if it is still an issue, but the programs that caused the problem
(Rhythmbox and Muine) now handle paused pipelines correctly, so I'd just say
WONTFIX, and it can be reopened if the problem pops up again in the future.
Comment 5 Sebastien Bacher 2005-05-17 07:38:57 UTC
right, I'm closing the bug for the moment. Feel free to reopen if that's an
issue again for you