Jump to content
Kieth

browsers

Recommended Posts

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 by scarecrow

Share this post


Link to post
Share on other sites

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

Share this post


Link to post
Share on other sites

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 by Kieth

Share this post


Link to post
Share on other sites

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.

Share this post


Link to post
Share on other sites

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

 

 

Share this post


Link to post
Share on other sites

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.

Share this post


Link to post
Share on other sites

Theoretically the order shouldn't cause a problem, but obviously in this case it does :D

 

Strange huh! :weird:

Share this post


Link to post
Share on other sites

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 by Kieth

Share this post


Link to post
Share on other sites

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.

Share this post


Link to post
Share on other sites

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.

Share this post


Link to post
Share on other sites

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?

Share this post


Link to post
Share on other sites

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.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...

×
×
  • Create New...