[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: gnome-session updated and lost sound on Sarge



Apparently, _H. S._, on 13/07/05 12:41,typed:
> I upgraded gnome-session to  2.10.0-5 last night on my Sarge, 2.6.11, on
> a PIV. After that, I logged out of Gnome and couldn't login back. The
> login process 'hanged' on the gray screen that comes just, before the
> splash screen appears.
> 
> I then deleted everything that belonged to me in /tmp (gconfd* alsa*
> .esd* orbit-* etc.) and relogged and was successful. But now sounds do
> not work. In my .xsession-erros, I get these messages:
> 
> /etc/gdm/PreSession/Default: Registering your session with wtmp and utmp
> /etc/gdm/PreSession/Default: running: /usr/X11R6/bin/sessreg -a -w
> /var/log/wtmp -u /var/run/utmp -x "/var/lib/gdm/:0.Xservers" -h "" -l
> ":0" "red"
> /etc/gdm/Xsession: Beginning session setup...
> SESSION_MANAGER=local/bijli:/tmp/.ICE-unix/8568
> ALSA lib pcm_direct.c:196:(make_local_socket) connect failed:
> /tmp/alsa-dmix-7175-1121233374-426838: No such file or directory
> ALSA lib pcm_dmix.c:834:(snd_pcm_dmix_open) unable to connect client
> esd: Esound sound daemon already running or stale UNIX socket
> /tmp/.esd/socket
> This socket already exists indicating esd is already running.
> Exiting...
> ALSA lib pcm_direct.c:196:(make_local_socket) connect failed:
> /tmp/alsa-dmix-7175-1121233374-426838: No such file or directory
> ALSA lib pcm_dmix.c:834:(snd_pcm_dmix_open) unable to connect client
> ALSA lib pcm_direct.c:196:(make_local_socket) connect failed:
> /tmp/alsa-dmix-7175-1121233374-426838: No such file or directory
> ALSA lib pcm_dmix.c:834:(snd_pcm_dmix_open) unable to connect client
> ....and so on.
> 
> 
> What do I need to do to correct this? I tried deleting
> /var/lib/alsa/asound.state and restarting alsa. No luck. Btw, when I
> login to a KDE session, sound works okay.
> 
> All help is appreciated,
> ->HS
> 


hmm ... nobody has any suggestions on how to go about solving this?

->HS

-- 
Please remove the underscores ( the '_' symbols) from my email address
to obtain the correct one. Apologies, but the fudging is to remove spam.



Reply to: