Hardy Heron...

The Update Manager gets its lists, sometimes asks for password, and
just hangs until a quit is forced. Synaptic is given up on after about
10 seconds, and Add/Remove Applications produces the lists, but won't
add or remove anything. Are they all related? More importantly, is
there a cure?

Mark illuminated alt.os.linux.ubuntu by typing:
> Hardy Heron...
>
> The Update Manager gets its lists, sometimes asks for password, and
> just hangs until a quit is forced. Synaptic is given up on after about
> 10 seconds, and Add/Remove Applications produces the lists, but won't
> add or remove anything. Are they all related? More importantly, is
> there a cure?

Yes. They are all related.

We've had similar issues in here recently. They all relate to sudo
checking the /etc/network/hosts file.

Basically, if the hosts file isn't passing information. then sudo will
not give adminsitrative access.

One way to check if it's this issue is to open a terminal

Applications -> Accessories -> Terminal

Type in (without the leading "$" sign)

$ sudo synaptic...

If you get an error like
"sudo: unable to resolve host {MARKSHOSTNAMEHERE}"
You've got the same issue.

If not, copy the output and paste here.

If you have the same error
Post the output of (in a terminal again)
$ cat /etc/network/interfaces

As a follow up to the post and I'll attempt to help you fix it.

On Tue, 10 Jun 2008 18:09:12 +0100, Mark wrote:

> Hardy Heron...
>
> The Update Manager gets its lists, sometimes asks for password, and just
> hangs until a quit is forced. Synaptic is given up on after about 10
> seconds, and Add/Remove Applications produces the lists, but won't add
> or remove anything. Are they all related?

Yes

> More importantly, is there a cure?

Might want to try the following:

http://www.joewein.net/blog/2008/05/...how-to-fix-it/

On Tue, 10 Jun 2008 18:26:07 +0000, Moog wrote:

> $ sudo synaptic...

sudo: synaptic...: command not found

just to be pedantic, lose the ellipses ;-)

propman illuminated alt.os.linux.ubuntu by typing:
> On Tue, 10 Jun 2008 18:09:12 +0100, Mark wrote:
>> Yes
>> Might want to try the following:
>
> [..]

Actually, that advice isn't particularly good.

It should read

127.0.0.1 localhost
xxx.xxx.xxx.xxx mycomputername.mydomain

Which is is not limited to the 127 address range, but could be
10.x.x.x or 192.xxx.xxx.xxx (as examples)

The best way to solve it (without losing your correctly labeled
domain-name)

127.0.1.1 mycomputername mycomputername.mydomain

Obviously the 127.0.1.1 should be edited to match your own local
network(s)

For instance, mine reads
127.0.0.1 localhost
192.168.1.15 hardy hardy.mooggravy

Also, the reason we should work directly with the output of
$ cat /etc/hosts
and advise accordingly is due to the likely presence of
IPV6 entries

HTH.

Trevor Best illuminated alt.os.linux.ubuntu by typing:
> On Tue, 10 Jun 2008 18:26:07 +0000, Moog wrote:
>
>> $ sudo synaptic...
>
> sudo: synaptic...: command not found
>
> just to be pedantic, lose the ellipses ;-)

It's those bloody fat fingers again!!!11!!one!!

On Tue, 10 Jun 2008 19:46:53 +0000, Moog wrote:

> Trevor Best illuminated alt.os.linux.ubuntu by typing:
>> On Tue, 10 Jun 2008 18:26:07 +0000, Moog wrote:
>>
>>> $ sudo synaptic...
>>
>> sudo: synaptic...: command not found
>>
>> just to be pedantic, lose the ellipses ;-)
>
> It's those bloody fat fingers again!!!11!!one!!

May I suggest a larger keyboard for your bunch of bananas?

In message <6b7v9vF3apljtU1>
Moog <efcmoog> wrote:

[..]
>
> Applications -> Accessories -> Terminal
>
> Type in (without the leading "$" sign)
>
> $ sudo synaptic...
>
> If you get an error like
> "sudo: unable to resolve host {MARKSHOSTNAMEHERE}"
> You've got the same issue.

sudo: unable to resolve host Time

>
> If not, copy the output and paste here.
>
> If you have the same error
> Post the output of (in a terminal again)
> $ cat /etc/network/interfaces
>
> As a follow up to the post and I'll attempt to help you fix it.
>

emarkj@Time:~$ cat /etc/network/interfaces auto lo iface lo inet
loopback


iface eth0 inet static
address 192.168.1.34
netmask 255.255.255.0
gateway 192.168.1.1

auto eth0

iface eth1 inet static
address 192.168.1.34
netmask 255.255.255.0
gateway 192.168.1.1

auto eth1
emarkj@Time:~$

Mark illuminated alt.os.linux.ubuntu by typing:

