I can confirm the same problem just upgraded a stock 8.04 Hardy with
Network Manager 0.7 to 8.10 Intrepid. My wired and wireless networking
stopped working. DHCP wasn't working for any interface. DHCP worked fine
before the upgrade.
I was able to manually configure a network interface, but was
Hi all,
Today I upgraded my laptop from Hardy to Intrepid, and I want to confirm
this issue (NM is buggy)
As Alexander explained before, the problem is the user under nm
configuration file.
After the upgrade:
[EMAIL PROTECTED]:~$ cat /etc/dbus-1/system.d/nm-dhcp-client.conf
!DOCTYPE busconfig
Hi,
The facts:
--
yesterday i'd setup a new hardy system, dhcp and internet access worked out of
the box
then, i used knetwork manager to configure another (not working) adsl modem
-- here network manager may have updated config files
i switched back to the working adsl modem,
I have never touched that file (before fixing it); why would I? My
system is fine now and I think all other people cc'd to this bug have
fixed it also.
The problem is that somehow the file was changed, and we are concerned
that whatever caused it gets fixed. If none of us manually changed the
not sure why that would have changed for you. current NM definitly ships
root as the dhcp user. if thats not the case for you something must have
modified your file in the past. Maybe it was you trying something or
some script ... hard to track down if we cannot reproduce it.
Maybe a plan would
this happens when you edited your /etc/dbus/system.d files manually
once. not a bug. properly clean your changes and get the maintainer
shipped config files in place should fix that for you.
** Changed in: network-manager (Ubuntu)
Status: New = Invalid
--
[NM 0.7 - intrepid] DHCP
I have this same issue. Updated a machine from Hardy and Networkmanager
died, or rather DHCP. Managed to get online with hard coded IPs and find
this report. :)
properly clean your changes and get the maintainer shipped config files
in place is not much of an instruction though, especially since
please check /etc/dbus-1/system.d/nm-dhcp-client.conf ... if there is
user=dhcp then you modified that file manually once. change that to
root ... or --purge network-manager and install again.
--
[NM 0.7 - intrepid] DHCP org.freedesktop.Dbus.Error.AccessDenied
I just updated my laptop to Intrepid and this bug is still present. It
looks like a major blocker for me
--
[NM 0.7 - intrepid] DHCP org.freedesktop.Dbus.Error.AccessDenied
https://bugs.launchpad.net/bugs/262817
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I can confirm that bug on the notebook of a friend of mine. It's
reproducible. If network manager 0.7 (from the ppa) is installed on the
system and you upgrade to intrepid the file says dhcp instead of
root. Because quite a few people have used the unofficial packages
for the network manager
Jut upgraded to Ibex. I can confirm this bug. As soon as I added the
policy for root, everything worked. I was using NM 0.7 on Hardy before.
It is worth mentioning that this bug affects wired and wireless.
--
[NM 0.7 - intrepid] DHCP org.freedesktop.Dbus.Error.AccessDenied
Alexander, this affects the PPA
0.7~~svn20080928t225540+eni0-0ubuntu2~nm3~hardy1 package.
I'd been using my own variation of the 0.7 package but yesterday allowed
it to upgrade to the network-manager PPA version. A few hours later
after a system restart neither the wired or wireless interfaces
Marking as 'new' to flag this up for the network-manager PPA hardy
packages.
** Changed in: network-manager (Ubuntu)
Status: Invalid = New
--
[NM 0.7 - intrepid] DHCP org.freedesktop.Dbus.Error.AccessDenied
https://bugs.launchpad.net/bugs/262817
You received this bug notification because
/etc/dbus-1/system.d/nm-dhcp.conf - should have user=root ... and
thats what we ship in intrepid (otherwise there would be more complains.
If you dont have that you most likely modified that file in the past.
** Changed in: network-manager (Ubuntu)
Status: New = Invalid
--
[NM 0.7 -
Adding both myself and root to the group dhcp did work. The only way
I can connect is to allow context=default Is NM being run as the
wrong user perhaps? I used sudo.
--
[NM 0.7 - intrepid] DHCP org.freedesktop.Dbus.Error.AccessDenied
https://bugs.launchpad.net/bugs/262817
You received this
15 matches
Mail list logo
