I`m running Ubuntu 12.04 updated till today (09 may 2014 ) and aswell Debian
Testing with KDE updated and I have the same trouble the network is not working
after a 30 o 45 minutes; I can not restart the network so if I wanna have the
network running well I must restart the machine and the
This is a network manager bug, as it affects a Gentoo system of mine
running Gnome. The problem is that Network Manager helpfully sets the
hostname, which confuses a lot of programs.
--
[hardy] Manually Configuring Network Causes Massive, Unreversable, Failure
most likely a kde admin or ifupdown issue.
There are many, many confirmations under Gnome.
--
[hardy] Manually Configuring Network Causes Massive, Unreversable, Failure
https://bugs.launchpad.net/bugs/185209
You received this bug notification because you are a member of Ubuntu
Bugs, which is
not a network manager bug. most likely a kde admin or ifupdown issue.
** Changed in: ubuntu
Sourcepackagename: network-manager = None
** Tags added: needs-reassignment
--
[hardy] Manually Configuring Network Causes Massive, Unreversable, Failure
https://bugs.launchpad.net/bugs/185209
You
I can confirm this bug in Hardy-Gnome. If a domain is added to the
hostname in /etc/hosts, sudo does not work any more. In Gutsy that did
not matter; sudo still worked even if a domain name was added:
172.0.0.1 localhost [hostname].[domain]
I think, the problem is not, how the domain name has
The problem is that under GNOME it is not network-manager that sets
static configurations - it is gnome-system-tools... The question is
whether the KDE equivalent uses the same backend. Either way I doubt
network-manager is the right place for this bug...
--
[hardy] Manually Configuring Network
Perhaps, but as I said if the same symptoms are caused by two different
bugs then it is certainly not appropriate to mark reports of this issue
in Gnome as duplicates of this bug, which is what has happened to date.
If this bug is to be transferred to KDE, then revive 208947 or tell me
to re-file
ArbitraryConstant:
I'm not disagreeing with you - I think this should have been two bugs myself
(unless the backend is in some way shared between KDE and GNOME) but we shall
see.
--
[hardy] Manually Configuring Network Causes Massive, Unreversable, Failure
Actually Matt, the bug took place while using KDE3...I ran into the bug
while assigning the machine a static ip, which is the first thing I do
after installing any OS. So I hadn't even gotten to the process of
installing the KDE4 packages when KDE3's network manager hosed my
system.
--
[hardy]
The bug actually occurred in KDE3, not KDE4. Setting to network-manager
since it affects Gnome as well as KDE.
** Changed in: network-manager (Ubuntu)
Sourcepackagename: meta-kde4 = network-manager
--
[hardy] Manually Configuring Network Causes Massive, Unreversable, Failure
There is at least one comment reporting a problem on GNOME, which is
surely a different bug and should be filed separately
No need. I submitted 208947 with Gnome, and it was marked as a duplicate
of this bug. Given identical corruption of /etc/hosts under similar
circumstances, that's probably
This bug, as originally reported, affects the KDE 4 Remix of Kubuntu,
not the 8.04 release itself. Moving to kde4 for further analysis and
reassignment, as it seems unlikely to be a network-manager problem.
There is at least one comment reporting a problem on GNOME, which is
surely a different
I can also confirm that it isn't just KDE that is having this problem. I
just ran into it today using network-anager under GNOME. How it happened
for me was to switch from 'roaming' to use DHCP... I too am getting the
sudo: unable to resolve host geoff-laptop error when trying to sudo.
I am using
I was the other Ubuntu (Gnome) poster. gmcalp's description is
_exactly_ what happened to me. I'm surprised anyone has any problems
reproducing it: it seems to happen 100% of the time and recipe is very
simple.
--
[hardy] Manually Configuring Network Causes Massive, Unreversable, Failure
It's not just manual configuration that causes this failure. I had
this exact thing happen to me when I tried to reconfigure my network
interface via the System - Administration - Network tool. I disabled
roaming mode and enabled DHCP... and NetworkManager whacked my
/etc/hosts file so that I
** Changed in: network-manager (Ubuntu)
Importance: Undecided = High
--
[hardy] Manually Configuring Network Causes Massive, Unreversable, Failure
https://bugs.launchpad.net/bugs/185209
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
The interaction with sudo is a very inconvenient, very visible symptom.
Without getting into whether or not it's desirable for sudo to do the
gethostbyname() lookup, we can say for certain that it is never the
correct behavior for a configuration GUI used by the user to produce an
incorrect
Agreed. The problem should be fixed at the source instead of putting a
band-aid on the symptoms as they appear.
--
[hardy] Manually Configuring Network Causes Massive, Unreversable, Failure
https://bugs.launchpad.net/bugs/185209
You received this bug notification because you are a member of
At least parts of the problem are releated to:
https://bugs.edge.launchpad.net/ubuntu/+source/sudo/+bug/32906
--
[hardy] Manually Configuring Network Causes Massive, Unreversable, Failure
https://bugs.launchpad.net/bugs/185209
You received this bug notification because you are a member of Ubuntu
Wait! I think this is in the wrong package which is why no-one is
looking at it. Attempting a punt to gnome-system-tools ...
** Changed in: gnome-system-tools (Ubuntu)
Sourcepackagename: network-manager = gnome-system-tools
--
[hardy] Manually Configuring Network Causes Massive, Unreversable,
kubuntu doesn't use gnome admin tools, reassigning to kde
** Changed in: kdeadmin (Ubuntu)
Sourcepackagename: gnome-system-tools = kdeadmin
--
[hardy] Manually Configuring Network Causes Massive, Unreversable, Failure
https://bugs.launchpad.net/bugs/185209
You received this bug notification
The problem occurred for me on gnome.
--
[hardy] Manually Configuring Network Causes Massive, Unreversable, Failure
https://bugs.launchpad.net/bugs/185209
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
This happens with KDE and Gnome, so it is probably a network-manager
backend issue.
** Changed in: network-manager (Ubuntu)
Sourcepackagename: kdeadmin = network-manager
--
[hardy] Manually Configuring Network Causes Massive, Unreversable, Failure
https://bugs.launchpad.net/bugs/185209
You
** Changed in: network-manager (Ubuntu)
Assignee: dlgandalf (gandalf-die-laterne) = Alexander Sack (asac)
--
[hardy] Manually Configuring Network Causes Massive, Unreversable, Failure
https://bugs.launchpad.net/bugs/185209
You received this bug notification because you are a member of
I, too, confirm this bug. It worked fine in Gutsy; and the network
manager edits the /etc/hosts file so that the first two lines look like:
172.0.0.1 localhost [hostname].[domain]
172.0.1.1 [hostname].[domain]
The second .[domain] should not be added; this is the part the messes
with sudo.
--
I ran into this after changing the hostname of a Hardy machine (dist-
upgraded yesterday) with KNetworkManager. The /etc/hosts file did not
contain the new hostname after this and because of this sudo refused
working from then on. One needs to boot into recovery mode or with a
live CD to fix this
Well, since I didn't set the root password, the only way for me to use
su was through sudo. But thanks for confirming this...glad to know I'm
not crazy.
dlgandalf wrote:
this bug is real, I ran into it many times now.
Btw, can someone tell me if it is necessary for the hosts file to have the
this bug is real, I ran into it many times now.
Btw, can someone tell me if it is necessary for the hosts file to have the rule
127.0.0.1 localhost hostname-name
with the emphasis on the name between ''
btw Mr Peoples you can still use 'su' -command, you don't have to do a
recovery mode
**
28 matches
Mail list logo
