|
From: Luis G. <lui...@us...> - 2011-04-07 22:27:56
|
Hi, Stephen. Upon further investigation, the problem appears when NetworkManager modifies /etc/hosts so the machine name is both associated to an IP and an IPv6 address, like in the following example: $ cat /etc/hosts 192.168.0.128 advent 127.0.0.1 localhost.localdomain localhost localhost4 ::1 advent localhost6.localdomain6 localhost6 In this situation both DSSI host and GUI can't communicate: the host launches the GUI process, but the startup protocol never progresses to the point the GUI is displayed on the screen. I don't know enough of the internals of name resolution as to hazard a guess about why a configuration like that is a problem. Apparently this causes problems with other software too, notably kerberos. As of 01/2011, NM developers seem to have given up on updating /etc/hosts automatically. https://bugzilla.redhat.com/show_bug.cgi?id=648725 Once the machine name is not associated to the IPv6 loopback address anymore the problem disappears. $ cat /etc/hosts 192.168.0.128 advent 127.0.0.1 localhost.localdomain localhost localhost4 ::1 localhost6.localdomain6 localhost6 I am not sure if there is something that can be done on liblo's side to make it more resilient to situations like this or not. Regards, Luis |