Talking this issue over a bit with Mario and running though the process
. It is highly unlikely we will be able to run into this issue with
network manager given the oem-config fix, as well as the inability to
have network manager demonstrate the behavior hacking up an Ubuntu
install.
With the fa
It looks like with the new ubiquity it is now unlikely we will get in a
state where Network Manger will try and fall back. But basically if the
hostname isn't set & nothing is in /etc/hosts. Network Manger tries to
create it's own /etc/hosts
Trying this with an Ubuntu install I'm unable to recreat
I was actually able to reproduce the issue of Network Manger putting a bad
/etc/hosts using Fedora with the following steps:
- remove hostname set from /etc/sysconfig/network
- remove all contents of /etc/hosts
- reboot
- Network manager puts invalid /etc/hosts
So to get int
In the Network Manager source code in
src/NetworkManagerPolicy.c
The issue is in function "update_etc_hosts". If Network Manager sees
that /etc/hosts is empty it puts an invalid /etc/hosts .. it's on line
318 of the network manager in karmic (0.8).
When this gets run I'm trying to figure out. Bu
@Rick
Apparently it's not as easy to reproduce but the code is in Network
Manager that is producing an invalid /etc/hosts . Will find code path (post it)
and hopefully an easy way to trigger it. Apparently the steps above where not
enough.
--
oem-config incorrectly setting up /etc/hos
This bug was fixed in the package ubiquity - 2.0.9
---
ubiquity (2.0.9) karmic-proposed; urgency=low
* Do not try to configure networking in oem-config (LP: #471498).
* pkgsel now provides a debconf question to avoid warning the end user
when the language packs could not be in
** Changed in: network-manager (Ubuntu)
Importance: Undecided => Low
--
oem-config incorrectly setting up /etc/hosts
https://bugs.launchpad.net/bugs/471498
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
u
First the network manager bug task is is New and not assigned to anyone.
This suggests the bug task will not be addressed. We shouldn't leave bug
tasks in this state if a customer cares about them.
Secondly, we should not commit to fix bugs without repro steps. If the
network manager is buggy, ple
For the network manager side of this bug. According to Mario
"If you replace /etc/hosts with a zero length file (as some editors may
do in the process of saving), there is a chance you'll hit this, but
it's still not guaranteed. You don't need to duplicate it to fix it.
You just need to modify N
** Tags added: verification-done
** Tags removed: verification-needed
--
oem-config incorrectly setting up /etc/hosts
https://bugs.launchpad.net/bugs/471498
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubu
Yes, I've tested the one from proposed, and the ubiquity side of the
bug does not show up in the tests I've ran.
On 11/30/2009, Brian Murray wrote:
> Mario you mentioned the following in comment 9:
>
> "b) If Network Manager calls update_etc_hosts at the exact same time
> that oem-config was chan
Mario you mentioned the following in comment 9:
"b) If Network Manager calls update_etc_hosts at the exact same time
that oem-config was changing the hostname, you can run into this
scenario. OEM-config shouldn't be changing the hostname at all in the
first place though as there is no place in the
** Changed in: oem-priority
Assignee: (unassigned) => Canonical Ubuntu QA Team (canonical-qa)
--
oem-config incorrectly setting up /etc/hosts
https://bugs.launchpad.net/bugs/471498
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
subscribed desktop manager for awareness of possible NetworkManager
issue.
--
oem-config incorrectly setting up /etc/hosts
https://bugs.launchpad.net/bugs/471498
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing lis
Apparently there is still an issue with Network Manger here. Mario
comments on it in comment #9.
Martin you marked it Invalid, do you have a reason? Please, if so
remark this invalid. Though I am going to reopen this issue for Network
Manger as chatting with Mario we only solved the ubiquity/oem-c
This bug was fixed in the package ubiquity - 2.1.0
---
ubiquity (2.1.0) lucid; urgency=low
[ Evan Dandrea ]
* Run X with -nolisten tcp (LP: #462394).
* Make sure we never try to install onto the live filesystem.
* Only print the filenames being blacklisted if in debug mode.
Accepted ubiquity into karmic-proposed, the package will build now and
be available in a few hours. Please test and give feedback here. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed. Thank you in advance!
** Changed in: ubiquity (Ubuntu Karmic
** Branch linked: lp:~ubuntu-installer/ubiquity/karmic
--
oem-config incorrectly setting up /etc/hosts
https://bugs.launchpad.net/bugs/471498
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.
** Also affects: network-manager (Ubuntu Karmic)
Importance: Undecided
Status: New
** Also affects: oem-config (Ubuntu Karmic)
Importance: Undecided
Status: New
** Also affects: ubiquity (Ubuntu Karmic)
Importance: Undecided
Status: New
** Changed in: ubiquity (Ubun
** Changed in: ubiquity (Ubuntu)
Status: Triaged => Fix Committed
--
oem-config incorrectly setting up /etc/hosts
https://bugs.launchpad.net/bugs/471498
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
** Branch linked: lp:ubiquity
--
oem-config incorrectly setting up /etc/hosts
https://bugs.launchpad.net/bugs/471498
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.
So two things worth mentioning:
1) This can't be reproduced 100% of the time, but when it does happen,
the results on the system are disastrous.
2) That /etc/hosts bares an uncanny similarity to the one that NetworkManager
would normally generate if it encountered an empty /etc/hosts. So there l
(I'm on-site this week, so if I get to this bug I'll consider it a
bonus, but can't guarantee it ...)
--
oem-config incorrectly setting up /etc/hosts
https://bugs.launchpad.net/bugs/471498
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Summary changed:
- All commands ran as sudo come up as "sudo: unable to resolve host test-laptop"
+ oem-config incorrectly setting up /etc/hosts
--
oem-config incorrectly setting up /etc/hosts
https://bugs.launchpad.net/bugs/471498
You received this bug notification because you are a member o
24 matches
Mail list logo
