After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 742818 - Will not find network after connection info is edited
Will not find network after connection info is edited
Status: RESOLVED OBSOLETE
Product: NetworkManager
Classification: Platform
Component: IP and DNS config
unspecified
Other Linux
: Normal major
: ---
Assigned To: NetworkManager maintainer(s)
NetworkManager maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2015-01-12 19:05 UTC by Jeb Eldridge
Modified: 2020-11-12 14:33 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Jeb Eldridge 2015-01-12 19:05:51 UTC
Originally reported at:
  https://bugs.launchpad.net/bugs/1409866

Network manager fails to connect after editing my connection information and rebooting. This becomes a real hassle when I need to use a different DNS server than what my ISP provides me by default. 
After reboot, if I want to try connecting to my old network connection setup by removing the auto-generated (default) one during that boot and then clicking on my connection in the applet, my computer instantly gives me an error message "connection not found".

Please fix. This does not happen in Windows.

ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: network-manager-gnome 0.9.8.8-0ubuntu7
ProcVersionSignature: Ubuntu 3.16.0-29.39-lowlatency 3.16.7-ckt2
Uname: Linux 3.16.0-29-lowlatency x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.14.7-0ubuntu8
Architecture: amd64
CurrentDesktop: Unity
Date: Mon Jan 12 13:58:36 2015
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
InstallationDate: Installed on 2014-11-08 (65 days ago)
InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
IpRoute:
 default via 192.168.1.1 dev wlan0  proto static 
 192.168.1.0/24 dev wlan0  proto kernel  scope link  src 192.168.1.11  metric 9
NetworkManager.state:
 [main]
 NetworkingEnabled=true
 WirelessEnabled=true
 WWANEnabled=true
 WimaxEnabled=true
ProcEnviron:
 LANGUAGE=en_US
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: network-manager-applet
UpgradeStatus: No upgrade log present (probably fresh install)
nmcli-con:
 NAME                      UUID                                   TYPE              TIMESTAMP    TIMESTAMP-REAL                     AUTOCONNECT   READONLY   DBUS-PATH                                 
 Wired connection 1        a611b55f-0934-43e9-91d5-ab32d4b0cd67   802-3-ethernet    1421088678   Mon 12 Jan 2015 01:51:18 PM EST    yes           no         /org/freedesktop/NetworkManager/Settings/2
 KCS96                     47fa8aac-d4c7-48ab-83bf-59f4aa4da740   802-11-wireless   1421089059   Mon 12 Jan 2015 01:57:39 PM EST    yes           no         /org/freedesktop/NetworkManager/Settings/6
nmcli-dev:
 DEVICE     TYPE              STATE         DBUS-PATH                                  
 wlan0      802-11-wireless   connected     /org/freedesktop/NetworkManager/Devices/1  
 eth0       802-3-ethernet    unavailable   /org/freedesktop/NetworkManager/Devices/0
nmcli-nm:
 RUNNING         VERSION    STATE           NET-ENABLED   WIFI-HARDWARE   WIFI       WWAN-HARDWARE   WWAN      
 running         0.9.8.8    connected       enabled       enabled         enabled    enabled         enabled
Comment 1 André Klapper 2020-11-12 14:33:57 UTC
bugzilla.gnome.org is being shut down in favor of a GitLab instance. 
We are closing all old bug reports and feature requests in GNOME Bugzilla which have not seen updates for a long time.

If you still use NetworkManager and if you still see this bug / want this feature in a recent and supported version of NetworkManager, then please feel free to report it at https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues/

Thank you for creating this report and we are sorry it could not be implemented (workforce and time is unfortunately limited).