Ubuntu
esound package

esd doesn't exit automatically after log in

Bug #38244 reported by Lucas Nussbaum
12
Affects Status Importance Assigned to Milestone
esound (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Hi,

When I log in in Gnome, esd is started, but doesn't exit automatically after the delay configured in /etc/esound/esd.conf

This is extremly annoying since it prevents all other apps from using the audio device directly.

I wasn't able to determine why esd was started.

Revision history for this message
Martin Pitt (pitti) wrote :

Is that breezy or dapper? What is the content of your /etc/esound/esd.conf?

Changed in esound:
status: Unconfirmed → Needs Info
Revision history for this message
Lucas Nussbaum (lucas) wrote :

Dapper.
[esd]
auto_spawn=1
spawn_options=-terminate -nobeeps -as 1
spawn_wait_ms=100
# default options are used in spawned and non-spawned mode
default_options=

Revision history for this message
Daniel T Chen (crimsun) wrote :

1) Do you use multiple sound devices, at least one of which is hotpluggable (usb)?

2) Does the symptom described by your bug report appear from (a) fresh boot into Dapper, (b) resume from suspend, (c) resume from hibernation?

3) If you answered "yes" to question #1 and either #2b or #2c, was the hotpluggable sound device inserted before the computer resumed or after?

Revision history for this message
Lucas Nussbaum (lucas) wrote : Re: [Bug 38244] Re: esd doesn't exit automatically after log in

On 19/04/06 at 01:46 -0000, Daniel T. Chen wrote:
> 1) Do you use multiple sound devices, at least one of which is hotpluggable (usb)?

Sometimes yes, sometimes no (my webcam provides USB sound). But the
problem arises with :

- fresh boot with no webcam plugged in.
- log in into ubuntu, still no webcam
- 'ps x |grep esd'

Lucas

Lucas Nussbaum (lucas)
Changed in esound:
status: Needs Info → Unconfirmed
Revision history for this message
Andreas Lloyd (lloydinho) wrote :

I can confirm this behaviour.

Could it be because esd is used to play the Ubuntu intro sound?

Also, I've related this to Lucas' filing of this bug upstream.

Changed in esound:
status: Unconfirmed → Confirmed
Revision history for this message
sam tygier (samtygier) wrote :

This and #30578 link to the same upstream bug. are they dupes?

Revision history for this message
Lucas Nussbaum (lucas) wrote :

On 04/12/06 at 10:55 -0000, sam tygier wrote:
> This and #30578 link to the same upstream bug. are they dupes?

No they aren't. This one is an esd bug.
--
| Lucas Nussbaum
| <email address hidden> http://www.lucas-nussbaum.net/ |
| jabber: <email address hidden> GPG: 1024D/023B3F4F |

Revision history for this message
Greg Grossmeier (greg.grossmeier) wrote :

This bug was reported over a year ago and the upstream bug has not been touched in over a year also. Is this still an issue for anyone?

Revision history for this message
Luke Yelavich (themuso) wrote :

This was reported against pulseaudio in hardy, which is what will be used to handle GNOME sound events/sound output in GNOME. This has been fixed in hardy, so marking as fix released.

Changed in esound:
status: Confirmed → Fix Released
Revision history for this message
Luke Yelavich (themuso) wrote :

Sorry, slightly misread the bug, totally different issue.

Changed in esound:
status: Fix Released → Confirmed
Revision history for this message
sam tygier (samtygier) wrote :

is this still an issue? the sound system has changed a lot since 2006

Changed in esound (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
sam tygier (samtygier) wrote :

no response in a long time.

Changed in esound (Ubuntu):
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.