failed esd on Linux Gnome 2.4 can lock Mozilla and Firefox



14 years ago
12 years ago


(Reporter: Gary Lawrence Murphy, Unassigned)


Firefox Tracking Flags

(Not tracked)




14 years ago
User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040301 Firefox/0.8
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040301 Firefox/0.8

There are many situations when the ESounD (esd) becomes unstable -- it can be as
simple as exiting a song in XMMS at the wrong point, but when this happens,
Mozilla (or Firefox) will lock solid as soon as you enter any _keystrokes_
(either location bar or in a form).  Ctrl-C or Kill will exit, so it's not a
hard lock, but it appears that you cannot restart Mozilla as it will always have
that same behaviour.

The bug is reproducible only once you have an esd process failed, and I haven't
yet figured out how to do that, but we may not need to:  I ran Mozilla in debug
mode, waited for the lockup, then did a bt and found ...

#0  0xffffe410 in ?? ()
#1  0x00000004 in ?? ()
#2  0x00000004 in ?? ()
#3  0xbfffbf68 in ?? ()
#4  0x4020ec7b in __read_nocancel () from /lib/tls/
#5  0x41f702e4 in esd_send_auth () from /usr/lib/
#6  0xbfffbf68 in ?? ()
#7  0x00000004 in ?? ()

my guess is the solution is to impose a timeout or some other protection on
esd_send_auth, and to either kill the esd (user owned) process or to just ignore
sound and move on.

Reproducible: Sometimes
Steps to Reproduce:
1. it's unknown how to crash esd
Product: Browser → Seamonkey
This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Last Resolved: 12 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.