Don't know about Evolution because I use Mozilla Thunderbird, but if I
had to guess, I would almost be willing to bet this will be what you are
looking for, at least from your description of the problem.
1) Launch HSOconnect and bring the network up, then open a terminal
window to verify the file permissions on the "/etc/resolv.conf" file.
ls -l /etc/resolv.conf
If the mode is 600 (-rw------- )rather than the correct 644
(-rw-r--r-- ) it should be, changing the mode of the file to it's
proper setting will provide a quick temporary fix.
sudo chmod 644 /etc/resolv.conf
Firefox and Evolution should then work normally without requiring
sudo, but as I said this is only a temporary fix.
Every time you bring the network up you would have to change the file
mode again.
2) If step 1 above temporarily helped, you can elect to install another
package which will provide a permanent fix.
sudo apt-get install resolvconf
I have found the HSOconnect tools work best if you also install the
resolvconf package to maintain and update the contents of the
/etc/resolv.conf file. Without the resolvconf package installed
something in the HSOconnect stuff defaults /etc/resolv.conf to 600 every
time you use HSOconnect which breaks a lot of network things.
As a minimum, I would gracefully shutdown hsoconnect and re-boot after
installing resolvconf, but I don't know if this graceful shutdown and
reboot is actually required.
I don't remember if I re-built and re-installed the HSO packages after I
installed the resolvconf package or not. You may need to have the
resolvconf package already installed when you build and install the HSO
stuff, I just do not remember.
This potential resolvconf fix should help Evolution, Firefox and just
about any other network application.
Curt:
Don't know about Evolution because I use Mozilla Thunderbird, but if I
had to guess, I would almost be willing to bet this will be what you are
looking for, at least from your description of the problem.
Potential fix ======= ======= ======= ======= ======= ======= ======= ======
1) Launch HSOconnect and bring the network up, then open a terminal
window to verify the file permissions on the "/etc/resolv.conf" file.
ls -l /etc/resolv.conf
If the mode is 600 (-rw------- )rather than the correct 644
(-rw-r--r-- ) it should be, changing the mode of the file to it's
proper setting will provide a quick temporary fix.
sudo chmod 644 /etc/resolv.conf
Firefox and Evolution should then work normally without requiring
sudo, but as I said this is only a temporary fix.
Every time you bring the network up you would have to change the file
mode again.
2) If step 1 above temporarily helped, you can elect to install another
package which will provide a permanent fix.
sudo apt-get install resolvconf
I have found the HSOconnect tools work best if you also install the
resolvconf package to maintain and update the contents of the
/etc/resolv.conf file. Without the resolvconf package installed
something in the HSOconnect stuff defaults /etc/resolv.conf to 600 every
time you use HSOconnect which breaks a lot of network things.
As a minimum, I would gracefully shutdown hsoconnect and re-boot after
installing resolvconf, but I don't know if this graceful shutdown and
reboot is actually required.
I don't remember if I re-built and re-installed the HSO packages after I
installed the resolvconf package or not. You may need to have the
resolvconf package already installed when you build and install the HSO
stuff, I just do not remember.
This potential resolvconf fix should help Evolution, Firefox and just
about any other network application.
======= ======= ======= ======= ======= ======= ======= ==
I strongly suspect the above will fix your problem. If this really is
the problem then the breakage is a lot bigger than just Evolution and
Firefox.
If this does not fix it, I have something else you can try which is
Firefox specific.
Later
Pat Hickel