Comment 12 for bug 84876

I'm having the same problem on a fresh install of Feisty. When I tried sudo ifup lo (like Shum), it reported that interface lo already configured. Pinging my localhost did not return any errors either. I have attached the requested information. Ignore the Microcode errors in dmesg, as I have been encountering them since Dapper and haven't had a chance to fix them (they don't seem to affect anything).
In addition, when I try running gnome-settings-daemon, it returns this text:

The program 'gnome-settings-daemon' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadValue (integer parameter out of range for operation)'.
  (Details: serial 1948 error_code 2 request_code 144 minor_code 29)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the --sync command line
   option to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)
[1177278971,000,xklavier.c:xkl_engine_start_listen/] The backend does not require manual layout management - but it is provided by the applicationadam@adam-laptop:~$ gnome-settings-daemon > gsd.txt
The program 'gnome-settings-daemon' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadValue (integer parameter out of range for operation)'.
  (Details: serial 2410 error_code 2 request_code 144 minor_code 29)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the --sync command line
   option to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)