*** This bug is a duplicate of bug 32906 ***
https://bugs.launchpad.net/bugs/32906
bluebox was the hostname when i installed feisty.
IWNETZ was the Workgroup when i used samba to connect with vmware.
System5 is the hostname now (/etc/hostname), but i don't remember when and how
i changed it.
*** This bug is a duplicate of bug 32906 ***
https://bugs.launchpad.net/bugs/32906
Do you know where "System5' comes from? Is that your actual hostname
which is set in /etc/hostname? Where and how did you set it?
** Changed in: sudo (Ubuntu)
Status: New => Incomplete
** This bug has b
i had the same issue/bug. trying your approach resolved the problem; or should
i say the "host" .
good one, kudos to you. hopefully someone is paying attention since this
single bug renders the system unable to complete the upgrade process just to
say the least.
--
dist-upgrade changes hostna
Related bug: sudo shouldn’t ABSOLUTELY NEED to look up the host it’s
running on https://launchpad.net/bugs/32906
--
dist-upgrade changes hostname in /etc/hosts breaking sudo
https://bugs.launchpad.net/bugs/178831
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I had the same problem with some odd effects.
barcc:~$ cat /etc/hosts
127.0.0.1 localhost
127.0.1.1 bluebox.IWNETZ
...
1) After installing sudo 1.6.9p9-1ubuntu1:
barcc:~$ sudo ls
sudo: unable to resolve host System5
barcc:~$ gksudo gedit test&
(nothing happens, i have to do: killall gksudo
