Le mercredi 06 janvier 2010 à 22:08 +0100, Andrzej Zięba a écrit :
> Josselin Mouette wrote:
> > Probably another functionality broken by the uncoordinated bindv6only
> > change.
>
> Yes, you are right. Setting bindv6only to 0 makes the problem go away.
> As I understand gdm should be able to list
Josselin Mouette wrote:
Probably another functionality broken by the uncoordinated bindv6only
change.
Yes, you are right. Setting bindv6only to 0 makes the problem go away.
As I understand gdm should be able to listen to ipv6 and ipv4 sockets at
the same time with bindv6only turned on, so the
Le samedi 02 janvier 2010 à 18:54 +0100, Andrzej Zięba a écrit :
>
> so I thought it should listen, but I have also done network sniff with
> wireshark on the server and I get:
>
> 4 0.004196192.168.178.22 192.168.178.23 XDMCP Query
> 5 0.004251192.168.178.23 192.168
Package: gdm
Version: 2.20.10-1
Severity: normal
--- Please enter the report below this line. ---
I have turned debug logging on and this is what I get in the syslog:
(...)
Jan 2 16:11:48 azieba gdm[2002]: DEBUG: Attempting to parse key string:
xdmcp/Enable=false
Jan 2 16:11:48 azieba gdm[
4 matches
Mail list logo
