Thank you for reporting this bug to Ubuntu. Intrepid Ibex 8.10 reached EOL on
30 March 2010.
Please see this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
Please feel free to report any other bugs you may find.
Thank you.
** Changed in: network-manager
I realized I had made a mistake.
Intrepid Ibex 8.10 will reach EOL on 30 APRIL 2010.
Sorry for this.
Anyway, I think that one month doesn't make any difference now.
--
NM 0.7 sets hostname to localhost.localdomain instead of what is in
/etc/hostname
https://bugs.launchpad.net/bugs/276253
You
If you clone your hard drive with something like rsync that tries to
be smart about ownership of files, then you might be running into
problems because of incorrect ownership of files on the cloned drive
that snowball into problems with network manager. Eg, I cloned a hard
drive with rsync via an
** Branch linked: lp:ubuntu/network-manager
--
NM 0.7 sets hostname to localhost.localdomain instead of what is in
/etc/hostname
https://bugs.launchpad.net/bugs/276253
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
this is definitly fixed in latest NM. I dont know the status in
intrepid. doesnt the workaround given in summary work? Are you using the
ifupdown plugin at all?
** Changed in: network-manager (Ubuntu)
Status: Confirmed = Fix Released
--
NM 0.7 sets hostname to localhost.localdomain
it could be that nm-system-settings process crashes for you. if no such
process is running, please try to run nm-system-settings with sudo from
command line and see if it goes down.
--
NM 0.7 sets hostname to localhost.localdomain instead of what is in
/etc/hostname
Hello Alexander,
This is still an issue for me and others in 8.10 (Intrepid). Of note is
that if I disable Network Manager then I am able to surf the Internet
just fine:
https://bugs.launchpad.net/ubuntu/+source/network-
manager/+bug/276253/comments/12
Is there any other information I can
I did a upgrade from 8.04 to 9.04, clearly reproducing this issue as
well. A fresh install of NM isn't fixing my issues. Additionally,
[keyfile] workaround is not helping me either.
--
NM 0.7 sets hostname to localhost.localdomain instead of what is in
/etc/hostname
It even happens when
[keyfile]
hostname=mize02
is declared. There is no process nm-system-settings running.
--
NM 0.7 sets hostname to localhost.localdomain instead of what is in
/etc/hostname
https://bugs.launchpad.net/bugs/276253
You received this bug notification because you are a member
Actually, I've completely disabled Network manager from starting up in
any runlevel:
$ ls -la /etc/rc?.d/*Manag*
lrwxrwxrwx 1 root root 24 Jan 13 2009 /etc/rc2.d/K01S28NetworkManager -
../init.d/NetworkManager
lrwxrwxrwx 1 root root 24 Jan 13 2009 /etc/rc3.d/K01S28NetworkManager -
Same problem. We use rsync to clone Jaunty systems. Can anyone explain
why NetworkManager does that?
--
NM 0.7 sets hostname to localhost.localdomain instead of what is in
/etc/hostname
https://bugs.launchpad.net/bugs/276253
You received this bug notification because you are a member of Ubuntu
I'm seeing a similar issue with 8.10. My solution was to disable
network manager:
$ cd /etc/rc2.d
$ sudo mv S28NetworkManager K01NetworkManager
This is a very bad solution for those who want to manage their networks
from within Gnome, but since I don't, it works for me.
Some details:
$ dpkg
I'm seeing this on a Jaunty system that I've cloned from one machine to
another using tar. Since /etc/init.d/hostname already takes care of
this, I don't understand why NetworkManager would ever need to trash a
system's hostname. Relevant stuff from /var/log/daemon.log attached.
** Attachment
On Sun, Dec 14, 2008 at 03:14:15AM -, Mark A. Hershberger wrote:
I just upgraded to Intrepid and am seeing this. System would come up
and set the name to localhost.localdomain and then localhost even
though I had a name in /etc/hostname.
Worse, my X session is started under the name
I just upgraded to Intrepid and am seeing this. System would come up
and set the name to localhost.localdomain and then localhost even
though I had a name in /etc/hostname.
Worse, my X session is started under the name localhost.localdomain
and the hostname changes. After the name changes, I
This bug was fixed in the package network-manager -
0.7~~svn20080928t225540+eni0-0ubuntu2
---
network-manager (0.7~~svn20080928t225540+eni0-0ubuntu2) intrepid; urgency=low
[ Alexander Sack [EMAIL PROTECTED] ]
* remove patches forwarded/applied upstream
- delete
quite serious issue. especially since we dont setup ifupdown system
settings plugin by default yet.
** Changed in: network-manager (Ubuntu)
Importance: Undecided = High
Status: New = Triaged
** Changed in: network-manager (Ubuntu)
Target: None = ubuntu-8.10
--
NM 0.7 sets
** Attachment added: system-plugin independent fix we are using now
http://launchpadlibrarian.net/18083657/lp276253_fix_system_hostname.patch
--
NM 0.7 sets hostname to localhost.localdomain instead of what is in
/etc/hostname
https://bugs.launchpad.net/bugs/276253
You received this bug
** Attachment added: system-plugin independent fix we are using now
http://launchpadlibrarian.net/18083661/lp276253_fix_system_hostname.patch
** Attachment removed: system-plugin independent fix we are using now
http://launchpadlibrarian.net/18083661/lp276253_fix_system_hostname.patch
--
works for me. setting to fix committed.
** Changed in: network-manager (Ubuntu Intrepid)
Status: Triaged = Fix Committed
--
NM 0.7 sets hostname to localhost.localdomain instead of what is in
/etc/hostname
https://bugs.launchpad.net/bugs/276253
You received this bug notification because
** Changed in: network-manager (Ubuntu Intrepid)
Importance: High = Critical
--
NM 0.7 sets hostname to localhost.localdomain instead of what is in
/etc/hostname
https://bugs.launchpad.net/bugs/276253
You received this bug notification because you are a member of Ubuntu
Bugs, which is
21 matches
Mail list logo