>
> emarkj@Time:~$ cat /etc/network/interfaces auto lo iface lo inet
> loopback
>

Thanks. So static IP's as I though.

> iface eth0 inet static
> address 192.168.1.34
> netmask 255.255.255.0
> gateway 192.168.1.1
>
> auto eth0
>
> iface eth1 inet static
> address 192.168.1.34
> netmask 255.255.255.0
> gateway 192.168.1.1
>
> auto eth1

Can you now post the output of
$ cat /etc/hosts

We'll then edit that and get it back up to speed.

Trevor Best illuminated alt.os.linux.ubuntu by typing:
> On Tue, 10 Jun 2008 19:46:53 +0000, Moog wrote:
>
>> Trevor Best illuminated alt.os.linux.ubuntu by typing:
>>> On Tue, 10 Jun 2008 18:26:07 +0000, Moog wrote:
>>>
>>>> $ sudo synaptic...
>>>
>>> sudo: synaptic...: command not found
>>>
>>> just to be pedantic, lose the ellipses ;-)
>>
>> It's those bloody fat fingers again!!!11!!one!!
>
> May I suggest a larger keyboard for your bunch of bananas?

Does anyone sell a 40" laptop?
;-)

On Wed, 11 Jun 2008 05:33:45 +0000, Moog wrote:

> Trevor Best illuminated alt.os.linux.ubuntu by typing:
>
> Does anyone sell a 40" laptop?
> ;-)

I could imagine Dom Jolly on a train with an annoyingly loud keyboard
click and a 40" screen that gets in everyone's way.

Mark wrote:
[..]
>
> auto eth0
>
> iface eth1 inet static
> address 192.168.1.34
> netmask 255.255.255.0
> gateway 192.168.1.1
>
> auto eth1
> emarkj@Time:~$


Why do you have the same IP assigned to two network interface adapters?

Certainly you don't expect that to work?!

Trevor Best illuminated alt.os.linux.ubuntu by typing:
> On Wed, 11 Jun 2008 05:33:45 +0000, Moog wrote:
>> I could imagine Dom Jolly on a train with an annoyingly loud keyboard
> click and a 40" screen that gets in everyone's way.

Indeed. With the Windows "start up" theme pounding out of a 1000 watt
attached PA system.

In message <6b96d3F39a3lbU2>
Moog <efcmoog> wrote:

> Mark illuminated alt.os.linux.ubuntu by typing:
>> Thanks. So static IP's as I though.
>> Can you now post the output of
> $ cat /etc/hosts

emarkj@Time:~$ cat /etc/hosts 127.0.0.1 localhost 127.0.1.1
Time.Poppyland

# The following lines are desirable for IPv6 capable hosts
::1 ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters
ff02::3 ip6-allhosts
192.168.1.2 Dell
192.168.1.10 Kinetic300
192.168.1.25 Workshop
192.168.1.40 Shack
192.168.1.30 Compaq
192.168.1.14 OWW
192.168.1.101 sohonas101
emarkj@Time:~$

>
> We'll then edit that and get it back up to speed.
>
If you say so :-)

Mark illuminated alt.os.linux.ubuntu by typing:
[..]
> 192.168.1.2 Dell
> 192.168.1.10 Kinetic300
> 192.168.1.25 Workshop
> 192.168.1.40 Shack
> 192.168.1.30 Compaq
> 192.168.1.14 OWW
> 192.168.1.101 sohonas101
> emarkj@Time:~$
>
> If you say so :-)

Excellent. OK. I'll post what you need to do.

First off, edit your Hosts file

$ gksudo edit /etc/hosts

if you get the authentication error, don't worry gedit should still
start. If it doesn't, you'll need to log in to recovery mode. This can
be found by rebooting and selecting the recovery mode entry in the
grub boot menu.
The command to edit while in recovery mode is slightly different and
gives you a cli text editor.
$ nano /etc/hosts
(You don't need sudo as you are already logged in as root)

Copy and paste everything between the "= signs"

============
127.0.0.1 localhost
127.0.1.1 Time Time.Poppyland

# Uncomment the following line and comment (place a # before it)
# out the line starting "127.0.1.1" if this edit doesn't work
# 192.168.1.34 Time Time Poppyland

# The following lines are desirable for IPv6 capable hosts
::1 ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters
ff02::3 ip6-allhosts
192.168.1.2 Dell
192.168.1.10 Kinetic300
192.168.1.25 Workshop
192.168.1.40 Shack
192.168.1.30 Compaq
192.168.1.14 OWW
192.168.1.101 sohonas101
=============

NOTE: I've left an alternative configuration in as the 127.0.1.1
doesn't always work. Also, you seem to be using the same static IP so
the second commented line will certainly work.

Save the file

You should be able to sudo again. (If you had to do this in recovery
mode you will need to reboot.

Any problems, let me know.