Ticket #281 (closed defect: fixed)

Opened 4 months ago

Last modified 3 months ago

Applications are sluggish because of disabled network access to local sound devices

Reported by: rodrigo Assigned to: lennart
Priority: normal Milestone:
Component: paprefs Severity: normal
Keywords: Cc:

Description

In openSUSE 11.0 betas we found out GNOME applications that use esound got sluggish because of the remote access to local sound devices being disabled by default. Enabling that in 'Configure Local Sound Server' from padevchooser fixed the problem.

Attaching a patch we wrote for it, but I'm sure there is an underlying reason for it, since it seems to slow down when that is not enabled.

Attachments

paprefs-enable-remote-access-by-default.patch (0.9 kB) - added by rodrigo on 04/23/08 12:53:26.
Patch with work around to enable that setting by default

Change History

04/23/08 12:53:26 changed by rodrigo

  • attachment paprefs-enable-remote-access-by-default.patch added.

Patch with work around to enable that setting by default

04/23/08 12:53:56 changed by rodrigo

  • component changed from daemon to paprefs.

(follow-up: ↓ 3 ) 04/23/08 15:00:21 changed by coling

In SuSE what path does ESD use for it's socket?

PA assumes that you have patched your esound package to enable per-user esound sockets (e.g. /tmp/.esd-501/ rather than just the default /tmp/.esd/. This is to allow for user switching and running >1 "esd" process (or rather >1 PA process providing esd capabilities!).

You can configure pulse (0.9.10) to use the old socket name but most people are patching esound instead. IIRC it's in the esound CVS.

This may be unrelated but figured I'd mention it.

(in reply to: ↑ 2 ) 05/09/08 07:56:03 changed by captain.magnus

  • status changed from new to closed.
  • resolution set to fixed.

Replying to coling:

In SuSE what path does ESD use for it's socket?

/tmp/.esd

PA assumes that you have patched your esound package to enable per-user esound sockets (e.g. /tmp/.esd-501/ rather than just the default /tmp/.esd/. This is to allow for user switching and running >1 "esd" process (or rather >1 PA process providing esd capabilities!). You can configure pulse (0.9.10) to use the old socket name but most people are patching esound instead. IIRC it's in the esound CVS. This may be unrelated but figured I'd mention it.

It wasn't unrelated :-) Works fine now after we found out about the ESD socket bit.