Jon N wrote: > Dec 21 16:36:38 (none) lightdm: pam_unix(lightdm-greeter:session): session > opened for user lightdm by (uid=0)
"(none)"? It thinks the hostname is "(none)"? That's not right. Unless you named your new system "(none)" with the parens which shouldn't work. > Dec 21 16:36:38 (none) avahi-daemon[2285]: Server startup complete. > Host name is none.local. Local service cookie is 3853520009. "none.local"? > Based on the time stamp these happened during the most recent boot. > All the previous lines have 'localhost-01' then all the subsequent > lines have '(none)'. I think there is an error with setting the new name. Just for verification what does hostname say? $ hostname It should return the hostname of your system. If it doesn't then something is wrong with /etc/hostname. I am thinking the hostname is empty for some reason. > One other thing - I rebooted again and tried the command 'service > lightdm restart'. It worked, sort of. I was able to log in, but my > desktop didn't start right. There were no panels, and when I tried to > run a Mate configuration app they wouldn't run. I switched back to > the virtual terminal I ran 'service lightdm restart' from, and there > were no error messages. Darn :-(. Usually the X system communicates with itself through a communication socket. The network communication socket connection could be tcp over the network or it could be a local unix comain socket. As I recall the hostname is encoded in there somewhere. Meaning that if you change the hostname while the system is up and running that it loses communication. As I recall this causes current windows to continue but causes failure to open any new windows. You can close windows but can't open them. But that knowledge is from years ago and things might be different now. Now everything should use a local unix domain socket by default for speed and security. Bob
signature.asc
Description: Digital signature
