Pat,

I remember having a ton of DNS issues for a while (they're all cleared
up, but for the life of me I wouldn't be able to tell you how), and
all the resolv.conf stuff sounds all too familiar. I use static DNS
(OpenDNS is a good DNS server, Google has a DNS server too) and I
haven't had any troubles for 3 weeks so far.

James

On Sun, Jan 17, 2010 at 4:23 PM, phickel <email address hidden> wrote:
> 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
>
> --
> USB device insertion causes total system lockup on Ubuntu 9.10
> https://bugs.launchpad.net/bugs/469376
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in Linux Hotplug Scripts: Confirmed
> Status in ModemManager (with NetworkManager support): New
> Status in udev - /dev/ management daemon: Confirmed
> Status in Ubuntu: Confirmed
>
> Bug description:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
>  affects udev
>
>  affects hotplug
>
>  affects ubuntu 9.10
>
> On two separate systems I have upgraded from 9.04 to 9.10 I get a
> complete, immediate and total system lockup when I install a specific
> device in a USB port.    The device is an AT&T Quicksilver GSM/HSDPA
> Cellular modem, on 8.10 and 9.04 systems, lsusb shows the device as "Bus
> 002 Device 006: ID 0af0:d033 Option".
>
> On 8.10 and 9.04 systems the device initially shows up as a CDROM
> containing the driver and application software needed on an MS Windows
> box.    There is a linux package ( Ozerocdoff found at
> http://pharscape.org/Quicksilver.html ) from the real device
> Manufacturer "Option" which uses udev to disable this "zerocd" and then
> the Option Cellular Modem appears which works with the linux hso kernel
> module.   On a 9.10 system with or without Ozerocdoff installed I get
> the lockup even before the CDROM or Modem appears or is logged.
>
> The device worked fine in the same systems before the 9.04 to 9.10
> upgrade.  Other USB devices work fine under 9.04 and 9.10.  I have not
> yet tried on a fresh 9.10 install only 9.04 to 9.10 upgrades.
>
> The lockup is immediate and total.    The only way I have found to
> regain access to the systems is to remove the device, then do a hard
> power cycle.
>
> I cannot identify or recover any meaningful details from the log files
> in /var/log.
>
> I would appreciate any clues on how I can capture better debug
> information on this situation.  The immediate and total system lockup
> has me stumped for where to go from here.    I do realize the above is
> insufficient to work with, I am asking for how to capture better
> information for a proper bug report.
>
> Thank you;
>
> Patrick Hickel
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.9 (GNU/Linux)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
>
> iEYEARECAAYFAkrt7YcACgkQGcFsRP9ZxTqsmQCfW99eDBuSwZKd1NWfnrdr9NZu
> /KcAnA86BvzDb0k78zJvnfQOIH1e4ia8
> =Q/Vp
> -----END PGP SIGNATURE-----
>
> To unsubscribe from this bug, go to:
> https://bugs.launchpad.net/hotplug/+bug/469376/+subscribe
>