scarecrow Posted November 15, 2009 Report Share Posted November 15, 2009 (edited) You will definitely have networking issues with that hosts file. Consider changing it to 127.0.0.1 localhost host-001 and restarting the network service. Edited November 15, 2009 by scarecrow Quote Link to comment Share on other sites More sharing options...
Kieth Posted November 15, 2009 Author Report Share Posted November 15, 2009 OK, I got it changed in MCC. [root@host-001 ~]# cat /etc/hosts# generated by drakhosts 127.0.0.1 localhost host-001 Thanks, Kieth Quote Link to comment Share on other sites More sharing options...
Kieth Posted November 17, 2009 Author Report Share Posted November 17, 2009 (edited) At times I still have the "host" problem. Not always, but maybe every other time. [root@host-001 ~]# cat /etc/hosts# generated by drakhosts 127.0.0.1 localhost host-001 [kieth@localhost ~]$ firefox_IceTransSocketUNIXConnect: Cannot connect to non-local host localhost.localdomain _IceTransSocketUNIXConnect: Cannot connect to non-local host localhost.localdomain (firefox:3090): GnomeUI-WARNING **: While connecting to session manager: Could not open network socket. (firefox:3090): Gdk-WARNING **: XID collision, trouble ahead (firefox:3090): Gdk-WARNING **: XID collision, trouble ahead Edited November 17, 2009 by Kieth Quote Link to comment Share on other sites More sharing options...
ianw1974 Posted November 17, 2009 Report Share Posted November 17, 2009 Mine looks like this: 127.0.0.1 esprit localhost.localdomain localhost esprit being my hostname for the machine, but you can put host-001 or whatever your hostname is. Note, I also have the localhost.localdomain in there too, and I don't have problems with Firefox. Maybe, reset yours something like: 127.0.0.1 host-001 localhost.localdomain localhost and see what happens. Quote Link to comment Share on other sites More sharing options...
Kieth Posted November 18, 2009 Author Report Share Posted November 18, 2009 Well, so far it seems to be working. Thanks. [root@host-001 ~]# cat /etc/hosts# generated by drakhosts 127.0.0.1 host-001 localhost.localdomain localhost [kieth@host-001 ~]$ firefox Quote Link to comment Share on other sites More sharing options...
scarecrow Posted November 18, 2009 Report Share Posted November 18, 2009 The sequennce of the entries in the HOSTS file is not critical, and if you have no domain/ LAN name defined at your router, then the "localhost.localdomain" part does nothing useful. Anyway, if this is working better for you then defintely keep it. Some DE's like Gnome and XFCE4 definitely need the machine name pinned in the /etc/hosts file to behave properly. Quote Link to comment Share on other sites More sharing options...
ianw1974 Posted November 18, 2009 Report Share Posted November 18, 2009 Theoretically the order shouldn't cause a problem, but obviously in this case it does :D Strange huh! Quote Link to comment Share on other sites More sharing options...
speedball2 Posted November 18, 2009 Report Share Posted November 18, 2009 I bet your flash plugin problem is fixed now too :) Quote Link to comment Share on other sites More sharing options...
Kieth Posted November 18, 2009 Author Report Share Posted November 18, 2009 (edited) Well, like before, sometimes it's OK and sometimes no. [root@host-001 ~]# cat /etc/hosts# generated by drakhosts 127.0.0.1 host-001 localhost.localdomain localhost [kieth@host-001 ~]$ firefox_IceTransSocketUNIXConnect: Cannot connect to non-local host localhost.localdomain _IceTransSocketUNIXConnect: Cannot connect to non-local host localhost.localdomain (firefox:3588): GnomeUI-WARNING **: While connecting to session manager: Could not open network socket. Flash plugin? Nope, after I wrote my last post, I tried to get it working, but to no avail. Edited November 18, 2009 by Kieth Quote Link to comment Share on other sites More sharing options...
speedball2 Posted November 18, 2009 Report Share Posted November 18, 2009 Hmm, maybe there's more permission problems? You changed UID & GID to 10001. Perhaps some files in your home partition are still set to the old IDs? Quote Link to comment Share on other sites More sharing options...
Kieth Posted November 19, 2009 Author Report Share Posted November 19, 2009 Hey, maybe that's the problem!! I opened dolphin and clicked on kieth. Then I right clicked the mouse and choose permissions. On the top, under "access permissions", the owner can view and modify content. The group can only view content (as well as others). Below, under "ownership", there it shows the owner being kieth and the group being 500 (so you were right speedball2!). Under "access permissions", should I change the group to: Can view and modify; and under "ownership", change the group to kieth? I would also apply the changes to all sub folders. Quote Link to comment Share on other sites More sharing options...
scarecrow Posted November 19, 2009 Report Share Posted November 19, 2009 In a root console: # chown -R kieth:kieth /home/kieth This WILL do some damage, if you use fuse modules to mount filesystems (the owner on those mountpoints should be "nobody" and the permissions 0666), but other than that, it will fix any other outstanding permissions' issues. Quote Link to comment Share on other sites More sharing options...
Kieth Posted November 22, 2009 Author Report Share Posted November 22, 2009 OK, the other day I ran the command # chown -R kieth:kieth /home/kieth. So far no adverse effects, but firefox continues to complain about not connecting to the local host. [kieth@host-001 ~]$ firefox _IceTransSocketUNIXConnect: Cannot connect to non-local host localhost.localdomain _IceTransSocketUNIXConnect: Cannot connect to non-local host localhost.localdomain (firefox:1441): GnomeUI-WARNING **: While connecting to session manager: Could not open network socket. But seamonkey doesn't have this problem. [kieth@host-001 ~]$ seamonkey So I renamed .mozilla and .mozilla2 to . . . -old, and this is what I got in console when I open firefox. [kieth@host-001 ~]$ firefox _IceTransSocketUNIXConnect: Cannot connect to non-local host localhost.localdomain _IceTransSocketUNIXConnect: Cannot connect to non-local host localhost.localdomain (firefox:1789): GnomeUI-WARNING **: While connecting to session manager: Could not open network socket. _IceTransSocketUNIXConnect: Cannot connect to non-local host localhost.localdomain _IceTransSocketUNIXConnect: Cannot connect to non-local host localhost.localdomain (firefox:1789): GnomeUI-WARNING **: While connecting to session manager: Could not open network socket. _IceTransSocketUNIXConnect: Cannot connect to non-local host localhost.localdomain _IceTransSocketUNIXConnect: Cannot connect to non-local host localhost.localdomain (firefox:1789): GnomeUI-WARNING **: While connecting to session manager: Could not open network socket I then disinstalled firefox, ran the command update-menus -v as a normal user and as root. After that I reinstalled firefox via urpmi, which also installed 2 dependencies: Preparing... ########################### 1/3: nspluginwrapper-i386 ########################### 2/3: firefox ########################### 3/3: nspluginwrapper ########################### Opening firefox in console gives me the same results: [kieth@host-001 ~]$ firefox _IceTransSocketUNIXConnect: Cannot connect to non-local host localhost.localdomain _IceTransSocketUNIXConnect: Cannot connect to non-local host localhost.localdomain (firefox:3094): GnomeUI-WARNING **: While connecting to session manager: Could not open network socket. _IceTransSocketUNIXConnect: Cannot connect to non-local host localhost.localdomain _IceTransSocketUNIXConnect: Cannot connect to non-local host localhost.localdomain (firefox:3094): GnomeUI-WARNING **: While connecting to session manager: Could not open network socket. Any ideas? Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.