*** This bug is a duplicate of bug 1676547 ***
https://bugs.launchpad.net/bugs/1676547
I tried all these suggestion, no joy.
Why won't dev fix? Please at least tell us what we're doing wrong. I may have
to install Desktop version because KVM/QEMU isn't playing nice with seeing the
network c
*** This bug is a duplicate of bug 1676547 ***
https://bugs.launchpad.net/bugs/1676547
I'm adding an observation here because the NetworkManager work-around
thread is here and not in #1676547.
Confirmed with additional information: Ubuntu 20.04 workstation ISO
(downloaded August 2020) exhibit
*** This bug is a duplicate of bug 1676547 ***
https://bugs.launchpad.net/bugs/1676547
New Install from netboot method ubuntu 20.04 focal same error, I did
everything, but nothing worked
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed t
*** This bug is a duplicate of bug 1676547 ***
https://bugs.launchpad.net/bugs/1676547
So I created a network bootable installation based on the 18.04.2 LTS
desktop download and I have the exact same problem. However none of the
workarounds are working for me. I have tried emptying the 10-glob
*** This bug is a duplicate of bug 1676547 ***
https://bugs.launchpad.net/bugs/1676547
actually this is what fixed this problem for me. In the file
/etc/NetworkManager/NetworkManager.conf I changed managed=false to
managed=true
--
You received this bug notification because you are a member o
*** This bug is a duplicate of bug 1676547 ***
https://bugs.launchpad.net/bugs/1676547
I use debootstrap and chroot to install. Just migrated from Debian where
this issue doesn't exist on any branch. Installed Ubuntu 20.04 and the
bug is still there. I was able to fix it using the instructions
*** This bug is a duplicate of bug 1676547 ***
https://bugs.launchpad.net/bugs/1676547
None of these solutions are working and I'm on 22.10 with kernel 5.19.
This is pretty absurd. I used NetworkManager 3 years ago on a Raspberry
Pi to build out a custom LTE solution using a Sierra Wireless CA
*** This bug is a duplicate of bug 1676547 ***
https://bugs.launchpad.net/bugs/1676547
Comment #6 fixed for me, thanks a lot buo-ren-lin
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpa
*** This bug is a duplicate of bug 1676547 ***
https://bugs.launchpad.net/bugs/1676547
Ubuntu 17.10 here, final solution for me was #36.
Not enough with a blank file in /etc/NetworkManager/conf.d/10-globally-
managed-devices.conf and not solved modifying directly on /usr/lib/. I
had to cp the
*** This bug is a duplicate of bug 1676547 ***
https://bugs.launchpad.net/bugs/1676547
Ubuntu Mate 17.10 and comment #36 worked for me as well. Although I did
remove the file in /lib, thanks to somebody posting it here before I was
able to recreate it.
--
You received this bug notification b
*** This bug is a duplicate of bug 1676547 ***
https://bugs.launchpad.net/bugs/1676547
I am on Ubuntu 18.04,
The problem still persists after trying the above solutions(comment #36 &
comment #30).
root@(none):~# nmcli d s
DEVICE TYPE STATE CONNECTION
eth0ethernet unmanaged -
*** This bug is a duplicate of bug 1676547 ***
https://bugs.launchpad.net/bugs/1676547
The same problem in Ubuntu 18.04. File /etc/NetworkManager/conf.d/10
-globally-managed-devices.conf does not solve the problem
--
You received this bug notification because you are a member of Desktop
Pack
*** This bug is a duplicate of bug 1676547 ***
https://bugs.launchpad.net/bugs/1676547
Hi there,
Anyone found work around solution for the problem mentioned in comment
#39 ??
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-m
*** This bug is a duplicate of bug 1676547 ***
https://bugs.launchpad.net/bugs/1676547
This bug still exists on Ubuntu 18.04.1. The problem is when network-
manager is upgraded this the fix in /etc/NetworkManager/conf.d/10
-globally-managed-devices.conf is over-written:
network-manager 1.10.6
*** This bug is a duplicate of bug 1676547 ***
https://bugs.launchpad.net/bugs/1676547
Workaround: in ubuntu 18.4
Create an empty file /etc/NetworkManager/conf.d/10-globally-managed-devices.
Create an file /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with
content:
network: {config:
*** This bug is a duplicate of bug 1676547 ***
https://bugs.launchpad.net/bugs/1676547
I also came across this bug on 17.10. Creating an empty
/etc/NetworkManager/conf.d/10-globally-managed-devices.conf file did not
work. But when I copied the file from /usr/lib and changed the value
"unmanage
*** This bug is a duplicate of bug 1676547 ***
https://bugs.launchpad.net/bugs/1676547
I've experienced this bug in a clean install of 18.04 via the server
edition first then adding a GUI. In the past editing
/etc/NetworkManager/NetworkManager.conf and setting managed=true was the
solution, th
*** This bug is a duplicate of bug 1676547 ***
https://bugs.launchpad.net/bugs/1676547
I confirm the bug on 17.04. Creating the file
/etc/NetworkManager/conf.d/10-globally-managed-devices.conf didn't solve
the problem.
--
You received this bug notification because you are a member of Desktop
*** This bug is a duplicate of bug 1676547 ***
https://bugs.launchpad.net/bugs/1676547
Upgrade from 16.04 to 16.10 to 17.04 and my UMTS modem would not
connect. Creating an empty /etc/NetworkManager/conf.d/10-globally-
managed-devices.conf solved my problem.
$ nmcli device show
GENERAL.DEVICE
** Summary changed:
- network-manager does not manage ethernet and bluetooth interfaces
+ network-manager does not manage ethernet and bluetooth interfaces when Ubuntu
16.10 is installed using chroot/netboot method
--
You received this bug notification because you are a member of Desktop
Packag
Subscribing Martin Pitt as they wrote the second changelog, no offense.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1638842
Title:
network-manager does not manage ethernet
Hi, I believe I have the same issue, however there's differences that
you installed Ubuntu 16.10 using chroot, while I installed Ubuntu 16.10
using netboot(and then tasksel ubuntu-desktop), here are the
investigation results:
## Possible Cause ##
The problem seems to be lies on the new override co
Update Workaround in #2, in fact you need to remove
/usr/lib/NetworkManager/conf.d/10-globally-managed-devices.conf instead.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/163884
Update Workaround in #2 (again), the proper way to deal with it is to
create a blank file with the same name under /etc/NetworkManager/conf.d
, in command-line:
```
# touch /etc/NetworkManager/conf.d/10-globally-managed-devices.conf
```
--
You received this bug notification because you are a mem
Comment #6 is the correct solution. On desktop images we want NM to
manage everything, thus the installer creates
/etc/NetworkManager/conf.d/10-globally-managed-devices.conf. But on a
server, container, or similar environment we do NOT want NM to suddenly
take over existing connections from netplan
Same problem here, as stated in
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1658921
Five computers (2 laptops and 3 desktops), upgraded from 16.04. No
chroot. Comment #6 did the trick.
I can't believe this is tagged as "won't fix"
--
You received this bug notification because
#4 worked for me, but refusing to fix this is ridiculous. Not everyone
is going to have alternative web access to search for the fix and there
will be laptop owners who will not discover the network port is not
working until they have a problem with their router configuration.
Please reconsider th
I just upgraded 16.04 to 16.10 and had to search and find the solution
on my fucking smartphone instead of the PC because somebody decided to
change the way the network manager *manages* the network interfaces.
Good job, you've just wasted tens of people's hours for nothing. I hope
somebody's reall
Comment #6 fixed it for me. Just needed to restart
NetworkManager.service after creating the blank file.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1638842
Title:
network-
*** This bug is a duplicate of bug 1658921 ***
https://bugs.launchpad.net/bugs/1658921
This needs fixing
** This bug has been marked a duplicate of bug 1658921
NetworkManager does not manage wired connection
--
You received this bug notification because you are a member of Desktop
Packag
*** This bug is a duplicate of bug 1658921 ***
https://bugs.launchpad.net/bugs/1658921
Same problem after an upgrade from 16.04 to 16.10 via "do-release-
upgrade". However in my case the issue occurred not for Ethernet or
Bluetooth, but for Mobile Broadband (device ttyUSB2 of type gsm over
int
*** This bug is a duplicate of bug 1658921 ***
https://bugs.launchpad.net/bugs/1658921
Same problem after an upgrade from 16.04 to 16.10 via "do-release-upgrade".
Ethernet and WiFi not managed.
Solved it creating blank file at
/etc/NetworkManager/conf.d/10-globally-managed-devices.conf
as pe
*** This bug is a duplicate of bug 1658921 ***
https://bugs.launchpad.net/bugs/1658921
I have lost 3 days to find out this solution. Fix it ASAP!
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs
I just upgraded from 16.04 desktop to 16.10 and the file
/etc/NetworkManager/conf.d/10-globally-managed-devices.conf was not created so
my wired network did not work.
Creating the file fixed this issue.
Is the file supposed to be created on desktop upgrades?
--
You received this bug notificatio
Same as post #8; this fixed it for me too...
thanks
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1638842
Title:
network-manager does not manage ethernet and bluetooth inter
Comment #6 fixes it fine for me.
Thanks
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1638842
Title:
network-manager does not manage ethernet and bluetooth interfaces when
Same problem after an upgrade from 16.04 to 16.10 via "do-release-
upgrade". #6 fixes the issue.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1638842
Title:
network-manager
This problem also occurs when installing from the alternative CD
install. Comment #4 worked for me.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1638842
Title:
network-manag
*** This bug is a duplicate of bug 1658921 ***
https://bugs.launchpad.net/bugs/1658921
Setting unmanaged-devices=none in {BASE}usr/lib/NetworkManager/conf.d/10
-globally-managed-devices.conf worked for me in getting NetworkManager
to manage the ethernet port, though I don't know if that messes
*** This bug is a duplicate of bug 1658921 ***
https://bugs.launchpad.net/bugs/1658921
I did a fresh install of 16.04 and an upgrade to 16.1 with no other
changes. I too lost the wired connection completely (including the
applet). I can confirm that fix #6 worked flawlessly.
--
You received
*** This bug is a duplicate of bug 1658921 ***
https://bugs.launchpad.net/bugs/1658921
Thank you.. this was annoying me no end, post #6 was very helpful, especially
me being relatively new to ubuntu and linux in general. Why on earth it managed
to save everything else on upgrading from 16.04
*** This bug is a duplicate of bug 1658921 ***
https://bugs.launchpad.net/bugs/1658921
Hi,
may be a fix could be to remove network-manager from server setup.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
*** This bug is a duplicate of bug 1658921 ***
https://bugs.launchpad.net/bugs/1658921
I just got a new Dell loaded with 16.04. Using wireless I updated to
16.10 then tried to get on our wired network. I ran into this problem
and comment #6 worked. Thank you!
--
You received this bug notifi
*** This bug is a duplicate of bug 1658921 ***
https://bugs.launchpad.net/bugs/1658921
On 2017-04-15 I upgraded from 16.04 to 16.10 on the way to 17.04. This
issue was the one and only problem I encountered.
In my case I started the wired interface manually (sudo ifconfig enp3s0
up && sudo dh
*** This bug is a duplicate of bug 1658921 ***
https://bugs.launchpad.net/bugs/1658921
I get this after 16.04→16.10→17.04.
#15 helped me to fix and to understand why Ubuntu will never be upper
than 1% on desktop. This crap happens every, [EVERY, Carl!] major
release or upgrade! Before this, i
*** This bug is a duplicate of bug 1658921 ***
https://bugs.launchpad.net/bugs/1658921
You are getting completely mad. Yn Chin Pu would not have Internet
connectivity from North Korea, and it would not be because
NetworkManager does not want its Ethernet interface to join the network.
But bec
*** This bug is a duplicate of bug 1676547 ***
https://bugs.launchpad.net/bugs/1676547
** This bug is no longer a duplicate of bug 1658921
NetworkManager does not manage wired connection
** This bug has been marked a duplicate of bug 1676547
No network connectivity after upgrade from 16.
*** This bug is a duplicate of bug 1676547 ***
https://bugs.launchpad.net/bugs/1676547
I have also had this problem after upgrade from 16.04 to 16.10.
Ethernet and WiFi not managed.
I solved it with the command:
touch /etc/NetworkManager/conf.d/10-globally-managed-devices.conf
I was about t
*** This bug is a duplicate of bug 1676547 ***
https://bugs.launchpad.net/bugs/1676547
Workaround:
Create an empty file /etc/NetworkManager/conf.d/10-globally-managed-
devices.conf and restart Network-Manager
--
You received this bug notification because you are a member of Desktop
Packages
*** This bug is a duplicate of bug 1676547 ***
https://bugs.launchpad.net/bugs/1676547
I was also affected by this after doing a release upgrade of my system.
Very very annoying and I was searching for ever until I found this.
--
You received this bug notification because you are a member of
*** This bug is a duplicate of bug 1676547 ***
https://bugs.launchpad.net/bugs/1676547
I have tried all the above but did not work for me? I was running Ubuntu
16.04.2 LTS Xenial with no problem until two days ago. Then, after I did
a routine software update which I was prompted to do but Ubun
*** This bug is a duplicate of bug 1676547 ***
https://bugs.launchpad.net/bugs/1676547
Installed 17.04 using minimal server install CD, wanted to use
networkmanager to manage my interfaces, encountered this pesky bug. I
had removed any mention of my wired interface in
/etc/network/interfaces,
I just upgraded network-manager to test your workaround but I cannot
reproduce this bug anymore. I tried to restart networking and the
network-manager services. I also tried to purge network-manager and
reinstall it again. I didn't try to reboot.
The bug might affect new installations only.
May
53 matches
Mail list logo