Magically, turning off ESD has also worked for me... after changing my
windows client machine, I was back at the problem even with no firewall.
Quite an elusive bug!
Thanks,
jaime
El mar, 20-02-2007 a las 08:21 +0000, sleuth escribió:
> After spending all day fighting nomachines windows client, freenx
> server, nomachines nxserver, on opensuse 10.2 with gnome. I found that
> turning off ESD in the gnome control center sound screen solved the
> error described above. I had tried commenting the hosts file for IP6 and
> it didn't work. Additionally I found that when logged in locally with a
> gnome session, when the error was encountered on the remote machine, a
> gnome control center window popped up.
>
--
Jaime Alemany
Lunático Astronomía S. L.
www.lunatico.es
TFN: +34 91 859 5567
FAX: +34 91 790 3589
Magically, turning off ESD has also worked for me... after changing my
windows client machine, I was back at the problem even with no firewall.
Quite an elusive bug!
Thanks,
jaime
El mar, 20-02-2007 a las 08:21 +0000, sleuth escribió:
> After spending all day fighting nomachines windows client, freenx
> server, nomachines nxserver, on opensuse 10.2 with gnome. I found that
> turning off ESD in the gnome control center sound screen solved the
> error described above. I had tried commenting the hosts file for IP6 and
> it didn't work. Additionally I found that when logged in locally with a
> gnome session, when the error was encountered on the remote machine, a
> gnome control center window popped up.
>
--
Jaime Alemany
Lunático Astronomía S. L.
www.lunatico.es
TFN: +34 91 859 5567
FAX: +34 91 790 3589