* esdlib.c: Check if the esd binary exists at all. If not, forego forking
a shell and trying to execute it. This both improves startup time and also
avoids the /bin/sh: /usr/bin/esd: not found warning. (LP: #134641)
I haven't looked at the source at all, but this makes me wonder if
** Changed in: libgnome (Ubuntu)
Assignee: (unassigned) = Martin Pitt (pitti)
Status: Triaged = In Progress
Target: None = ubuntu-7.10-rc
--
[tribe 5] any time I open a document in gedit (from the shell) I get
/usr/bin/esd: not found
https://bugs.launchpad.net/bugs/134641
You
This actually comes from the esd client lib.
** Changed in: esound (Ubuntu)
Sourcepackagename: libgnome = esound
** Changed in: esound (Ubuntu)
Importance: Wishlist = Low
** Changed in: esound (Ubuntu)
Status: In Progress = Fix Released
--
[tribe 5] any time I open a document in
esound (0.2.38-0ubuntu4) gutsy; urgency=low
* esdlib.c: Check if the esd binary exists at all. If not, forego forking
a shell and trying to execute it. This both improves startup time and also
avoids the /bin/sh: /usr/bin/esd: not found warning. (LP: #134641)
-- Martin Pitt [EMAIL
I get this too from all gnome programs.
If not using esd is the intended behaviour for gnome in gutsy, then why
is it producing warnings?
--
[tribe 5] any time I open a document in gedit (from the shell) I get
/usr/bin/esd: not found
https://bugs.launchpad.net/bugs/134641
You received this bug
Thank you for your bug. That's not really an error, rather an indication
of libgnome that esd is not used, why do you think that's an issue?
** Changed in: libgnome (Ubuntu)
Sourcepackagename: gedit = libgnome
Importance: Undecided = Wishlist
Status: New = Triaged
--
[tribe 5] any
