On Thu, 01.11.07 12:36, Juergen Bausa (Juergen.Bausa at web.de) wrote: > Hi, > > I wanted to switch from esd to pulseaudio on my debian etch system. So I > stopped the esd (which worked fine before, using alsa as backend), installed > all the pulseaudio packages, added myself to the pulse, pulse-rt and pulse-access > groups and started the daemon. However, I cant hear any sound: Please make sure to run PA 0.9.7 and provide me with the output of pulseaudio -vv when you try to acces it with "pacat" or suchlike. > So, pulseaudio seems to run. These are the messages from syslog, when starting the system: > ------------------------------------------ > Nov 1 12:29:14 lisa pulseaudio[3775]: alsa-util.c: device doesn't support 44100 Hz, changed to 48000 Hz. > Nov 1 12:29:14 lisa pulseaudio[3775]: alsa-util.c: device doesn't support 44100 Hz, changed to 48000 Hz. > Nov 1 12:29:14 lisa pulseaudio[3775]: sound-file.c: Failed to open file /usr/share/sounds/gtk-events/activate.wav > Nov 1 12:29:14 lisa pulseaudio[3775]: x11wrap.c: XOpenDisplay() failed > Nov 1 12:29:14 lisa pulseaudio[3775]: module.c: Failed to load module "module-x11-bell" (argument: "sample=x11-bell"): initialization failed. > Nov 1 12:29:14 lisa pulseaudio[3775]: x11wrap.c: XOpenDisplay() failed > Nov 1 12:29:14 lisa pulseaudio[3775]: module.c: Failed to load module "module-x11-publish" (argument: ""): initialization failed. > Nov 1 12:29:14 lisa pulseaudio[3775]: module-gconf.c: Unable to read or parse data from client. > Nov 1 12:29:14 lisa pulseaudio[3775]: module.c: Failed to load module "module-gconf" (argument: ""): initialization failed. > Nov 1 12:29:14 lisa pulseaudio[3775]: main.c: Failed to load sound file. > Nov 1 12:29:14 lisa pulseaudio[3775]: main.c: Module load failed. > Nov 1 12:29:37 lisa pulseaudio[3775]: protocol-esound.c: kicked client with invalid authorization key. > > ------------------------------------------ > The 'authorization' messages seems to come from kde, which tries to connect to esd, which is emulated by pulseaudio. > > Any hints? The ESD errors are authentication errors. Is PA running as differnt user as your clients? If so you have to make sure to copy the same ~/.esd_auth to all users home directories that shall have access. Lennart -- Lennart Poettering Red Hat, Inc. lennart [at] poettering [dot] net ICQ# 11060553 http://0pointer.net/lennart/ GnuPG 0x1A015CC4
